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
AI as part of how you build. You use AI as real infrastructure in your workflow. Think agentic pipelines, custom tooling, and generators you've authored and rely on daily, with strong verification discipline. (Be ready to talk about the most complex AI system you've built recently.)
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
You set the standards for our SDKs and developer tooling, and the rest of the team adopts them
The team has a clear direction for developer experience, and follows it, because you set it; and the engineers around you get better at DX because of how you work
You're a recognized authority on developer experience; engineers and partners reference your work at the integration layer
More signups reach a successful first call, and fewer drop at integration, because the SDKs and docs make activation effortless
Support load drops, because the tooling and documentation answer the question first
The hardest, least-defined problems in our developer experience get named and solved, often before anyone else has spotted them
WHY THIS ROLE MATTERS
Deepgram wins when developers move from "is this possible?" to "this is in production" with zero friction. For almost every developer, that path runs through an SDK: it's where a new signup either makes a successful first call or quietly drops, which makes it one of the highest-leverage activation points in our product-led growth funnel. As a Staff Developer Experience Engineer, you own that surface and the architecture behind it: you don't just tell developers what's possible, you build the path that makes it effortless
Notice: We're aware of individuals impersonating Deepgram recruiters. All legitimate Deepgram recruiting communication comes from an .com email address. If you've received a message claiming to be Deepgram, please forward it to careers .com