Solutions Architect
Customer calls, reference architectures, PoCs, occasional code review.
The most pragmatic architect seat going. Real delivery work, real authority, less politics than enterprise architecture, more autonomy than tech lead.
- You've delivered complex builds end-to-end and can defend the choices in writing
- You enjoy stakeholder management and pre-sales conversations
- You can hold a system in your head across multiple teams
- You're comfortable writing things down so the next person doesn't have to ask you
- You want to be hands-on every day, you won't be
- You'd resent owning outcomes without controlling the engineers
- You can't tolerate sales cycles or commercial scoping
- Your designs ship roughly as you drew them
- Engineering teams ask for you on the rebook
- You can spot a doomed scope before contract signature
- You're trusted to push back on sales without being dismissed
Solutions architects at consultancies live and die by the sales pipeline. Quiet quarters are stressful even if you're doing good work, and busy quarters mean six concurrent engagements with the wrong context-switch cost. In-house solutions architect roles trade variety for stability, but the variety is part of why people take the title in the first place. Be honest about which trade-off suits you.
Tradeoffs at a glance
Hover any chip for the calibrated meaning. Ratings are directional, not absolute.
Promotion ceiling
High, principal SA comp at hyperscalers is excellent.
- +Senior cloud engineer
- +Pre-sales SE
- +Consulting engineer
- −That you'll still code daily, most don't.
Where this leads
- Cloud Architect
- Pre-sales
- Enterprise Architect
Certifications people pair with this
Listed because the graph connects them to this role, not because you need all of them. Most practitioners pick one or two.
Pathways that pass through here
- Cloud Engineer → Cloud Architect
Highest-paid generalist track. Stack: networking + Linux + cloud + IaC.
- Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
- Security Architect (after 7+ years)
Design the trust boundaries. Pursued after 7+ years of hands-on work, not as a starting lane.
The serious next step
You've read about the role. The harder question is whether it's the right one for you.
A Career Verdict is the written, practitioner-authored call on your specific route into and out of this role. Six primitives, same format every time.
Built on POST's practitioner-authored assessment framework, calibrated by James from twenty years across helpdesk, infrastructure and security. Framework is human-authored; the verdict applies it to your inputs.