Senior Analytics Engineer – Decision Intelligence

Deepgram; United States; Remote; USD 180,000 - 240,000; Full time

Job summary

Deepgram is building its decision layer—an AI-native, auditable data contract that agents can rely on. You’ll shape conformed entities across customer, account, project, product and contract, and own the semantic layer so dashboards, notebooks, and agents return the same numbers.

You’ll craft the agent-facing tools and enforce accuracy with clear ownership and governance. This senior IC position is early in a new team; you’ll be among the first engineers and will help define the data platform

Qualifications

• Demonstrated AI-native practice and ability to work with AI as a workflow
• Production-grade SQL and Python writing and instrumentation
• Semantic or metrics layer ownership with defined definitions and governance

Responsibilities

• Model the gold layer: entities spanning customers, accounts, projects, products and contracts
• Own the semantic layer and ensure consistent metrics across dashboards, notebooks, and agents
• Build agent-facing surfaces and governance to ensure correct, auditable outputs
• Evaluate agent outputs for accuracy and confidence, with clear ownership and traceability
• Respond to cross-functional questions by producing robust, reusable data assets

Skills

AI-native practice

SQL

Python

Data modeling

Tools

dbt

LookML

Cube

Job description

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:

• 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.

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.

About the role

Deepgram is building its decision layer: one governed set of numbers that people and AI agents can act on without re-deriving them. This role builds it.

You are not building pipelines. Ingestion, orchestration and latency belong to the data platform team, and they’re good at it. You take what lands in the warehouse and turn it into the layer above the conformed gold tables, the semantic models, and the agent-facing tools that let someone (or something) ask a question and get an answer that holds up.

This is a senior technical IC role on a new team. You’ll be the first or second engineer in.

What you’ll work on

• Model the gold layer. Conformed entities for customer, account, project, product and contract. Our identity model spans Salesforce, the console, Stripe and the billing system, with no authoritative key between them resolving that is week one.
• Own the semantic layer. Author the models that define our metrics once, so a dashboard, a notebook and an agent all return the same number. Version them. Retire the superseded ones.
• Build the agent-facing surface. The tools, permissions and MCP surfaces that let analyst agents navigate our data without inventing a join that looks plausible and is wrong.
• Make correctness checkable. Assertions on the things that break silently grain, uniqueness, cross-system reconciliation routed to a named owner. Evaluation of agent output against known-correct answers, tracking accuracy, refusal, and confidently-wrong rates separately.
• Absorb the questions. Sales, product and finance bring real questions. You answer them, and you leave behind a model that makes the next version of that question cheaper.

What we’re looking for

• AI-native practice, demonstrated. You use AI daily and intricately not to autocomplete, but as a way of working that has changed what you attempt. We will ask what the most interesting thing you’ve built with AI in the last month is, and we’ll go three questions deep on the answer.
• Production-grade SQL and Python. Code that ships on a schedule, has broken, and was found by your own instrumentation rather than by a stakeholder.
• Semantic or metrics layer ownership. dbt, Cube, LookML or equivalent owned, not used. You’ve changed a definition people already depended on, and can say who you told and what the number moved by.
• Modelling judgement over tool knowledge. You reason about grain and keys before you write the query. You can tell a data defect from an undecided business definition and treat them differently.
• Comfort in work-in-progress infrastructure. Nothing here is finished. There is no ticket queue to work from and no process to inherit you’ll be building both as you go.
• Clear writing. Much of the output is a definition or a contract someone else has to trust without re-deriving it.

Bonus Points

• Usage-based or consumption business models, where committed, consumed, invoiced and recognised revenue are genuinely different numbers.
• Real-time billing and consumption systems.
• Lakehouse architectures - Iceberg, Athena, Trino or similar.
• Contributions to open-source data or AI projects.