Skip to content
FDE Spot

For engineers moving into Forward Deployed roles

Your demo works.
The meeting is where it dies.

Rubric-graded simulations for engineers who can build AI demos and want to deploy them in front of customers. You'll practice the CEO pitch, the discovery call and the 3am incident, and get scored on each.

Who it's for: aspiring FDEs and the solutions, customer and implementation engineers doing the same work. The bar is Python and one real LLM project.

53 lessons available6 boss battles6 mock rounds

Try a graded drill with no account. Sign in free to unlock Modules 1 to 3. All-Access has a 30-day money-back guarantee.

M01 · Boss · Stage 1 of 3Live grader

The Skeptical CEO

Budget owner at an insurance company · simulated stakeholder

Presses on value first, then reliability, then invented numbers.

You're pitching PolicyPilot, an AI reply assistant for the insurance help desk.

View brief
  • The help desk has 40 agents.
  • Replies use approved policy documents and cite the relevant clause.
  • A human agent approves every draft.
  • The assistant never decides claims or coverage.
  • Agents currently spend about 20 minutes per ticket searching policy documents.
  1. The CEO: I have 60 seconds. What does it do, and why should I fund it? One paragraph. No jargon.

Enter adds a new line. Press Control or Command with Enter to send.
Hint

The CEO wants a funding decision, not an architecture tour: the job, the value, the limits.

No account needed · 0 / 1200

Rubric: The One-Paragraph BriefPass mark 60 / 100Stages 2-3 in the app
  1. Your answer
  2. rubric score
  3. evidence
  4. the CEO's reaction
  5. revise

The three moments a Forward Deployed Engineer is judged on.

Each leaves a document behind, here for the same help-desk deployment the CEO is asking about.

In the boardroom

Module 1 · the Skeptical CEO

Common failure mode
Explaining architecture when the executive asked for a decision.
FDE standard
Value, boundaries and risk in under 60 seconds.
Output
A one-paragraph executive brief.
Executive brief: PolicyPilotto: CEO · 1 paragraph
Decision requested
Fund a four-week pilot on one ticket category
Business impact
40 agents spend about 20 minutes per ticket searching policy documents
Human approval
Required. An agent approves every draft.
Out of scope
Claims and coverage decisions
Risk posture
No approved clause, no answer: it says so instead of guessing

Next question in the room, stage 2: “Your demo worked once. What happens on the 500th weird customer message, and how do you know?”

In discovery

Module 3 · a live call with Meridian Mutual's CTO, compliance and claims ops

Common failure mode
Taking the feature request literally and scoping a six-month build.
FDE standard
Find the real constraint; cut the smallest slice that can ship.
Output
A scoped first slice with its assumptions and exclusions.
Discovery notes: help deskscoping · slice 1

Customer ask

“We need an AI chatbot.” A feature, not a problem.

Actual bottleneck

Agents spend about 20 minutes per ticket finding the right policy clause.

Slice 1

  • Draft the reply and cite the clause
  • An agent approves every draft
  • Measure handle time on one ticket category

Out of scope

  • Claims decisions
  • Replies sent without an agent
  • Interpreting ambiguous policy

Assumptions to confirm

The policy library is current and approved. The help desk can tag tickets by category.

In production

Modules 4 and 5 · ending in the 3am page

Common failure mode
Treating the prototype as the deployment.
FDE standard
Least privilege, traces, an eval gate, cost alerts and a rehearsed rollback.
Output
A readiness review, and an incident call you can run.
Day-2 readiness review: PolicyPilot6 of 7 checks
  • Passed: Least-privilege service account2 roles, no project-wide accessM05
  • Passed: Secrets out of code and configread from a secret storeM05
  • Passed: Traces across retrieval, model, toolp95, errors, tokens per requestM05
  • Passed: Golden eval set reruns every releaserelease stops if misses riseM05
  • Passed: An agent approves every draftno reply leaves without a humanM01
  • Passed: Rollback to last good revisionrehearsed, under five minutesM05
  • Missing: Alert on cost per requestlatency alerted, spend is notM05
DecisionNO-GO until the cost alert exists

See exactly how an answer is judged.

Two real attempts at the Module 1 boss, measured and scored by the same pipeline that scores yours. Unedited; only the highlights are ours.

“But what happens when it gets a clause wrong, and how do we safely test this first?”
The simulated CEO, after attempt 1 scored 15
  1. Submission
  2. Evidence
  3. Rubric
  4. Reaction
  5. Retry
  6. Record
M01 / The Skeptical CEO / Stage 1 of 3: The One-Paragraph Brief

Submission

PolicyPilot is a RAG pipeline on Gemini: we chunk your policy PDFs, embed them into a vector store, retrieve the top-k clauses for each ticket and generate a grounded draft with citations. It plugs into the help desk through an API, and we can fine-tune the prompts as we learn. It should make the support team a lot faster.

Highlighted: the phrases the evaluator's reasons point to.

Evidence · measured by code

  • Present: Within 120 words, one paragraph
  • Missing: Plain language
  • Missing: Business problem stated
  • Present: Business outcome stated
  • Check: Value backed by a number
  • Missing: Human approval point stated
  • Missing: Limit or failure behaviour stated
  • Missing: Way to prove it before scaling
  • Check: Opens with the architecture, not the business

Graded 5 Oct 2026 · 59 words · pass mark 60

Rubric · scored by the evaluator

15/100NOT YET
  • Executive clarity5 / 25

    The pitch opens with a technical architecture tour filled with jargon like RAG, vector stores, and chunking rather than focusing on executive outcomes.

  • Value framing8 / 25

    It mentions making the support team faster, but omits the current time spent searching policies and lacks any quantified target.

  • Boundaries2 / 25

    It fails to state that human agents approve every draft or that the assistant never makes coverage decisions.

  • Risk and proof0 / 25

    There is no mention of how the system handles uncertainty or any pilot decision gate to prove value before scaling.

