Intervooh · Interview questions by job · Data & AI
Data Engineer interview questions (2026)
Data Engineer interviews in the UK are assessed on pipeline design & etl, data modelling & warehousing, reliability & data quality, usually across 4 stages — phone or video screen, then competency and behavioural questions, then panel interview, then technical interview or test. The 12 questions below are the ones actually asked, each with what a strong answer does.
Researched, current questions asked in real data engineer interviews in the UK (Data & AI), with what a strong answer actually does. Questions marked 2026 are the newer, AI-era questions employers now ask. Last reviewed 2026-07-22.
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
- Pipeline design & ETL
- Data modelling & warehousing
- Reliability & data quality
- Cloud & distributed systems
- Working with data consumers
How a data engineer interview usually runs
- Phone or video screen
- Competency and behavioural questions
- Panel interview
- Technical interview or test
The questions to expect
Walk me through a pipeline you built end to end — sources, orchestration, storage. What would you change now?
Draw the boxes out loud and own one honest regret. Self-critique of a real system beats a textbook architecture.
ETL versus ELT — what actually changes, and when would you choose each?
Go beyond the acronym: modern warehouses make ELT the default, so name the cases where transforming first still wins.
How would you model clickstream or event data for analytics — star schema, one big table, something else?
There's no single right answer — show the trade-off between query ergonomics, cost and evolution, and ask who consumes it.
You discover a daily pipeline has been silently producing wrong numbers for a week. What do you do first?
Tell consumers before you fix it — quantify the blast radius, stop the bleeding, backfill, then add the test that catches it next time.
Batch or streaming for a new use case — how do you decide, and what does streaming really cost you?
Interrogate the freshness requirement first; most 'real-time' asks are happy with minutes. Name the operational burden streaming adds.
Tell me about a time an analyst or scientist couldn't use your data the way you'd intended.
Show you treat analysts as customers: how you found out, what you changed — naming, docs, grain — and the feedback loop you added.
Describe the worst data incident you've handled. What did you change afterwards?
Mitigate, communicate, root-cause — then spend most of your answer on the prevention you built. Blameless tone throughout.
Why data engineering, rather than software engineering or analytics?
Say what you genuinely enjoy about infrastructure serving people — and show you've chosen it deliberately, not fallen into it.
Your company wants its data 'AI-ready'. What does that actually mean, and what would you do first?2026
Translate the buzzword: quality, lineage, metadata, access controls and retrieval-friendly structure. A first step beats a manifesto.
How do you use AI coding assistants for pipeline work — and how do you stop generated SQL quietly degrading quality?2026
Assistants for boilerplate and tests, humans for schema and semantics — plus review and data tests as the safety net. Judgement is the answer.
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.
How to prepare for a data engineer interview in the UK
UK data-engineering interviews usually pair a SQL/Python screen with a systems-design conversation about a pipeline you've built — be fluent in one cloud (Azure is disproportionately common in UK enterprises) and ready for dbt and Airflow questions. Public-sector and finance roles will probe data governance and GDPR handling.
How Data & AI interviews are run in 2026
- Technical screens increasingly allow — or expect — an AI assistant for SQL and Python; live rounds then verify depth by making you reason out loud, so practise narrating your analysis without a keyboard.
- Case-style business scenarios ('retention dropped eight points — investigate') now carry as much weight as syntax questions; structured thinking beats memorised definitions.
- Take-home tasks are routinely followed by a live walkthrough and challenge round, because a polished take-home is now assumed to be AI-assisted.
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 data engineer interview — company research, story building with an AI coach, spoken practice with delivery feedback, and scored mock interviews. It never writes your answers for you.
Related Data & AI roles
- AI Engineer interview questions
- Analytics Engineer interview questions
- BI Analyst interview questions
- Data Analyst interview questions
- Data Scientist interview questions
- Database Administrator interview questions
- Machine Learning Engineer interview questions