> Markdown version of [/jobs/ext/2722734-forward-deployed-engineers](https://www.wearedevelopers.com/jobs/ext/2722734-forward-deployed-engineers). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Forward-Deployed Engineers - **Company:** DEEPGRAM, INC. - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Contract:** Internship / Graduate position - **Skills:** Application Programming Interfaces (APIs), Software Debugging, Python (Programming Language), Systems Integration, TypeScript, Rust (Programming Language), Cloud Platform System, Prompt Engineering, Backend, Kotlin, Containerization, Information Technology, Low Latency, Api Design, Docker, Web Api, Golang - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/forward-deployed-engineer-fde-strategic-accounts-deepgram-9672902 ## About the Role * A Bachelor's or Master's degree in Computer Science, Engineering, or a related field, or a record of building that speaks for itself * Hands-on experience developing and deploying backend systems that run in production, whether through internships, co-ops, your first years in industry, or projects that shipped to live users * Experience with cloud-based infrastructure and API design * The instinct to proactively recognize problems and to care about the impact of your work And because you'll be in the room with customers, we look for the raw materials of customer-facing craft: * Relationship building - You genuinely enjoy getting to know the people that you work with, and you invest in those relationships beyond what the immediate task requires. * Reading the room - You notice who in a meeting is engaged, who is skeptical, and what is going unsaid. * Acting on what you notice - When you spot an opening, whether a stakeholder with a problem that you can solve or a question behind the question, you move on it. * Coachability - Nobody arrives with all of this polished. We'll teach the craft. We look for the appetite to learn it and openness to feedback along the way. It Would Be Great if You Had * Experience working with audio or voice interfaces * Experience building and maintaining a system that integrates with many third-party APIs, particularly point-of-sale systems * Experience taking a system from zero to one * Depth in one or more modern languages (our field work spans Python, JavaScript and TypeScript, Rust, Go, Kotlin, and whatever your customer runs), and the flexibility to pick up the next one * Experience with containerization tools, such as Docker and Kubernetes * Any experience being the technical person in front of a non-technical audience (teaching, tutoring, demos, hackathons, support) ## Description * Build and ship whatever the solution needs, whether that's an end-to-end service, an integration, internal tooling, or agent and prompt engineering * Design, develop, and maintain production-scale integrations with the third-party systems that your customer runs on (in today's pods: point of sale, loyalty, payment gateways, customer data platforms) * Spend regular time on site with your customer, working directly with their technical and business teams * Monitor, debug, and optimize what you ship in production, including some of the hardest audio environments in voice AI (noisy, multi-mic, drive-thru) * Work with our research and product teams to push the platform where your customer needs it to go, and feed what you learn in the field back into the product * Test changes against live production data and measure whether they move accuracy, latency, and throughput Time Allocation * Embedded customer delivery (60-80%) - Deployments, integrations, and technical problem-solving with your account, plus turning what the field teaches you into reusable solutions, automation, and documentation. Where you sit in that range depends on where your engagement is in its cycle. * Scoping and expansion support (10-25%) - Joining detailed solution scoping, shaping statements of work so that what gets promised can be built, and surfacing the expansion opportunities that you spot from inside of the account. Discovery and demos belong to a pre-sales Applied Engineer in your pod; you'll take parts of that work when the account needs it and hand it back when delivery peaks. * Internal collaboration (~15%) - Product feedback, knowledge sharing, and contributing to Applied Engineering strategy. The delivery and scoping buckets trade against each other: at the peak of an engagement, delivery takes the scoping share. The On-Site Expectation You'll have regular, recurring time with your customer, and you'll be on site at least once or twice a month. On some accounts, and at the peaks of an engagement (a launch, a critical integration, a high-stakes pilot), on-site time can rise to as much as 80%. Between those stretches, most of your time goes to making the solution succeed: building, integrating, debugging, and shipping. Additionally, this role will maintain an in-office presence in either our San Francisco or New York City office. Your First 90 Days * First 30 Days - Complete the accelerated Forward-Deployed onboarding in your first two weeks, covering Deepgram's technology, products, competitive landscape, and core APIs. The standard Applied Engineer ramp runs four to six weeks. Yours is faster because your pod is waiting. Then spend the back half of the month in motion: + Shadow your pod's active engagement + Make your first customer site visit alongside a senior Forward-Deployed Engineer + Take ownership of your first workstream (an integration, a tool, or a production issue), with your work reviewed before it ships * 60 Days - Own a meaningful slice of your customer's solution: + Join the on-site rhythm and build relationships with your customer's technical team + Ship work that runs in production * 90 Days - Operate with independence: + Run your own on-site visits and own your slice end to end + Bring what the field teaches you back to the team as product feedback and reusable building blocks + Join your first solution-scoping conversations with the pod You'll Love This Role If You * See yourself as an engineer first who happens to be great with customers, not the other way around * Thrive in high-ambiguity environments where moving fast and making sound decisions under pressure are part of the job * Enjoy embedding deeply with customers, building trust, and becoming their go-to technical partner * Find satisfaction in shipping production systems and watching them run in the physical world (a drive-thru at rush hour is an honest test environment) * Want to grow quickly, with high-stakes accounts, a steep learning curve, and a senior engineer reviewing your work ## Related Videos - [Go with the Flow: Stop the Leaks Before Your Memory's a Waterfall!](https://www.wearedevelopers.com/videos/100073-go-with-the-flow-stop-the-leaks-before-your-memory-s-a-waterfall) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [Kotlin Multiplatform - True power of native code reuse](https://www.wearedevelopers.com/videos/4-kotlin-multiplatform-true-power-of-native-code-reuse) - [Throwing off the burdens of scale in engineering](https://www.wearedevelopers.com/videos/608-throwing-off-the-burdens-of-scale-in-engineering) - [Retooling and refactoring - an investment in people.](https://www.wearedevelopers.com/videos/371-retooling-and-refactoring-an-investment-in-people) - [Scoring 2000 Products per Request: Performance Pitfalls in Golang](https://www.wearedevelopers.com/videos/2073-scoring-2000-products-per-request-performance-pitfalls-in-golang) ## Related Articles - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers)