A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.
How to answer
This is a failure question with an alibi built in: you did what was asked. Don’t use the alibi. Ben Kracker, director at Salesforce, said on Salesforce’s blog in November 2025 that FDEs must peel back the layers of a request to give customers the right solution rather than the one they ask for. Source 1Today's Hottest Role: Forward Deployed EngineerPublisherSalesforce 360 BlogSource typecompany blog Show that you now peel back the layers, and how.
- The request and the sign-off, in two sentences. The ticket, spec line or email and who wrote it, then the proof you delivered it: acceptance criteria met, a sign-off, a demo that went well.
- How you found out it was wrong. Usage that never came, a workaround users kept, a number that didn’t move.
- The gap, in one sentence. “They asked for X because they believed Y; what they needed was Z.” This sentence is the center of the answer, so say it plainly.
- Why your process missed it. Say whether the person who wrote the request used the output, and which one you talked to. Then name the user you never watched and the question you never asked. This is your share, and it stands even if the spec was wrong.
- The fix and what it cost. What you changed, how long the rework took, and who waited for it.
- The habit you use now. Something observable: watching one user do the task before writing a spec, asking them to show you the last time they did it by hand, or asking what they will do with the output the morning after it ships. Then a later time it caught a gap before you built anything.
Two traps. “They didn’t know what they wanted” answers the question about the customer, not the one about you. And requirements that changed after you shipped are scope change, not this.
Follow-ups
What the interviewer may ask next, once your first answer is on the table.
- Who signed off on what you shipped, and did they know it was wrong before you did?
- What question, asked in the first week, would have caught the gap?
- When did your new habit last catch a gap before you built anything?
Where answers go wrong
- Blames the requester for not knowing what they wanted, when the question asks what the speaker learned about gathering requirements.
- Ends with a lesson nobody could observe, such as “communicate more with stakeholders”, instead of a specific habit and a later time it worked.
Answer this in two minutes
Write the answer you would say out loud. The clock starts with your first word.
Illustrative answer about a fictional project
A construction company’s safety director asked us for a dashboard of near-miss reports: counts by site and by category, updated weekly, with a PDF export for her Monday safety meeting. She wrote the requirements herself, I built exactly that in four weeks, and she signed it off after a demo that went well.