Intervooh · Interview questions by job

Analytics Engineer interview questions (2026)

Researched, current questions asked in real analytics engineer interviews (Data & AI), with what a strong answer actually does. Questions marked 2026 are the newer, AI-era questions employers now ask.

Build my free day-by-day prep plan →
Tell it the company, role and date; it does the rest. Free, no card.

What they assess

The questions to expect

Explain ref() versus source() in dbt and why the distinction matters.

Lineage is the point: source() declares raw inputs, ref() builds the DAG. Mention what you get for free — ordering, docs, selective runs.

When would you make a model incremental, and what can go wrong with incremental models?

Cost and speed on big tables — but name the failure modes: late-arriving data, schema drift, the lookback window. Full-refresh humility helps.

What tests do you put on a model before it's allowed to power a dashboard?

Unique and not-null on keys, accepted values, referential integrity, freshness — plus one bespoke business-logic test. Testing is the job's soul.

Three teams define revenue three different ways. How do you get to one version of the truth?

It's a people problem wearing a technical hat: convene the owners, document the definition, encode it once in the semantic layer, deprecate the rest.

Tell me about inheriting a messy tangle of SQL. How did you approach refactoring it?

Show restraint: understand and test before rewriting, layer models (staging, intermediate, marts), and keep outputs identical while you work.

Describe a time a bad data change reached production. What did you change afterwards?

The aftermath is the answer: the CI check, test or review step you added so that class of error can't recur.

Tell me about turning an analyst's one-off request into something reusable.

This is the role in miniature: spotting the pattern behind the request and building the model everyone quietly starts depending on.

How do you run CI/CD for a dbt project?

Slim CI against production manifests, tests on changed models plus downstream, review environments — describe your actual pipeline, not the docs.

Why analytics engineering — the seam between data engineering and analysis?

Say what you love about the craft: software rigour applied to analytical logic. Show you chose the seam, not that you fell between stools.

AI assistants write passable dbt models and tests now. How do you use them, and what still needs you?2026

Generation is cheap; judgement about grain, definitions and edge cases is not. Describe your review discipline for AI-drafted models.

Walk me through a piece of analysis or a model that changed a business decision.

Name the decision, not just the deliverable. The strongest answers end with what the business did differently and what that was worth.

Tell me about a time a stakeholder challenged your numbers. How did you respond?

Show you checked before defending. Being openly willing to find your own error is what builds trust in your numbers.

Preparation notes

[object Object]

Turn this into a plan

A list of questions is a start; a programme is what changes the outcome. Intervooh builds a day-by-day plan for your exact analytics engineer interview — company research, story building with an AI coach, spoken practice with delivery feedback, and scored mock interviews.

Start free — arrive ready →

Related roles

← All 200 jobs · Intervooh home