# Staff Developer Experience (DX) Engineer at Deepgram

- Company: Deepgram
- What the company does: Power enterprise voice solutions with Deepgram’s Speech-to-Text, Text-to-Speech, and Voice Agent APIs. Real-time, accurate, and built for scale. Backed by Y Combinator and Madrona.
- Company website: https://www.deepgram.com
- Type: Startups (AI role)
- Level: Senior
- Location: USA | Remote
- Work setup: Remote
- Pay: $219K to $277K base salary per year (USD)
- Posted: 2026-07-17
- Apply by: 2026-10-08
- Apply: https://jobs.ashbyhq.com/deepgram/c0a4b3fb-2c15-4b03-86f9-688eec8a8187
- Page: https://www.1752.vc/careers/jobs/deepgram-staff-developer-experience-dx-engineer/

## About the role

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.

## What they're looking for

- A track record of owning developer-facing tooling across multiple languages. Starts with libraries, and expands to the SDK generators, templates, and release automation that produce them, with direction others built against
- An instinct to build reusable systems. Your standout work is something that outlived you. It could be a generator, automation, pipeline, or architecture that others adopted
- First-principles reasoning about systems. You think about SDKs, code generation, and partner ecosystems as systems. They have inputs, outputs, feedback loops, and boundaries
- Production ownership instincts. You treat production SDKs as production: observability, incident response, backward-compatibility discipline, and a bias toward removing recurring toil
- Range beyond your core. You go deep on developer experience and tooling, and you can pick up developer content, demos, or community work when the moment calls for it
- You think in developer outcomes, not just shipped code: you connect SDK and docs work to product activation and retention

Tags: Engineering