VP of Sales Interview Questions That Actually Work

Most VP of Sales interviews test for confidence, not competence. That's part of how 8 of 10 first-time VP of Sales hires fail, often within 11 months. The fix isn't a longer list of questions, it's the right five: how they built a team from scratch, how they forecast without lying to themselves, how they'd review a rep's pipeline live, what a losing quarter actually taught them, and what they'd do in your first 90 days. Ask those well, with follow-ups that force specifics, and you'll separate operators who've done the job from talkers who've described it.

Key takeaways

• 8 of 10 first-time VP of Sales hires fail, most within 11 months, which means the interview carries more weight than the resume.
• The single highest-signal question is about recruiting, not selling: roughly half of the job is building and hiring the team, so ask them to name it, not describe it.
• A candidate who can't walk you through a specific forecast miss, with the number and the cause, hasn't managed a real number before.
• A live pipeline review, using a sample deal list, surfaces more about judgment in 15 minutes than three rounds of behavioral questions.
• Reference checks matter more for this hire than any other GTM role, because the failure mode is usually the team, not the close rate, and that never shows up in the room.

What questions actually predict VP of Sales performance?

Most VP of Sales interviews spend an hour on questions any competent operator has answered a dozen times: "Tell me about your biggest win," "How do you motivate a team," "Where do you see the sales org in three years." These questions select for people who interview well, which is a different skill from running revenue. The candidates who fail at month nine are frequently the ones who were most polished in round one.

Five questions do almost all the work. Everything else is color.

"Walk me through the last sales team you built." Not managed, built. You want headcount, hire dates, who you'd rehire tomorrow, and who you'd never hire again. A candidate with a real answer rattles off names and numbers without checking notes. A candidate without one talks about "culture" and "ownership" in the abstract.

"Tell me about a quarter you missed, and the specific number you were off by." Everyone has a win story ready. Few have rehearsed the miss. Listen for whether they owned the call that caused it, or reached for the market, the product, or a rep who "didn't execute."

"Here's a sample pipeline. Which three deals worry you and why?" Give them a real (anonymized) or representative pipeline and 15 minutes. This is the closest thing to watching them do the job. Weak candidates ask about deal size. Strong candidates ask about last activity date, champion seniority, and what changed since the deal was created.

"What would you do in your first 90 days here, specifically?" Push past "listen and learn." You want a real sequence: who they'd sit with in week one, what they'd audit, when they'd make their first people decision.

"What's the worst hiring mistake you've made, and how did you catch it?" This is the recruiting question's mirror image. It tests self-awareness about the exact skill that determines whether your revenue org compounds or churns.

How do you test whether they can build a team, not just run one?

Push for specifics the way you would in a reference check, except now. Ask for the headcount they inherited versus the headcount they left behind. Ask what percentage of their hires they'd make again, and what they'd change about how they hired the ones they wouldn't. A candidate who answers in percentages and names is describing a real org. A candidate who answers in adjectives is describing a story.

The uncomfortable follow-up worth asking: "Who did you have to let go, and how long did it take you to make that call?" Slow, avoidant answers here are a preview of how long underperformance will sit on your team once they're running it.

One more useful probe: ask them to describe the sourcing channel for their best two hires. Referral, agency, inbound applicant, cold outreach on LinkedIn. Candidates who've actually built teams from scratch, at a company your size, usually sourced most of their best reps themselves rather than waiting on a recruiting function they don't have yet. That's a meaningfully different skill set than inheriting an established team and optimizing it.

What should you ask about forecasting and pipeline discipline?

Forecasting questions catch more bad hires than closing-story questions, because forecasting is where confidence and accuracy diverge. Ask for a specific number they committed to the board, what they actually delivered, and what they changed in their process afterward. If every forecast they describe was hit or beaten, either they've never carried real accountability or they're not telling you the whole story.

Then get concrete about method: how they weight stage, recency, and champion strength; whether they forecast bottom-up from reps or apply a haircut to whatever the CRM says; how often they update the board mid-quarter when the number moves. Vague answers here predict the same vagueness once they're running your board updates.

A useful stress test: ask what they do when a rep's forecast and their own gut disagree by more than 20%. Strong candidates describe a specific reconciliation process, usually a deal-by-deal review with the rep before the number goes anywhere near the board. Weak candidates say some version of "I trust my reps" or "I go with my number," both of which mean they don't actually have a process.

What's different about interviewing for a $5M company versus a $30M one?

The questions stay mostly the same. The bar for the answers moves. At $1M to $3M ARR, the right hire is still hands-on: writing call scripts, sitting in on deals, closing personally when needed. At $20M-plus, you need someone who has run a multi-segment or multi-motion org, because the coordination problem is bigger than any one person's quota. If a candidate's best team-building story tops out at 4 reps and your plan requires 25, that's a stage mismatch, not a talent problem. Our guide on when to hire a VP of Sales covers the readiness signals in more depth, and the VP of Sales salary guide has current comp benchmarks by stage and region so you're not anchoring the offer on an outdated number.

How should you structure the interview process so it doesn't waste everyone's time?

Five stages, capped at three to four weeks end to end. Longer than that and you lose strong candidates to faster processes; shorter and you skip the parts that actually predict performance.

Notice references sit last, not first. Everything before that stage is designed to generate specific, checkable claims. A reference call against a vague interview just confirms the vagueness.

On references specifically: ask the candidate to provide two to three former direct reports, not just peers or their old boss. Peers and bosses talk about strategy and presence. Direct reports talk about whether the person actually coached them, whether comp plans were fair, and whether they'd follow them to another company. That last question, "would you work for this person again," asked plainly, tends to surface more truth than anything else in the whole process. A hesitant answer or a long pause is worth more than a glowing one.

What red flags should end the process early?

A few patterns are worth ending on the spot, even mid-interview. Vague team-building answers that never resolve into names, dates, or numbers when you push. Zero questions about equity or vesting, which at the venture stage usually means they either don't understand startup comp or haven't done real diligence on your business. A one-size-fits-all playbook pitched without a single question about your ICP, motion, or stage. And any answer that blames the market, the product, or "the previous CEO" for every miss they've had, with no version where the call was theirs to make.

None of these are disqualifying on their own if a candidate is otherwise strong and self-aware about it. Strung together, they're the same pattern that shows up in the 11-month exits: someone who talked well in the room and had never actually built the thing they described.

One more worth watching for: a candidate who spends the interview selling you on the role instead of asking questions about your ICP, your current pipeline health, or why the last person in the seat left. A VP of Sales is supposed to be good at reading a room and diagnosing a situation before acting. If they can't do that about the job in front of them, in the one hour they have the most incentive to try, they won't do it for your revenue org either.

If you're interviewing for the individual-contributor layer under this hire at the same time, the questions and the bar are different; our breakdown on how to interview enterprise AEs covers that separately.

FAQ