What Sales Representative Interviews Actually Test

Who actually interviews you

For most commercial roles the first conversation is a recruiter or an internal talent screen, checking basic fit and comp expectations. The interview that matters is with the hiring sales manager — regional sales manager, area manager, head of sales, whatever the title — because that person has a number to hit and is deciding whether you help or hurt it. For enterprise or field sales roles you'll often then meet a panel: the sales manager, a VP of Sales or Commercial Director, and sometimes a sales engineer or solutions consultant if the product needs technical support during the sales cycle. Smaller companies substitute the founder for the VP. Some processes add a peer interview — an existing rep who will sit near you or share the same territory — partly for fit, partly because peers ask questions managers forget to.

What rarely happens: a generic HR-only process with no one who carries quota in the room. If nobody in your interview loop currently owns a number, that's worth noting, because it usually means the practical assessment will be weak too.

The roleplay: what it's actually checking

Most sales interviews include a live exercise, not a written test. The classic version is a cold call or discovery call roleplay: the interviewer plays a prospect, sometimes a named persona in your target vertical, and you run the first few minutes of a call. This is not about polish. It's checking whether you ask questions before pitching, whether you listen to the answer and adapt, and whether you can handle a stall ("we're happy with our current supplier") without either caving or steamrolling.

A second common format: present a deal you actually closed, end to end, including numbers — deal size, sales cycle length, number of stakeholders, why it nearly fell through. A manager who does this for a living can tell within a minute whether you're recounting a real deal from memory or reconstructing a plausible-sounding one. Real deals have odd details: a procurement delay, a champion who left mid-cycle, a discount you had to fight internally to get approved.

A third: a 30-60-90 day plan or territory plan, sometimes as a take-home, sometimes live on a whiteboard. This tests whether you understand how to build pipeline from a cold or half-built book of business — how you'd segment a territory, what your prospecting cadence looks like, how many meetings you think it takes to hit quota given a stated average deal size and close rate. If you've never had to reason backwards from quota to activity volume, this exercise will show it.

For SDR/BDR roles specifically, expect a written cold email or a short outbound call recording exercise instead of a full discovery roleplay — they're testing message quality and objection handling in miniature, not deal management.

The questions that aren't small talk

Some questions sound conversational but are doing real diagnostic work.

"Walk me through your last deal, from first contact to signature." This isn't an invitation to tell a nice story. It's checking whether you can narrate a sales process in order, name the qualification framework you used (MEDDIC, BANT, SPIN, or whatever your last employer ran on), and identify the moment the deal could have died.

"What was in your pipeline at the start of last quarter, and what happened to everything that didn't close?" This tests pipeline honesty. A rep who only remembers the wins hasn't been managing a real pipeline. A rep who can tell you three deals slipped because procurement cycles ran long, one was lost to a competitor's pricing, and one they should have disqualified two months earlier is showing you they actually run their CRM rather than just logging activity into it.

"How did you know this was a real opportunity and not just interest?" This is a qualification question in disguise. Weak answers describe enthusiasm ("they seemed really keen"). Strong answers describe budget, authority, need, and timeline — or whatever qualification language your discipline uses — and give a concrete example of a deal they walked away from because it didn't qualify.

"Tell me about a forecast you got wrong." Every experienced rep has one. If someone claims their forecast accuracy has always been near-perfect, that's not a good sign — it usually means they sandbox, or they've never been held to account on a number in front of a VP.

"How do you handle a champion going quiet mid-cycle?" This tests whether you have an actual multi-threading habit — do you have a second contact, does your champion have internal cover, do you know who signs off — rather than relying on one relationship and hoping.

On tools: if the job specifies Salesforce, HubSpot, Outreach, Salesloft or Gong, expect a direct question about how you used it, not whether you've heard of it. "How did you structure your stages in Salesforce?" or "What did you use Gong for beyond call recording?" separates people who've actually lived inside a CRM from people who've logged into one.

What a shallow answer sounds like

To someone who runs a sales team, a shallow answer has a specific texture. It's the STAR-format story with no numbers in it: no deal size, no cycle length, no quota percentage, no close rate. "I always exceed my targets" without a figure attached is a claim, not evidence — a hiring manager will usually just ask directly, "what was your attainment last year?", and a rep who hesitates or rounds vaguely has told them something.

It's also the answer that only mentions wins. Every rep loses deals; that's the job. A candidate who can't describe a specific loss and why it happened either hasn't been tracking outcomes or is editing the story. Similarly, an answer to "how do you qualify a deal" that stays at the level of "I make sure they're a good fit" without naming what a good fit actually means — budget range, decision-making structure, timeline — reads as someone who has heard the word qualification without having built the habit.

On the roleplay specifically, the giveaway is pitching before asking anything. A rep who launches straight into features when asked to run a discovery call is showing the interviewer exactly what they do on a real call with a real prospect, and it isn't discovery.

Last thing worth naming: fluency with the company's own product or market. If the advert names a vertical — mid-market SaaS, medical devices, industrial distribution — and a candidate can't say anything specific about how buying decisions get made in that space, that's a gap the interviewer will register even if they don't say so.

What to do next

Before the interview, pull your last four to six quarters of numbers: attainment, average deal size, cycle length, and at least two lost deals with the actual reason they were lost. Write out, in one paragraph, how you qualify a deal and what framework — if any — you use, because you will be asked to defend it live. If the role names a CRM or sales engagement tool, be ready to describe specifically what you did in it, not that you've used it. For the roleplay, practise asking questions for the first two minutes before you say anything about the product — that's usually the entire test.

jobmarket.pro reads the advert for you, checks it against your actual sales record — quota history, tools, sector — and tells you plainly where you fit and where you don't before you spend an evening on the application.