Key Takeaways:

Most founders make their VP of Sales hiring decision based on resume, energy, and a good interview. None of those things predict whether this person can build what your company actually needs.
The interview is a sales call. The candidate is selling you. Your job is to be the skeptical buyer — asking hard questions and listening for what is and is not in the answers.
The single most important thing to determine before writing a check: are you hiring a Builder or a Driver? One constructs sales systems from scratch. The other optimizes systems that already exist. At $1M–$10M ARR, you almost always need a Builder.
There are ten questions that separate candidates who can do this job from those who cannot. Most founders ask none of them.
A candidate who cannot answer these questions clearly and specifically in the interview will not perform clearly and specifically on the job. What you see in the interview is the best version of what you will get.

The Interview Is the Cheapest Due Diligence You Will Ever Do

Most founders approach the VP of Sales interview like a first date. They are trying to like the person. They want it to work out. They ask broad questions, get broad answers, and leave the room feeling good about someone they have known for forty-five minutes.

Six months and $150,000 later, they are sitting across from me describing how nothing changed. Revenue flat. Pipeline still a mess. Team still winging it. And a VP who is very busy — just not doing the things that move the business forward.

The painful truth is that nearly everything they needed to know was available to them in that interview. They just did not know what to ask.

The interview is the cheapest due diligence you will ever do on this hire. At $200,000+ base salary, every question you fail to ask in the interview costs you real money. Not hypothetical money. Runway.

Here is what I have learned from fifty years on both sides of this conversation — as a founder who hired salespeople, a sales leader who was hired, and a fractional leader who has been brought in to clean up the aftermath of bad hires: the questions that matter most are not on anyone's standard interview template. They are the ones that force a specific, concrete answer — because vague answers in an interview always translate to vague execution on the job.

What you see in the interview is the best version of what you will get. A candidate who cannot answer a direct question clearly in the room will not perform clearly when you are not in the room.

Before the First Question: Know What You Are Actually Hiring For

There are two kinds of sales leaders. Most founders do not know this before they start interviewing, which is why they hire the wrong one.

A Builder creates the machine from scratch. They have written first playbooks, configured CRMs from zero, hired and trained first reps, and built pipelines where none existed. They are comfortable with chaos because they have lived in it. They do not need infrastructure to function — they create it.

A Driver optimizes a machine that already exists. They have improved close rates, scaled teams, refined comp plans, and accelerated pipelines. They are excellent at making a good system better. They have spent most of their careers at companies where someone else had already built the foundation.

At $1M–$10M ARR, with no documented sales process, no functional CRM, and a founder still closing most deals, you need a Builder. Not because Drivers are less capable — they are not. Because a Driver who walks into a company with no system will freeze. They will ask for resources. They will produce strategy decks. They will wait for the infrastructure that has always existed in every other place they have worked — and it will never arrive, because you do not have it yet.

Every question in this article is designed to tell you which one you are talking to.

What You Are Listening For in Every Interview Answer

Builder Signals vs. Driver Signals — One Is Right for Your Stage

BUILDER SIGNALS ✓

Hire this person at $1M–$10M ARR

→ Says "I built," "I wrote," "I created from scratch"

→ Stories start with nothing already in place

→ Gives specific Day 1–30 milestones unprompted

→ Comfortable and specific about what they'll do first

→ Has worked at companies under $10M ARR

→ Asks about your current team and CRM state

DRIVER SIGNALS ✗

Wrong fit for $1M–$10M ARR

→ Says "I scaled," "I optimized," "I led the team"

→ Stories start with a team already in place

→ First 90 days answer is "assess and align"

→ Asks about budget and headcount early

→ Career entirely at companies over $50M ARR

→ Talks strategy before asking about your process

Neither type is wrong. The Builder is wrong for a scaled company. The Driver is wrong for yours.

The Ten Questions That Tell You Everything

Ask all ten. In every VP of Sales interview. Do not skip any because the conversation is going well or the candidate seems impressive. Impressive in a room is not the same as capable in the field.

Question 1

