Sales Hiring – The Interview Question Most Founders Forget to Ask
Most founders hire for polish – a slick pitch, a confident handshake, a resume full of wins. But the sales hires who actually last are the ones who know exactly what they did on their worst day, not their best.

The hire that looks right on paper
Most founders can spot a strong resume in sales. Good numbers at the last company, a confident handshake, a story about crushing quota. What's harder to spot is whether that person can sell in your environment, with your product, at your stage.
This is the problem that quietly costs early companies the most money. Not a bad candidate. A good candidate hired for the wrong reason.
The choice founders actually face
When a sales seat opens up, there are usually two candidates in the mix. One has polish: big-company training, a smooth pitch, references who will say all the right things. The other is rougher around the edges but has actually built something from nothing, maybe at a smaller company, maybe in a role that wasn't purely sales.
Founders tend to default to polish. It feels safer. It's also frequently the wrong call in an early-stage business, where there's no brand recognition to lean on and no established process to plug into.
Bradley Hisle, founder of Pinnacle Health Group, has hired sales teams from the ground up more than once. His view is that the skill that matters most isn't the pitch. It's what a person does when the pitch doesn't work.
"Anyone can sell when the product sells itself, and the leads are warm," he says. "What I want to know is what someone does on the tenth cold call of the day, after nine of them went nowhere. That's the actual job."
The question most interviews skip
Here's what gets left out of most sales interviews: a real conversation about failure, not the sanitized version.
Candidates are practiced at answering "tell me about a time you overcame a challenge" with a story that has a clean arc and a happy ending. That story tells you almost nothing. What tells you something is asking a candidate to walk through a losing streak in detail: how long it lasted, what they changed, what they didn't change, and how they knew the difference.
People who have actually sold under pressure can answer this without flinching. People who haven't tend to get vague fast.
What to listen for
A few signals separate candidates worth a second interview from candidates who sound good but haven't been tested:
They can name a specific number, a specific week, a specific thing that wasn't working. Vague answers usually mean the "failure" was minor or invented for the interview.
They describe a change in approach, not just a change in effort. "I just pushed harder" is not the same as "I changed how I opened the call."
They talk about what they learned about themselves, not only about the market. Self-awareness under pressure is rare, and it's the thing that predicts whether someone burns out six months in.
Why this gets skipped
Founders skip this question for a simple reason: it takes longer, and hiring for a sales role is usually happening because the founder is already stretched thin and needs the seat filled. The instinct is to move fast on someone who interviews well.
Hisle's approach runs the other way. He treats the hiring conversation as the first test of whether someone can handle direct, sometimes uncomfortable feedback, because that's exactly what the job requires every day. A candidate who gets defensive when asked to go deep on a failure is showing you, in real time, how they'll react to a manager's feedback six months from now.
What it costs to get this wrong
The cost of a bad sales hire isn't just the salary. It's the pipeline that goes cold while that person is learning the job, the relationships with early customers that get mishandled, and the months it takes to recognize the mismatch and start over. In a small company, one bad hire in a revenue-generating seat can set momentum back for a full quarter or more.
The fix isn't a longer interview process or more rounds. It's one better conversation, aimed at the part of the job that actually determines whether someone lasts.
A practical version of the question
Founders who want to try this don't need a formal framework. A simple version works: "Tell me about the worst stretch you've had in a sales role. How long did it last, and what did you actually change?"
Ask a follow-up if the answer stays general: "What was the specific number before, and what was it after?" Candidates who've lived it will have the numbers. Candidates who haven't will start speaking in generalities about attitude and mindset.
It's a small change to an interview process, and it takes maybe ten extra minutes. What it buys is a much clearer picture of who's actually built for the seat, before the paycheck starts and the pipeline is on the line.









