How to Hire a Solutions Architect

Hiring a solutions architect is a translator search, not a senior-engineer search. You are looking for the person who can sit in a room with a VP of engineering, a skeptical CFO, and a client’s security officer, then walk out with agreement on an architecture that actually ships. The people who can do that job well run $165,000 to $235,000 base in 2026. The people who look like they can on a resume but cannot run a room are the reason most SA searches take 90 days instead of 45.

Here is the screening trap I watch companies fall into every month. The hiring manager promotes her strongest individual contributor. Call her Priya. Priya can draw any system on a whiteboard from memory, the team trusts her on hard technical calls, and to the hiring manager this feels like the obvious signal for who should get the architect title. It is not. It is the signal for who should get the principal engineer title, which is a different job. Six weeks in she is miserable. The client workshops drain her. The pre-sales calls feel like a performance she never signed up for. The migration plan she produced is brilliant and nobody reads it because she could not defend it in the executive review. The architecture was right. The hire was wrong. We have seen this exact pattern three times in the last year, and twice the company paid us to replace the person they had promoted.

My name is Tom Kenaley. I run technical placements through KORE1’s IT staffing practice, and solutions architect searches are one of the longer-running categories on my desk. A disclosure before you read further. We earn a fee when you fill a search with us. I have structured this guide the way I structure intake calls, which means I will flag the moments when going it alone is the cheaper move and the moments when it is not. Some of what follows will not be flattering to staffing firms.

What a Solutions Architect Actually Does

A solutions architect designs technical systems that solve a specific business problem, defends those designs in rooms full of non-technical stakeholders, and stays close enough to the delivery team to catch the moments when reality diverges from the diagram. The job sits between sales, engineering, and operations. Most of the week is meetings, diagrams, and writing. Some of the week is code review. Very little of the week is writing new code, and that is the first expectation most hiring managers get wrong.

The U.S. Bureau of Labor Statistics tracks the closest analog under computer network architects, with a May 2024 median wage of $129,840 and projected growth of about 13 percent through 2034. Read that number with caution. BLS groups network architects, cloud architects, and general solutions architects into one bucket, and the pay range inside that bucket is enormous. A solutions architect at a SaaS vendor with a quota attached is probably making $210K base plus commission. A solutions architect at a regional insurance carrier supporting internal delivery is probably making $145K flat. Same title. Very different jobs. For the management track many senior architects eventually move into, the BLS tracks computer and information systems managers as a separate category, and the pay curve there is where most principal SAs end up looking once they grow past the individual contributor ceiling.

The Naming Collision Nobody Warned You About

Before you write the job description, settle an internal question. Do you want a pre-sales solutions architect or a delivery solutions architect. The title is the same on both sides. The jobs are barely related.

A pre-sales SA works at a vendor or a consulting firm. Their seat is inside the sales team, usually next to an account executive who owns the commercial side. The SA owns technical credibility in the room. Most weeks it looks like this. Back-to-back video calls, a handful of proof-of-concept builds running in parallel, one or two onsite visits, and a quota that is usually attached to the AE but follows the SA around like a ghost. They are measured on deals closed. They travel. Some of them have a quota and a variable component to their comp. The strongest ones in my network are ex-consultants from the Big Four or former senior engineers who got tired of building and started enjoying the selling.

A delivery solutions architect works inside a customer organization or a services firm and owns the technical design of a specific program. The catch is that the program has already been sold by someone else. They inherit the commitments. They inherit the statement of work, which was written under optimistic assumptions, and the delivery calendar, which rarely has enough slack for the first real problem to surface. Then they have to ship it anyway. They are measured on delivery milestones, budget, and whether the architecture holds up once the traffic shows up. No quota. No commission. Usually more technically deep on the chosen stack, less polished in front of an executive audience. Many of them came up through senior engineering roles at the same company.

Both jobs are called solutions architect on LinkedIn. Both get posted with overlapping keyword salads. Pick one for the req and mean it. The JDs that hit our desk trying to straddle both jobs at one comp number are the ones that sit open for 90 days, get twenty bad shortlists, and end with the hiring manager calling us because the internal recruiter gave up.

Salary Ranges in 2026

Here is what we are seeing actually close in the last six months across West Coast and Texas markets. Remote US-based searches bottom out roughly 8 to 12 percent below onsite in a top-tier city and settle about halfway below San Francisco if we are pulling from secondary metros.

For the role breakdown and career path detail, we published the full solutions architect salary and career guide a few months back. Use that one if you are trying to understand the labor supply side of the picture. This post is for the hiring side.

