Interview scorecard for sales roles, with anchors for each competency
On this page
- The six competencies this scorecard covers
- The scorecard template
- Anchors for each competency
- A five-minute role-play that tests three competencies at once
- A filled example
- Weighting this scorecard
- Adjusting for role type
- Mistakes specific to sales scorecards
- Comparing candidates across a sales requisition
- Questions people ask
A sales interview scorecard has to score things a generic competency list misses: whether a candidate actually uncovers a buyer's problem before pitching, how they handle a real objection rather than a rehearsed one, and whether their forecast numbers can be trusted. Below is a copy-ready scorecard built around six sales-specific competencies, each with a 1–4 anchored scale, plus a short role-play script and a filled example.
For a printable version you can edit, start the scorecard builder from its sales preset.
This uses the same 1–4 structure as interview scorecard template; what is different here is entirely the competencies and their anchors, written for a quota-carrying sales role rather than a general interview loop.
The six competencies this scorecard covers
- Discovery and qualification. Does the candidate ask open questions to understand a buyer's situation before proposing anything?
- Objection handling. Do they engage with a real objection or deflect it with a scripted rebuttal?
- Closing process. Do they have a repeatable way to move a deal to a decision, or do they wait for the buyer to decide when to buy?
- Forecasting honesty. Can they explain their pipeline math, including deals they correctly called as unlikely to close?
- Resilience after a loss. How do they talk about a deal they lost, and what changed afterward?
- Territory or account planning. Do they have a method for prioritizing where to spend time, or do they work whatever comes in first?
The scorecard template
Candidate: [name] Role: [title]
Interviewer: [name] Stage: [screen / role-play / final]
Competency: Discovery and qualification
Score (1-4): [ ]
Evidence: [specific questions or examples the candidate gave]
Competency: Objection handling
Score (1-4): [ ]
Evidence: [the objection used and how they responded]
Competency: Closing process
Score (1-4): [ ]
Evidence: [their described process, or role-play behavior]
Competency: Forecasting honesty
Score (1-4): [ ]
Evidence: [how they categorize and explain their pipeline]
Competency: Resilience after a loss
Score (1-4): [ ]
Evidence: [the loss they described and what changed after]
Competency: Territory or account planning
Score (1-4): [ ]
Evidence: [their method, or absence of one]
Overall recommendation: [Strong yes / Yes / No / Strong no]
What would change this recommendation: [ ]Anchors for each competency
Discovery and qualification
| Score | Anchor |
|---|---|
| 1 | Jumps to product features within the first minute of a role-play, with no questions about the buyer's situation. |
| 2 | Asks a few questions, but they are closed ("Do you use a CRM today?") rather than open, and the pitch follows regardless of the answer. |
| 3 | Asks open questions that uncover a specific problem and its business impact before proposing anything. |
| 4 | Uncovers a problem the buyer had not fully articulated themselves, and reflects it back before moving forward. |
Objection handling
| Score | Anchor |
|---|---|
| 1 | Responds to a price or timing objection by immediately discounting or backing off, with no attempt to understand the objection first. |
| 2 | Gives a rehearsed rebuttal that does not address what the interviewer specifically raised. |
| 3 | Asks a clarifying question about the objection, then responds to what was actually said. |
| 4 | Reframes the objection into the underlying concern and addresses that directly, without being defensive. |
Closing process
| Score | Anchor |
|---|---|
| 1 | Cannot describe how they typically move a deal forward, or says they wait for the buyer to bring it up. |
| 2 | Describes asking for the sale, but with no mitigation for a buyer who stalls or goes quiet. |
| 3 | Describes a repeatable process: a next step proposed at the end of every conversation, with a mutual close plan for larger deals. |
| 4 | Describes identifying and addressing a stalled deal's real blocker (budget, a missing stakeholder) rather than just following up repeatedly. |
Forecasting honesty
| Score | Anchor |
|---|---|
| 1 | Describes their pipeline in terms of hope ("this one feels good") with no defined stages or criteria. |
| 2 | Uses stage names but cannot explain what moves a deal from one stage to the next. |
| 3 | Explains clear criteria for each forecast category and can name a deal they correctly downgraded before it slipped. |
| 4 | Describes a specific case of pushing back on their own optimism or a manager's pressure to inflate a number, and why. |
Resilience after a loss
| Score | Anchor |
|---|---|
| 1 | Blames the loss entirely on the buyer, price, or competitor, with no reflection on what they controlled. |
| 2 | Acknowledges a factor they controlled but describes no change in behavior afterward. |
| 3 | Names a specific loss, what they missed, and a concrete change they made in the next deal. |
| 4 | Describes a pattern noticed across multiple losses and a change to their process, not just their behavior in a single deal. |
Territory or account planning
| Score | Anchor |
|---|---|
| 1 | Works whichever lead came in most recently, with no stated method for prioritizing. |
| 2 | Has a rough sense of which accounts matter but cannot explain the criteria. |
| 3 | Describes specific criteria (deal size, fit, urgency signals) used to prioritize a territory or account list. |
| 4 | Describes building or reshaping their own territory plan based on data they gathered themselves, not just criteria handed to them. |
A five-minute role-play that tests three competencies at once
Give the candidate this scenario and play the buyer yourself. It surfaces discovery, objection handling and closing in a single exercise, which is harder to rehearse than three separate questions about each.
Scenario given to the candidate: "I'm the head of operations at a 200-person company. We're using a spreadsheet to track this today and it mostly works, though it's getting painful. I have fifteen minutes. Go."
As the buyer, use these moves in order:
- Give a vague answer to their first question ("it's fine, just a bit slow sometimes") and see if they push for specifics.
- Once they propose something, raise a real objection: "This looks like it would cost more than what we're paying now."
- If they handle that, stall: "This sounds good, let me think about it and get back to you."
What to watch for: whether they get past your vague first answer to a specific cost of the current process, whether they ask what "more" is being compared to before responding to the price objection, and whether they propose a specific next step rather than accepting "let me think about it" as an answer.
A filled example
An invented candidate, screened for a mid-market account executive role:
Discovery and qualification — 3. Asked what the spreadsheet process was costing in hours per week before mentioning the product. Did not uncover who else the decision would need to involve, so did not reach a 4.
Objection handling — 4. On the price objection, asked "compared to what you're paying today, or compared to the cost of the errors you mentioned?" before responding, which reframed the comparison correctly.
Closing process — 2. Accepted "let me think about it" without proposing a specific next step or timeline.
Forecasting honesty — 3. Described a clear stage-to-stage definition and gave an example of downgrading a deal from "commit" to "best case" after a champion went quiet.
Resilience after a loss — 3. Named a loss to a lower-priced competitor and said they now ask about budget range earlier instead of at proposal stage.
Territory or account planning — 2. Said they work leads in the order their CRM assigns them, with no independent prioritization.
Overall recommendation: Yes, with a note. Strong on discovery and objection handling; the closing process gap is coachable and worth a specific 30-day goal rather than a reason to pass.
Weighting this scorecard
For most quota-carrying roles, weight discovery and qualification and objection handling highest: weak performance there tends to produce deals that discount heavily or churn, which shows up months after the hire, not in the first quarter. Forecasting honesty matters more the larger the deal size and the more a sales leader relies on the number for planning. See weighted interview scorecard for how to set and total weights with the arithmetic shown; the short version for this role is to avoid weighting closing process above discovery, since a candidate who closes without having qualified well is a forecasting risk, not a strength.
Adjusting for role type
| Role type | Adjustment |
|---|---|
| SDR or BDR | Drop closing process and forecasting honesty; add a cold-call role-play and a competency on handling rejection volume. |
| Enterprise account executive | Add multi-stakeholder navigation as a seventh competency; extend the role-play to include a second "buyer" playing a skeptical stakeholder. |
| Account manager or customer success with a renewal quota | Replace discovery with a competency on spotting expansion or churn risk signals in an existing account. |
| Sales leader or manager candidate | Add a competency on coaching: give them an invented rep's deal notes and ask how they would coach that rep, not how they would run the deal themselves. |
Mistakes specific to sales scorecards
| Mistake | Why it fails | Fix |
|---|---|---|
| Scoring only on stated quota attainment | Attainment is shaped by territory and market, not just skill | Score how they reason about their numbers, not the numbers themselves |
| No role-play, questions only | Rehearsed answers about discovery are easy to give without the skill | Use the five-minute role-play above, even briefly |
| Treating an aggressive close as automatically a strength | Confuses pressure with a repeatable process | Score whether the close addressed a real blocker, not just persistence |
| No competency for forecasting honesty | A confident pitch says nothing about whether their pipeline numbers can be trusted later | Include it explicitly, with the anchors above |
| Same scorecard used for SDR and enterprise AE roles | The two roles need different skills at different depths | Adjust per the role-type table above |
Comparing candidates across a sales requisition
Once several candidates have this scorecard filled in, line up their evidence for each competency side by side before ranking, rather than comparing overall recommendations directly. See how to compare candidates after interviews for a decision matrix that works the same way for a sales requisition as for any other role, once the competencies and anchors are role-specific like the ones above.
Questions people ask
Should quota attainment numbers from a resume count as part of the score?
Use them as context, not as a score input. Attainment depends heavily on territory, quota-setting and market conditions you cannot verify in an interview. Score how the candidate reasons about their numbers instead: whether they can explain a miss, a stretch quarter and their pipeline math in detail.
How do I score a candidate who has never sold this specific product before?
Score the transferable competencies (discovery, objection handling, closing process) at full weight, and treat product or industry knowledge as a separate, lower-weighted line or a training-plan conversation rather than a disqualifier, unless the role has no ramp time built in.
Is a role-play necessary, or can discovery skill be assessed through questions alone?
Questions alone can surface how a candidate talks about discovery, but a short role-play (even five minutes, using a simple scenario) shows whether they actually ask open questions under a bit of pressure instead of pitching immediately. Most sales scorecards that skip the role-play end up scoring rehearsed answers.
Should sales scorecards weight closing higher than discovery?
For most B2B roles, no. Weak discovery produces a candidate who closes deals that later churn or discounts to win, because they never understood what the buyer actually needed. Weight discovery and qualification at least as heavily as closing.