Technical Business Analyst → Solution Architect
A realistic transition from Technical Business Analyst to Solution Architect: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 24%. Difficulty: Hard.
Difficulty: Hard6 stepsDuration: 16 to 20 monthsOverlap: 24%
Transition from Technical Business Analyst to Solution Architect.
Transferable skills
- Stakeholder management
- Documentation
Skills to learn
- Solution design
- Integration architecture
- Cloud architecture
- Security by design
- Cost & sizing
- Mentoring
Step-by-step learning plan
1. Build on your Technical Business Analyst experience
2–4 weeks
Leverage
- Stakeholder management
- Documentation
Map transferable skills — Stakeholder management, Documentation — against what a Solution Architect needs.
2. Learn the core of the Solution Architect role
6–10 weeks
Learn
- Solution design
- Integration architecture
- Cloud architecture
Technologies
AWSAzureGCP
Cover the biggest gaps first: Solution design, Integration architecture, Cloud architecture.
3. Master advanced Solution Architect skills
6–10 weeks
Learn
- Security by design
- Cost & sizing
- Mentoring
Technologies
KubernetesTerraformKafka
Handle the advanced topics: Security by design, Cost & sizing, Mentoring.
4. Get productive with the Solution Architect toolchain
4–8 weeks
Technologies
AWSAzureGCPKubernetesTerraformKafkaPostgreSQLAPI Gateway
Be hands-on with AWS, Azure, GCP and the rest of the target stack.
5. Practise Solution Architect work in real conditions
4–8 weeks
Ship a portfolio project or take on Solution Architect tasks at work.
6. Get certified and position yourself as a Solution Architect
4–8 weeks
Technologies
AWS Solutions Architect ProfessionalTOGAF 9 CertifiedAzure Solutions Architect Expert
Update your CV and LinkedIn around Solution Architect, then apply to target roles.