Data Engineering interviews. 13 titles, each with its own model.
Each page shows the competency model, the questions that test it, what changes with seniority, and where candidates lose the interview.
Last reviewed
Every Data Engineering title
13 titlesWhat the report looks like for Data Engineering
- The situation in one sentence: where, what was short, and by how much.
- The decision that was yours rather than the team’s, and what you chose not to do.
- One number or one consequence that shows it worked.
Every competency is scored out of five with a line you actually said as evidence, and the weakest answers are rewritten as structure and specifics, never a script.
What Data Engineering interviewers keep scoring
Pipeline design & reliability
Builds batch and streaming pipelines that are idempotent, restartable and observable, and designs for late data, backfills and failure from the start.
Data modelling & warehousing
Designs schemas and layered models (raw, cleaned, business) that serve analytics efficiently, evolve safely and have clear ownership and definitions.
Data quality & observability
Makes data trustworthy with automated tests, freshness and volume checks, lineage and clear SLAs, and catches problems before consumers do.
Performance & cost efficiency
Optimises storage, compute and query performance with measurement, and keeps cloud data platform costs proportionate to value.
Platform, orchestration & software engineering practice
Applies software engineering discipline to data: version control, testing, CI/CD, infrastructure as code and orchestration that other engineers can maintain.
Security, privacy & data governance
Handles personal and sensitive data lawfully and safely: access control, encryption, masking, retention and lineage that satisfy POPIA/GDPR and internal governance.
Working with data consumers & producers
Partners with analysts, scientists and source-system teams: negotiates contracts, communicates changes and outages clearly, and prioritises by consumer value.
Incident ownership & follow-through
Takes responsibility when data is wrong or late, communicates impact honestly, and fixes root causes rather than patching symptoms.