Software Architect Roadmap
You own the decisions that are expensive to change. Architect is a destination role - typically 8+ years in, at $140-180k+ US - but the skills are built deliberately from mid-level onward. This roadmap is the deliberate version: design reps, trade-off literacy, and writing that moves organisations.
By Carl Mills • Last updated • tap any step for guidance and free resources • progress saves in your browser • free printable PDF roadmap poster.
Take this roadmap with you
Save your progress as a free personalized PDF study plan, plus one practical break-into-tech email each week. Unsubscribe anytime.
Software Architect roadmap FAQ
How do I become a software architect from developer?
Grow the scope of your decisions: own a service, then a system, then cross-team designs. Write design docs people actually follow, run architecture reviews, and build the trade-off vocabulary (consistency vs availability, build vs buy, coupling costs). Titles follow demonstrated scope.
Do architects still code?
The credible ones do - enough to prototype, review meaningfully and keep their instincts honest. The failure mode is the ivory-tower architect whose designs ignore friction. Most orgs now prefer "architect who codes" or principal-engineer shapes.
Is there a certification for architects?
Cloud architect certs (AZ-305, AWS SA Pro) usefully structure platform knowledge and pass HR filters for cloud-architect roles. For software architecture broadly, a portfolio of design docs and delivered systems outweighs any certificate.
What next once the list is green?
Prove it under pressure: take the free Mock Interview, then check your application signals.
Related roadmaps
Not sure this is your direction?
Compare every tech role - what you'd build, what it pays, and who it suits - on the roadmaps hub.
Compare all roadmaps