Two cautions on those ranges. First, the AWS Certified Solutions Architect Professional cert carries a 10 to 15 percent premium in our placement data, not 30. Do not overpay for the paper. Second. Pre-sales variable comp is only real if the employer actually closes deals in the territory you are hiring for. Two senior pre-sales hires I placed walked away in year two because the OTE turned out to be marketing fiction. The pipeline in their assigned accounts was never going to hit the number on the offer letter and nobody had told them so on the way in. A $275K OTE that never pays out because the pipeline is empty is a $175K job with a broken promise attached.

Skills That Actually Predict Success

The cert and the cloud keyword list are the easiest part of the screen. The hard part is the translation layer. Nobody puts that on a rubric because translation is almost impossible to measure in a 45-minute interview with a stranger whose best stories are all under NDA and whose worst stories they are not going to tell you in the first round. The senior SAs in my network who keep getting hired share a specific cluster of behaviors that have nothing to do with which cloud they prefer.

• They explain architecture using whatever the audience understands. To an engineer, a diagram with boxes and arrows. To a CFO, a sentence about total cost of ownership over three years. Same architecture, two different translations, zero visible strain.
• They say no in a room full of people who want a yes. A real SA will tell a client that their requested architecture will not work, will explain why in 60 seconds, and will propose an alternative before the client has a chance to be offended. The ones who cannot say no become expensive yes-men in under a year.
• They write. Not novels. Architectural decision records, tradeoff memos, one-pagers that a busy executive can read in the elevator. If the candidate cannot point to three documents they wrote that influenced a real decision, they are not an architect yet.
• They recover from being wrong in public. Every SA I have placed who lasted past the three-year mark has a story about a time they defended the wrong approach in front of a client and had to walk it back. The ones who cannot tell that story are either early-career or lying.
• They know when the right answer is to buy something off the shelf. Not every problem wants a custom architecture. The SAs who reach for SaaS first have longer careers than the ones who build from scratch by reflex.

Notice what is not on that list. Specific certifications. Years of experience on a particular cloud. Having worked at a name-brand company. They help you sort a resume stack in the first fifteen minutes. They tell you almost nothing about whether the candidate can sit through a four-hour vendor negotiation, push back on a CFO about depreciation schedules, and still leave the room with a signed statement of work and a client who does not hate them. Which is most of the job in year one.

Interview Questions That Filter the Title Padders

Do not ask them to explain the CAP theorem. You are not hiring a database professor. Ask them to walk you through a real architectural decision they owned, what they got wrong, and how they found out. Then push.

The questions below work because they force the candidate into specifics. Vague answers self-identify as vague answers. Strong candidates will land on particular client situations, particular tradeoffs, particular numbers. Use two or three of these in a 60-minute panel. Do not machine-gun all eight.

1. Tell me about a time a stakeholder asked you for an architecture that would not have worked. What did you tell them, and what did you propose instead. I am looking for the language they used, not the technical details.
2. Walk me through a system you designed that is still running in production. Where does it feel uncomfortable now, two or three years later, and what would you change if you could.
3. You have thirty minutes with a CFO who is nervous about a $2 million cloud migration. What do you open with. What do you absolutely not say.
4. Think of an architecture you designed that turned out to be wrong once it was in production. How did you find out. What did you tell the team the morning after you figured it out.
5. Here is a one-paragraph client scenario. Sketch the high-level architecture at a whiteboard and talk us through your thinking. I will interrupt with objections and change requirements halfway through. I want to see how you adjust.
6. Which is harder, getting technical agreement from an engineering team or commercial agreement from a buyer. Why.
7. Show me a decision record or memo you wrote. I will read it silently and then ask you about it.
8. You have two finalist vendors for a critical component and the decision has to happen this week. The engineering team prefers vendor A. The security team prefers vendor B. You have no strong opinion. What do you do.

Question 7 is the one most candidates fail. They have not written a decision record. They describe one instead, usually in the past tense, often with a few details borrowed from a project they worked on two companies ago where they were not actually the person holding the pen. That is a soft signal worth taking seriously.

Direct Hire, Contract, or Fractional

Three paths to get a solutions architect onto your team. Each fits a different kind of problem.

Direct hire is right when the work is continuous, the architecture will evolve over two or more years, and the person needs standing in the organization to influence decisions outside their immediate project. Most in-house SAs should be direct hire. The fee is higher than a contract but the person is in the building, in the meetings, and on the hook.

A contract solutions architect is the right call when the work is program-shaped. A six-month migration. A specific platform rollout. An M&A integration with a hard deadline. Contract rates for senior SAs run $135 to $185 an hour on a corp-to-corp basis in 2026, which sounds like a lot and is usually cheaper than a botched full-time hire that has to be unwound.

Fractional SAs sit in between. An experienced architect working with your team two days a week on a retainer while you build out a permanent structure. I see this model most often at Series A and Series B companies that do not yet have the scale for a full-time architect but need senior design input on a specific set of decisions. Usually $18K to $35K a month depending on involvement. Not a line item we place a lot of, but worth knowing it exists.