Describe the last time you built a sales process completely from scratch — no existing playbook, no functional CRM, no documented system.

Why You Ask It

This is the most important question on this list. It separates Builders from Drivers faster than anything else. The word "completely" is doing critical work here — do not let them reframe it as "I came in and improved the existing process." That is not what you asked.

Builder Answer"There was nothing. No playbook, no defined stages, reps doing it differently every time. I spent the first three weeks listening to every call and documenting what worked. By Day 30 we had a V1 playbook. By Day 60 the CRM reflected our actual process for the first time."

Driver Answer"I came into a team that had some process but it wasn't optimized. I restructured the pipeline stages and improved the comp plan and we saw a 30% improvement in close rate." — This is optimization. Not building from zero.

Question 2

Walk me through exactly what you will do in your first 30 days. Be specific.

Why You Ask It

A candidate who has done this before will give you a specific, sequenced answer without hesitating. A candidate who has not will give you a strategy. "Assess the landscape" and "align with stakeholders" are not plans. They are ways of sounding busy while avoiding accountability.

Builder Answer"Days 1–5: I listen to every recorded call and ride along on live ones. Days 6–10: I interview every rep and map what they are actually doing versus what they think they are doing. Days 11–20: I write V1 of the playbook. Days 21–30: I configure the CRM to match the real process and start running pipeline reviews."

Driver Answer"I will do a comprehensive assessment of the team, the tools, and the strategy, and put together a go-to-market plan that aligns with where the company wants to go." — No specifics. No sequence. No deliverable by Day 30.

Question 3

Have you ever worked at a company under $10M ARR? What was that experience like?

Why You Ask It

This is not a disqualifier on its own. But if the answer is no — if their entire career has been at scaled companies with established infrastructure — proceed with real caution. The resource constraints, the ambiguity, the founder involvement, the absence of RevOps and marketing support — these are things you either have experience navigating or you do not. You cannot learn them on your first day at a $3M ARR company on your dime.

Strong AnswerDescribes a specific company at your stage or earlier, names the constraints, and explains what they built or did to work around them. The story involves resourcefulness, not resources.

Weak Answer"My smallest company was around $40M ARR when I joined" — or any answer that reveals they have only operated where infrastructure already existed. The skills do not transfer the way they think they will.

Question 4

Show me a Sales Playbook you have written personally. Not contributed to — written.

Why You Ask It

Ask for it in the interview or as a pre-work assignment before the final round. A candidate who has actually built a playbook will either have one ready or will be able to reconstruct a version of one quickly. If they say they cannot share it due to confidentiality, that is fair — ask them to walk you through the structure from memory, section by section. The answer will tell you everything.

Strong SignalCan describe ICP definition, pipeline stages with entry/exit criteria, discovery framework, objection responses, and email templates — in detail, from memory, without notes.

Weak Signal"We had a playbook but I did not personally write it — I contributed to sections of it." Or a description so vague it is clear they are describing a concept, not something they actually built.

Question 5

Tell me about a sales hire you made that did not work out. What happened, and what did you do wrong?

Why You Ask It

How a candidate handles this question tells you more about their character than almost anything else on this list. You are not looking for a perfect track record. You are looking for self-awareness, honesty, and the ability to take ownership of a failure without deflecting blame onto the person they hired. A candidate who cannot name a single bad hire is either inexperienced or unwilling to be honest with you.

Strong AnswerNames the situation specifically, owns their part in it — hired too fast, ignored red flags, failed to set clear expectations — and describes what they changed in their hiring process as a result.

Weak Answer"I hired someone once who turned out not to be a culture fit — but that was really more of a team dynamics issue." The blame goes sideways. Nothing was their fault. Nothing changed.

Question 6

Our founder is still closing most deals. What is your plan for changing that, and what do you need from the founder to make it work?

Why You Ask It

This tells you whether they understand the real problem — founder dependency, not just weak reps. And it tells you whether they have done this specific transition before. Getting a founder out of the day-to-day close is a distinct skill. A candidate who has never done this will give you a generic answer about "empowering the team." A candidate who has done it will describe the specific friction of that transition.

