Role hub · live · updated 20 Nov 2026

Solutions engineer: the role, pay and who is hiring

A solutions engineer is the technical expert on a sales team: they understand the customer’s systems, design how the product fits, run demos and proofs of concept, and make the technical case for the deal. AI made the role bigger: every company selling AI needs engineers who can show it working on the customer’s own data.

Open roles
1,297
Companies hiring
540
Median posted pay
$150k to $200k
Remote
43%
Demand
up 1.7x in a year

This week · 20 Nov 202683 new Solutions engineer roles, most from Cisco, Kong and Backblaze.

01 · The role

What does a solutions engineer do

Half engineer, half advisor. A typical deal:

  1. DISCOVERY

    Learn the customer’s stack

    Join the first calls, map their systems, data and constraints, and find what would make them buy.

  2. DESIGN

    Shape the solution

    Design how the product fits: integrations, security, architecture diagrams, sizing.

  3. PROVE

    Run the proof of concept

    Build a demo or pilot on the customer’s data and get their engineers to sign off.

  4. HAND OFF

    Set up the win

    Answer security reviews, hand over to implementation, and feed product gaps back to the team.

Read the long version →

02 · Pay

Solutions engineer salary

Median posted pay on landed, next to the bands the biggest employers publish.

Median posted range, USD base

$150k to $200k

From 484 live postings that publish a range, before equity and bonus.

03 · The way in

How to become a solutions engineer

People come from software engineering, support engineering, consulting and IT. The way in:

  1. [x]
    Know one technical area wellCloud, data, security or developer tools. Teams hire for the domain they sell into.
  2. [x]
    Get comfortable in front of customersSupport, consulting or internal demos all count.
  3. [ ]
    Build demo-quality prototypes fastA working integration in a day beats a perfect one in a month.
  4. [ ]
    Learn how deals workDiscovery, champions, security reviews. Interviewers check you can talk about this.
  5. [ ]
    Apply the day roles openEarly applicants get read first. Full Solutions engineer roadmap →

04 · The roadmap

How to become an AI Solutions Architect: the roadmap

About 4–8 months, 7 stages, 7 core skills, aiming at $205k. The AI Solutions Architect in 2026 sits explicitly between the Solutions Engineer (deep technical, narrow) and the Account Executive (deep sales, narrow). It is a discover-then-scope role, not a draw-boxes role: the "Stop Drawing Boxes" piece (Jan 5 2026) reframes the whole job as trade-off acceptance in the face of business-unit budget, time, and risk, not encyclopedic knowledge or diagram beauty. The 2026 KPI is a shipped POC. And because 74% of B2B deals stall from internal conflict, an SA's real leverage is on stakeholder consensus as much as on architecture.

  1. Stage 0 · 0-3 months

    Cloud foundations

    AWS Solutions Architect Associate OR Azure Fundamentals + AI-900 OR GCP ACE + Gen AI Cloud Digital Leader, plus VPC, IAM, S3, KMS, and networking basics. Build a multi-account AWS Organization with cross-account roles and a sandbox org.

  2. Stage 1 · 3-5 months

    AI/ML foundations

    LLM basics, embeddings, RAG taxonomy, vector DBs (pgvector + Pinecone + Weaviate), and the classic ML lifecycle on your chosen cloud. Ship a working Bedrock + Claude RAG demo (or Azure OpenAI, or Vertex Gemini) with a Gradio UI.

  3. Stage 2 · 5-7 months

    Reference architectures

    Cloud Well-Architected for AI and the "10 RAG architectures in 2026" taxonomy (Standard, Multi-modal, GraphRAG, Agentic, Self-RAG, CRAG, Corrective, Modular, Real-time, Multi-source). Write up a reference architecture for an enterprise RAG system on your own blog.

  4. Stage 3 · 7-9 months

    Demo craft

    Streamlit, Gradio, Vercel AI SDK, and MCP servers to look futuristic. Build a live demo app that runs in production with an LLM, an agent, an MCP server, and a real use case.

  5. Stage 4 · 9-12 months

    Pre-sales craft

    Discovery, scoping, SOW authoring, and objection handling with cost/risk/timeline tradeoff scripts (74% of B2B deals stall from internal conflict). Produce a 4-page reference architecture doc for a pretend customer and a 30-minute Loom demo recording.

  6. Stage 5 · 12-14 months

    Governance + platform composition

    MCP (2026-07-28 RC), AI governance tooling, and the agent-platform landscape. Assemble an end-to-end SA portfolio site with demos plus writeups.

  7. Stage 6 · 14-18 months

    First hireable role

    Stay narrow on one cloud and a sweet-spot vertical (LLM apps + agents is the 2026 sweet spot). Apply to AI SA / Pre-Sales SA / Founding SA roles.

