Forward deployed engineer vs solutions architect

By FDE Interview Prep, a SourceStrongAI company

On this page12 sections

1. The short answer
2. The two roles side by side
3. Same company, both roles
4. Titles that sit in between
5. The post-sale myth
6. How the interviews differ
7. Moving from SA to FDE
8. Which role should you apply for?
9. Read further: four narrower questions
10. Your next step
11. Questions people ask
12. Keep reading

Anthropic hires for both jobs. Its forward deployed engineer posting says “build production applications”; its Applied AI Architect posting says “near-production examples that customers can extend”. ^{[1, 2]}Source 1Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job postingSource 2Job Application for Applied AI Architect, Commercial at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting Those two phrases, not the titles, tell you which job you would be doing on a Tuesday afternoon. Around phrases like those, postings for the two roles can read alike: customers, discovery, architecture, travel. If you are holding two postings like these, or wondering whether FDE is a real step up from solutions architect, this guide is for you.

Here is the plain answer. A forward deployed engineer (FDE) writes production code that runs with or inside one customer’s systems, and answers for it after launch. A solutions architect (SA) shapes the solution, proves it with prototypes and proofs of concept, and guides others to build and run it, usually from a sales, go-to-market or field organization. The rest of this guide shows you how to tell the two apart from the posting itself, using employers’ own words, then how the interviews differ and how to move from SA to FDE. If you want the drill version first, the free lesson telling FDE apart from its neighbors runs the same tests on a different set of posting lines.

The short answer