Strong Answer"First I shadow you on every call for two weeks and document exactly how you sell. That becomes the first draft of the playbook. Then I train the reps on your process — not a generic process, yours. And I need you to agree to a rule: you ride along without speaking for the next ten deals. That is the hardest part and most founders resist it."

Weak Answer"I will get the team confident so that you can step back." No methodology. No acknowledgment of the real friction. No ask of anything specific from the founder.

How to Score What You Hear

After the Interview — Score Each Answer Before You Debrief

What They Said

✓ Strong Hire

⚠ Proceed with Caution

✗ Do Not Hire

First 30 days answer

Specific + sequenced

Some specifics, some vague

"Assess and align"

Built from scratch

Clear story, zero start

Partial build, had help

Only describes optimization

Bad hire story

Owns it, changed process

Partial ownership

Deflects / no bad hires

Founder exit plan

Done it, names friction

Understands, no experience

"Empower the team"

If the first 30 days answer is "assess and align" — stop the process. That answer predicts six months of nothing.

Question 7

What metrics will you own, and how will you report on them to me weekly?

Why You Ask It

A sales leader who cannot answer this question concretely before they start is not a sales leader — they are a title. The metrics they name tell you whether they understand the leading indicators that drive revenue, or whether they are focused only on the lagging indicator everyone already knows: closed revenue. Pay equal attention to the second half: how they will report. A great VP wants accountability and will tell you exactly how they plan to keep you informed.

Strong AnswerNames 4–6 specific metrics with context: outbound activity per rep, conversion from discovery to proposal, pipeline coverage ratio, average sales cycle length, and win rate by source. Proposes a specific weekly reporting format.

Weak Answer"Revenue, pipeline, and quota attainment." These are outcomes, not leading indicators. A candidate who only names lag metrics does not understand how to manage a sales team — they only know how to measure its results.

Question 8

What does your coaching process look like? Walk me through how you would develop one of my current reps.

Why You Ask It

Hiring a VP of Sales who cannot coach is hiring an expensive pipeline reviewer. Ask this question and then go quiet. A great answer will be specific, structured, and grounded in real practice: call recording review, role-play cadence, specific feedback methodology, written notes. A weak answer will be philosophical.

Strong Answer"I listen to two recorded calls a week per rep. I score them against a rubric — discovery quality, objection handling, next step close. I give written feedback within 24 hours. We role-play the specific moments that need work before the next live call. Monthly I review trend data per rep. I track whether the coaching is landing."

Weak Answer"I believe in regular 1:1s and creating a culture where reps feel comfortable bringing challenges to me." Good intent. No process. No rigor. No accountability loop.

Question 9

Tell me about a time the team missed quota. What did you do?

Why You Ask It

Every sales leader has had a bad quarter. What they did when it happened is who they are. You are listening for: did they diagnose the root cause or react to the symptom? Did they take ownership or distribute blame? Did they make changes to the process or just push harder on activity?

Strong AnswerDescribes the diagnosis: "The problem was our discovery calls — reps were pitching too early and losing deals at proposal stage." Then the intervention: specific process change. Then the result: measurable improvement in the metric they targeted.

Weak Answer"It was a tough market. We pushed harder on outbound and ran some contests to motivate the team." Activities without diagnosis. Results attributed to effort, not insight.

Question 10

What do you need from me to succeed — and what will you do if you are not getting it?

Why You Ask It

This reveals whether you are about to enter a partnership or a dependency. A great VP needs specific things from a founder: access to customers, realistic targets, clear decision-making authority, and the founder's willingness to step out of the close. The second half of the question — what will you do if you are not getting it — is where most candidates stall. A strong candidate will tell you they will have a hard conversation before things go sideways.

Strong Answer"I need you out of the day-to-day close within the first ninety days. I need a commitment that if I bring a problem to you, we solve it that week — not next month. And if I am not getting what I need, I will tell you directly and immediately. I am not someone who waits until a quarterly review to surface a problem."

