A day as a Solutions Architect
A solutions architect spends the day turning somebody's messy business problem into a design that engineers can build and a buyer can sign off on. This walkthrough follows one at a software vendor, working with prospects and existing customers. Internal solutions architects at a bank or a retailer have fewer sales calls and more committee meetings, but the core work is the same: listen, draw, defend, write it down.
One Tuesday, from inbox to whiteboard
Triage before the calls start
You open Slack and find three account executives asking for your time this week. One wants a demo tomorrow, one needs a security questionnaire answered, and one has a prospect asking whether your platform can run inside their own cloud account. You sort them by which deal is closest to a decision and block your calendar before someone else fills it.
Discovery call with a new prospect
The account executive runs the call, but the technical questions land on you. You ask how their data moves today, who owns identity, what they've already tried and why it stalled. Most of the value is in the follow-up questions, like finding out the nightly batch job everyone complains about is really a compliance requirement nobody wrote down.
The design review goes sideways
You'd planned a quick walk through the reference architecture with an existing customer's platform team. Instead, their lead engineer says the SSO setup you proposed won't pass their security review because they don't allow SAML from outside vendors. You spend the hour sketching an alternative in Lucidchart live on screen share, and you promise a revised diagram by Thursday.
Writing the part nobody sees
You draft the solution design document for a deal in its final stage: the integration pattern, the data flow, what the customer's team owns and what yours does. You also fill in the technical section of an RFP response, which is slow, careful work where one sloppy yes can turn into an angry implementation team months later.
Handing off and closing loops
You post notes from every call into Salesforce so the account team isn't guessing. Then you message the product manager about the SAML issue, because several customers have raised it lately, and product roadmaps move on patterns like that.
What separates this from an engineering job
You rarely write production code. You write proof-of-concept code, sample scripts, Terraform snippets and API calls in Postman that show something works, then you hand it to people who will build it properly. Your output is decisions, diagrams and documents. If you love shipping features and seeing your commits go live, that trade can feel hollow after a while. If you love understanding how a whole system fits together and explaining it to a room, it's the best seat in the building.
The tension you carry into every deal
Sales wants the answer to be yes. Engineering wants the answer to be accurate. You sit exactly between them, and your reputation depends on saying no early when the product genuinely can't do the thing. Architects who overpromise get popular with account executives for a quarter and then get quietly routed around by delivery teams. The ones who last learn to say "not like that, but here's what would work" in the same breath.
Where solutions architects usually come from
Senior engineer who kept getting pulled into customer calls
This is the most common route. Backend, cloud and DevOps engineers who were already the ones explaining the system to clients or other teams move over, often inside the same company first. Your design experience carries straight across; the new part is presenting and handling pushback from people who aren't technical.
Sales engineer or technical consultant moving up
If you already run demos and answer RFPs, the step up is depth. Solutions architects are expected to design the whole integration, not just show the product. Getting a cloud architecture certificate and owning a few complex deployments end to end usually makes the case.
Implementation or professional services lead
You've seen what happens after the contract is signed, which makes you unusually good at spotting designs that will break in delivery. Vendors like hiring from this pool because you already know where the product's rough edges are.
What Solutions Architect postings ask for
Hiring the most
- Bah30
- 360ITProfessionals115
- Accenture13
- Accenture Federal Services13
- AvanceConsultingServices210
Remote
20% of openings are fully remote.
Posted pay
$152,000 – $230,000
Typical range in the 39 of the newest 60 postings that list pay.
Questions people ask
Is a solutions architect a sales job or a technical job?
It depends heavily on where you work. At a software vendor or a cloud provider, the role is usually pre-sales, and part of your pay may be tied to deals closing. At a consultancy it's a mix of winning work and designing it. Inside a large company's IT department there's no quota at all, and you're designing systems for internal teams. Read the posting for words like quota, pre-sales or pipeline to tell which one you're looking at.
How is a solutions architect different from a cloud architect or enterprise architect?
A cloud architect designs infrastructure on one or more cloud platforms and usually goes deeper on networking, cost and reliability. An enterprise architect works across the whole organisation, setting standards and deciding which systems should exist at all. A solutions architect works one problem or one customer at a time and cares most about how the pieces connect for that specific need.
Do you need to code?
You need to read code comfortably and write small working examples: a script that calls an API, a Terraform module, a SQL query that proves a data model works. You won't spend your days in a codebase, but you'll lose credibility fast with an engineering audience if you can't open the terminal during a call.
1,849 Solutions Architect jobs are open today
HeroApply applies to them for you, so you can keep doing the job you have.