The full roadmap: projects, skills and what to learn at each stage

The roadmap, stage by stage

The realistic AWS AI Architect timeline runs about 9-14 months to beginner-to-junior-hireable, synthesized from HackerNoon's "How to Become an AWS AI Architect" (Jun 10 2026) and the Azure AI-102 path. It is deliberately longer than a plain AWS Solutions Architect Associate ramp because the AI/ML portfolio and demo-craft backgrounds have to be real, not paper.

Stage 0-1 buys you the price of admission: a cloud certification (AWS SAA, or Azure Fundamentals + AI-900, or GCP ACE + Gen AI Cloud Digital Leader) plus a working RAG demo on Bedrock, Azure OpenAI, or Vertex. Stage 2 is where an SA starts to differentiate from an engineer: you learn Well-Architected for AI and the ten 2026 RAG architectures, then publish a reference-architecture write-up under your own name. Stage 3-4 is the pivot to customer-facing craft: demo apps that run in production, then discovery, scoping, SOW authoring, and objection handling. Stage 5-6 layers on governance and MCP, then narrows you onto one cloud and one vertical.

The blunt nuance from HackerNoon: having just the cert, with no shipped demos, will not land a job. The four common entry paths are Cloud SA transitioning to AI SA (6-12 month ramp, most common), backend SWE going Founding SA at a startup (steeper, higher upside), pre-sales consultant from an SI like Accenture or Capgemini (strong consulting craft), and ML engineer moving customer-facing (deep knowledge, weak sales craft). The single most important skill you can train for free is discovery: pick three friends with businesses, run a one-hour mock discovery each, and write a one-page read-out.

The 2026 stack to learn deeply

Tier 1 is non-negotiable. Pick one cloud deeply: AWS (Bedrock, SageMaker, S3-Vectors, Q), Azure (Azure OpenAI, AI Foundry, Cosmos DB vector), or GCP (Vertex AI, Gemini); the Databricks Pre-Sales SA job explicitly accepts any of GCP/AWS/Azure/Databricks. Pick one LLM app framework from the seven the LangChain 2026 comparison ranks: LangChain + LangGraph, LlamaIndex Workflows, Microsoft Agent Framework, CrewAI, Google ADK, OpenAI Agents SDK, or Mastra. Learn one hosted plus one OSS vector DB (Pinecone + pgvector, Weaviate + pgvector, or Qdrant both ways), an eval/tracing stack (Langfuse, LangSmith, RAGAS, DeepEval), and Terraform. Crucially, the Databricks JD lists AI-assisted coding tooling as a must-have, so bring Cursor, Claude Code, or Copilot fluency.

Tier 2 is where you look like a 2026 SA rather than a 2023 one:

  • Demo platforms: Gradio, Streamlit, Vercel AI SDK, v0, and bolt.new or Lovable for prototype-then-prod; the 2026 Vercel AI Accelerator cohort ran 39 AI startups, so that network is high-leverage.
  • MCP: read the 2026-07-28 Release Candidate (stateless core + Extensions namespace) and write it up in your portfolio, because the supply of people who can build a competent MCP server is still tiny.
  • AI governance: Venn, OneTrust AI Governance, Credo AI, Protect AI, IBM watsonx.governance, so you can answer "what if a regulator audits this."
  • Agent platforms: LangSmith, Pydantic AI, Mastra, Vertex AI Agent Engine, Azure AI Foundry Agent Service, AWS Bedrock Agents; know at least one deeply.

Tier 3 is emerging: DSPy for prompt-as-code, FastMCP/MCP-Use/Composio scaffolding, and AI cost calculators (OpenRouter pricing, Helicone dashboards) so you can bring real numbers to every objection.

Portfolio projects that get you hired

An SA portfolio is judged on whether you can scope under uncertainty and defend an architecture in front of a security review, not on how pretty the boxes are. Build up the ladder, because the top rungs are what almost no candidate has.

