Sales Interview Questions to Ask Candidates: 8 Evidence Checks
Ask eight job-related sales interview questions, inspect concrete work and compare evidence. Includes a fictional B2B exercise and clear limits.
By Miljan @ Lead Scorer 8 min read
Useful sales interview questions to ask candidates should reveal how someone approaches the work your role requires. Ask for a specific situation, the candidate's own actions, the evidence behind a decision and what they would change. Agree on the job and evaluation criteria before the interview; a persuasive answer is not proof of future sales performance.
This employer guide offers eight questions, observable follow-ups and a fictional work sample for a B2B seller. It helps you compare evidence before hiring. The sales onboarding plan addresses the next stage, after someone joins.

Define the work before choosing the questions
A first seller who must discover a repeatable motion needs a different brief from an account executive handling established demand. Write down the customer situation, sales cycle, available pipeline, support and decisions the person will own. A revenue target alone does not describe that work.
Choose job-related capabilities you can actually examine: understanding a buyer's problem, prioritizing accounts, investigating missing information, explaining evidence and recording commitments. If you need to clarify who the team serves, use an ideal customer profile before inventing a candidate test.
Make the assignment realistic about the resources supplied. A candidate should not be evaluated as if they have a mature demand engine when the founder is still testing the offer. Separate skills needed on arrival from skills the company will teach. This makes an interview brief more useful than a list of impressive former employers.
What the podcast evidence supports
In the June 2026 Crew Podcast interview, Granola sales leader Bardia Shahali discusses hiring people whose experience fits the company's operating stage. He also describes probing beyond a candidate's stated enthusiasm for a product by asking how they use it and adjacent tools. Those are accounts of his practice and judgment, not a published validation study.
He recounts an SDR sending a short video explaining an approach to Granola's market. It stood out to him. That does not establish that video production, charisma or access to a particular tool predicts job performance. The transferable question is whether a candidate can explain relevant work and the reasoning behind it.
Becc Holland's August Sales Talk for CEOs interview emphasizes understanding the buyer's work rather than learning only the seller's product. Our application to hiring is to examine customer reasoning alongside product fluency. Neither speaker tested the questions or example exercise below.
Eight sales interview questions, with evidence to examine
1. Which part of this role resembles work you have done, and which part would be new? Ask the candidate to describe the actual customer, deal stage and support available in a relevant example. Examine the comparison with your role. A familiar company name is not enough to establish comparable responsibilities.
2. Tell us about a buyer problem you initially misunderstood. What changed your understanding? Ask what the buyer said or did, what was inferred and which subsequent action changed. Look for a traceable distinction between observation and interpretation. Do not reward a dramatic story merely because it sounds memorable.
3. In a deal you can discuss without confidential details, what work did you personally own? Separate the candidate's actions from the team's contribution and existing market demand. Ask how the outcome was observed and which facts remain unknown. A large contract value alone cannot explain individual contribution.
4. What would you clarify before agreeing to demonstrate this fictional product? Give everyone the same brief with a buyer request and some missing context. Examine which uncertainties the person notices and why they matter. A useful discovery question should serve a decision, rather than demonstrate knowledge of a named methodology.
5. How would you respond when a buyer asks for proof your team does not yet have? Ask for a response, a proposed check and a record of the unresolved claim. Examine whether the candidate distinguishes known capability from an expectation. Do not treat confidence or an invented guarantee as evidence of commercial judgment.
6. Describe a tool you use: what job does it help with, and when would you use a different approach? Probe the workflow, inputs, review and limits. This adapts Shahali's interest in understanding actual use. Evaluate job-relevant reasoning rather than loyalty to a brand or the cost of the candidate's personal software access.
7. If AI prepared a prospect brief or message, how would you check it? Supply a fictional brief containing an unsupported claim. Ask the candidate to identify what can be verified, what should be removed and what needs a question. Keep tool permissions and available materials consistent; this is a reasoning exercise, not permission to contact real prospects.
8. Tell us about feedback that changed a repeatable part of your sales work. Ask what was changed, how it was applied and what evidence was available afterward. A claim of being coachable is less informative than an example someone can explain. Do not assume that one improvement proves a universal method.
Use a small, bounded work sample
Here is a fictional exercise for a role that includes prospect research and discovery. Provide a short product description, two fictional account notes and a buyer's request for a demo. Include a missing dependency and one unsupported benefit claim. Explain the task, time allowance, permitted tools and evaluation criteria in advance.
Ask for an account choice, the questions needed before the meeting and a brief reply to the buyer. Then ask the candidate to walk through the decisions. Keep the scope small enough to discuss; it should not produce unpaid outreach or a usable campaign for your business.
A polished reply that repeats the unsupported benefit needs investigation. A less polished reply that flags the uncertainty may show relevant reasoning worth exploring. Compare the observed work against the stated role, not an imagined perfect response. Make reasonable arrangements so the format does not become an unrelated obstacle.
Do not require a video because a video impressed a podcast guest. A written example or live explanation can explore the same reasoning when appropriate. If tool use is part of the role, define the relevant task and review standard instead of turning ownership of a subscription into a hiring criterion.
Keep an evidence record rather than an overall impression
For each capability, record the question, observed answer or artifact, interpretation and unresolved follow-up. Use the same agreed criteria across comparable candidates. Keep “not observed” distinct from “did not demonstrate”: an interview that never covered a capability cannot establish its absence.
The US Office of Personnel Management's structured-interview guidance describes predetermined questions and common rating standards. This is a methodological reference, not a claim that this editorial worksheet is a validated selection instrument or US legal advice.
If more than one interviewer is involved, have each record their observations before discussing differences. Revisit disagreement against the brief. Do not let an unexplained “culture fit” label replace evidence of relevant work. The hiring decision remains a human responsibility informed by the full, appropriate recruitment process.
Use the interview to improve the role brief too
Repeated confusion can reveal an unclear assignment or unrealistic expectations. Distinguish that from a candidate's knowledge gap. If every exercise requires resources your company does not supply, revise the role before interpreting the results.
Preserve the job expectations that mattered in the interview and carry them into onboarding. Your sales playbook can then document the recurring decisions and support available. A hiring worksheet does not replace training, management or a workable offer.
Sources and limits
- Bardia Shahali, The Crew Podcast, June 2026: hiring-stage fit, product-use probes and the candidate video he recounts; full archived transcript used.
- Becc Holland, Sales Talk for CEOs, August 2026: buyer-work knowledge; full archived transcript used.
- OPM, structured interviews: method reference.
The questions and work sample are editorial examples. No hiring success rate, causal improvement, candidate ranking or current vendor capability is claimed. A job-relevant explanation is evidence to examine, not a guarantee of future results.
Frequently asked questions
What sales interview questions should employers ask?
Ask about comparable work, buyer problems, individual contribution, missing evidence, tool use and learning from feedback. Connect each question to a capability the role actually requires.
How do you evaluate a sales candidate’s answers?
Record the observed answer, its relevance to the job and what remains uncertain. Use common criteria across comparable candidates rather than relying on an overall impression.
Should a sales interview include a work sample?
A small fictional task can make reasoning observable when it reflects the role. Explain the scope, tools and criteria in advance, and avoid requesting real unpaid outreach.
Does a strong interview predict sales performance?
It provides evidence for a recruitment decision, not a guarantee. The podcast anecdotes and editorial questions here do not establish a hiring success rate.
How should AI be used in a sales interview exercise?
If relevant to the job, define consistent permissions and ask the candidate to verify a supplied claim. Human interviewers remain responsible for interpreting the evidence and the recruitment process.