Most founders ask sales candidates how they handle competitors and grade the answer on confidence. That's the wrong test. The candidate who tells the best story about a past deal is not the same candidate who can hold their ground on a live call three weeks from now. If competitive pressure is costing you deals, the only interview question that matters is whether the person can think on their feet when a prospect says your rival's name, not whether they can narrate a memory about it.
Why "tell me about a time" fails for this specific skill
Behavioral questions test recall and storytelling, not real-time judgment. A candidate can rehearse a clean STAR-format answer about handling a competitor objection without ever proving they can do it live, under pressure, with your specific product and your specific rivals.
This matters more in competitive selling than almost any other sales skill. Objection handling in the moment requires knowing your own weak spots well enough to acknowledge them, knowing the competitor's actual weak spots, not the generic ones, and doing both without sounding defensive. None of that shows up in a rehearsed anecdote. It only shows up when you make them do it.
The test: hand them your battlecard and role-play it cold
If you've already built a one-page competitive battlecard, the interview test is simple: give the candidate five minutes with it, then run a role-play where you play the prospect and bring up your toughest competitor unprompted, mid-conversation, the way real buyers actually do it.
Don't warn them which competitor is coming. Real deals don't send an agenda. What you're testing is whether they can absorb a page of positioning and turn it into a natural response inside a single conversation, which is exactly the job.
If you haven't written a battlecard yet, a rough one-pager works fine for this exercise: your top two competitors, the one thing each does better than you, the one thing you do better than both, and the specific customer segment where that difference actually matters.
What a strong response looks like versus a weak one
A weak candidate does one of two things. They either bad-mouth the competitor outright, which reads as insecure to any experienced buyer, or they freeze and pivot straight to price, which signals they have no answer beyond discounting.
A strong candidate does three things in order, usually within 15 to 20 seconds: they acknowledge the competitor by name without flinching, they ask one clarifying question about why the prospect brought it up, and they reframe the comparison around the one dimension where you actually win, using specifics from the battlecard rather than vague claims like "better support."
Score it on those three moves separately, not as one overall impression. A candidate who nails the acknowledgment and the reframe but skips the clarifying question is coachable. A candidate who does none of the three after reading the battlecard is telling you they can't do this job at your stage, regardless of their resume.
A worked example script
Run it like this. After five minutes with the battlecard, say: "Walk me through your demo. I'm a prospect who's already three calls deep with [competitor] and I'm mostly doing this call out of politeness."
Listen for whether they name the competitor back to you instead of dancing around it. A candidate who says "a lot of teams end up comparing us to them, so let me ask what's working and not working in those conversations so far" is already ahead of most hires, because they turned an interview trick into a real discovery question. That instinct, treating a competitor mention as a discovery opportunity instead of a threat to survive, is the actual skill you're hiring for.
What this test doesn't replace
This is not a substitute for checking whether someone can build pipeline, run discovery, or close. It tests one narrow, specific skill: real-time competitive handling. Run it alongside your normal sales interview process, not instead of it.
It also won't help you if your battlecard itself is vague. If your one-pager just says "we have better customer service," no candidate can turn that into a sharp answer, because there's nothing sharp in it to work with. Fix the battlecard first, then use it as the test.
Frequently asked questions
How long should the role-play take?
Ten minutes is enough. Five minutes reading the battlecard, five minutes of role-play. Longer than that and you're testing stamina, not the skill.
Should I use a real competitor or a fictional one?
Always real. Fictional competitors let candidates invent an easy opponent. Real names force them to handle the actual objections your buyers raise.
What if the candidate has never seen my product before this interview?
That's fine, and arguably better. The battlecard is designed to be absorbed in minutes. If a candidate can't apply five minutes of reading to a live conversation, they'll struggle with the pace of a real deal too.
Can I run this test over video instead of in person?
Yes. Most competitive objections happen on video calls now anyway, so testing it in that format is more realistic, not less.
What's the biggest mistake founders make running this test?
Grading on politeness instead of substance. A candidate who is warm and vague sounds better in the room than one who is direct and specific, but the direct one is the one who wins deals against a named rival six months from now.
Does this work for a first sales hire with no prior competitive-selling experience?
Yes, and it may matter more there. A first hire with no track record against your specific competitors needs to prove real-time judgment, since there's no deal history to fall back on when you check references.
The best account executives don't avoid the competitor conversation. They steer into it before the prospect finishes the sentence. That's not a trait you can spot on a resume, but it's one you can watch for in ten minutes, if you make the candidate actually do the job before you hire them for it.