Question 3Discovery and scoping
Tell me about a time the customer asked for one thing but needed another.
Good FDEs spot when a request is a guess at a solution. They want proof you can redirect a customer without losing their trust.
“Run discovery and translate ambiguous business problems into clear requirements, scope, and acceptance criteria”Senior Forward Deployed Engineer, Applied AI · Juniper Square
The answerFour steps
- 1
What they asked for, and the detail that made you doubt it
Say it like this
“What bothered me: the help center only had 80 articles, so search shouldn't be that slow.”
Why it scores
Names the detail that raised the doubt. The hunch had a reason.
- 2
How you tested the doubt (shadowed users, looked at logs, ran a quick prototype)
Say it like this
“I sat with four agents for an afternoon and timed them. Most of the lost minutes went into copying order numbers into a second system to check shipping status.”
Why it scores
Tests the doubt by watching real users before pushing back.
- 3
How you made the case to the customer
Say it like this
“I showed the lead the timings next to her request, and offered a one-week test of the other fix before we built the chatbot.”
Why it scores
Doesn't overrule her. Brings evidence and a cheap test, and keeps her idea alive.
- 4
What shipped and what changed for them
Say it like this
“We put order status in the ticket sidebar. Average handle time went from 9 minutes to 6, and the chatbot moved to the backlog.”
Why it scores
Ends with a number. A story without a result reads as an opinion.
StrongAll together
About a minute, out loud. The marked parts are the four steps; hover one to find it above.
At a retail customer, the support lead asked for a chatbot so agents could search the help center faster. What bothered me: the help center only had 80 articles, so search shouldn't be that slow.1 I sat with four agents for an afternoon and timed them. Most of the lost minutes went into copying order numbers into a second system to check shipping status.2 I showed the lead the timings next to her request, and offered a one-week test of the other fix before we built the chatbot.3 We put order status in the ticket sidebar. Average handle time went from 9 minutes to 6, and the chatbot moved to the backlog.4
WeakThe answer that fails
Sounds fine. Common. Scores low.
“The client wanted a dashboard, but I realized they really needed alerts, so I explained why alerts were better and built those instead. They were happy with it in the end.”
Interviewer's note
No evidence, no result. Sounds like the candidate overrode the customer on a hunch.
PracticeTwo minutes, then they push back
Your turn
Tell me about a time the customer asked for one thing but needed another.
Answer like you're in the room: about two minutes, no notes. Say it out loud, even alone. It feels different from thinking it. Then check your answer against what interviewers score.