Menu

The DataDank 90-day plan

Become a job‑ready Data Engineer in 90 days.

One clear plan, day by day: SQL, DSA, PySpark, Snowflake, Kafka, Airflow, AWS and system design, with mock interviews and applications built in. Every topic opens a full lesson.

Days
90
Planned hours
348
Topics tracked
1017
Lessons
135
See the full 90-day planEvery day, week and phase, with milestones

Your progress

Saved in this browser only, no account needed.

Open a lesson or tick off an interview question and your progress appears here.

The roadmap

Three phases. Thirteen weeks. One goal.

Foundations first, then advanced topics and projects, then interview mastery. Each week ends with a clear milestone, and every day has one topic per skill.

  1. Days 1–30 · 114 hours

    Foundations

    Core SQL+DSA+Spark mastered; 1 project; start applying

    1. Week 1SQL joins/windows solid + 15 DSA done
    2. Week 2Advanced SQL + 30 DSA + Spark core
    3. Week 3PySpark performance + Snowflake basics
    4. Week 41 end-to-end project + 50 DSA

    Target 60% prep • first OAs & recruiter calls

    Open phase 1
  2. Days 31–60 · 114 hours

    Advanced + Projects

    Cloud+Streaming+Modeling done; 2 projects; active interviews

    1. Week 5Kafka + streaming fundamentals
    2. Week 6Airflow + AWS Glue/Redshift
    3. Week 7Data modeling + 80 DSA
    4. Week 82nd project + system design start

    Target 85% prep • multiple onsites in pipeline

    Open phase 2
  3. Days 61–90 · 120 hours

    Interview Mastery

    Interview-ready across the stack; mocks done, project demo ready, applications under way

    1. Week 95 system design scenarios + mocks
    2. Week 10110 DSA + revise weak areas
    3. Week 11Full mock loops + behavioral prep
    4. Week 12Final revision + apply aggressively
    5. Week 13Final mocks, project walkthrough and applications

    Target All 90 days reviewed • full mock interviews done • project demo and résumé ready

    Open phase 3

Courses

Pick a technology and start learning

Each course has ordered lessons, interview questions, projects and a cheat sheet.

How we write

Editorial principles

  • Reviewed technical content

    Claims about tools are checked against official documentation, and each page shows when it was last reviewed.

  • Version-aware

    Where behaviour depends on a version or platform release, the page says which one it describes.

  • Evidence-labelled interviews

    Company material is labelled as attributed, reported or representative practice. We never present invented questions as real ones.

  • Structured paths

    Every lesson sits in a course with a clear previous and next step.

Search
Filter by type