How to Become a Solutions Architect in 2026

By Tim O. Updated October 16, 2026.

A solutions architect turns a customer's problem into a technical design and stays with that customer while the design is tested. Three routes in: software engineering or DevOps, pre-sales or sales engineering, and customer success, TAM, or support. In a sample of 25 US postings checked October 16, 2026, 21 used the words customer-facing or pre-sales. Levels.fyi puts US median total compensation at $217,000. The salary guide has the company table.

What a solutions architect actually does

The job is the design conversation with a customer, not a private engineering task. In the October 16, 2026 sample, 13 of 25 postings name discovery, 14 of 25 name presentation, and 7 of 25 name a proof of concept or a demo. Salesforce asks for system and functional designs on its Data 360 posting. GitLab asks for reference architectures on its staff solutions architect posting. The sample does not describe one weekly calendar, so this page does not invent one.

Titles in the sample include Solutions Architect, Senior Solutions Architect, Pre-Sales Solutions Architect, and Product Solutions Architect. Stripe's enterprise posting lists solution consultant, solutions architect, and sales engineer as one kind of customer-facing role. Pre-sales and delivery are different motions. Snowflake's services-delivery posting is not the same job as the pre-sales titles. Databricks had many open Delivery Solutions Architect roles on the same date. They are not in this sample, because the sample keeps at most two postings per company and those two are the non-delivery titles.

From software engineering or DevOps

This route is for people who already write software or run production systems. The sample does not count how many hires come from that background.

What you may already have: 12 of 25 postings named Python. A programming background matches a skill employers wrote down.

What the sample says is still missing: 21 of 25 postings used the words customer-facing or pre-sales, and 13 of 25 named discovery. If you have not had that conversation with a customer, that is the gap these postings describe.

Two first steps:

Take one system you know and write the design as if a customer had to approve it, then say it out loud. Presentation was named on 14 of 25 postings.
If you do not have a cloud project yet, follow the Cloud Resume Challenge guide, then put the result in the shape described in the portfolio projects guide.

From pre-sales or sales engineering

This route is for people who already run discovery, demos, or sales engineering. The sample does not count how many hires come from that background.

What you may already have: the customer conversation. 21 of 25 postings use customer-facing or pre-sales language for the role.

What the sample says is still missing when that language is not enough on its own: Python on 12 of 25 postings, AWS on 9 of 25, and CI/CD or DevOps on 9 of 25. The gap is whichever of those you cannot show.

Two first steps:

Build a small demo on one cloud the postings name, and be ready to change it while someone watches.
Write that design down and present it. The portfolio projects guide is the format to use.

From customer success, TAM, or support

By Tim O., a senior customer success engineer.

This is the route I know best. A customer success engineer already does much of what a solutions architect does: technical workshops, architecture discussions, demos, and helping customers make an implementation work in their environment. The biggest difference is timing. Pre-sales solutions engineers and architects work before the deal; customer success engineers work after it, on adoption and expansion. The core skill is the same: translating business requirements into a technical solution.

What a CSM or TAM is usually missing is technical depth. Not expert programming, but enough hands-on experience with APIs, cloud infrastructure, scripting and integrations to hold your own with engineers, architects and DevOps teams, and the ability to explain it clearly to people who aren't technical.

My first two steps for anyone on this route:

Build projects with the same tools your customers use. You learn the most when something breaks and you have to work out why. Build things, break them, fix them, repeat.
Take on the technical work in your current role. Run the first round of troubleshooting yourself before escalating, and ask to join architecture and implementation discussions.

A certification can give that learning a structure, and I often study toward one for that reason. But the projects are what give you the confidence to solve problems in front of a customer.

If you want to start with the post-sale version of this work, see what 25 technical customer success postings ask for.

Skills employers ask for

These counts are from the 25 postings checked on October 16, 2026. Company slogans, pay footnotes, and interview-step labels were not counted. A skill counts once per posting. Azure and Google Cloud were each named on 7 of 25 postings, usually in the same sentence as AWS, so they sit just outside this table.

