Software Engineer - Applied AI
Posted yesterday
The role in short
Ship production voice-agent features, fine-tuning and evals for Deepgram enterprise customers (drive-thru, phone ordering) on the Applied AI team.
Company Overview
Deepgram is the leading platform underpinning the emerging trillion-dollar Voice AI economy, providing real-time APIs for speech-to-text (STT), text-to-speech (TTS), and building production-grade voice agents at scale. More than 200,000 developers and 1,300+ organizations build voice offerings that are ‘Powered by Deepgram’, including Twilio, Cloudflare, Sierra, Decagon, Vapi, Daily, Cresta, Granola, and Jack in the Box. Deepgram’s voice-native foundation models are accessed through cloud APIs or as self-hosted and on-premises software, with unmatched accuracy, low latency, and cost efficiency. Backed by a recent Series C led by leading global investors and strategic partners, Deepgram has processed over 50,000 years of audio and transcribed more than 1 trillion words. There is no organization in the world that understands voice better than Deepgram.
Company Operating Rhythm
At Deepgram, we expect an AI-first mindset—AI use and comfort aren’t optional, they’re core to how we operate, innovate, and measure performance.
Every team member who works at Deepgram is expected to actively use and experiment with advanced AI tools, and even build your own into your everyday work. We measure how effectively AI is applied to deliver results, and consistent, creative use of the latest AI capabilities is key to success here. Candidates should be comfortable adopting new models and modes quickly, integrating AI into their workflows, and continuously pushing the boundaries of what these technologies can do.
Additionally, we move at the pace of AI. Change is rapid, and you can expect your day-to-day work to evolve just as quickly. This may not be the right role if you’re not excited to experiment, adapt, think on your feet, and learn constantly, or if you’re seeking something highly prescriptive with a traditional 9-to-5.
Team Overview
The Applied AI team takes on the voice AI problems that don’t have off-the-shelf answers. We work directly with enterprise customers and technology partners, from conversational AI and customer experience platforms to restaurant brands, and much of the work is zero to one. Current focus areas include robust ASR in noisy outdoor environments, self-service fine-tuning and model adaptation, domain-aware voice agents for drive-thru and phone ordering, agent scoring and evaluation, real-time operational analytics, and on-site hardware integration. We’re a small team that works in person in San Francisco, ships to production quickly, and stays close to the customers we build for.
Key Goals
- Ship production features in live voice agent products, such as drive-thru and phone ordering, within your first quarter.
- Own customer problems end to end: hear the issue, find the root cause, and get the fix into production.
- Help build reusable agent modules, like ordering and reservations, so new customers and industries launch faster.
- Make agents more accurate on real-world menus and catalogs, keeping structured data consistent across hundreds of locations.
- Contribute to fine-tuning and model adaptation so customers get accurate results on their own vocabulary and domains.
- Spot problems across the product before anyone asks, then fix them or bring a proposed solution.
- Run experiments that show whether new functionality improves outcomes for customers.
Minimum Skills, Knowledge & Capabilities
- Experience building and shipping backend services that run in production in the cloud.
- Operates AI-native: you build with modern AI coding tools as your default way of working, not occasionally, and use them to move fast without lowering the quality bar.
- Learns quickly and takes on unfamiliar parts of the stack with little ramp-up.
- Finds work instead of waiting for it: you recognize problems, propose solutions, and follow them through.
- Has taken something from idea to production, at work or on your own time.
- Communicates clearly with teammates and is comfortable working directly with customers.
- Builds for the customer’s outcome, with a high bar for quality and no over-engineering.
- Comfortable working across languages. Our stack is mainly Kotlin and Python, with TypeScript on the front end.
Preferred Qualifications (nice-to-have)
- Hands-on experience training, fine-tuning, or adapting models, through work, research, or substantial projects.
- Experience building evaluation or scoring for models or agents.
- Experience with audio, speech-to-text, or text-to-speech.
- Experience as a founder or early startup engineer, or taking a system from zero to one.
- Typically 2+ years of engineering experience, or equivalent demonstrated experience.
Notice: We're aware of individuals impersonating Deepgram recruiters. All legitimate Deepgram recruiting communication comes from an @deepgram.com email address. If you've received a message claiming to be Deepgram, please forward it to careers@deepgram.com.
Prep for this interview
2 questions likely to come up at Deepgram, each matched to a line in this posting.
- 1Coding
They wrote: “Comfortable working across languages. Our stack is mainly Kotlin and Python, with TypeScript on the front end.”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 2LLMs, RAG and agents
They wrote: “Contribute to fine-tuning and model adaptation so customers get accurate results on their own vocabulary and domains.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.
