Engineer to solution architect
A solution architect designs how a set of systems, teams and constraints fit together to solve a business problem, and then stays accountable for the design as reality pushes back. The job is as much about communication, constraints and trade-offs as about technology, and titles differ widely between companies, so read each description carefully.
What changes
- You work across systems and teams, often as an influencer rather than as the person who builds.
- You are expected to explain the same design to executives, engineers, security and operations, in different terms.
- Cost, risk, compliance, vendor choices and the existing landscape matter as much as technical elegance.
- You document and defend decisions, and stay involved after the diagram is approved.
Skills to build
- System and integration design. Reasoning about boundaries, data flow, failure modes, scalability and evolution.
- Trade-off analysis and decision records. Making options and reasons explicit so decisions survive staff turnover.
- Cloud and infrastructure literacy. Enough breadth across hosting, networking, identity and observability to judge proposals.
- Security and compliance basics. Threat thinking and an understanding of the regulatory context you work in.
- Communication with non-engineers. Diagrams and short documents that a stakeholder can act on.
- Cost awareness. Estimating and comparing run costs, build effort and risk of options.
How to show evidence
- Designs you authored or materially shaped, with the constraints, alternatives considered and what happened in production.
- Cross-team initiatives such as a migration or integration where you aligned several teams.
- Architecture decision records, design reviews you ran, or standards you introduced and who adopted them.
- Post-mortem learnings and how you changed a design because of them.
- Certifications can help signal breadth for some employers but are not a substitute for design evidence.
Common pitfalls
- Drawing diagrams detached from delivery; architects who never see production lose credibility fast.
- Optimising for technology fashion instead of the organisation's skills and constraints.
- Becoming a gatekeeper rather than enabling teams to decide well themselves.
- Underestimating the communication load, especially with senior non-technical stakeholders.
First steps
- Write an architecture decision record for a real decision you took part in, including the alternatives you rejected.
- Present one design to a non-technical audience and ask what was unclear.
- Compare your skills with two solution architect job descriptions to find the gaps that repeat.
- Practise system-design and leadership interview questions with examples from your own work.
This guide describes common patterns, not guarantees. Roles and expectations differ between employers.
See which skills you still need for this move and get ordered learning resources.
Build my roadmapAlso see the role guide and interview questions.