Find your architect path

“Architect” covers very different jobs. A cloud architect, a data architect and an enterprise architect spend their days on completely different problems. Answer four questions to see which path fits you best and where to start. There are no wrong answers, and nothing is saved.

1 of 4Where are you today?

Student or new to software (less than a year)Developer with 1 to 4 years of experienceSenior developer or tech leadOperations, infrastructure or DevOpsData or analyticsBusiness analyst or product manager

2 of 4Which work sounds most enjoyable?

Deciding how an application should be structuredRunning systems reliably on the cloudDesigning data models and pipelinesConnecting many systems so data flows between themProtecting systems from attackersPutting AI models into real productsShaping technology strategy for a whole companyBuilding tools and platforms for other developers

3 of 4Which problem would you most like to be handed?

Our app is slow and every change breaks somethingOur cloud bill doubled and outages keep happeningEvery report shows different numbersTwenty systems swap data through fragile scriptsA partner's passwords leaked; what can attackers reach?Leadership wants an AI assistant over our documentsFive teams bought five tools that do the same jobDevelopers wait days to get a test environment

4 of 4How do you like to spend your day?

Mostly hands-on, building and automatingA mix of design work and hands-on buildingMostly diagrams, documents and conversations with people

Show my path

---

The result is a starting point, not a verdict. Many architects move between paths over their careers. When you’re ready, follow the full developer to architect roadmap.