Overview
Sales candidates arrive pre-loaded with answers. "Tell me about yourself," "what's your biggest weakness," "why do you want to work here", every one of these has a rehearsed response sitting in the candidate's holster, polished across dozens of interviews, and asking them collects theater, not information. A working interview question has a different design: it demands specifics the candidate could not have pre-packaged, and its answer is readable, meaning you know in advance what a strong response contains and what a weak one reveals. Here is the bank, organized by what each section is mining for, built to run alongside the gauntlet, the signals, and verification, never instead of them.
Mining the track record
"Walk me through your last full year: quota, attainment, average deal size, and how many reps were on the floor." The foundation question, and its reading is texture: real performers answer in immediate specifics, and the numbers you collect here feed the consistency interrogation later, so spread the components out and check the math.
"What was your best month ever, and what specifically drove it?" Strong answer: a mechanism, "I started double-dialing every set inside a minute and my show rate jumped." Weak answer: weather, "leads were great that month." You are learning whether they believe performance is caused or happens.
"Tell me about a deal you lost that you should have won. What did you change afterward?" The double test: ownership, does the loss have an internal author, and iteration, did a behavior actually change. Candidates with no such deal, or whose losses are all lead quality, are writing the blame trail flag for you.
Mining the operating system
"Walk me through what you do in the first ten minutes after a new lead books a call." Reps from disciplined floors describe a sequence, speed, texts, dials, and reps from improvised floors say "I review the calendar." You are checking for installed speed-to-lead wiring, or at least the recognition of it.
"A call ends without a close. What happens next, exactly?" You want to hear next-step booking and a follow up cadence in some form, whatever they call it. "I send a recap email and check in later" is the sound of pipeline entropy.
"What did your manager coach you on most recently, and what did you do with it?" Possibly the highest-yield question in the bank: it tests whether they were coachable enough to be coached, self-aware enough to remember it, and honest enough to name a flaw, all in one sentence. "Nothing really, I was pretty much left alone" is an answer to hear as a warning about what they expect from your daily-review floor.
Mining the motive and the fit
"Why are you leaving, and what did you do to try to fix it first?" The second clause is the point: performers who left broken floors usually fought for the floor first, asked for the lead-rules fix, proposed the comp adjustment, and the fight's story rings specific. Leavers with no fix attempt at two consecutive stops are pattern candidates.
"What would your last sales manager say you were still working on when you left?" You will verify this literally in the reference call, and say so: "we ask them the same thing." Watch the answer get honest in real time. The alignment between this answer and the manager's later one is itself a integrity measurement.
"What questions do you have for me?" Not a courtesy, a scored item: killers interrogate lead flow, calendar density, attainment rates, and coaching cadence, and the question-quality signal reads their list like a confession of what they optimize for.
Reading answers: the three-layer drill
Whatever the question, strong interviewing applies the same drill discovery applies to prospects: never accept the first answer, because the first answer is the rehearsed one. Layer two: "take me inside one specific example of that." Layer three: "what exactly did you say or do at that moment?" Rehearsed candidates hold up through layer one and go foggy at layer three, real histories get more vivid the deeper you drill, and the fog-versus-vivid gradient is often more informative than any answer's content. Silence works here too: ask, then wait, and let the pause pull out the unpolished second half.
What the interview cannot do
Keep the tool in its lane. The interview mines history, motive, and self-narrative, and even run perfectly it is testimony. Skill lives in the gauntlet, truth lives in verification, and temperament lives in the behavioral signals running silently through the whole process. A candidate who aces this question bank has earned the next stage, never the offer, and the moment interviews start issuing offers directly is the moment your funnel starts hiring its best storytellers again.
Summary
Ask questions that demand mechanisms, specifics, and ownership: the year in numbers, the caused best month, the owned loss, the post-booking sequence, the last coaching received, the fix-before-leaving story, and their questions for you. Drill every answer three layers, let silence work, cross-check against verification and the gauntlet, and treat every great answer as a ticket to the next test, not a verdict.
Frequently asked questions
How long should this interview run?
Forty five minutes covers the bank with drilling. Shorter means you skipped layers, longer usually means you let speeches happen.
Should every candidate get identical questions?
Identical core bank, so answers compare across candidates and feed the rubric, plus follow-ups earned by their specific history. Consistency is what makes the readings mean anything.
Where does this sit relative to the roleplay gauntlet?
Typically after the group interview and before or alongside the gauntlet, and always before verification, since half these answers generate exactly the claims verification exists to check.