Solutions Architect Jobs

Solutions Architects design customer deployments and integrations on top of a platform — the architecture and integration side of deployed engineering, with less hands-on code than an FDE. The hiring is concentrated in enterprise data and infrastructure platforms, cloud vendors, and the AI labs now selling into large accounts. Every posting below is scored for coding intensity and travel, so you can tell a design-and-review role from a build role before you apply.

7 verified roles

What a Solutions Architect actually does

A Solutions Architect owns the shape of a deployment: how a platform will fit the customer's existing systems, what has to be built to bridge the gap, and which of the customer's constraints are real. The output is usually a design and a plan that other people — the customer's engineers, an implementation team, sometimes an FDE — will build against.

The role sits closer to the account than product engineering does and closer to the architecture than pre-sales does. It is common for a Solutions Architect to be involved before the contract is signed and to stay through the first production deployment, which is what separates it from a purely pre-sales title.

Seniority varies more here than in the other four titles. The same words cover a first architecture role and a principal position advising an enterprise's platform strategy, so read the posting rather than the title.

Day to day

  • Mapping a customer's existing stack and deciding where the platform fits
  • Writing reference architectures, integration designs, and migration plans
  • Running technical workshops with a customer's engineering and data teams
  • Prototyping enough to prove a design works before a team commits to it
  • Reviewing what was built against what was designed, and unblocking it

What hiring teams screen for

  • Cloud architecture (AWS, GCP, Azure)
  • Data modelling and pipelines
  • API and integration design
  • Security, networking, and identity basics
  • SQL
  • Python or another scripting language
  • Technical writing and diagramming
  • Stakeholder management across engineering and business

Common questions

How much do Solutions Architects actually code?
Less than an FDE and more than a pre-sales engineer, but the spread is wide. Some postings are design-and-review only; others expect working prototypes. Every posting here is scored for coding intensity, so you can filter rather than guess from the title.
Is this a pre-sales or a post-sales role?
Often both, and the posting usually says which side dominates. Where it is purely pre-sales with a quota attached, it tends to be titled Solutions Engineer or Sales Engineer instead.
Does it require travel?
Frequently, though far less than it once did. Travel expectations are extracted from each posting and shown as a band on the job page, so you can filter to the roles that match what you want.

Related roles