Staff Developer Experience (DX) Engineer

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. The Staff Developer Experience Engineer will own the developer experience surface and architecture, ensuring that developers can seamlessly integrate SDKs into their workflows.

Responsibilities:

• Own the direction of developer experience. Set the DX roadmap (what we build, in what order, and why) and act as the technical lead for the area without direct reports. You're the person Product, Engineering, and Partnerships come to for the DX point of view, and the one who represents it in planning
• Own the SDK code-generation architecture. Design and own the system that produces our SDKs, so every supported library ships predictably and adding a new language is a known, low-cost effort rather than a one-off project
• Set the standard for how developers experience the platform. Define the quality bar, cross-language parity, versioning and release discipline, and observability across all of our SDKs. These are the standards the rest of the team builds against
• Raise the level of everyone who touches the SDK surface. Through code review, patterns, documentation, and pairing, you make the engineers around you better at developer experience, leading through influence rather than management
• Attack friction at the root. Find the systemic causes that slow developers down across whole segments and fix them once, structurally, before developers ever hit them
• Build the tooling the whole team relies on. The code-generation pipeline, CI and supporting infrastructure, starter repositories, and context that both human developers and AI coding agents can build on (including emerging standards like llms.txt)
• Design for resilience and longevity. Build documentation, automation, and architecture that the whole team can operate and extend, so the work lasts and scales beyond any one person
• Be the technical voice into Product, Engineering, Marketing, and Partnerships. Give cross-functional stakeholders the context and technical input they need to make good decisions about the developer-facing surface across our partner ecosystem

Requirements:

• A track record of owning developer-facing tooling across multiple languages
• AI as part of how you build
• An instinct to build reusable systems
• First-principles reasoning about systems
• Production ownership instincts
• Range beyond your core
• You think in developer outcomes, not just shipped code