Start with a "Brand RAG" (chat with a brand's docs on Streamlit/Gradio + pgvector) and a multi-page LangGraph agent with two or three custom tools and a LangSmith eval. Then write a Vertical Reference Architecture for a fictitious bank or hospital adopting an LLM, with a real diagram and a six-section write-up, and build a Multi-modal RAG POC using CLIP or ColPali embeddings into Weaviate with vision models: that proves you do 2026-grade RAG, not 2023 RAG.

The standout projects lean into the discover-then-scope reframing. First, a Customer-style Discovery-to-POC simulation: write a fake SOW for a fintech replacing a chat agent with a RAG over its knowledge base, including a cost estimate and a risk register, so you demonstrate Day-1 SA thinking. Second, a Production reference architecture with cost + risk + governance (Bedrock + Pinecone + Langfuse + IAM + CloudWatch alarms + WAF + cost dashboards, all in Terraform) that you could defend in an enterprise security review, which is the 2026 differentiator. The rarest of all: an MCP-server architecture write-up with three integrations (Slack, GitHub, internal docs) and a clear "what an agent could do with this" diagram, built on the 2026-07-28 RC. Two required decorations: a public site at your-name.com with 3-5 live demos and at least one 1500+ word architecture write-up, plus a sub-6-minute Loom or YouTube walk-through of you demoing.

How the role is evolving

Rising in 2026: agent platforms as a genuine category (Google's Agentic AI trends 2026 report is required reading, and the market is "no longer a clean leaderboard of chatbots with tool access"). MCP is becoming the de-facto tool-use protocol, and the 2026-07-28 RC is the version any SA should be able to speak to. AI governance and observability are now table stakes because SAs must answer the "what if a regulator audits this" question, and multi-agent reference architectures (Microsoft's Multi-Agent Reference Architecture repo, plus Microsoft Agent Framework in LangChain's ranking) are becoming standard deliverables. AI sovereignty and data-residency are shaping reference architectures, especially for EU customers.

Fading: the "watch me prompt" demo (SAs are graded on outcome, not snippet), big-box pre-sales decks (replaced by live demos), one-cloud lock-in (multi-cloud literacy is now baseline), and the AWS ML Specialty cert (retiring March 31 2026; swap to the forthcoming AWS AI Practitioner Specialty or Databricks ML Professional).

Where it heads over 12-24 months: an SA in 2027 may well be writing agent-and-MCP-server specifications rather than diagrams. As MCP becomes the agent tool-use lingua franca, specification authoring becomes the new diagram, and SAs who learned to write RFCs as well as boxes will own the next two cycles. Two non-obvious signals worth noting: the Databricks reorganization on June 11 2026 that launched a Forward Deployed Engineering org lives in the same field-engineering umbrella as its Pre-Sales SA role, hinting that SA and FDE are converging into "field engineer"; and many of the highest-quality 2026 SA postings, including the Databricks one, are EU-based rather than SF-based.

How to actually get hired

The 2026 AI SA interview, synthesized from Meta, Stripe, and AWS SA guides, runs roughly six stages: a hiring-manager phone screen on your story and portfolio; a customer-conversation simulation (often two interviewers, 45-60 min live); a system-design whiteboard (60 min); a Python or TypeScript coding round; a behavioral/Bar-Raiser round ("tell me about a failed POC"); and a soft skip-level.

The two rounds that actually decide it are the customer simulation and the whiteboard. In the simulation a scenario like "a VP of Customer Service wants to deploy a RAG agent, what do you ask first?" is testing discovery, scoping, and objection handling. The right answer is not "what model," it is: what is the success metric, what is the worst-case blast radius, what is the budget, what data do you have permission to use, and who is the buyer versus champion versus coach. On the whiteboard you are graded on trade-off acceptance, not diagram purity, so bring opinions.

What real 2026 postings screen for: the Databricks SA Pre-Sales Strategic Accounts role wants Python + SQL + Apache Spark, any of GCP/AWS/Azure/Databricks, and "adept skillset in use case discovery, scoping, and delivering complex solution architecture designs to multiple audiences"; Version1's Pre-Sales AI Architect wants you to shape and scope AI solutions and lead AI bid responses; Sopra Steria's role wants you to own technical solutions and promote AI offerings. To stand out: a live public demo site with at least four working apps, a write-up of a public RFP you would answer for a vertical, one MCP server in your portfolio, a Notion or Google Sheet of 2026 cloud-pricing math for a fake customer, and a HackerNoon or Medium cross-post of an architecture write-up. Discovery is the single most important skill, and you can rehearse it without anyone paying you.

Resources to learn from

Cert tracks

  • AWS Skill Builder + AWS SA Pro + AI Practitioner Specialty — Free Skill Builder plus paid pro track; AWS AI Practitioner Specialty rumored for late 2026 - confirm.
  • Azure AI Engineer Associate (AI-102) — $165 with AI-900 ($99) prerequisite; pair with Azure Solutions Architect Expert (AZ-305).
  • Google Cloud Digital Leader + Professional Cloud Architect — Add the new Gen-AI track.
  • Databricks Certified Machine Learning Professional — Recognized by the Databricks Pre-Sales SA job.

Courses

Books

Blogs & newsletters

Papers & docs

Communities worth joining

  • AWS Heroes (AI sub-category) — Direct line to AWS SAs and PMs; recommends ML, generative AI, and agentic solutions.
  • Microsoft MVPs - AI track — Community recognition track for Azure AI practitioners.
  • Google Developer Experts (GDE) - Cloud + AI/ML — The GCP + AI/ML expert community.
  • DeepLearning.AI community — Good for SA-focused Q&A.
  • LangChain / LlamaIndex / Anyscale Discords — One is mandatory for the OSS agent conversation.
  • r/MachineLearning + r/learnmachinelearning — Higher-traffic than r/mlops for SA use.
  • AI Engineer World's Fair 2026 — Jun 29 - Jul 2 2026 SF, Moscone; 29 tracks, 300 speakers, 6000+ attendees.
  • SaaStr AI 2026 Annual — May 12-14 2026 SF Bay Area; running 132% of last year.
  • AWS re:Invent 2026 — First week of December 2026 in Las Vegas (typical).
  • LangChain careers - Deployed / Customer Engineer — Deployed Engineer (Bay Area, on-site) and Customer Engineer (West Coast, remote) hybrid SA-style roles.

Sources

05 · The difference

Solutions engineer vs sales engineer vs forward deployed engineer

Neighbouring roles, split by when they engage and what they own.

Sales engineerForward deployed engineerSolutions engineer
EngagesDuring the saleAfter the sale, through deliveryBefore and during the sale, sometimes after
OwnsDemos and technical answersA system running in productionThe technical design and proof of concept
Pay structureOften base plus commissionBase plus equityBase plus variable, often 70/30 or 80/20
Writes production codeRarelyYesPrototypes and integrations

06 · The interview

The solutions engineer interview

Less algorithm practice, more showing you can explain and design.

  1. Technical screen

    APIs, networking, cloud, data, and the product’s own domain.

    Every loop
  2. Demo or presentation

    Present the product or a solution to a panel playing the customer.

    The core round
  3. Solution design

    Design how the product fits a customer’s architecture, on a whiteboard.

    Most loops
  4. Sales partnership

    A round with an account executive about how you work deals together.

    Often

07 · Hiring

Who is hiring solutions engineers

1,297 open roles at 540 companies, refreshed daily. Each links to the company's own page.

09 · Hiring now

Solutions engineer jobs

1,297 open today. The newest openings first, from the companies' own career pages.

Apply to solutions engineer roles the day they open.

landed watches every solutions engineer opening and applies within the hour, with answers written for each company. 10 free applications, no card.

Start applying free →

FAQ

Solutions engineer, answered

What is a solutions engineer?

A solutions engineer is the technical expert on a sales team: they understand the customer’s systems, design how the product fits, run demos and proofs of concept, and make the technical case for the deal.

How much does a solutions engineer earn?

Across 484 live Solutions engineer postings on landed that publish pay, the median range is $150k to $200k in USD base, before equity and bonus. Senior roles at AI labs post well above that.

Who is hiring solutions engineers?

landed tracks 1,297 live Solutions engineer roles at 540 companies. Cisco, SHI, F5, Verkada, SentinelOne, Databricks, Dash0 and Trend Micro have the most open right now.

Are Solutions engineer jobs remote?

43% of live Solutions engineer postings on landed are fully remote. Most of the rest are hybrid in the biggest tech cities.

Is a solutions engineer a sales job?

It sits in the sales team and is usually paid base plus a variable part tied to deals, but the work is technical: architecture, demos, proofs of concept and integrations.

What is the difference between a solutions engineer and a forward deployed engineer?

A solutions engineer mostly works before and during the sale, designing and proving the solution. A forward deployed engineer works after the sale, building and running the system in the customer’s production environment.