The Data Foundry

Built by Data with Pranjal

Public Beta

The Data Foundry is improving every week. If something feels unclear, broken, or missing, tell us and we will use it to improve the platform.

Core Practice Path

Know what to practise next without losing the full library.

Follow 30 reviewed exercises in a deliberate order, or open the complete SQL, Python, PySpark, Airflow, AWS, scenario, and system-design libraries whenever you need more repetition. The core is a recommendation, not an access limit.

Progress comes from completed exercises. Completing this path records practice evidence; it does not guarantee an interview or job outcome.

Core progress

0/30

reviewed exercises completed

0%
Start: Top salary bands per department

01

Core for direction

Use the reviewed sequence when you do not know what should come next.

02

Library for depth

Open every track's full problem collection for repetition and interview drilling.

03

Evidence for progress

Stages complete from actual exercise results, never from a manual checkbox.

Your learning sequence

Seven stages, thirty core exercises

The curated exercises establish a dependable foundation. The secondary action in every stage keeps the entire practice library available from the same place.

Stage 1Current stage

0/8 core exercises

SQL correctness

Build reliable grain, joins, windows, deduplication, change detection, and late-data reasoning.

Stage 2

0/5 core exercises

Python for pipelines

Use Python for validation, idempotency, reconciliation, deterministic selection, and CDC handling.

Stage 3

0/5 core exercises

PySpark production

Practise deterministic DataFrame transformations, schema evolution, timezones, and join strategy.

Stage 4

0/4 core exercises

Airflow and operations

Recover safely from backfill, retry, observability, and orchestration failures.

Stage 5

0/2 core exercises

AWS judgment

Make cloud decisions from workload evidence, delivery guarantees, cost, and operating constraints.

Ready to move on when you can

  • Start with workload, scale, latency, and failure constraints
  • Compare the chosen service with its closest alternative
  • Include security, cost, idempotency, and observability
Stage 6

0/2 core exercises

Broken-pipeline scenarios

Combine technical diagnosis, business impact, safe recovery, and prevention in realistic incidents.

Ready to move on when you can

  • Use the supplied evidence before proposing a fix
  • State the root cause and affected business outcome
  • Describe recovery, reconciliation, and prevention
Stage 7

0/4 core exercises

System design

Turn requirements into defensible architectures with reliability, replay, quality, and cost trade-offs.

Ongoing review loop

Reattempt weak areas instead of collecting completion badges.

After every few exercises, use the dashboard to revisit failed attempts, explanations with gaps, and concepts that did not hold up on the first try. Review remains ongoing and is not presented as a final readiness claim.

Review practice evidence