FDE · Interview Gym

The Conversations That Decide Deployments.

Most deployments do not fail on code. They fail in four conversations: the demo that breaks in front of executives, the customer who insists on the wrong feature, the security gatekeeper who will not release the data, and the manager whose team gets smaller if you succeed. Every FDE interview probes these — reported OpenAI loops weight case and empathy work at roughly half the evaluation — and every guide tells you to rehearse them with a friend. Here they are as branching dialogue, with a live trust meter and a scored verdict.

4 scenarios · branching replies · live trust meter · signals scorecard · verdict
trust

The only currency you have. It buys scope changes, bad news, and time. Spend it deliberately.

scope the failure

When something breaks, say what it is not. Uncontained failure contaminates the whole system in the room’s mind.

the outcome behind the ask

Every wrong request is a right outcome wearing a bad costume. Find the outcome and you can redirect without refusing.

rational opposition

Blockers are almost never villains. They are people whose incentives your project threatens. Find what they win.

customer-room.live
Choose a scenario
Each scenario runs four beats. Your reply changes what the customer says next and moves the trust meter. There is no perfect script — there are answers that keep the room, and answers that lose it.
50
trust
0/4
beat
room

The four signals being scored

Interviewers running a roleplay round are not grading your charisma. They are checking four specific behaviours, and each one maps to a way real deployments die.

01

Listen before you answer

The first move in every scenario is a question, not a position. Engineers lose this round by answering the question that was asked instead of finding the one that matters. In a deployment, the same reflex is what makes you build the requested feature instead of the needed one.

02

Deliver bad news early and plainly

Bad news does not improve with age; it compounds. Saying “this will not be ready Friday, here is what will” on Tuesday costs a fraction of what it costs on Friday afternoon. Candidates who soften the message into unintelligibility score worse than candidates who are blunt.

03

Say no in a way that increases trust

The move is: ask what outcome they want, name the mismatch, offer a path to the outcome. Never bare compliance (you build the wrong thing) and never bare refusal (you lose the relationship that lets you build the right thing).

04

Treat opposition as an incentive problem

The person blocking you usually has a reason: headcount, credit, workload, risk exposure, or being the only one who understands the current process. Escalating first converts a solvable incentive problem into a permanent adversary, and everyone in the room remembers who escalated.

The sixty seconds after a demo breaks

This is the single most-tested scenario, because it is a compressed sample of everything else. There is a script that works, and it takes about fifteen seconds to deliver.

// the four moves, in order 1. name it "That's failing — let me tell you what that is." 2. scope it "That's the ingest path, not the model. Everything you saw before it is real." 3. commit "I'll have the cause by end of day and a fix or a workaround tomorrow." 4. continue "The next part doesn't depend on it — can I show you that?"

What makes it work is move 2. An unscoped failure expands in the room’s imagination until it covers the entire system; a scoped one stays a bug. What breaks it is apologising at length, blaming the environment, or quietly restarting things and hoping nobody noticed — all three read as someone who cannot be trusted alone at a customer.

worst move
silence
second worst
blame
best move
scope it
time budget
~15s

Check yourself

A customer insists on a feature you are confident will not solve their problem. Best first response?

Security has blocked your data access for three weeks. What does a strong FDE do?

A middle manager keeps raising objections that stall the rollout. Most likely explanation?

Common questions

What is a client roleplay round in an FDE interview?

An interviewer plays a customer in a difficult situation and scores how you listen, how honestly you handle bad news, and whether you can decline a request without losing the room. Reported OpenAI forward deployed engineer loops weight case, empathy and business judgement at roughly half the total evaluation.

What do you do when a demo fails in front of the customer?

Name it, scope it so it does not contaminate everything else, commit to a specific time for the cause and the fix, and continue with the parts that do not depend on it. Handled that way a visible failure builds more credibility than a flawless demo, because the customer learns how you behave when something breaks — which is what they are actually buying.

How do you say no to a customer?

Ask what outcome they want, name the mismatch between the request and the outcome, then offer a path to the outcome. Bare compliance builds the wrong thing; bare refusal costs you the relationship you need in order to build the right thing.

How do you handle a stakeholder who is blocking the project?

Assume a rational interest rather than malice: headcount, credit, workload, or risk exposure. Find out what they win if the project succeeds and make it explicit. Escalating over their head first is the most common mistake and it turns a solvable incentive problem into a permanent adversary.

Can you really practise this alone?

Partly. What a simulator drills well is recognising the shape of each situation and knowing the strong move — which is most of what candidates get wrong. The conversational half, including handling an interviewer who probes your answer, still needs a human. Run all four scenarios here first so you are not spending a real rehearsal on the basics.

Keep going

Finished this one? 0 / 55 Labs done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

More Labs