Most-named items in 25 US solutions architect postings, checked October 16, 2026.
What the posting named	Postings
Customer-facing or pre-sales, using those words	21 of 25
Presentation	14 of 25
Discovery	13 of 25
Python	12 of 25
AI or machine learning, in the duties or requirements	12 of 25
AWS	9 of 25
CI/CD or DevOps	9 of 25
APIs or integration	8 of 25
Security	8 of 25
Proof of concept or demo	7 of 25

Customer-facing or pre-sales language matters because 21 of 25 postings use it to describe the role, not an internal engineering task. Presentation matters because 14 of 25 ask you to explain the design to the people who have to accept it. Discovery matters because 13 of 25 name the conversation that turns a customer's problem into requirements before the design is drawn.

9 of 25 postings named any certification. Only 1 named an AWS or Azure solutions architect certification. That posting named AWS Solutions Architect Professional or the Azure Solutions Architect Expert equivalent. 2 named a Databricks certification, 2 named a Salesforce certification, and the other 4 named a FinOps certification, a MongoDB certification, a dbt certification, or an optional Kubernetes, cloud, or security certification. The sample does not pick a first certification.

A realistic roadmap

The postings do not share one number of months or years. The phrases they do use run from 2+ years in a post-sales role to 15+ years overall. How long the move takes depends on the route.

Foundations

Learn the customer conversation the postings name most often: discovery and presentation. If you need a cloud project to point at, start with the Cloud Resume Challenge guide.

Proof

Build one project you can present. 7 of 25 postings named a proof of concept or a demo. Use the portfolio projects guide for the project, including the architecture writeup.

Positioning

Read the salary guide before you talk about pay, and apply to titles that match the motion you want. Pre-sales and delivery are both in the sample, and they are not the same job. If the work you want is building the system inside the customer's environment, the forward-deployed engineer guide is a related role. See what those postings ask for instead of a forward deployed engineer certification.

What it pays

The US median total compensation for a solution architect is $217,000, from 1,214 submissions on Levels.fyi, checked October 13, 2026. Glassdoor's median total pay for the same title is $221K, checked the same day. The two medians are within about 2%. Both figures are total compensation, not base salary. The company-by-company table is in the salary guide.

Go deeper

Solutions Architect Salary 2026: $217K Median Total Pay. Median solutions architect pay is $217K total comp (Levels.fyi, Oct 2026). Company medians from Salesforce at $240K to Databricks at $410K, all sourced.
5 Portfolio Projects That Prove You're Ready for Solutions Architect. Build a portfolio that demonstrates architectural thinking: RAG Pipeline, Well-Architected Review, FinOps Case Study, and more.

FAQ

How do you become a solutions architect?

This page covers three routes: from software engineering or DevOps, from pre-sales or sales engineering, and from customer success, TAM, or support. The 25 postings checked on October 16, 2026 do not share one timeline. Use the route that matches work you already do.

What is the solutions architect career path?

The postings do not describe one ladder. This page uses three stages: foundations, proof, and positioning. How long each stage takes depends on the route, and the sample does not support one number of months.

What skills matter for a solutions architect in 2026?

In the sample of 25 US postings, 21 used the words customer-facing or pre-sales, 14 named presentation, and 13 named discovery. The skills table on this page lists the rest of the counts.

How do you become a solutions architect from a software engineer?

12 of 25 postings named Python, so a developer may already have a skill employers wrote down. 21 of 25 still used customer-facing or pre-sales language. The software route on this page starts with that gap: a discovery conversation and a design you can present.

Do you need to code to be a solutions architect?

12 of 25 postings named Python. The sample does not say the job is free of code. It also does not say you write production code every day.

Which certification should you take first?

Can you become a solutions architect without a degree?

9 of 25 postings mention a degree. Each of those also accepts equivalent experience, or says the degree is preferred but not required. The other 16 do not mention a degree.

How is a solutions architect different from a solutions engineer?

One Stripe posting lists solution consultant, solutions architect, and sales engineer as the same kind of customer-facing role. Other postings in the sample use pre-sales for the solutions architect title. One Snowflake posting is a services-delivery title. The titles overlap, and pre-sales work and delivery work are not the same motion.

Postings in the sample

Checked October 16, 2026. The count rules are in the research note that sits with this repo. Each link is the career page the count came from.