• The FDE builds and ships. OpenAI’s San Francisco FDE posting says “You will own discovery, technical scoping, system design, build, and production rollout”, and asks for people who “write and review production-grade code”. ^[3]Source 3Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job posting Google Cloud’s GenAI FDE postings set the role against “traditional advisory roles”: the FDE codes, debugs and jointly ships agentic solutions inside the customer’s environment. ^[4]Source 4Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting
• The SA scopes, proves and advises. Baseten’s Solutions Architect posting asks for “technical depth to scope solutions, without needing to write production code”, and says the SA pulls in the FDE team when deeper technical work is needed. ^[5]Source 5Solutions Architect @ BasetenPublisherBaseten (Ashby)Source typecompany job posting
• The same contrast, in one company. The Pragmatic Engineer reported, in August 2025, that OpenAI’s FDEs write code directly on customer infrastructure using customer tooling, while its solutions architects are more advisory. ^[6]Source 6What are Forward Deployed Engineers, and why are they so in demand? (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report

Discovery, design and customer trust belong to both roles. What differs is who writes the code that ends up running.

The title is the weakest evidence on the page. Some FDE postings carry pre-sales duties, and some architect postings ship real code. The sections below give you the lines that decide it.

The two roles side by side

Read this table as “what to check in the posting”, not as a rule for every employer. The evidence for each row follows it.

In one sentence: the FDE writes and answers for production code for one customer or a few, and the SA proves and advises across many, usually from a sales or field unit; the department, the pay line and the interview tend to follow from that, though not at every employer.

The code

FDE postings describe code that ships and keeps running. Anthropic’s FDE posting asks the FDE to “work within customer systems to build production applications with Claude models”. ^[1]Source 1Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting Cursor’s FDE postings put it bluntly: “This is not a demo role. You are responsible for systems that work in the real world.” ^[7]Source 7Forward Deployed EngineerPublisherCursor (Ashby job board)Source typecompany job board

Architects write code too, but a different kind. Anthropic’s Applied AI Architect posting says “Ship working code”, then defines it: prototypes, proofs of concept, eval frameworks and “near-production examples that customers can extend”. ^[2]Source 2Job Application for Applied AI Architect, Commercial at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting Code the customer extends is code the customer owns. The Pragmatic Engineer, describing OpenAI, wrote that its SAs rarely write code on customers’ infrastructure and usually build MVPs or proofs of concept on anonymized or offline cuts of data. ^[6]Source 6What are Forward Deployed Engineers, and why are they so in demand? (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report

Here is what that difference looks like in code. Both versions below pull support tickets from a paginated API.

SA: proves the API can answer. This is the proof of concept, and it is the right thing to write in a pre-sales week.

import requests

URL = "https://api.example.com/v1/tickets"
params = {"limit": 100}
tickets = []
while True:
    page = requests.get(URL, params=params).json()
    tickets += page["data"]
    if not page["next_cursor"]:
        break
    params["cursor"] = page["next_cursor"]
print(len(tickets), "tickets")

It works on a quiet afternoon. On the first 429 or 503 it dies, a rerun starts again from page one, and nothing is saved anywhere.

FDE: proves it keeps answering. First, one request with retries: back off on 429 and 5xx, honor Retry-After when the API sends it in seconds, add jitter, and fail loudly on any other error.

import json, random, sqlite3, time, requests

URL = "https://api.example.com/v1/tickets"

def get(params, tries=6):
    for n in range(tries):
        r = requests.get(URL, params=params, timeout=10)
        if r.status_code != 429 and r.status_code < 500:
            r.raise_for_status()  # other 4xx: fail loudly
            return r.json()
        wait = r.headers.get("Retry-After", "")
        wait = int(wait) if wait.isdigit() else min(2 ** n, 30)
        time.sleep(wait + random.random())  # jitter
    raise RuntimeError(f"gave up after {tries} tries: {params}")

Then the sync itself. Each page’s rows and the cursor after them commit in one transaction, and the insert is an upsert keyed on the ticket id, so a crashed run resumes from the last saved page and a replay changes nothing. Every page writes one structured log line.

db = sqlite3.connect("sync.db")
db.execute("CREATE TABLE IF NOT EXISTS tickets"
           " (id TEXT PRIMARY KEY, body TEXT)")
db.execute("CREATE TABLE IF NOT EXISTS checkpoint"
           " (k TEXT PRIMARY KEY, cursor TEXT)")
row = db.execute("SELECT cursor FROM checkpoint").fetchone()
cursor = row[0] if row else None
while True:
    page = get({"limit": 100} | ({"cursor": cursor} if cursor else {}))
    cursor = page["next_cursor"]
    with db:  # rows and cursor commit together, or not at all
        db.executemany(
            "INSERT INTO tickets VALUES (?, ?) ON CONFLICT(id)"
            " DO UPDATE SET body = excluded.body",
            [(t["id"], json.dumps(t)) for t in page["data"]])
        db.execute("INSERT OR REPLACE INTO checkpoint"
                   " VALUES ('tickets', ?)", (cursor,))
    print(json.dumps({"event": "page_synced",
                      "rows": len(page["data"]), "cursor": cursor}))
    if not cursor:
        break  # done: the next run starts a fresh pass

We ran both against a fake API that returns a 429 or a 503 every few calls. The proof of concept died on its third request. The production version finished; killed halfway, it resumed from its saved cursor, and a second full run left the row count unchanged. The sentence to say aloud in an interview is: “My proof of concept showed it could work; the production version is the one I was paged for.” The flaky API integration question asks you to build exactly this under interview conditions.

Something else separates the two: what flows back into the product. The Pragmatic Engineer wrote, in August 2025, that Solutions Architect is among the roles closest to FDE, and that the difference comes down to FDEs also contributing to the product their company sells. ^[6]Source 6What are Forward Deployed Engineers, and why are they so in demand? (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report Baseten’s FDE manager posting says its FDEs “contribute to the core Baseten codebase” and “drive large portions of our feature roadmap”. ^[8]Source 8Engineering Manager, Forward Deployed Engineering (LLM) @ BasetenPublisherBaseten (Ashby)Source typecompany job posting An SA who sees the same gap at several accounts can write it up for the product team; at an employer like Baseten, an FDE can be the one who builds it once. If you are asked how you decide between a custom build and a product change, an SA background gives you the start of a strong answer: “At my last company I saw the same connector gap at several accounts and wrote it up for product. As an FDE I want to be the one who builds it once, for everyone.”

After launch

This row is easy to skim past, and it decides the most. OpenAI’s financial-services FDE posting asks the FDE to own “integrations, data flows, reliability, observability, and on-call readiness” for the production AI systems it ships. ^[9]Source 9Forward Deployed Engineer (FDE), Financial Services- NYCPublisherOpenAI (Ashby)Source typecompany job posting That is a running system with your name on it.

Staying with an account after the sale is not the same as writing the fix. Databricks’ Delivery Solutions Architect becomes the post-sale technical lead and leads the technical account strategy after the technical win. ^[10]Source 10Delivery Solutions ArchitectPublisherDatabricks (Greenhouse)Source typecompany job posting As of September 2026, the posting does make the DSA the first contact for technical issues on the production or go-live status of agreed use cases, and has it plan how use cases move from “win” to production, coordinating with Professional Services on delivering its engagement proposals. ^[10]Source 10Delivery Solutions ArchitectPublisherDatabricks (Greenhouse)Source typecompany job posting It asks for programming experience in Python and Spark, but the duties we hold describe planning and coordinating, not building. ^[10]Source 10Delivery Solutions ArchitectPublisherDatabricks (Greenhouse)Source typecompany job posting Being first contact for a running system is not the same as writing its fix. Even an FDE engagement can end: AWS says its FDE model is designed so customers are self-sufficient when a deployment ends. ^[11]Source 11AWS invests $1 billion to embed AI forward deployed engineers with customersPublisherAbout AmazonSource typecompany blog The difference is what you own while you are there.

How many customers

The second thing that separates the roles is depth against breadth. An FDE goes deep on one customer, or a few; an architect covers many. The AWS Sr FDE “embeds directly inside a strategic enterprise customer”. ^[12]Source 12Sr Forward Deployed Engineer, AWS Forward Deployed Engineering - Job ID: 10517491PublisherAmazon.jobsSource typecompany job posting Palantir describes its FDEs’ focus as “one customer, many capabilities”. ^{[13, 14]}Source 13Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 14A Day in the Life of a Palantir Forward Deployed Software EngineerPublisherPalantir BlogSource typecompany blog OpenAI’s Applied AI Architect, by contrast, is the technical owner for a named portfolio of customers. ^[15]Source 15Applied AI ArchitectPublisherOpenAI (Ashby)Source typecompany job posting

Colin Jarvis, who leads forward deployed engineering at OpenAI, said on a South Park Commons panel in May 2026 that OpenAI’s FDE unit works only about 10 engagements at a time and has to say no more often than yes, and he described solutions architecture as the post-sales “scale motion” for the wider market. ^[16]Source 16The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview

That is the honest answer to “is FDE a step up?”: it is a different bet, not a higher rung. The SA’s leverage is breadth: many accounts moving at once. The FDE’s leverage is depth: one system that has to work. Choose the kind of leverage you want.

Where it sits

The department or team field on a posting often says more than the title. OpenAI’s board puts its San Francisco FDE posting in a “Forward Deployed Engineering” department and most Applied AI Architect postings in “Go To Market”. ^{[3, 15]}Source 3Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job postingSource 15Applied AI ArchitectPublisherOpenAI (Ashby)Source typecompany job posting An AWS Solutions Architect posting sits within AWS Global Sales. ^[17]Source 17Solutions Architect, Enterprise GreenfieldPublisherAmazon (amazon.jobs)Source typecompany job posting Vercel’s Solutions Architect sits in Field Engineering. ^[18]Source 18Solutions ArchitectPublisherVercel (Greenhouse)Source typecompany job posting

The field is evidence, not proof. Palantir’s careers page puts its Forward Deployed Software Engineers (“Deltas”) in its Business Development organization, unlike its Software Engineers (“Devs”) in Product Development. ^[19]Source 19Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring page Notion’s Forward Deployed Engineer, GTM, AMER posting sits in the Sales department. ^[20]Source 20Forward Deployed Engineer, GTM, AMER @ NotionPublisherNotion (Ashby job board)Source typecompany job posting Both are FDE roles by their duties: Palantir gives its Deltas a mandate to achieve technical and operational outcomes for customers, and Notion’s FDE leads hands-on technical delivery of its most complex customer engagements. ^{[19, 20, 21]}Source 19Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring pageSource 20Forward Deployed Engineer, GTM, AMER @ NotionPublisherNotion (Ashby job board)Source typecompany job postingSource 21Forward Deployed Engineer @ NotionPublisherNotion (Ashby job board)Source typecompany job posting When the field and the duties disagree, trust the duties and ask the hiring manager who they report to.

Palantir also shows that the role closest to an architect is not always called one. There, the role that builds demos and scopes new engagements is the Deployment Strategist, who works with FDEs to integrate customer data. ^[22]Source 22Palantir Technologies - Deployment StrategistPublisherPalantir Technologies (Lever)Source typecompany job posting Deployment strategist vs FDE covers that pair, and FDE vs software engineer covers Palantir’s Devs and Deltas.

The pay line

Pay structure varies by employer, whatever the title. On the SA side, the AWS Solutions Architect posting asks the architect to work with the sales team on a strategy “to exceed revenue objectives”. ^[17]Source 17Solutions Architect, Enterprise GreenfieldPublisherAmazon (amazon.jobs)Source typecompany job posting Vercel states its Solutions Architect pay as an on-target earnings range. ^[18]Source 18Solutions ArchitectPublisherVercel (Greenhouse)Source typecompany job posting Elastic’s Partner Solutions Architect posting spells out the split: on-target earnings on a 70/30 mix of base salary to target variable. ^[23]Source 23Partner Solutions ArchitectPublisherElastic (Greenhouse)Source typecompany website The variable part depends on a target, so ask what that target is.

On-target earnings (OTE) on an FDE title is not proof of a sales job. Okta states its Principal FDE pay as OTE “inclusive of base salary and incentive compensation”, and the same posting says “You still write code.” ^[24]Source 24Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOkta (Greenhouse)Source typecompany job posting Baseten, for its part, says in an FDE manager posting that “FDE at Baseten is not a sales function”. ^[8]Source 8Engineering Manager, Forward Deployed Engineering (LLM) @ BasetenPublisherBaseten (Ashby)Source typecompany job posting

The fairest pay comparison is one employer posting both titles. Baseten and Modal both do, with pay attached, and they give different answers. As of September 2026, Baseten’s Forward Deployed Engineer posting shows “$165K – $330K • Offers Equity”, recorded as salary. ^[25]Source 25Forward Deployed Engineer postingPublisherBaseten (Ashby job board)Source typecompany job posting Its Solutions Architect posting, in the go-to-market department, shows the same range and the same equity line; our record of it does not say whether that range is base or total. ^[5]Source 5Solutions Architect @ BasetenPublisherBaseten (Ashby)Source typecompany job posting The FDE posting sits in a department Baseten calls “EPD”. ^[25]Source 25Forward Deployed Engineer postingPublisherBaseten (Ashby job board)Source typecompany job posting So at Baseten, posted pay does not separate the roles; the department and the code do. Modal’s bands differ: as of September 2026, its Solutions Architect posting shows $200K–$280K plus equity, without saying whether that is base or total, and asks for 5+ years in solutions or sales engineering, while its Forward Deployed Engineer - ML posting lists a salary of $180K–$250K plus equity. ^{[26, 27]}Source 26Solutions Architect @ ModalPublisherModal (Ashby)Source typecompany job postingSource 27Forward Deployed Engineer - ML @ ModalPublisherModal (Ashby)Source typecompany job posting The SA band is higher on paper, but it may include variable pay, and the two postings may not be pitched at the same level. Two employers, two answers: posted pay does not tell you which role pays more in general.

For posted bands and filings at other companies, read the FDE salary guide.

Travel

Travel is stated per posting, and the ranges overlap. As of September 2026, on the FDE side, OpenAI’s San Francisco posting requires travel of up to 50%, and Anthropic’s estimates 25%. ^{[1, 3]}Source 1Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job postingSource 3Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job posting On the SA side, the AWS Solutions Architect posting expects 15–20%, and Modal’s Solutions Architect posting asks for willingness to travel up to 30%. ^{[17, 26]}Source 17Solutions Architect, Enterprise GreenfieldPublisherAmazon (amazon.jobs)Source typecompany job postingSource 26Solutions Architect @ ModalPublisherModal (Ashby)Source typecompany job posting An architect posting can ask for more travel than an FDE posting, so in these postings travel does not separate the roles. Read the line, and the travel lesson shows what to ask before the recruiter call.

Try it on five real lines

Here are five lines from real postings. Before you read the answers, say for each one: FDE, SA, or neither? If you are listening, pause here.

1. “This is not a demo role. You are responsible for systems that work in the real world.”
2. “This role is not demo support.”
3. “Unlike traditional advisory roles,” you will “code, debug, and jointly ship” solutions “directly within the customer’s environment”.
4. “You still write code”, on a posting that states its pay as on-target earnings.
5. “A product-focused, quota-carrying technical sales role.”

The answers, and the words that decide them:

1. FDE. Cursor’s FDE postings. ^[7]Source 7Forward Deployed EngineerPublisherCursor (Ashby job board)Source typecompany job board The second sentence decides it, not “not a demo”: “responsible for systems that work in the real world” is a running system the role answers for.
2. SA, and this is the trap. Modal’s Solutions Architect posting says it, then calls itself “a strategic, consultative position”. ^[26]Source 26Solutions Architect @ ModalPublisherModal (Ashby)Source typecompany job posting If the first line taught you that “not a demo” means FDE, the second shows why it doesn’t: a keyword can rule a role out, but it rarely rules one in. Read the next sentence.
3. FDE. Google Cloud’s GenAI FDE postings. ^[4]Source 4Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting The line names the role it is not (“advisory”) and the verbs it is: code, debug, ship, inside the customer’s environment.
4. FDE. Okta’s Principal FDE. ^[24]Source 24Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOkta (Greenhouse)Source typecompany job posting The pay line looks like sales, but “you still write code” is the duty, and duties beat the pay line.
5. Neither: closer to sales than to either. Ramp’s AI Solutions Engineer is a quota-carrying technical sales role, not a forward deployed engineering one. ^[28]Source 28Ramp Ashby job board (AI Solutions Engineer)PublisherRamp (Ashby job board)Source typecompany job posting “Quota-carrying” is the deciding word, and near-miss titles like this one are why you read past the title.

If you got all five, you have the method: find the duty that decides it, read the sentence after any slogan, and let the duty outrank the title and the pay line. Telling FDE apart from its neighbors has another set to practice on, with a trap of its own.

Same company, both roles

The cleanest comparison is one employer that posts both jobs, because the words are chosen by the same people. Here are five.

OpenAI: FDE vs applied AI architect

This is the pair behind the search “applied AI architect vs FDE”. The FDE, quoted above, owns the work through build and production rollout. ^[3]Source 3Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job posting The Applied AI Architect is the technical owner for a named portfolio of customers, guiding them from pre-sales discovery through deployment, and the posting splits the work: “The Account Director owns commercial strategy; you own the technical strategy, customer journey, and path to production value.” ^[15]Source 15Applied AI ArchitectPublisherOpenAI (Ashby)Source typecompany job posting

So the architect owns the technical plan across several accounts; the FDE owns building and rolling out the system. OpenAI’s Applied AI Engineer sits between them: it works hands-on in code to build prototypes, evaluation harnesses, reference implementations, integrations and production accelerators. ^[29]Source 29Applied AI EngineerPublisherOpenAI (Ashby)Source typecompany job posting On the South Park Commons panel, Colin Jarvis put OpenAI’s FDE unit apart from solutions engineering, which he called pre-sales, and solutions architecture, which he called post-sales, and tied both to the “scale motion” for the wider market. ^[16]Source 16The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview At OpenAI, FDE is its own unit, not a flavor of architecture.

Anthropic: FDE vs applied AI architect

Anthropic’s FDE, quoted above, builds production applications. ^[1]Source 1Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting Its Applied AI Architect (Commercial) is “a Pre-Sales architect” who partners with account executives. ^[2]Source 2Job Application for Applied AI Architect, Commercial at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting Its Applied AI Engineer (Enterprise Tech) is a technical advisor who builds customized pilots. ^[30]Source 30Job Application for Applied AI Engineer, Enterprise Tech at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting The dividing words are “production applications” against “prototypes” and “pilots”.

Baseten: the SA calls in the FDE

Baseten’s Solutions Architect sits in its go-to-market department and pulls in Forward Deployed Engineering “when deeper or more complex technical work is needed”. ^[5]Source 5Solutions Architect @ BasetenPublisherBaseten (Ashby)Source typecompany job posting Its FDE posting, in the “EPD” department, describes “an engineering role with hands-on coding and software development” that also includes aspects of product management, technical customer success and pre-sales solution engineering. ^[25]Source 25Forward Deployed Engineer postingPublisherBaseten (Ashby job board)Source typecompany job posting The FDE does some pre-sales work; the SA is not expected to write production code. As the pay section showed, the two postings show the same pay range, so the difference is the work, not the money.

Databricks: the post-sale architect and the billable builder

Databricks’ Delivery Solutions Architect is “a hybrid technical and commercial role” that becomes the post-sale technical lead and reports into the Field Engineering organization. ^[10]Source 10Delivery Solutions ArchitectPublisherDatabricks (Greenhouse)Source typecompany job posting It is the first contact for go-live issues and plans how use cases reach production, coordinating with Professional Services on delivering its engagement proposals. ^[10]Source 10Delivery Solutions ArchitectPublisherDatabricks (Greenhouse)Source typecompany job posting Its FDE postings describe billable, customer-facing builders who “own the architecture, lead design decisions, and implement end-to-end systems”. ^[31]Source 31Sr. Forward Deployed Engineer (FDE) - Financial Services (New York City)PublisherDatabricks (careers site / Greenhouse)Source typecompany job posting The DSA coordinates delivery; the FDE is the delivery.

AWS: a sales architect and an embedded builder

The AWS Solutions Architect, as above, sits in Global Sales. ^[17]Source 17Solutions Architect, Enterprise GreenfieldPublisherAmazon (amazon.jobs)Source typecompany job posting The AWS Sr FDE “embeds directly inside a strategic enterprise customer” to build and run production systems. ^[12]Source 12Sr Forward Deployed Engineer, AWS Forward Deployed Engineering - Job ID: 10517491PublisherAmazon.jobsSource typecompany job posting What AWS adds is a line that draws the boundary itself, in its Senior FDE Manager posting: “This is not a Solutions Architect management role and not a consulting engagement manager role.” ^{[32, 33]}Source 32Forward Deployed Engineering Manager, AWS Forward Deployed Engineering - Job ID: 10517532PublisherAmazon.jobsSource typecompany job postingSource 33Senior Forward Deployed Engineering Manager, AWS Forward Deployed Engineering - Job ID: 10475967PublisherAmazon.jobsSource typecompany job posting

Titles that sit in between

Hybrid titles are where the confusion comes from. Run the same who-writes-the-fix test on each.

• Forward deployed architect. Notion’s Forward Deployed Architect sits on its Services team and partners with Forward Deployed Engineering “when deeper engineering support is required”. ^[34]Source 34Forward Deployed Architect @ NotionPublisherNotion (Ashby job board)Source typecompany job posting MongoDB’s Forward Deployed Architect acts as the technical escalation point for its FDEs. ^{[35, 36]}Source 35Forward Deployed Architect, Industry SolutionsPublisherMongoDB CareersSource typecompany job postingSource 36Forward Deployed Architect, Industry SolutionsPublisherMongoDB (Greenhouse job board)Source typecompany job posting Same “forward deployed” prefix, different job at each company: one hands deep engineering to FDEs, the other backs them up.
• Delivery or resident solutions architect. Post-sale architect roles, like Databricks’ Delivery Solutions Architect above, sit closest to FDE work in their duties. Databricks resident solutions architect vs FDE looks at one candidate’s report that the title was being folded into FDE.
• Partner or deployment engineer in go-to-market. OpenAI’s Partner AI Deployment Engineer works across pre- and post-sales and builds prototypes, POCs and reference implementations, from its Go To Market department. ^[37]Source 37Partner AI Deployment Engineer - AWSPublisherOpenAI (Ashby)Source typecompany job posting “Deployment” in the title, SA work in the duties.
• Solutions architect on an FDE-style team. In Japan, Snowflake posts a Solutions Architect role on “Snowflake Frontier Engineering”, which the posting describes as Snowflake’s implementation and strategy organization. ^[38]Source 38Solutions Architect, Frontier Engineering @ SnowflakePublisherSnowflake (Ashby job board)Source typecompany job posting The team name says implementation; the duties, not the title, say whether it ships production code.

Some observers think the FDE label itself gets stretched. Andreessen Horowitz’s Joe Schmidt wrote, in June 2025, that at complex AI application companies the implementation role is often filled by a professional services employee, sometimes rebranded as a forward deployed engineer or an implementation or solutions specialist. ^[39]Source 39Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in StartupsPublisherAndreessen HorowitzSource typeindependent analysis Industry writer Thomas Otter wrote, in December 2025, that he suspects a lot of jobs labeled FDE are implementation or pre-sales roles with a cooler label. ^[40]Source 40on the forward deployed engineerPublisherThomas Otter (Substack)Source typeindustry writer’s personal blog That is his suspicion, not a finding, but it is a good reason to read duties before titles.

One Hacker News commenter who said they lead a team of FDEs at a database company wrote, in July 2026, that their engineers do “basically devops, software engineering + some more traditional solution architecting”, and that “their purpose is not to make sales demos”. ^[41]Source 41Hacker News comment by stingraycharles on 'What are Forward Deployed Engineers, and why are they so in demand? (2025)'PublisherHacker NewsSource typecandidate comment on Hacker News An FDE does some architecting; the test is whether architecting is all the role does.

The post-sale myth

You will read that FDEs work only after the contract is signed, and solutions architects only before it. The recruiting platform Paraform, for example, describes the FDE as picking up where the solutions engineer left off, and cites no source for that handoff. ^[42]Source 42Forward-Deployed Engineer vs. Solutions Engineer vs. Customer EngineerPublisherParaformSource typerecruiting platform Employers’ own postings do not support a clean split.

FDEs working before the sale. OpenAI’s financial-services FDE posting asks the FDE to “lead discovery and scoping from pre-sales through post-production”. ^[9]Source 9Forward Deployed Engineer (FDE), Financial Services- NYCPublisherOpenAI (Ashby)Source typecompany job posting As of September 2026, Anthropic was hiring its first Pre-Sales Program Lead for Forward Deployed Engineering, to take the FDE team “from opportunity to a signed contract”, beside a post-sale counterpart who owns delivery from signature onward. ^[43]Source 43Pre-Sales Program Lead, Forward Deployed EngineeringPublisherAnthropic (Greenhouse)Source typecompany job posting Ramp’s engineering blog says its FDE team works with customers “from when they are prospects in the sales funnel, to implementation and rollout, to long-tail support”. ^[44]Source 44Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog LangChain’s Deployed Engineering team covers work “from pre-sales evaluations to post-deployment advisory work”. ^[45]Source 45Deployed Engineer (UK) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting The Pragmatic Engineer reported that many startups employing FDEs use them to help win customers. ^[6]Source 6What are Forward Deployed Engineers, and why are they so in demand? (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report

Architects working after the sale. OpenAI’s own FDE lead, Colin Jarvis, called solutions architecture the post-sales “scale motion” in May 2026, and put the FDE unit apart from it. ^[16]Source 16The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview Anthropic’s Applied AI Architect is explicitly pre-sales. ^[2]Source 2Job Application for Applied AI Architect, Commercial at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting But Vercel’s Solutions Architect spans “both technical pre-sales and post-sales”, and Databricks’ Delivery Solutions Architect is the post-sale technical lead. ^{[10, 18]}Source 10Delivery Solutions ArchitectPublisherDatabricks (Greenhouse)Source typecompany job postingSource 18Solutions ArchitectPublisherVercel (Greenhouse)Source typecompany job posting

So “before or after the sale?” does not separate the roles. Ask a better question: what does this role own after the signature, the revenue, the plan or the running system? Revenue is sales. The plan is architecture. The running system is FDE work.

How the interviews differ

No employer in our research publishes an FDE loop and a solutions architect loop side by side, so treat this section as what employers say about each, plus our reading of what that means for your prep.

FDE loops carry an engineering bar. Palantir’s careers site says its engineering interview process varies by whether you are going for Forward-Deployed Software Engineer or Software Engineer. ^[19]Source 19Palantir Careers | Students and Early TalentPublisherPalantir TechnologiesSource typecompany hiring page Its students and early-talent timeline, which does not say which of the two roles it covers, starts with a HackerRank coding challenge and includes a virtual onsite of a learning interview and a decomposition interview, before a hiring manager interview. ^[46]Source 46Students | Palantir Careers (timeline image: RecruitingTimeline_V3.jpg)PublisherPalantirSource typecompany hiring page Leo Mehr, Ramp’s Director of Engineering, said in a June 2026 dearCC interview that FDE candidates at Ramp face the same technical bar and must pass the software engineering interview loop. ^[47]Source 47What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interview Ramp’s engineering blog lists what it checks: coding, debugging, data structures and system design. ^[44]Source 44Forward Deployed EngineeringPublisherRamp Builders (engineering blog)Source typecompany blog The decomposition interview guide walks through that round step by step.

Architect loops can include coding too. Databricks has published a Solutions Architect interview guide: a PDF on databricks.com titled “Field Engineering Careers Site Interview Prep April 2025” and headed “Solutions Architect”. ^{[48, 49]}Source 48Field Engineering Careers Site Interview Prep April 2025 (PDF)PublisherDatabricksSource typecompany hiring pageSource 49Interviewing at DatabricksPublisherDatabricksSource typecompany hiring page It lists eight steps: a recruiter screen, a hiring manager interview, a technical screen, a coding assignment, a full panel of 2–3 interviews, a presentation, references and an offer. ^{[48, 49]}Source 48Field Engineering Careers Site Interview Prep April 2025 (PDF)PublisherDatabricksSource typecompany hiring pageSource 49Interviewing at DatabricksPublisherDatabricksSource typecompany hiring page The coding assignment covers “problem-solving, feature implementations, data frame operations (Python or Scala)”, and in the presentation “You’ll act as a Solutions Architect”, asking about customer needs and then “pitching Databricks’ value proposition”. ^{[48, 49]}Source 48Field Engineering Careers Site Interview Prep April 2025 (PDF)PublisherDatabricksSource typecompany hiring pageSource 49Interviewing at DatabricksPublisherDatabricksSource typecompany hiring page When we read Databricks’ interview-prep page in September 2026, its Field Engineering tile had no link, so treat the PDF as a guide Databricks published, not a promise of today’s loop. ^{[48, 49]}Source 48Field Engineering Careers Site Interview Prep April 2025 (PDF)PublisherDatabricksSource typecompany hiring pageSource 49Interviewing at DatabricksPublisherDatabricksSource typecompany hiring page The lesson is in the presentation: this SA loop has a coding assignment, but its last interview is a pitch, not a production build.

A second published example is Databricks’ Delivery Solutions Architect posting in Tokyo, a different role from FDE, which lists a recruiter screen, a hiring manager screen, design and architecture, “Vibe Coding”, “Build, Demo & Delivery” and a reference check. ^[50]Source 50Delivery Solutions Architect (Tokyo, Japan)PublisherDatabricks (careers site / Greenhouse)Source typecompany job posting And one Blind poster reported, in April 2024, a CodeSignal screen for Anthropic’s combined “Solutions Architect/Forward Deployed Engineer” listing with two LeetCode-style questions. ^[51]Source 51Anthropic Solutions Architect/Forward Deployed Engineer CodesignalPublisherBlind (teamblind.com)Source typecandidate report on Blind

In our reading of the duties, the prep differs like this:

In one sentence: for an SA loop, rehearse presenting and pitching; for an FDE loop, rehearse coding against a clock and owning a system; for a hybrid, bring one story for each.

The biggest trap for architects is the coding round. What FDE coding rounds test sorts the reported formats into four kinds and gives a drill for each, and the flaky API integration question is the kind of practical build to rehearse. For the customer rounds, the free practice case puts you in front of an AI customer with a vague problem and a clock.

Moving from SA to FDE

As a solutions architect, you already have half of the FDE job. You run discovery, handle stakeholders and design under constraints. Some postings ask for exactly that background: Sierra’s Forward Deployed Infrastructure Engineer posting names solutions architecture among the backgrounds it wants, with significant time spent on customer-facing deployment work, and Adobe’s Experience Platform FDE postings list solution architecture in their typical background. ^{[52, 53]}Source 52Deployed Infrastructure Engineer (San Francisco)PublisherSierra (Ashby)Source typecompany job postingSource 53Senior Forward Deployed Engineer (Bucharest)PublisherAdobe (Workday careers site)Source typecompany job posting LangChain’s Deployed Architect postings ask for hands-on customer-facing roles “such as Solutions Architect or Forward Deployed Engineer”. ^[54]Source 54Deployed Architect, Professional Services (San Francisco) @ LangChainPublisherLangChain (Ashby job board)Source typecompany job posting

The gap is production code you owned. Jia Wu, a deployed engineering lead at Cognition, said at the AI Engineer World’s Fair 2026 that business sense can be learned, while being the technical expert in the room is very hard to teach. ^[55]Source 55How Forward Deployed Engineering is done at Cognition (Jia Wu; AI Engineer World's Fair 2026)PublisherAI EngineerSource typerecorded talk or interview Kevin Bai, who was the first member of Rippling’s FDE team, said in a talk at the AI Engineer World’s Fair 2026 that an FDE is someone you would hire as a software engineer and also trust in front of a customer. ^[56]Source 56Forward Deployed Engineering 101 (Kevin Bai, Member of Technical Staff, Anthropic; AI Engineer World's Fair 2026)PublisherAI EngineerSource typerecorded talk or interview That was his general view, not a statement of any employer’s hiring criteria.

Here is our plan for closing the gap. It is our method, not something interviewers publish.

1. Build one thing end to end, and run it. Pick the version your target employers would recognize, deploy it, write tests, and keep it running for a few weeks. This becomes your production story.
   • Aiming at AI labs and AI product companies: an LLM triage service over an exported support-ticket queue, with an eval set of 50 labeled tickets, retries, request tracing and a cost-per-ticket log. The number to quote is how many eval tickets it labels correctly, before and after your last change.
   • Aiming at enterprise software and data companies: an incremental sync from a paginated API into a warehouse, with a cursor checkpoint, an idempotent MERGE, a row-count reconciliation against the source and a one-page runbook. The number to quote is rows reconciled per day, and how long it has run without a mismatch.
2. Practice timed coding weekly. Architects rarely code against a clock. Rehearse practical builds and debugging, not just puzzles, and say your reasoning out loud as you go.
3. Rewrite your stories from “recommended” to “shipped”. The verbs carry the evidence. “I designed the reference architecture and the customer’s team built it” is SA evidence. “I wrote the ingestion service, rolled it out behind a flag and was paged when the upstream API changed” is FDE evidence. Use the second kind wherever it is true.
4. Prepare the “why leave SA?” answer. Keep it about the work, not the title, as in the callout below: what you handed off, and what you want to own.
5. Consider a bridge role. Some applied AI engineer and post-sale architect roles carry more code than a pre-sales SA seat. OpenAI’s Applied AI Engineer, for one, works hands-on in code to build prototypes, evaluation harnesses, integrations and production accelerators. ^[29]Source 29Applied AI EngineerPublisherOpenAI (Ashby)Source typecompany job posting Time in a role like that gives you production stories to bring to an FDE loop.

Two answers to avoid: “SA was too salesy” and “I want to be more technical”. The first sounds like you are avoiding customers, and this page has shown that some FDE roles carry pre-sales work too. The second names no work; say what you want to own instead.

Then back it with one story from your own work. A project you owned end to end and working inside a customer’s environment are the two questions an SA’s history is most likely to be probed on, and both are free to practice. The bridge story lesson shows how to connect your past work to the FDE job in two minutes.

Which role should you apply for?

Answer these about yourself before you pick a posting.

Mostly yes: aim at FDE postings, and use the tests above to confirm each one is really FDE work. Mostly no: an SA or applied AI architect role may suit you better, and it is a respectable job in its own right, not a lesser one. Mixed: look at the hybrid titles, and ask each recruiter who writes the fix after launch.

The three questions to ask on any recruiter call, whichever title you apply for:

• “After launch, who is on call for what I build?”
• “Who does this role report to, and what number is that person measured on?”
• “If part of the pay is variable, what is it measured on: bookings, renewals, delivery milestones or company results?”

Read further: four narrower questions

This guide is the hub for four posts, each taking one question further.

• Is the posting a real FDE role? FDE or a solutions architect role in disguise? walks through the lines in a posting that give it away, with real lines annotated, and what to ask the recruiter when the posting is unclear.
• Databricks specifically. One Blind poster reported, in July 2026, that a recruiter told them Databricks’ Resident Solutions Architect roles were being converted into FDE roles. ^[57]Source 57Databricks Interview ExperiencePublisherBlind (teamblind.com)Source typecandidate report on Blind Databricks has not said so in anything we read, though it did announce, in June 2026, a Forward Deployed Engineering organization that brings its Professional Services organization under one roof. ^[58]Source 58Forward Deployed Engineering: Delivering Business Outcomes with AI (Jason Martin)PublisherDatabricks BlogSource typecompany blog Databricks resident solutions architect vs FDE sets what the postings show beside that report.
• Making the move. From solutions architect to FDE expands the plan above into a full program for closing the production-code gap, with stories rewritten from architect to delivery.
• The support-side neighbor. AWS’s Sr. Technical Account Manager posting sits in Enterprise Support and says “This is not a sales role”. ^[59]Source 59Sr. Technical Account Manager, TAMPublisherAmazon (amazon.jobs)Source typecompany job posting FDE vs technical account manager shows who builds and who supports, and how to tell from the posting.

For the other neighbors, read FDE vs sales engineer. If you are still deciding whether the job is for you at all, start with what a forward deployed engineer is, and when you have an interview booked, the FDE interview guide takes you through it round by round.

Your next step

If you are coming from SA, your gap is production code, so start there. Module 0, the FDE role decoded, is free and teaches you to read any posting the way this guide does. Then take the free lesson What FDE coding rounds test, and try the free practice case once you have signed in. The flaky API integration question is the build this guide tells you to rehearse: its framework is free, and Pro opens the full model answer, including what to do when records are added while you page and how to resume after a crash.

Questions people ask

Is a forward deployed engineer the same as a solutions architect?

No, although titles blur them. The FDE postings we read describe building production systems with or inside a customer’s systems. The architect postings we read describe scoping, advising and building prototypes and proofs of concept. Baseten’s Solutions Architect posting, for example, asks for technical depth without needing to write production code, and pulls in its FDE team for deeper technical work.^{[1, 2, 3, 5, 17]}Source 1Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job postingSource 2Job Application for Applied AI Architect, Commercial at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job postingSource 3Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job postingSource 5Solutions Architect @ BasetenPublisherBaseten (Ashby)Source typecompany job postingSource 17Solutions Architect, Enterprise GreenfieldPublisherAmazon (amazon.jobs)Source typecompany job posting

Do forward deployed engineers write more code than solutions architects?

In the postings we read, yes, and the difference is the kind of code. Anthropic’s FDE posting has the FDE build production applications within customer systems. Its Applied AI Architect posting still asks for working code, but as prototypes, proofs of concept and near-production examples that customers can extend.^{[1, 2]}Source 1Job Application for Forward Deployed Engineer at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job postingSource 2Job Application for Applied AI Architect, Commercial at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job posting

Are FDEs post-sale and solutions architects pre-sale?

Not reliably. OpenAI’s financial-services FDE posting runs from pre-sales through post-production, and Anthropic is hiring a Pre-Sales Program Lead for its FDE team. On the architect side, Anthropic calls its Applied AI Architect a pre-sales architect, while Databricks’ Delivery Solutions Architect is the post-sale technical lead.^{[2, 9, 10, 43]}Source 2Job Application for Applied AI Architect, Commercial at AnthropicPublisherAnthropic (Greenhouse)Source typecompany job postingSource 9Forward Deployed Engineer (FDE), Financial Services- NYCPublisherOpenAI (Ashby)Source typecompany job postingSource 10Delivery Solutions ArchitectPublisherDatabricks (Greenhouse)Source typecompany job postingSource 43Pre-Sales Program Lead, Forward Deployed EngineeringPublisherAnthropic (Greenhouse)Source typecompany job posting

Do solutions architects or FDEs carry a sales quota?

It depends on the employer, so read the pay line. AWS’s Solutions Architect posting sits in AWS Global Sales and asks the architect to help exceed revenue objectives. Okta states its Principal FDE pay as on-target earnings that include incentive compensation, while Baseten’s FDE manager posting says FDE at Baseten is not a sales function. Ask what any variable pay is measured on.^{[8, 17, 24]}Source 8Engineering Manager, Forward Deployed Engineering (LLM) @ BasetenPublisherBaseten (Ashby)Source typecompany job postingSource 17Solutions Architect, Enterprise GreenfieldPublisherAmazon (amazon.jobs)Source typecompany job postingSource 24Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOkta (Greenhouse)Source typecompany job posting

What is the difference between an applied AI architect and an FDE?

At OpenAI, the FDE sits in a Forward Deployed Engineering department and owns build and production rollout, while most of its Applied AI Architect postings sit in Go To Market, where the architect owns the technical strategy for a portfolio of customers, beside an Account Director who owns the commercial side.^{[3, 15]}Source 3Forward Deployed Engineer (FDE) - SFPublisherOpenAI (Ashby)Source typecompany job postingSource 15Applied AI ArchitectPublisherOpenAI (Ashby)Source typecompany job posting

Can a solutions architect become a forward deployed engineer?

Yes, and some postings name solutions architecture as a background they want, including Sierra’s Forward Deployed Infrastructure Engineer (which also asks for significant customer-facing deployment work) and Adobe’s Experience Platform FDE. The gap to close is the coding bar: Ramp’s Director of Engineering has said FDE candidates there must pass the software engineering interview loop.^{[47, 52, 53]}Source 47What is a Forward Deployed Engineer? (FDE Explained) feat. Leo Mehr of Ramp (YouTube auto-generated English captions)PublisherdearCC (Clara Shih), YouTubeSource typerecorded talk or interviewSource 52Deployed Infrastructure Engineer (San Francisco)PublisherSierra (Ashby)Source typecompany job postingSource 53Senior Forward Deployed Engineer (Bucharest)PublisherAdobe (Workday careers site)Source typecompany job posting

Which pays more, an FDE or a solutions architect?

No source we hold compares the two across employers, and pay varies by company, level and city. As of September 2026, Baseten’s FDE and Solutions Architect postings both show $165K to $330K plus equity: salary for the FDE, while the SA posting does not say whether it is base or total. As of September 2026, Modal’s Solutions Architect posting shows $200K to $280K plus equity, base or total unstated, against a $180K to $250K salary plus equity for its FDE - ML posting. Okta and Notion state FDE pay as on-target earnings, as Vercel does for its Solutions Architect. Compare the bands for the roles you are weighing, and ask what any variable part is measured on.^{[5, 18, 20, 24, 25, 26, 27]}Source 5Solutions Architect @ BasetenPublisherBaseten (Ashby)Source typecompany job postingSource 18Solutions ArchitectPublisherVercel (Greenhouse)Source typecompany job postingSource 20Forward Deployed Engineer, GTM, AMER @ NotionPublisherNotion (Ashby job board)Source typecompany job postingSource 24Principal Forward Deployed Engineer - Okta for AI AgentsPublisherOkta (Greenhouse)Source typecompany job postingSource 25Forward Deployed Engineer postingPublisherBaseten (Ashby job board)Source typecompany job postingSource 26Solutions Architect @ ModalPublisherModal (Ashby)Source typecompany job postingSource 27Forward Deployed Engineer - ML @ ModalPublisherModal (Ashby)Source typecompany job posting

Keep reading

Guides

• What is a forward deployed engineer?
• Forward deployed engineer vs software engineer
• Forward deployed engineer vs sales engineer
• The forward deployed engineer interview, round by round
• Forward deployed engineer salary: what employers post and file

Lessons

• FDE, software engineer, solutions architect, sales engineer: telling them apart
• How to read an FDE job posting line by line
• The bridge story, and the short ‘why FDE’ answer
• What FDE coding rounds test, by the evidence

Questions

• What customer-facing experience do you have? Be specific about who the customer was.
• Tell me about a project you owned from the first customer conversation to production. Which decisions were yours alone?
• Tell me about a time you worked inside a customer’s environment rather than your own. What was hardest?
• How do you decide between building a custom solution for one customer and pushing for a product change?