Treat the feature request as a symptom and work backward. Ask what they would do with it, what they do today instead, and what happens when that workaround fails. Most feature requests are a fix someone already picked for a problem they have not described. Once you have the underlying problem and its cost, you can decide whether your product solves it, and whether the deal is worth running.
Why interviewers ask this
Reps who answer feature questions literally end up in feature bake-offs they cannot win, and they lose to whoever has the longer checklist. The interviewer wants to see whether you can redirect without sounding evasive, and whether you can hold a prospect's attention while you dig. It is also a test of honesty: a good rep will say that sometimes the answer really is no, and will qualify out rather than promise roadmap.
How to structure your answer
- Answer the surface question briefly so you earn the right to dig.
- Ask what they would do with the feature and what they do today.
- Trace the request back to a business outcome and a cost.
- Confirm the reframe with them before you position anything.
Example answer
First I answer it, because dodging the question kills trust. Yes we do that, or no we do not, then I ask permission to back up. Something like: can I ask what made that the thing you led with. Nine times out of ten there is a story behind it. I had a logistics prospect who opened by asking for a specific export format. If I had just said yes, that is a two-line answer and a dead call. Instead I asked what happens to the file after they export it, and it turned out three people were hand-reconciling it against an ERP every Monday because the systems disagreed. The export was never the problem. The problem was that nobody trusted the numbers, and it was costing them the first day of every week plus a lot of internal arguing. That reframe changed who needed to be in the room, and it moved the conversation from a feature to a reconciliation problem their finance lead cared about. I always play the reframe back to them and check I have it right before I position anything.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What if the feature genuinely does not exist and they need it?
- How do you avoid sounding like you are dodging the question?
- How do you handle a prospect who insists on a scored feature matrix?
Related account executive questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions