Road Mates EnterHow to become a Software Developer, phase by phase: what you do in each one, how long it takes, and the proof that shows you're done.
5 phases1–2 years18 resources
Working through one language daily (e.g. Python or JavaScript), writing small programs covering variables, control flow, functions, data structures and basic Git. By the end, the person can solve beginner exercises without following a tutorial step by step.
You're done when you can show
A GitHub repo with 30+ solved exercises committed over several weeks.
Resources
Stops doing isolated exercises and starts building full applications end to end: frontend or CLI, backend, database, deployment. Produces two or three working projects that solve real problems, with readable code and READMEs.
You're done when you can show
A live deployed project URL with its public source repository.
Resources
Shifts from solo greenfield code to reading and changing other people's code: contributing to open source, freelance fixes, or team projects with code review, issues and pull requests. Proves the ability to work within existing conventions and accept feedback.
You're done when you can show
Links to merged pull requests in a codebase you didn't create.
Resources
Stops building new features and focuses on job search: polishing resume and portfolio, practicing data structures and algorithm problems, doing mock interviews, and sending targeted applications. Ends with a signed offer for a developer role.
You're done when you can show
A signed job offer letter for a software developer position.
Resources
Working on a team delivering features, fixing bugs, writing tests and handling code reviews in a production system. By the end, the person independently owns and ships tasks from ticket to deployment.
You're done when you can show
A shipped feature in production credited to you, e.g. a merged PR or release note.
Resources
Walk this road with people on it.
Track each phase, post your proofs, and get matched with people in the same phase.