83%strong route
Career transition
Go Developer → Solutions Architect
Not generic reskilling advice, but an analysis of the distance between two specific occupations: tasks, skills, pace, money and risk.
01 · Starting distance
Transition realism index
Five factors answer a more useful question than “will it work?”: where the route is naturally strong and where proof is needed.
This is a strong route. The strongest support is Market opportunity (94%), while the main constraint is Task similarity (75%). The index estimates the distance between roles, not your ability.
Skill transfer81%
Task similarity75%
Entry accessibility86%
Market opportunity94%
Resilience gain88%
Starting roleGo Developer · 52%
→
Learning estimate3–6 months
→
Target roleSolutions Architect · 22%
02 · What changes in the work
Task comparison
The work shifts from Routine operations toward Control and accountability, a 13-point change. This is the main behavioral adjustment in the move.
Go DeveloperSolutions Architect75% · profile similarity
Analysis and data+12
People and communication0
Creation and design-6
Hands-on work0
Control and accountability+13
Routine operations-19
Go Developer: high-exposure tasks
Solutions Architect: high-exposure tasks
03 · Foundation and gaps
Skill-gap map
The map shows the gap between your starting point and a level you can demonstrate to an employer through work evidence—not simply “know / do not know.”
Already transferable
- knowledge of the sector, terminology and typical work situations
- software-system understanding
- debugging
- requirements work
- reading existing code
Needs development
- AI-agent architecture
- observability and resilience design
- architectural trade-offs
- component integration
- technical-debt management
- a practical case for the Solutions Architect role
013 wk
AI-agent architecture
Prove it in “Working prototype: Go Developer → Solutions Architect transition case”: include a distinct output that uses aI-agent architecture.
start 33%target 82%
023 wk
observability and resilience design
Prove it in “Working prototype: Go Developer → Solutions Architect transition case”: include a distinct output that uses observability and resilience design.
start 54%target 76%
033 wk
architectural trade-offs
Prove it in “Working prototype: Go Developer → Solutions Architect transition case”: include a distinct output that uses architectural trade-offs.
start 31%target 92%
043 wk
component integration
Prove it in “Working prototype: Go Developer → Solutions Architect transition case”: include a distinct output that uses component integration.
start 41%target 85%
054 wk
technical-debt management
Prove it in “Working prototype: Go Developer → Solutions Architect transition case”: include a distinct output that uses technical-debt management.
start 55%target 88%
064 wk
a practical case for the Solutions Architect role
Prove it in “Working prototype: Go Developer → Solutions Architect transition case”: include a distinct output that uses a practical case for the Solutions Architect role.
start 30%target 81%
04 · Choose a pace
Three transition scenarios
The same route affects work, money and fatigue differently. A duration without weekly effort says very little.
Keep your current job
8mo.4 h/week
139 hours total
139 hours total
Two short weekday sessions and one hands-on weekend block.
- First applications
- 6 months
- Trade-off
- Income is protected, but market feedback arrives later.
First apply AI-agent architecture in the current role, then build the portfolio.
Balanced route
5mo.7 h/week
152 hours total
152 hours total
Three weekly sessions: theory, practice and one end-to-end project.
- First applications
- 4 months
- Trade-off
- The pace allows market feedback without abruptly ending the current career.
After the foundation in AI-agent architecture, move into the project and first interviews.
Accelerated entry
4mo.12 h/week
208 hours total
208 hours total
Four study blocks weekly, weekly practice and mentor review.
- First applications
- 3 months
- Trade-off
- The new qualification develops faster, but fatigue and a shallow portfolio are real risks.
Start applying before training ends and improve evidence every week.
05 · If the direct jump is too large
Bridge occupations
These are not mandatory stops. They matter when they provide paid experience in the new kind of work before the full move.
Go Developer→AI Workflow Designer→Solutions Architect
in 89%out 81%≈ 10 mo.
The AI Workflow Designer role lets you learn part of the new task set in a more familiar context, then approach Solutions Architect with stronger evidence.
Go Developer→AI Application Engineer→Solutions Architect
in 89%out 81%≈ 10 mo.
The AI Application Engineer role lets you learn part of the new task set in a more familiar context, then approach Solutions Architect with stronger evidence.
Go Developer→Cybersecurity Engineer→Solutions Architect
in 72%out 64%≈ 18 mo.
The Cybersecurity Engineer role lets you learn part of the new task set in a more familiar context, then approach Solutions Architect with stronger evidence.
06 · Evidence over certificates
Portfolio project
One project cannot replace experience, but it gives an employer something concrete to discuss and shows you can finish real work.
24 hours
Working prototype: Go Developer → Solutions Architect transition case
Take a real but anonymized situation from your current field and solve it as a Solutions Architect would. The central project task is a role-specific task.
Your advantage is domain context from Go Developer. Make it visible: show which beginner mistakes it helps you avoid.
What the project folder should contain
- A repository or interactive prototype with architecture, tests and a demo
- A concise decision memo covering inputs, constraints and two rejected alternatives
- A result check using measurable criteria plus one failed approach and what changed
- A public 5–7-screen case study with all confidential data removed
What makes the project strong
- visible use of aI-agent architecture
- a real-world problem rather than a tutorial exercise
- a measurable outcome and explicit limitations
- enough depth to support technical interview questions
07 · France · pay before tax
Income trajectory
In the baseline scenario, modeled income returns to the current level about 5 months after learning begins. This is a scenario model, not a pay promise.
Now€4 230
During study€4 145
First offer€5 461
+1 year€6 106
+2 years€6 860
Model horizon€8 720
Show long-term salary comparison through 2035
08 · Technology horizon
How automation risk changes
The move reduces modeled automation exposure by 21 points by 2035, but the target role is not immune: its task mix also changes.
2026
52%Go Developer22%Solutions Architect
2028
56%Go Developer28%Solutions Architect
2030
60%Go Developer35%Solutions Architect
2035
66%Go Developer45%Solutions Architect
09 · An honest check
What you may not like
A good career choice is more than a list of benefits. Before studying, check whether you can live with the target role’s daily reality.
Debugging consumes real time
Much of the output is invisible until late; days include root-cause analysis, documentation and detail work.
The daily rhythm will change
The target role contains substantially more rules and repeatable operations. That can be tiring even when the occupation sounds appealing in theory.
Market pay is not first-offer pay
Even when average pay is higher, a newcomer’s first offer is usually lower. A strong project and domain experience reduce—but do not erase—the gap.
10 · Where to start
Suggested sequence
- 01
Review 20–30 Solutions Architect vacancies and record actual tasks, mandatory requirements and tools.
- 02
Define the bridge from Go Developer: knowledge of the sector, terminology and typical work situations. Prepare two examples where this experience produced a measurable result.
- 03
Learn AI-agent architecture and observability and resilience design to the level of completing an independent practical task—not merely finishing a course.
- 04
Build a working prototype, publish the code in a repository, and add tests, documentation and a decision record.
- 05
Review 20–30 vacancies and choose only courses or certificates that repeatedly appear in employer requirements.
- 06
Rewrite your résumé for Solutions Architect, add the case and begin with test applications, internships, projects or adjacent tasks at your current employer.
All timelines, salaries and percentages are scenario estimates. They depend on starting skills, location, experience, weekly study time and employer requirements. Validate the route through practitioner conversations, a test project and real vacancies.