# Senior Data Engineer Interview Questions > Senior and staff data engineer interview questions with rubric-scored verdicts. Canonical URL: Breadcrumb: [Home](https://datadriven.io/) > [Senior DE](https://datadriven.io/senior-data-engineer-interview-questions) ## Summary Senior and staff data engineer interview questions filtered from the full catalog. The bar is not whether you can solve the problem; it is whether you can name 2 alternatives, defend the choice, adapt cleanly when the interviewer changes a requirement mid-round, and call out the failure modes you would have to handle on-call. ## What this page covers The senior (L5) and staff (L6) data engineer interview rubrics differ from mid-level (L4) on three dimensions. First, trade-off articulation. L4 candidates are scored on producing a correct solution; L5 candidates are scored on naming 2 alternatives and defending the choice. "I would use Spark because it is good for this" does not pass L5. "I would use Spark over a pandas job because the data will not fit in driver memory once we scale to 100M rows, and over Dask because our team already has Spark in production and the operational story is simpler" does. Second, failure-mode naming. L5 candidates are expected to state 3 failure modes per component in a design round: what happens when this Kafka broker dies, what happens when this Snowflake warehouse hits the credit limit, what happens when this MERGE operation runs while a backfill is also writing. Third, mid-round pivot. The interviewer will change a requirement halfway through: SLA tightens from 15 minutes to 1 minute; data volume jumps 100x; the BI tool cannot handle table swaps. The L5 signal is adapting cleanly without throwing out the existing design. The senior data engineer SQL bar specifically tests the 7 advanced patterns. Recursive CTEs for hierarchy and graph. Gap-and-island for streak detection. Sessionization with LAG plus SUM OVER. SCD2 half-open joins. EXPLAIN plan reading. Skew handling with salt-and-rebalance. Idempotent MERGE for late-arriving data. The mid-level catalog covers JOIN, GROUP BY, basic windows; the senior tier composes these into multi-CTE queries with explicit edge-case handling for NULL and ties. The optimization round at L5+ almost always centers on EXPLAIN reading: the interviewer hands you an EXPLAIN ANALYZE showing a sequential scan where you expected an index seek, and the question is what is wrong (typically: a function in WHERE, an implicit cast, or a stale statistic). The senior data engineer design round is end-to-end: 10M events per day with 15-minute SLA, multi-region replication, idempotent reconciliation for late events, schema evolution without downtime, and the on-call story (what gets paged, who responds, what is the runbook). The L6 follow-up is usually a meta-question: how would you design the data platform itself, the orchestrator, the lineage system, the catalog. Less about the pipeline you would build for one use case, more about the substrate the whole org would build pipelines on top of. Senior data engineer Python rounds add complexity reasoning that mid-level rounds skip. Big-O articulation for every data structure choice. Memory bounds analysis (when does a list-of-dicts blow up versus a generator). Library familiarity (pandas, polars, asyncio, tenacity). Trade-off articulation (dict vs sort-and-iterate, generator vs list, when async vs sync). The senior data engineer is expected to default to the right choice and explain why. Companies whose data engineer L5+ loops appear in interview reports: Meta (E5, E6, E7), Amazon (L5, L6), Google (L5, L6, L7), Netflix (Senior, Staff), Stripe (E4, E5, E6), Databricks (L5, L6, L7), Snowflake, Airbnb, Uber. Each has its own rubric calibration. Use the company-specific list for company-tagged senior-level problems. ## Frequently asked questions ### What is the bar difference between L4 and L5 data engineer? Three dimensions. Trade-off articulation: L5 names 2 alternatives and defends the choice; L4 produces a correct solution. Failure-mode naming: L5 states 3 failure modes per component in a design round; L4 produces a high-level architecture. Mid-round pivot: L5 adapts cleanly when the interviewer changes a requirement halfway through; L4 often has to throw out the design and restart. ### What advanced SQL is tested at L5 data engineer interviews? Seven patterns: recursive CTEs for hierarchy or graph traversal, gap-and-island for streak detection, sessionization with LAG and SUM OVER, SCD2 half-open joins, EXPLAIN plan reading and predicate-pushdown reasoning, skew handling with salt-and-rebalance, and idempotent MERGE for late-arriving data. The mid-level catalog covers JOIN, GROUP BY, basic windows; the senior tier composes these into multi-CTE queries with explicit edge-case handling. ### What does the optimization round look like at L5+? Interviewer hands you a query and an EXPLAIN ANALYZE output. Typical scenarios: sequential scan where you expected index seek (likely a function in WHERE preventing pushdown, an implicit cast, or a stale statistic), a JOIN with a long-running task (likely skew on the join key, salt and rebalance), or a window function that is slower than expected (likely a missing PARTITION BY or an inefficient frame clause). The bar is identifying the cause from the plan alone and proposing the fix. ### How is the design round different at L5 versus L4? L4 design round: produce a working high-level architecture for the given scenario. L5 design round: same scenario but the rubric weights '3 failure modes per component', explicit cost reasoning (back-of-envelope numbers), and the on-call story (what gets paged, who responds, what is the runbook). The interviewer typically changes a requirement halfway through to test the mid-round pivot. ### What is expected for staff (L6) data engineer interviews? L6 weights org-level design influence: how would you design the data platform itself (the orchestrator, the lineage system, the catalog, the testing framework) versus 'how would you build this one pipeline'. Behavioral rounds probe technical leadership (driving a multi-team migration, defining the technical strategy, mentoring senior engineers). The bar is the substrate the org builds on, not the surface workload. ### How should a data engineer prepare for the mid-round pivot? Practice with a peer or AI mock interviewer that explicitly changes the requirements halfway through. Common pivots: SLA tightens from 15 minutes to 1 minute (requires moving from micro-batch to streaming), data volume jumps 100x (requires partitioning strategy review, broadcast versus sort-merge join decision flip), the BI tool cannot handle table swaps (requires materialized view or insert-overwrite pattern instead of CTAS). The L5 signal is articulating what changes and what stays in the existing design without throwing it out. ### What about the behavioral round at senior data engineer level? Senior behavioral rounds probe ownership ('tell me about a time you caught a bug in production data nobody else noticed'), trade-off judgment ('tell me about a time you chose to ship the imperfect version'), and disagreement ('tell me about a time you disagreed with a senior engineer and how you resolved it'). STAR-D format: Situation, Task, Action, Result, Decision-postmortem. The decision-postmortem (what I would do differently) is the senior signal. ### How many mocks should I do before a senior data engineer onsite? 3 timed mocks in the final 2 weeks: one SQL+modeling, one Python+PySpark, one full design round. Plus 1-2 behavioral mocks with someone in the same level band. The part most candidates fail is not the technical content; it is the narration under pressure and the mid-round pivot. Mocks expose both. ## Senior Data Engineer Interview Preparation Self-paced practice across the 5 rounds of a senior data engineer interview loop, calibrated to L5+ rubrics with trade-off articulation, failure-mode naming, and mid-round pivot signal. Provided by DataDriven. ## Related practice catalogs - [Advanced SQL for L5+](https://datadriven.io/advanced-sql-interview-questions): The 7 advanced patterns: recursive CTE, gap-and-island, sessionization, SCD2 half-open, EXPLAIN, skew, MERGE. - [System design with senior rubric framing](https://datadriven.io/system-design-interview-prep): End-to-end design with 3 failure modes per component. - [ETL design with idempotency and replay](https://datadriven.io/etl-design-interview-prep): Idempotent backfills, MERGE on composite key, schema evolution. - [Data modeling at senior level](https://datadriven.io/data-modeling-interview-questions): Late-arriving dimensions, slowly-changing facts, conformed dimensions. - [PySpark for senior data engineer roles](https://datadriven.io/pyspark-interview-questions): Skew handling, Spark UI reading, AQE overrides. - [Staff data engineer (L6) interview prep](https://datadriven.io/staff-data-engineer-interview): Org-level design influence, platform thinking, technical leadership. - [Meta data engineer E5/E6 problems](https://datadriven.io/meta-data-engineer-interview-questions): Meta's senior bar with trade-off and communication weighting. - [Stripe data engineer E4/E5 problems](https://datadriven.io/stripe-data-engineer-interview-questions): Stripe's senior bar with failure-mode articulation. - [Netflix senior data engineer problems](https://datadriven.io/netflix-data-engineer-interview-questions): Netflix's Spark-heavy senior bar with streaming and late-arriving data. --- Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.