Weak Answer"I just need support and buy-in from leadership." Vague. Tells you nothing about whether they will hold up their end or hold you to yours.

The Assignment That Closes the Loop

After the final interview, before you make an offer, give the finalist one assignment. Ask them to spend one week interviewing your entire sales team — every rep, and you — and come back with a written report on what they found.

Here is what this assignment tells you that the interview cannot:

Can they ask good questions and draw out real information from people who have no obligation to impress them?
Do they identify the actual problems in your sales motion — or do they tell you what sounds impressive?
Is the written report specific, organized, and actionable — or polished observations that commit to nothing?
Did they connect with your team? Did your reps feel heard — or interviewed?
How do they handle the assignment itself — do they show up prepared, ask clarifying questions, meet the deadline?

A candidate who cannot do this assignment well will not do the job well. They are showing you exactly how they operate when the stakes are real and the audience is not just you.

If they do it well — if the report identifies real problems, proposes specific solutions, and demonstrates genuine curiosity about your business — you have found your Builder. Make the offer.

The assignment is the cheapest pilot program you will ever run. What you see in that report is what your sales team will see every day for the next twelve months.

Frequently Asked Questions

Q: How many rounds of interviews should a VP of Sales go through before I make an offer?

Three at minimum: an initial screening call, a deep-dive interview using the questions above, and a final conversation that includes the assignment debrief. The screening call tells you whether the conversation is worth having. The deep-dive interview tells you whether they can do the job. The assignment debrief tells you how they think and work when there is no one coaching them through it. Do not skip the assignment. It is the only stage that tests execution rather than self-presentation.

Q: What if the candidate has an excellent resume from a brand-name company but gives weak answers to these questions?

The resume reflects where they have worked. The answers reflect what they can do. At the $1M–$10M ARR stage, where they worked is almost irrelevant. What matters is whether they have built something from scratch and can do it again for you. A weak answer to "walk me through your first 30 days" does not get stronger because it comes from someone who spent five years at Salesforce. Hire the answers, not the logo.

Q: Is it reasonable to ask a candidate for a sample Sales Playbook before making an offer?

Yes — and their reaction to the ask is itself informative. A candidate who has built playbooks before will not be threatened by the request. They will either have one ready with identifying details removed, or they will offer to reconstruct the structure from memory. A candidate who has only used other people's playbooks will often push back, deflect, or produce something so thin it reveals they have never actually written one. The discomfort in that reaction is useful data.

Q: Should I involve my existing sales reps in the interview process?

Yes — at the final round. Your reps are going to be managed by this person. They will pick up on things you cannot: whether the candidate listens more than they talk, whether they ask good questions about the team's day-to-day reality, whether they seem genuinely curious or just performing interest. After the meeting, ask each rep one question: "Would you want to be managed by this person?" Trust their instincts. They have no incentive to be wrong.

Q: What if I cannot afford a full-time VP of Sales right now but know I need sales leadership?

Do not hire one. The all-in cost of a VP of Sales — base salary, OTE, equity, benefits, and recruiting fees — runs $400,000 to $500,000 per year before they have closed a single deal. If you are between $1M and $5M ARR and need someone to build the system, a Fractional Sales Leader is almost always the better answer. You get the same leadership, embedded in your business, at 60–70% less cost, with no long-term commitment and no ramp time. Build the machine first. Hire the VP to run it after it already works.

Not sure if your current VP candidate is a Builder or a Driver?

Let's spend 30 minutes going through what you are hearing in the interviews. I have been on both sides of this conversation for fifty years. I will tell you honestly whether what you are describing sounds like the right hire — or an expensive mistake you can still avoid.

Schedule a 30-Minute Call

About the Author

Louie Bernstein

Fractional Sales Leader with 50 years of sales experience helping $1M–$10M ARR companies build scalable, repeatable sales systems. Founder of MindIQ (INC 500). LinkedIn Top Voice in Sales Management, Sales Operations, and Sales Coaching.

LinkedIn | Subscribe to The Sunday Starter | YouTube