Feedback

The CEO: “I get that you want to speed up support tickets using our policy docs. But what happens when it gets a clause wrong, and how do we safely test this first?”

Retry

What would improve this answer →

  • Reframe the pitch around the 20 minutes agents spend searching policy documents per ticket, ensuring every draft requires human approval before sending.
  • Replace technical terms like RAG, vector store, and top-k with plain business language.
  • State the baseline operational problem, human approval guardrails, and a pilot proof plan.

What landed: Keeps the submission short and well within the word limit.

Your assessed work stays on your account.

Sign in to keep it. There is no public profile or share link yet.

Boss battles
Every Module 1 brief attempt in full; best score and cleared stages for the rest
Stakeholder calls
Every attempt: transcript and scorecard
Interview rounds
Transcript and scorecard, or a Bronze-to-Gold medal for coding rounds
Progress
Lessons, boss battles and modules completed

The core track, then the interview loop.

Modules 1-6 and the Module 7 interview loop are live. Module 6 takes your pilot through privacy, compliance and identity review.

Open the full Campaign ↗
  1. 01

    The boardroom decision

    Prompt contracts · few-shot · grounding · the executive pitch

    You'll be able to: Write a one-paragraph brief a CEO can say yes or no to, with value, limits and a way to test it first.

    The Prompt Forge · 4 lessons + boss · Free

    Boss · The Skeptical CEO

  2. 02

    Long context under pressure

    Gemini API · context budgets · structured outputs · function calling

    You'll be able to: Budget context, force structured output and wire function calls so the demo holds up on messy input.

    Gemini API & Context Architecture · 7 lessons + boss · Free

    Boss · The Flaky Integration

  3. 03

    The customer doesn't know what they need

    Discovery · solution hypothesis · first-slice scoping · live Meridian call

    You'll be able to: Find the real bottleneck behind "we need a chatbot" and cut the smallest first slice that can ship.

    Customer Discovery & Solution Architecture · 4 lessons + boss · Free

    Boss · The Moving Goalposts

  4. 04

    The 24-hour demo

    Tool design · schemas the model won't misuse · tool-using agents

    You'll be able to: Put a working tool-using demo in front of a customer within a day, with tool contracts that hold when the model gets creative.

    Rapid Prototyping & Tool Building · 5 lessons + boss · All-Access · free previews

    Boss · The 24-Hour Demo

  5. 05

    Survive day 2

    Least privilege · secrets · tracing · cost alerts · evals · rollback

    You'll be able to: Take the 3am page: find the cause in your traces and cost alerts, then roll back a release you have already rehearsed.

    Production Deployment on Google Cloud · 5 lessons + boss · All-Access · free previews

    Boss · The 3am Page

  6. 06

    The enterprise handoff

    Privacy review · compliance evidence · identity offboarding

    You'll be able to: Get a working pilot past the privacy, compliance and identity reviews, with the evidence each reviewer asks for.

    Enterprise Delivery: Privacy, Compliance & Identity · 8 lessons + boss · All-Access · free previews

    Boss · The Board Review

  7. 07

    The FDE interview gauntlet

    Nine prep lessons, then six graded mock rounds, from ownership screen to client interview

    You'll be able to: Walk into each FDE interview round already graded on it: ownership, decomposition, coding, learning, AI solution design and the client interview.

    The FDE Interview Loop · 9 lessons + 6 mock rounds · All-Access · free previews

    6 mock rounds

Built by engineers who ship this work.

FDE Spot is built from the architecture trade-offs, customer conversations and production constraints we meet in enterprise AI delivery.

Independent: not affiliated with or endorsed by our employers or Google.

Paweł Pisarski at a desk in front of a screen showing an enterprise RAG architecture

Paweł Pisarski

LinkedIn ↗

Solution architect · enterprise AI

Builds governed agentic AI platforms for enterprise clients.

Rafał Bogusz at a desk in front of a screen showing TypeScript code

Rafał Bogusz

LinkedIn ↗GitHub ↗

Software engineer · AI systems

Ships enterprise AI solutions, and built FDE Spot's grader and simulations.

One pass for every simulation that is live.

All-Access pass

$99per year, one learner

Get All-Access, $99/yr

Train, retry and revisit every live simulation for 12 months.

  • 53lessons available now
  • 6boss battles, each graded against a written rubric
  • 6mock interview rounds
  • 12months of access, renewing yearly until you cancel

Module 6 is included now; the capstone exam is included when it ships. Access starts when payment completes, on your FDE Spot account (or the one you create later with the email you pay with). Billed yearly through Stripe; email [email protected] to cancel. 30-day money-back guarantee. Recently laid off? $49/yr, no conditions: email us.

In development, no ship dates: the Module 7 full-loop boss, the capstone exam and the FDE credential.

Enterprise, for teams

Custom quote

Quotes start at $299. Seats, billing period and total price are set out in a written quote before anything is charged.

  • All-Access for each seat
  • Invoice or purchase-order billing
  • Onboarding call with your team
  • Priority email support
Ask for a quote

By email. No card needed.

Free drill, no account. Try a graded drill with no account. Sign in free, with Google or any email address, to unlock Modules 1 to 3 and their boss battles, plus preview lessons in Modules 4, 5 and 7.

Sign in free

The ones people actually ask.

Software engineers who can already build with LLMs and want the customer-facing half of the FDE job: discovery, scoping, production readiness and the interview loop. The bar is Python and one real LLM project behind you; no Google Cloud experience is assumed. If you haven't built anything with an LLM yet, this isn't the place to start. If you have shipped an AI demo and want to be the person a customer trusts with the deployment, start with Module 1.