Technical Architect → Solution Architect

A realistic transition from Technical Architect to Solution Architect: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 86%. Difficulty: Easy.

Difficulty: Easy5 stepsDuration: 4 to 8 monthsOverlap: 86%

Transition from Technical Architect to Solution Architect.

Transferable skills

  • Solution design
  • Integration architecture
  • Cloud architecture
  • Security by design
  • Stakeholder management
  • Documentation

Skills to learn

  • Cost & sizing

Step-by-step learning plan

  1. 1. Build on your Technical Architect experience

    2–4 weeks

    Leverage

    • Solution design
    • Integration architecture
    • Cloud architecture
    • Security by design

    Map transferable skills — Solution design, Integration architecture, Cloud architecture — against what a Solution Architect needs.

  2. 2. Learn the core of the Solution Architect role

    6–10 weeks

    Learn

    • Cost & sizing

    Technologies

    GCPAPI GatewayLucidchart

    Cover the biggest gaps first: Cost & sizing.

  3. 3. Get productive with the Solution Architect toolchain

    4–8 weeks

    Technologies

    GCPAPI GatewayLucidchartVault

    Be hands-on with GCP, API Gateway, Lucidchart and the rest of the target stack.

  4. 4. Practise Solution Architect work in real conditions

    4–8 weeks

    Ship a portfolio project or take on Solution Architect tasks at work.

  5. 5. 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.

Alternative routes