Solutions Architect

You're the technical person who designs the answer — mapping a customer's messy reality onto systems that actually work, then convincing both the engineers and the executives it's right. It's where deep tech skill meets talking for a living, and it pays like both. Here's the honest picture.

Median pay (US)

~$140k / yr (+ bonus in pre-sales)

Typical range

$105k–$190k+

Degree required?

No — experience + certs win

What the job actually is

Solutions architects design how technology fits a specific problem. The role comes in two main flavors: customer-facing SAs at cloud and software vendors (part of sales teams — running discovery, designing architectures, building proofs-of-concept, answering 'will this work with our stack?' credibly), and internal/enterprise architects who design how their own company's systems evolve. A week is discovery calls, whiteboard sessions (literal or virtual), architecture diagrams, a POC build, and translating between a customer's engineers ('show me the API') and their executives ('what's the risk?'). The job's essence: technical credibility deployed through communication.

Is it actually you?

You'll probably love it if

You're the engineer people already pull into customer calls — and you secretly like it
Whiteboarding a system from a messy conversation is your best skill
Breadth beats depth for you: fifty architectures shallowly-then-deeply, not one codebase forever
You can hold your own with a skeptical engineer AND a bored executive in one meeting
You want senior-engineer money without the pager or the sprint board

Maybe not, if

Talking is the tax and building is the joy — this job inverts that ratio
Sales pressure (quotas, deal timelines, 'can you just say yes?') would corrode your integrity meter
Travel and customer-schedule chaos don't fit your life
You need to own what you design; SAs hand blueprints to others and move on
Hands-on depth is your identity — the role's danger is slowly becoming slideware

The real day-to-day (no hype)

Pre-sales vs internal is the fork that defines everything. Vendor SAs (AWS, Salesforce, every SaaS company) live on sales teams: commission-flavored comp, customer travel, deal energy. Internal enterprise architects live in IT orgs: steadier, more governance, less adrenaline. Same title, different lives — choose the metabolism, not the logo.
Credibility is the entire product. The moment a customer's engineer catches you hand-waving, the deal wobbles. Great SAs keep building — labs, POCs, side projects — because 'I've actually done this' is the only sentence that closes technical objections.
The certs are real currency here (unusually). Cloud architecture certifications — AWS SA Professional above all — function as genuine hiring signals in this field, more than certs do almost anywhere else in tech. They're the documented path in for ops and support people.
It's the senior engineer's exit from the pager. Engineers who tire of on-call and sprint grind but love systems thinking find SA work is the same brain, better hours, comparable-or-better pay — with communication skill as the price of admission.

How people break in — or switch in

The routes: engineers and SREs who kept getting borrowed for customer calls (the natural slide), support engineers who mastered the product deeper than anyone and moved to pre-sales, sysadmins and consultants who stacked cloud certifications into vendor SA roles. The AWS/Azure/GCP certification ladder is the most-documented path — SA Associate then Professional, plus one real architecture you can defend in depth. Interviews test whiteboard reasoning and communication: practice designing systems out loud, handling the hostile question, and saying 'I don't know, here's how I'd find out' without flinching.

If engineers already trust your designs AND customers already like talking to you, you're sitting on this career without collecting its salary — the certification is mostly paperwork for what you can already do.

Your application, already half-written

Here's a question every Solutions Architect application asks, answered the way pirch would — in a real voice, grounded in real experience:

“Walk us through a solution you designed for a customer.”

A logistics customer wanted 'real-time tracking' — and the sales team had already promised it. Discovery revealed the real constraint: their telemetry arrived in batches from vehicle hardware they couldn't replace for three years. Instead of designing the fantasy, I whiteboarded two honest options: true streaming (contingent on the hardware refresh) and a near-real-time pipeline off their existing batches — 90-second latency, 20% of the cost, shippable in a quarter. I built the POC for option two in a week, and their engineers stress-tested it themselves, which is exactly what I wanted: their conviction, not my slides. They bought, deployed, and upgraded to streaming two years later — with us, because we'd been straight with them when it mattered. That's the job: designing the thing that's true, not the thing that's promised.

pirch's co-pilot writes answers like this for your background and the exact job — try it free →

pirch finds the architect roles that are actually you

Vendor pre-sales with commission energy or internal architecture with governance calm — the title hides the fork. Tell pirch who you are and it hunts down real, still-open solutions architect roles that fit the whole you, with a tailored cover letter already written. No spray-and-pray. No dead links.

start your free hunt

first hunt free · we never auto-apply · you stay in control

Common questions

What does a solutions architect actually do?

They design how technology solves a specific problem — running discovery, producing architectures, building proofs-of-concept, and communicating trade-offs to both engineers and executives. Vendor SAs do this in sales cycles; internal architects do it for their own company's systems.

How much do solutions architects make?

Roughly $105k–$190k+ with a median around $140k. Pre-sales SAs at cloud vendors add bonus/commission on top; principal and specialist architects at major vendors exceed the range.

How do I become a solutions architect?

From engineering, support, or ops — plus demonstrated communication and (unusually for tech) certifications that genuinely count: the AWS/Azure/GCP architect tracks are documented hiring currency. One real architecture you can defend in depth beats a portfolio of diagrams.

Do solutions architects still write code?

Some — POCs, demos, automation — but designing and communicating replace daily building. Staying credibly hands-on is a deliberate discipline (labs, side builds); SAs who let it lapse drift into slideware and lose the technical trust the job runs on.