# Sales interview questions for the hiring manager: how to test CRM habits and pipeline honesty before the offer

https://salesbond.app/blog/sales-interview-questions-hiring-manager-crm-habits/
Published: 2026-10-20 · Updated: 2026-10-20

The sales interview questions worth asking as a hiring manager test habits, not stories: how a candidate describes their open pipeline, what they log and when, how they handle next steps and lost deals, and how early they tell a manager a deal is slipping. Score each answer with what you heard, not a number. Below is the questionnaire we use: twelve questions in four blocks, each with a good answer, a weak one, and what it tells you about the first ninety days.

This is for the interviewer hiring a rep (not a sales manager), usually the same person who runs the pipeline review and closes the biggest deals. Most of what ranks for this search is written for the candidate. The top result, [Salesforce’s sales interview questions page](https://www.salesforce.com/blog/sales/sales-interview-questions/), covers what to expect, how to prepare, ten common questions with sample answers and a few questions to ask the interviewer. Useful if you’re the one being hired. Very little of it tells the manager what to listen for.

## Why most sales interview questions test the story, not the habits

“Walk me through your biggest win” has a rehearsed answer. So do “how do you handle rejection” and “sell me this pen”. We’ve written about [why the hardest-deal story mostly tells you about the candidate’s last employer](https://salesbond.app/blog/interview-sales-rep-closed-deal-exercise-pipedrive/); the short version is that you end up grading the polish.

What a small team actually suffers from after a hire is duller. Deals with no next step. A pipeline that looks fine on Monday and empties on the thirtieth. Notes that say “good call” and nothing else. Nobody tells a story about the field they didn’t fill in, so the questions below ask about the dull things on purpose. They take about twenty-five minutes and go before any exercise. It’s our method, not a study, so keep what fits.

![One-page card of 12 interview questions in four blocks, each block labelled with what it tests](https://salesbond.app/wp-content/uploads/2026/10/sales-interview-questions-hiring-manager-crm-habits-2.png)

## Block 1: how they describe their pipeline

Open with the pipeline. Every candidate thinks they’re ready for it, and almost nobody is ready to be specific.

1. “Describe your current open pipeline. How many deals, what stages, what’s closing this month?” A good answer has numbers and hesitation in the right places: “around fourteen open, four in proposal, two I’d call this month, one of those I’m not sure about”. A weak answer is a total (“about 400k”) with no shape, or a refusal to estimate at all. You are not checking the numbers. You are checking whether this person carries a picture of their pipeline in their head, because a rep who does will keep the CRM close to that picture.
2. “Pick one deal you expect to close this month. Why do you believe that?” The answer we want names a buyer action: “they asked for the security questionnaire and the signer is on the Thursday call”. The answer that worries us names a feeling: “they’re really engaged, great rapport”. Our piece on [sales forecast accuracy for small teams](https://salesbond.app/blog/sales-forecast-accuracy-small-teams/) explains why we forecast from buyer actions and not from rep sentiment. In the interview you only need to notice which one you heard.
3. “Which deal in your pipeline should probably be marked lost, and why haven’t you done it?” Every honest rep has one. The good answer admits it quickly and gives a reason about the buyer (“they’ve gone quiet since the budget meeting, I’m giving it one more call on Friday”). The weak answer is “none, they’re all live”, which is rarely true, or a reason about the rep’s own number. This question does more work than any other on the list. It shows you how the candidate will behave in your pipeline review when a deal is dying and the month is short.

## Block 2: questions about CRM habits

Here is where interviews usually go vague (“I’m very organized, I’m diligent with the CRM”). Push past the adjective and ask for the mechanics.

1. “After a call, what do you write down, and where?” Listen for a shape: outcome, what the buyer said, the next step, when. Listen for whether it goes into the CRM or into a notebook that gets “transferred later”. Both answers can come from a good rep. Only one of them survives a a busy week. A long, elaborate answer usually means a template that dies by week two; we’d rather hear a short, fixed shape.
2. “When do you update the CRM: as you go, end of day, or before the pipeline review?” Any of the three can work. What you’re listening for is whether the answer is true. “Immediately, always” from a rep who takes six calls a day is a claim, not a habit. “End of day, and I block fifteen minutes for it” is a habit. “Before the pipeline review” is honest too. It also tells you the CRM will be a week old most of the time, and you can decide whether you accept that.
3. “What’s the field you skip most often, and why?” The field doesn’t matter much. What matters is whether the candidate can answer at all. A rep who says “probably lost reason, because by then I just want it gone” has told you something true and fixable. A rep who says “I fill in everything” doesn’t want to talk about it, and that’s what you’ll be dealing with in month three.

## Block 3: next steps and lost deals

This block checks follow-up discipline: whether a stalled deal gets a dated action from this person, and whether their lost-reason notes would tell you anything true.

1. “A proposal has been out for ten days with no reply. What’s your next activity, exactly?” We’re listening for an action with a date and a person: “call the champion Thursday, ask whether the owner has seen it”. “Follow up” is not an answer. “Send a check-in email” is barely one. The specific version is what this person will type into the next step field on your deals, and its the difference between a pipeline you can manage and one you can only hope about.
2. “Tell me about a deal you lost. What was the real reason, and what did you log as the reason?” The second half is the test. A good answer notices the gap: “I logged ‘price’ but honestly we never got to the decision maker”. A weak one has no gap, because the logged reason and the real reason are both “price” and nothing was learned. You’re not judging the loss. You’re judging whether this person can write down an uncomfortable reason, since your lost-reason field is only as useful as the reps who fill it in.
3. “How long does a deal sit with no activity before you either act on it or close it?” We don’t care about the number. We care that there is one. “Depends” is the worrying answer. “Two weeks, then I call, and if nothing, I mark it lost and set a reminder for the quarter” is the kind of rule a rep builds after getting burned, and those rules hold.

## Block 4: working with a manager

Most hiring managers skip this block. It predicts more about your own week than the other three.

1. “A deal you forecast as closing this month starts slipping. When do you tell your manager, and how?” Early and plainly is the answer we want: “as soon as the signer misses a meeting, I’d flag it in the pipeline review and move the date”. The answer that worries us is “I’d try to fix it first”. Listen also for whether the candidate moves the close date or quietly leaves it. The second habit turns every forecast you run into fiction.
2. “What did your last manager do in pipeline reviews that was useful, and what wasn’t?” A candidate with an opinion here has sat through real reviews. “Useful: asking me what the buyer’s next step was. Not useful: reading every deal aloud” comes from someone who will show up to your review prepared. “They were great, very supportive” comes from someone who wasn’t paying attention, or who is being careful, and either way you learn little. If you’re still designing your own review rhythm, the [meeting cadence for a small sales team](https://salesbond.app/blog/sales-meeting-cadence-small-team/) is the structure we run these questions against.
3. “When was the last time you asked for help on a deal, and what did you ask for?” Specific help is the good sign: “I asked my manager to join the pricing call because the CFO wanted a discount I couldn’t give”. No example at all, or “I don’t really need help”, tells you the candidate will manage your perception of thier deals instead of the deals. In a team of four, that costs more than a weak closer does.

## What you heard, and what it usually means

We don’t score these answers with points. Twelve questions on a one-to-five scale give you a number that looks like a decision and is really twelve guesses added up. Instead, in the ten minutes after the interview, write one line per block: what you heard, in the candidate’s words where you can, and what it means for how they’ll run your deals. After two or three candidates, the lines compare themselves.

Four answers carry the most weight for us. This is our reading, not a rule set, so disagree where your team is different.

“They’re all live” on question 3 usually means a rep who will defend dying deals in your pipeline review. The forecast runs hot, and you find out at month end.

“Follow up” as the next step on question 7 means deals will sit. Someone will notice eventually. It’ll be you.

On question 8, a candidate who volunteers that the logged reason and the real one were different is rare. Hire-worthy, almost on its own: that person’s lost-reason data will be worth reading.

“I’d try to fix it first” on question 10 sounds like ownership. In practice you hear about the slip on the last day of the month.

One warning on calibration. A candidate from a large team with a sales ops function may give weaker Block 2 answers because someone else policed the CRM for them. We wouldn’t rule them out for that. Say it out loud in the offer conversation, so “the CRM is yours here” isn’t a surprise in week one. And if the habits still haven’t shown up a few months in, a [performance improvement plan for a small team](https://salesbond.app/blog/sales-performance-improvement-plan-small-team/) is the next conversation.

## After the interview: the closed-deal exercise as the second round

The questionnaire tells you what candidates say about their habits. It can’t show you what they do with a live record, and a determined candidate can rehearse even the dull questions. So anyone who passes this round gets a second one, built on a real closed deal from your own CRM; the setup is in [interview a sales rep with one of your own closed deals](https://salesbond.app/blog/interview-sales-rep-closed-deal-exercise-pipedrive/). The twelve questions go first because they’re cheaper: twenty-five minutes, no preparation, and they screen out the people for whom the exercise would waste an afternoon.

A disclosure, since this whole article is about CRM habits: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It doesn’t evaluate candidates and won’t tell you whom to hire. Its part starts after the offer. Deal Health checks every deal in the connected CRM against a set of rules. Each problem it finds comes with the reason, so the habits you interviewed for are visible in the record a month later instead of assumed. If you want to see what your current team’s record looks like before the new rep arrives, [check your CRM with SalesBond](https://salesbond.app/).

Got a candidate on the calendar this week? Print the twelve questions, leave a blank line under each block, and write down what they actually say.