70% of first-time VP Sales hires don't make it past 12 months, and the interview is where hiring committees try to find out in advance which side of that number you're on. Here's exactly what gets asked about how you built your team, what the numbers underneath your revenue story actually are, and how to answer the board-level question without flinching.
When we prep VP Sales candidates for a client interview, these are the four areas every serious hiring committee probes, in some order. Pull the specifics from your own CRM and comp history before the interview, not from memory in the room.
Who was rep one, what pipeline looked like in month one versus month twelve, and what you'd change if you did it again. Specific names and months, not a summary.
Attainment before you arrived versus 12 months after, rep-level attrition (voluntary and involuntary, separated), and average ramp time to full quota.
How close your committed number landed versus actuals, plus one specific quarter where you missed your own forecast and why.
What was broken about it, what you changed, and what it did to behavior, not just to revenue.
| Question | Weak answer | Strong answer |
|---|---|---|
| "Tell me about your team." | "We grew from 5 to 20 reps and tripled revenue." | "I hired reps one through five myself, rewrote the comp plan in month four because it over-rewarded logo count over ACV, and the 3x revenue followed from that, not the other way around." |
| "What was your rep attrition? | "Pretty low, people liked working for me." | "18% annualized, all but one involuntary — I moved fast on two reps in their first 90 days who weren't hitting activity benchmarks, which kept the rest of the team's bar high." |
| "How accurate was your forecasting?" | "I always hit my number." | "Within 8% of commit for five of the last six quarters. I missed Q3 by 22% because I over-weighted a single enterprise deal in commit instead of best-case — I changed my forecast methodology the next quarter to require two independent confirmations before a deal counts as commit." |
| "Walk me through a quarter you missed." | "The market was tough and pipeline dried up." | "We missed by 15% because two reps were still ramping and I'd under-hired for the back half of the year. I flagged it to the board four weeks out with a specific recovery plan, not at quarter close." |
Every strong answer has the same shape: a specific number, a specific mechanism behind it, and a specific decision you made. That's the pattern hiring committees are actually listening for — see the Builder's Standard breakdown below for exactly why.
Most VP Sales interviews at the Series A/B stage include some version of: "Walk me through how you'd present this quarter to the board if you missed by 15%." This question isn't really about the miss, it's about whether you own outcomes or just report them. A hiring committee is testing whether you'd surface a problem four weeks out with a recovery plan attached, or wait until quarter close and explain it after the fact.
The candidates who get the offer don't claim a perfect track record, they name the specific quarter that went wrong, the specific mechanism behind it, and the specific thing they changed afterward. That's a far more useful signal than four quarters of green, because it shows me how they think under pressure instead of how a market happened to behave.
Revenue growth under your leadership is real evidence, but on its own a hiring committee can't tell if you built the engine or inherited one that was already running and kept adding headcount to it. The fix isn't to downplay the revenue number, it's to lead with the mechanism: who you hired, what you changed about the comp plan or process, and what broke along the way. The revenue number becomes the proof of a story you've already told, not a claim you're asking the interviewer to take on faith. For the client-side version of exactly this distinction, see how Beacon's Builder's Standard screens for it.
Walk me through building your sales team from zero: who was rep one, what did pipeline look like in month one versus month twelve, and what would you change. A builder answers with names, specific months, and a real mistake. Someone who inherited a working team gives a vague, outcomes-only answer because they were never close enough to the mechanics to remember the details.
State the number, separate voluntary from involuntary, and name the specific cause for each. A VP who fired two underperformers in month three and can explain exactly why reads as more credible than one who claims zero turnover, because zero turnover on a growing team usually means low standards, not great management.
Expect to be asked for your forecast accuracy over the last 4 to 6 quarters, how you build a forecast (rep-level commit and best-case rolled up, or top-down), and a specific quarter where you missed your own forecast and why. Hiring committees use this to test whether you actually run the business or just report a number someone else rolls up.
Lead with how you built the team, then let the revenue number follow as evidence. "Revenue grew 3x" on its own is a story a hiring manager cannot verify in the room. "I hired reps one through six myself, rewrote the comp plan in month four because it over-rewarded logo count, and revenue grew 3x as a result" is a number with a mechanism behind it, which is what the interview is actually testing for.
Expect something like "Walk me through how you'd present this quarter to the board if you missed by 15%." Strong answers name the specific driver (rep ramp, a stalled segment, a comp-plan gap), what's already been done about it, and a committed recovery plan with a number attached. Weak answers describe the miss without a cause or a plan, which reads as someone who reports results rather than owns them.
Join the candidate network and we'll privately match you to unlisted VP Sales roles when your track record fits, no cold applications required.
Join the network