1 min lesson
Close by interviewing them
Answer "Why is 'closing by interviewing them' a stronger move than ending with 'any questions?' and what does it set up?" Use one lesson detail to support it.
Step 1 of 2
Close by interviewing THEM
Amateurs end a demo by asking "any questions?" Field engineers turn the table into a discovery conversation instead. You've earned credibility. Now spend it learning their constraints so your follow-up is laser-targeted. The questions you ask reveal as much competence as the demo you ran.
- "Where does code review actually bottleneck for you today - is it reviewer availability or scope of changes?"
- "Who owns the merge gate and what evidence does your audit team need to see on every PR?"
- "What's your blast-radius rule - which repos or modules would you fence off first with an allowlist?"
- "If you ran a pilot, what's the one metric that would make your VP say yes - cycle time, change-failure rate, onboarding time?"
- "What killed the last tool you tried - was it security review, senior pushback or it just wrote garbage?"
Learn more
Advanced table
FE vs FDE: where the interview emphasis differs
FE vs FDE: where the interview emphasis differsknow which loop you're in
- Dimension
- Center of gravity
- Field Engineer (FE)
- Demo, objection handling, persona translation
- Forward-Deployed Engineer (FDE)
- Hands-in-the-repo implementation at the customer
- Dimension
- Interview proves
- Field Engineer (FE)
- Can you make the room believe + name controls
- Forward-Deployed Engineer (FDE)
- Can you ship real change in a hostile legacy codebase
- Dimension
- The demo is...
- Field Engineer (FE)
- The performance - narrate, frame, close
- Forward-Deployed Engineer (FDE)
- The starting point - then you actually build with them
- Dimension
- Failure mode they probe
- Field Engineer (FE)
- Hype without substance, can't handle a skeptic
- Forward-Deployed Engineer (FDE)
- Can't navigate a 15-yr monolith, weak on guardrails in practice
- Dimension
- Strongest signal
- Field Engineer (FE)
- Concede-first fluency + 90-sec POV
- Forward-Deployed Engineer (FDE)
- Deep value-stream + DORADORA metrics. Four widely-used delivery measures: deployment frequency, lead time for changes, change failure rate and time to restore service. Press Enter for the full definition. + ITGCIT General Controls. The baseline IT controls auditors check: who can change what, how changes get approved and how systems are run. Press Enter for the full definition. fluency under real code
| Dimension | Field Engineer (FE) | Forward-Deployed Engineer (FDE) |
|---|---|---|
| Center of gravity | Demo, objection handling, persona translation | Hands-in-the-repo implementation at the customer |
| Interview proves | Can you make the room believe + name controls | Can you ship real change in a hostile legacy codebase |
| The demo is... | The performance - narrate, frame, close | The starting point - then you actually build with them |
| Failure mode they probe | Hype without substance, can't handle a skeptic | Can't navigate a 15-yr monolith, weak on guardrails in practice |
| Strongest signal | Concede-first fluency + 90-sec POV | Deep value-stream + DORADORA metrics. Four widely-used delivery measures: deployment frequency, lead time for changes, change failure rate and time to restore service. Press Enter for the full definition. + ITGCIT General Controls. The baseline IT controls auditors check: who can change what, how changes get approved and how systems are run. Press Enter for the full definition. fluency under real code |
For an FE loop, your demo is the deliverable. They're watching whether you can frame, name controls and survive a hostile question with a concede-first reflex.
For an FDE loop, the demo is just proof you can start; they'll push on whether you can actually land change in their legacy mess and keep it inside the guardrails over weeks, not minutes.
Either way, the spine is your universal answer structure: when you don't know what to say, narrate the value streamThe end-to-end path a change takes from idea to running in production. Press Enter for the full definition. and name the control at each station.
"Before I tell you what I'd build, let me ask what would make your VP say yes - because I'd rather solve that than demo something you don't need."