Staff Conversational Designer

Company Overview

Deepgram is bringing the world’s most natural interface, voice, to the technology we use every day. Our speech models and real-time infrastructure power AI systems that keep up with the way people actually speak. More than 5,000 organizations run conversational voice AI on Deepgram in production, including Twilio, Cloudflare, Sierra, Decagon, Vapi, Cresta, Granola, and Jack in the Box.

The Deepgram Voice Agent Platform brings together speech-to-text, text-to-speech and speech-to-speech, with voice-native foundation models available through cloud APIs or self-hosted and on-premises deployments. Built for accuracy, low latency and cost efficiency, Deepgram makes high-quality voice experiences practical to build and run at scale. More than 650,000 developers have used Deepgram to process more than 200,000 years of audio. Every day, more of the world’s conversations with AI run on our models.

Operating Principles:

Deepgram is a research company that productizes as fast as possible. Four Operating Principles shape how we think, decide, and work together:

•

Compress before you communicate. You think it through first, then lead with the bottom line.

•

Resist entropy. You question what already exists before adding more process or tools.

•

Solve the category. You fix recurring problems at the source, not one case at a time.

•

Work at the frontier. You go after problems no one has solved yet.

We look for people who already work this way, and these principles shape how we grow and evaluate our team.

AI-First by Default

We build AI that millions of people talk to, and we run the company the same way. AI is how we centralize work here, and is core to how we operate.

That means more than using the tools. We expect you to:

•

Build, not just use. Design your own workflows and agents, and use AI to remove whole categories of work instead of doing the same work faster.

•

Own the output. AI can speed up the work. It doesn’t make anyone less accountable for it. You understand, verify, and stand behind everything you share, including what an agent produces for you.

•

Spend the time you get back at the frontier. The capacity AI creates goes toward problems no one has solved yet.

•

Keep pace. Models and tools change every month, and so will your work. You adopt what’s new quickly and drop what no longer earns its place.

We judge AI by what it helps you deliver and whether you stand behind the result, not by how often you use it. In interviews, expect to walk us through a workflow you built and where you drew the line between AI and your own judgment.

Note: This is a remote role based in Pacific Time, with a preference for candidates located in San Francisco.

About The Role

Deepgram builds the models and APIs that put voice agents into production at scale. What decides whether those agents feel human is not a screen. It is whether the agent knows when you have finished speaking, what it does when you cut it off, how it recovers from a misheard word, how it confirms something consequential before acting, and how it covers the milliseconds it cannot remove.

Today those decisions live inside prompts and pipeline config, made ad hoc by whoever is closest to the problem. No one owns them end to end. We are hiring a Staff Conversational Designer to own them.

You will define how Deepgram's voice agents converse: persona, turn-taking, repair, confirmation, and pacing. You will work directly with ML and Engineering on the tradeoffs that make those behaviors real, including endpointing, barge-in, and latency budgets. You will build the evals that tell us whether a conversation is actually good, and publish the guidance and reference experiences that show developers how to build natural conversations on the Voice Agent API.

This is a leading edge role. Very few companies have a titled equivalent. You will be defining this discipline at Deepgram, not inheriting it.

You'll report directly to the Director of Product Design. This is a Staff IC role, and your impact shows up mostly in the leverage you create for others: the patterns our own experiences run on, and the guidance our customers build against.

Your first chapter: a documented persona and voice system, and turn-taking and repair behavior designed and shipped with Engineering. From there, scope expands into conversational-quality evals and developer-facing guidance.

What You’ll Do

•

Define the persona and voice system for Deepgram voice agents, and keep it coherent across experiences and use cases

•

Design turn-taking, barge-in, and end-of-turn behavior with ML and Engineering, tuning responsiveness against the risk of interrupting the user, per use case

•

Design conversational repair, no-match and no-input handling, and confirmation strategy, including guardrails that require confirmation before high-stakes actions

•

Own latency-aware pacing and perceived responsiveness: brevity, backchanneling, hold and filler speech, all against real-time budgets

•

Establish conversational-quality evals and a transcript review practice that turns production failures into a repeatable design loop

•

Build the reference agent experiences and developer-facing design guidance that demonstrate best-practice conversation on the Voice Agent API

•

Partner with ML and Research on ASR and TTS behavior, and on the quality criteria that define a good conversation

•

Set the conversation-design principles, review standards, and shared vocabulary the broader team adopts

You’ll Love This Role If You

•

Believe conversation is an interface with real craft behind it, not a prompt someone tunes on the side

•

Want the hard real-time problems: endpointing, barge-in, and the half-second you cannot design away

•

Get energized by being foundational, defining what good means for a discipline that does not exist here yet

•

Think the fastest way to raise quality is to make it measurable, then make it repeatable

•

Are excited by a category still inventing its interaction patterns, where the wo