Learning roadmap to become Software Architect

I’ve held a few dozen mentoring sessions on how to become a software architect - and I figured that’s enough to finally automate the process

So I created a learning roadmap for entering the architect role.
- Focus on what truly matters and on simplicity - it’s not one of those endless lists like “learn every tech in the world and achieve zen.”
A simple roadmap doesn’t mean an easy journey.
- No narrow specializations.
A mobile architect doesn’t care about DWHs, and a backend architect doesn’t need to fiddle with frontend state management.
- Architectural bureaucracy (all that Enterprise/Solution/etc. division) is mentioned only briefly - it’s mostly irrelevant in today’s world.
- The roadmap will keep evolving, but its focus on clarity and simplicity will remain.

What do you think?