For engineering students and freshers

Don't study for a tech career. Build your way into one.

Four of the most in-demand tech roles, each a roadmap you learn by building. You get short time boxes, real company briefs and honest rules for using AI, and every quest you finish reveals something new.

4career paths
5 daysto start building
80quests, each ending in proof
0hour-long video courses
How every roadmap works

Five stages, from first line of code to people using your work

Every role follows the same arc. Each stage unlocks a real capability you can put on your resume.

Sprint Zero

Language, core ideas and framework in 5 days. Just enough to start building.

5 days

Learn by building

Small builds that each teach one real concept by doing it.

4–6 weeks

Company-style builds

Real briefs: problem, goal, definition of done. Working out the how is up to you.

~4 weeks

Architect mode

You write the spec, AI agents build it, and you review like a tech lead.

~1.5 weeks

Meaningful project

Something real people use. This is your story in interviews.

4–6 weeks
The rules of this place

Learn the way working engineers actually learn

Build first, study on demand

You won't remember a framework from a course. You'll remember the bug that cost you two hours. Read just enough to start, then learn each detail the moment a build needs it.

Time-box everything

Each quest has a time box. If you go over by 2×, stop, ship what you have, and note what was hard. Finishing matters more than perfection at this stage.

Read, don't binge-watch

Docs are faster than videos, and you can search them. When a video is linked, it's short and meant to be watched in one sitting.

Every quest ends in proof

A repo, a URL, a chart, a memo. Log it in your journal and by the end you'll have a portfolio without ever 'making a portfolio'.

Using AI while you learn

AI is your tutor first, and your team later

Used well, AI makes you learn faster. Used badly, you end up with a portfolio you can't explain. Here are the rules. The AI Playbook covers how to architect and prompt once you're past the basics.

Use AI freely for

  • Explaining a concept, an error message or someone else's code, then asking follow-up 'why' questions
  • Quizzing you: 'ask me 5 questions on what I just learned'
  • Reviewing code you wrote: bugs, edge cases, security holes
  • Boilerplate you already understand (config files, repetitive types, test data)
  • Brainstorming edge cases and failure modes for your design

Use carefully

  • Writing code for a concept you're learning: write it yourself first, then compare with the AI's version
  • Choosing libraries: AI may suggest outdated packages, so check the docs and the last release date
  • Facts and numbers: verify anything you'll put in a README, resume or memo

Don't use AI for

  • Code you can't explain line by line. If you can't explain it, you don't own it, and interviews will show it
  • Skipping the struggle. The 20 minutes you spend stuck is when learning happens
  • Deciding what to build or what your analysis concludes. That judgement is your job
  • Pasting secrets, API keys, or private user data into chats
Type the first version yourself. Delegate the second. Review every one.