about d8loop

Most practice tests what you remember.D8LooP tests what you’d decide.

How D8LooP evaluates your design

  1. Data model correctness
  2. Partitioning strategy
  3. Scalability
  4. Failure handling
  5. Idempotency
  6. Data quality
  7. Cost considerations
  8. Operational reliability
why it exists

Nobody gets hired for reciting a definition. Turn any one of these over.

how practice works here

Three beats, every scenario — and each one runs on its own here.

Build

Design the pipeline or the schema. You get the business problem — never the table names.

Review

Scored on structure, requirements, and how it fails. Not against one blessed answer.

Defend

Then the probes. What if it arrives twice? What was this value last Tuesday?

who it's for
  • Interviewing soon

    You can write the query. You have never been asked to justify the schema under it.

  • Two years in

    Everything you have built started from a table someone else designed.

  • Senior, out of practice

    You make these calls weekly. Saying why, in nine minutes, is the rusty part.

  • Starting from scratch

    New to data engineering. One roadmap takes you from Python and SQL to pipelines and Spark, a decision at a time.

    See the roadmap
what's next

One person builds this, in evenings. So this is what is moving, what is stopped, and why — rather than a roadmap that only lists the good news.

  1. In progress

    Data engineering projects

    End-to-end briefs instead of single scenarios: ingest it, model it, load it, test it, and write up the decisions. The thing you can actually point at in an interview.

  2. Ongoing

    Deeper scenarios

    Pipelines, Modeling, SQL and Python, reworked one scenario at a time up to the depth the newest ones already have. One person, most evenings — which is why it is a standing item and not a date.

  3. Open

    Collaborators

    If you have sat on either side of these interviews and would rather build something than complain about them, I would like to hear from you. This should stop being a one-person project.

who's behind it

Vijay Singh

  1. 2019 — 2026Ex-AmazonData Engineer · 7 years

I have been 7 years at Amazon, on both sides of the interview table. I built the thing I kept wishing candidates had.