TechPrep

Path 2 of 10, by 2026 demand

Forward Deployed / Applied AI Engineer and Architect

Customer-facing engineers who scope, build and ship LLM solutions inside customer environments, and the architects who guide them.

Demand The fastest-growing customer-facing AI title (third-party, M1, M7). On 2026-11-19 OpenAI listed 40 Forward Deployed Engineering and 128 Applied AI roles; Anthropic 37 Applied AI Architect, 12 Applied AI Engineer and 8 FDE roles (our count, §2.3).

What the role is

Forward Deployed Engineers (FDEs) work inside a customer's systems to deliver production AI applications. OpenAI's post asks the FDE to "own the technical solution end to end, from customer discovery and workflow scoping through architecture, hands-on implementation, evaluation, production deployment, adoption, and handoff" (official, O6). Anthropic's FDEs deliver "MCP servers, sub-agents and agent skills" into production workflows (official, A8).

Applied AI Engineers and Applied AI Architects sit closer to pre-sales and advisory: technical discovery, architecture guidance, eval frameworks, proofs of concept and executive communication (official, A6, A7). This research added the Architect title to the path: it is the largest customer-facing AI group at Anthropic, and its asks (5+ years as a Solutions Architect, enterprise integration, "comfortable with python") match your background most closely.

Level signals

The typical loop

Neither lab publishes an FDE-specific loop. OpenAI's single guide applies to all roles (official, O1, O2). Expect a customer case alongside engineering rounds.

StageWhat it testsBasis
Recruiter and hiring managerCustomer experience, motivation, travel tolerance (up to 50% in one OpenAI post)Official job post (O6)
Skills assessmentPair coding, take-home or technical test, team-dependentOfficial OpenAI guide (O1)
Customer case / role-playDiscovery, scoping, objection handlingCommon industry pattern; no single source
LLM system designArchitecture inside customer constraints: identity, data, residencyCommon industry pattern; no single source
CodingPractical Python; sometimes building with a model APICommon industry pattern; no single source
Behavioural and valuesOwnership, communication, judgementOfficial OpenAI guide (O4); third-party for Anthropic (A9)

Track order

Work top to bottom. Ticks come from the lessons you mark complete.

  1. 01Working with customersCustomer discovery and technical consulting track. The half of the job most engineers have not practised.
  2. 02Building blocksLLM and agent engineering track. What you will build in the field.
  3. 03Production AI systemsLLM and agent engineering track. Evals and guardrails are how you win trust and launches.
  4. 04Securing AI systemsSecurity engineering for AI systems track. Security reviews gate every enterprise deployment.
  5. 05The design methodSystem design track. Architecture reasoning for customer constraints.
  6. 06Worked promptsSystem design track. The enterprise Q&A and gateway prompts are FDE-shaped.
  7. 07Arrays and stringsCoding patterns track. Keep Python sharp for the coding round.
  8. 08Behavioural rounds at Staff levelLeadership and behavioral track. Customer-impact and influence stories.
  9. 09Mock roundsMock rounds track. Do the customer case mock at least twice.

Role practice set

Prompts written for this site. They are not reported interview questions.

  1. Run the customer case mock (insurer claims) with a partner, then write the one-page POC charter.
  2. Build a working prototype in an afternoon: an agent that answers questions over a CSV and a PDF, with three eval cases and a README a customer engineer could follow.
  3. Draw the data-flow diagram for deploying an assistant inside a customer's Azure tenancy with private networking and managed identity; annotate each security question you expect.
  4. Present a business case to a "CFO" partner in five minutes: cost, value, risk, time to value.
  5. Write the post-deployment handoff document: runbook, eval suite, owner, escalation path.

Your résumé and story angle

Your background, as the brief states it: Staff/Principal engineer and Enterprise Solutions Architect; C#/.NET, Angular, Azure, Kubernetes, distributed systems and AI integrations. The angle below frames it for this role. Replace the bracketed prompts with your real projects and numbers; never claim experience you do not have.

Six-week plan

Tick weeks off as you go

Research notes

Title drift: "Forward Deployed Engineer", "Applied AI Engineer", "Applied AI Architect", "Solutions Architect, AI" and "Deployment Lead" overlap heavily. Read the responsibilities, not the title, and apply across them.

Sources