Red Flags in Resumes and Interviews

Resume inflation is bad in this category. The word architect has become a title bump. A lot of what hits the pipeline is a senior engineer with one line on the resume changed. New skills section. Cloud acronyms. Bullet points dressed up in the language of architecture with none of the architectural work underneath them. Here is what I scan for.

• Every bullet point starts with the word “architected.” Real architects lead designs, run workshops, write memos, and review decisions. If every bullet is a past tense verb variant of architect, the candidate was coached or does not understand the range of the job.
• No meetings described. If the resume is a list of systems and technologies with no mention of stakeholders, committees, or clients, the person may have been a principal engineer wearing the title for comp reasons.
• A cert list longer than the experience section. The AWS Solutions Architect Professional, the Google Cloud Professional Architect, the Azure Solutions Expert, plus four more. I have hired great people with one cert and no great people with seven.
• Buzz word vomit on every line. Microservices, event-driven, cloud-native, zero trust, service mesh, observability, platform engineering. A real architect can tell you what any one of those means in the context of a specific system they built. The padders can only recite the list.

In the interview itself, listen for the second sentence. Junior candidates will give you a clean first answer and then trail off into generalities they picked up from a podcast. Senior candidates will give you a cautious first answer, pause long enough that you worry they have forgotten the question, and then sharpen the answer in the second sentence with a specific caveat, a real dollar amount, or a client situation that complicates the simple version they just told you. The sharpening is the signal.

How We Source Solutions Architects at KORE1

Short version. We keep a bench of around 1,400 vetted architects across the West Coast, Texas, and remote US. Every one of them has been through a screen for the translation skills in the section above, not just a keyword match against the job description. Most intake calls end with a shortlist of three or four people, not twenty. Our cloud infrastructure staffing practice handles the pre-sales and cloud-focused architects. Our general IT staffing team handles delivery-focused and on-premises work.

The searches that go well are the ones where the hiring manager walks us through a real scenario the architect will face in their first ninety days and we can interview candidates against that scenario rather than a keyword list. The searches that go poorly are the ones where the company wants us to find a mythical generalist who can do both the pre-sales road warrior job and the head-down delivery job at the same time for one salary. That person exists. We have placed about six of them since 2020. Every one of them started above $245K.

If your SA req has been open for more than 60 days and you are not sure why, talk to a recruiter on our team and we will give you a straight read on whether it is the comp, the JD, the interview panel, or the candidate pool, and whether the search is one we think we can help you close. Some searches we decline. That is in the guide for a reason.

Common Questions

So what exactly does a solutions architect do that a senior engineer does not

The solutions architect owns the design across multiple teams and has to defend it to non-technical stakeholders. A senior engineer owns the implementation of one part of it and rarely has to sell the approach outside their own group. Overlap exists. The difference shows up in who is in the room when the budget gets argued.

Realistically, how long does an SA search take

45 to 75 days for a clean direct-hire search with a clear scope and a reasonable budget. Closer to 100 days if the req is trying to serve two jobs at once or the comp is ten percent below market. Contract engagements can move in two to three weeks when the scope is tight.

Is the AWS or Azure certification actually worth paying a premium for

10 to 15 percent in our placement data, not 30. The cert signals effort and gives you a floor on cloud literacy. It does not predict whether the person can lead a client workshop or survive a tough executive review.

Do you actually need a dedicated solutions architect if you already have senior engineers

Depends on how much of the work touches people outside your engineering team. If most architecture decisions are internal and your seniors are comfortable writing them up for non-technical leaders, you probably do not. If the work crosses into client conversations, vendor selection, and board-level strategy, the SA pays for themselves by year two.

Pre-sales versus delivery, how do I know which one I actually need

Ask yourself whether the person will spend their first year in deal rooms or in design reviews. If deal rooms, pre-sales, and you should be comping with a variable component. If design reviews, delivery, and a flat base is cleaner. The worst outcome is hiring one and giving them the other job.

Can a senior engineer grow into this role internally

Sometimes. The ones who do well in the transition share two traits. They already enjoyed cross-functional meetings before the promotion, and they have written documents that influenced a decision. The ones who struggle are the engineers who took the promotion for the title and comp and find out six months later that the work is mostly meetings they did not want to go to.

How much travel should I plan for

Pre-sales, expect 30 to 60 percent in the first two years depending on the territory and the sales cycle. Delivery, closer to 10 percent, mostly for kickoff meetings and the occasional on-site during a tough integration.

What does a strong solutions architect resume actually look like

Three to five paragraphs describing programs they owned, not systems they touched. Two or three links to public writing, a talk, a published reference architecture, or an open-source contribution. A cert list kept short. One or two named clients or products. And no bullet point that starts with the word architected.