You already have the skill that decides most sales job interviews. You use it every week, with customers. Then you walk into your own interview and switch it off. You start presenting.

That is the mistake. A sales interview is not a pitch. It is a discovery call. And at that table, you are the salesperson, not the applicant. Once you see it that way, you stop reciting your CV and start doing the exact thing you get paid to do.

Why treating a sales interview like a pitch costs you the offer

Most candidates prepare for an interview the way they would prepare a product demo. They line up what they want to say about themselves, then run through it feature by feature, number by number. No good salesperson opens a first customer meeting with the demo. They run discovery. They ask, they listen, they understand the problem before they say a word about their own solution.

Your interview works the same way. The only difference is that this time the solution is you. Candidates who understand that have a structural advantage. They do not need to learn anything new for the interview. They just need to do what they are already paid for. Very few actually do it.

The three sales moves that win a job interview

It comes down to three moves: diagnose, qualify, close. All three are lifted straight from your own sales process, run one round earlier.

1. Diagnose before you present

Most candidates answer every question with their full biography. A good salesperson asks first. What is the biggest problem in this team right now? What does success in this role look like in twelve months? Where did the last person fall short? Only once you know that do you position yourself — not against an abstract job description, but against the real problem the hiring manager has to solve. That is the difference between a candidate looking for a role and one offering a solution.

2. Qualify the role the way you qualify a deal

In enterprise sales you check every deal. Is the budget real? Is there a champion? Is the need genuine or just a pleasant conversation? In interviews most people forget all of that and slide into the role of the supplicant. But you are assessing too. Ask about the team's real priorities. Ask the person across from you what keeps them at the company. That does not read as arrogance. It reads as someone used to testing deals instead of taking every one that comes along. People want the person who does not say yes to everything.

3. The conversation itself is your demo

The person across from you, recruiter or hiring manager, cannot fully test your technical depth in forty-five minutes. What they can judge is how you run the meeting. Are you clear? Do you listen, or wait for your turn to talk? Do you stay composed when an uncomfortable question lands? That is the real test. If you sweat here, why would a CISO believe you can sell a seven-million platform in a room full of skeptics? You are running the customer meeting live. Run it well.

One practical note: when people are nervous, they speed up. Fast talking reads as unsure. Speak more slowly than feels right. People who are in control are not afraid to take their time.

The small moments most candidates give away

The conversation never starts with the first technical question. It starts with a casual "How are you?" Most people answer on reflex — "Fine, thanks" — and hand back the easiest chance to build a relationship. You would not open a customer meeting cold with the price list. You warm the room. Use those thirty seconds. A small human note and you stop being a sheet of paper and become someone worth spending an hour with.

Then there is the next step, obvious in sales and almost always forgotten in interviews. A good salesperson never leaves a meeting without a next step. Do the same here. Ask at the end: what do the next steps look like, and does this fit from your side? Afterward, send a short, specific message that ties back to something you discussed. Not as a courtesy. Because that is how you run every deal.

How to prepare without sounding rehearsed

A lot of candidates overcook this part. You do not need a script. People hear a script in the first sentence, and it proves the opposite of what is being tested — your ability to read the room and react. What you need are examples. Go through the job description, look at which skills are asked for, and have one concrete example from your own work ready for each. Not memorized. Just within reach.

A real example: two candidates, one offer

Some time ago I had two candidates for an enterprise account executive role at a cybersecurity vendor in the DACH region. Anonymized, of course.

Candidate A was the stronger one on paper. Strong numbers, big logos. But in the conversation he presented. Every question got the full biography. He did not ask a single question back. The VP Sales feedback was short: "He read me his CV. I still don't know if he can sell."

Candidate B was weaker on paper. But he ran the conversation like a discovery call. His first question back was: "Before I talk about myself, what's the biggest blocker in the team right now?" The VP talked for ten minutes. Then Candidate B mapped his examples exactly onto that problem. At the end he asked about next steps and, that evening, sent a short message with one concrete thought on that exact blocker.

The feedback was one sentence: "That's the guy I want in front of customers." Candidate B got the offer. Not because he knew more. Because in the interview he proved the thing he was going to be paid for.

Three things to take into your next interview

• Diagnose before you present. Ask about the real problem behind the role before you position yourself. Then position against that, not against the job ad.

• Qualify the role the way you qualify a deal. You are assessing too. Someone who tests rather than begs comes across as composed — and is.

• Never leave without a next step. Ask about the process and follow up with something concrete, exactly as you would after any good customer meeting.

The job rarely goes to the best presenter. It goes to the one who runs the conversation like a good deal: calm, curious, with a clear next step. That is not an interview technique. It is your job, one round earlier. Master that and you master this.

FAQ

How should a salesperson prepare for a job interview?

Skip the script. Go through the job description, identify the skills being tested, and prepare one concrete example from your own work for each. Keep them within reach rather than memorized, so you can match them to the problem the hiring manager actually raises.

What questions should I ask in a sales interview?

Ask diagnostic questions before you talk about yourself: What is the biggest problem in the team right now? What does success in this role look like in twelve months? Where did the last person fall short? Then ask what keeps your interviewer at the company. You are qualifying the role the same way you qualify a deal.

Why does treating an interview like a discovery call work?

A recruiter or hiring manager cannot fully test your technical depth in forty-five minutes, but they can see how you run the meeting. Running it like a discovery call — diagnose, qualify, close — shows them directly what you would do in front of their customers, which is exactly what they are hiring for.

Work with Nordh Executive Search

I'm Jan Nordh, founder of Nordh Executive Search. For 19 years I've run executive search in cybersecurity, enterprise software, and AI infrastructure across the DACH region and the Nordics, after 25 years in enterprise sales myself. If you want to sharpen your own positioning for a senior sales role, reach out on LinkedIn or at nordh.de.