AI Data Readiness Lead

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.

About the role

Analytics is only as trustworthy as the definitions underneath it. As more reporting and decision-making moves to AI agents, the cost of ambiguous or conflicting metric definitions compounds, an agent applies the wrong rule confidently, at scale, and nobody catches it.

This role exists to prevent that. You will own what our numbers mean, make those definitions enforceable in the systems that serve them, and verify that both people and agents are using them.

This is a governance-first role with real technical depth. You will spend your time defining, implementing, and validating, building pipelines and developing agentic reporting are secondary.

What you'll work on

Own the metric registry. Establish canonical definitions for the metrics the business runs on. Where competing versions exist, convene the owners, document the disagreement, and drive to a decision. Publish changes with a clear statement of what moves and why.

Make definitions enforceable. Implement agreed definitions in the semantic layer and data catalog so they are applied by the system rather than described in a document. Retire superseded versions.

Reduce the surface area. Audit the reporting estate, retire assets with no audience, and establish ownership for what remains.

Build data quality checks/agents. Freshness, uniqueness, referential integrity, and cross-system reconciliation — with failures routed to named owners/agents who act on them.

Verify AI agents. Maintain an inventory of agents accessing company data and the definitions each relies on. Evaluate agent output against known-correct answers and track accuracy, refusal, and error rates.

Enable self-serve. Make governed data accessible and trustworthy for people querying it directly or through AI tools.

Qualifications

5+ years in analytics, analytics engineering, or a closely related field

Strong SQL, including comfort reverse-engineering undocumented transformation logic written by others

Direct ownership of a semantic or metrics layer in production — dbt, Cube, LookML, or equivalent. Not just usage: responsibility for what went into it and why

Demonstrated ability to resolve conflicting metric definitions across functions and land a decision

Clear written communication. Most of your output is documentation others must trust without re-deriving it

Comfort deprecating and removing work that others built