Skip to content
Resume Studioby M2Toolkit

8 role-specific questions

Sales & Customer Support Interview Questions & Answers

Sales and support interviews test how you discover needs, handle objections, build pipeline and hit targets — or, in support, how you calm frustrated customers and resolve problems for good.

Free, no sign-up. 53 questions in this role's practice pool, including behavioural, HR and situational questions.

Sales & customer support interview questions

Prospecting, discovery, objections, closing, customer service, de-escalation and targets.

  1. 1.

    Sell me this pen.

    BeginnerProblem solving

    What the interviewer is evaluating

    Whether you discover needs before pitching.

    Key points a strong answer covers

    • Ask questions first. Ask questions to understand the buyer's needs first.
    • Tie to their need. Tie the product's benefits to what they said.
    • Handle objections. Handle objections.
    • Close. Ask for the sale or next step.

    Suggested answer structure

    1. Restate the problem and your assumptions.
    2. Break it into steps and reason out loud.
    3. Check your answer against an edge case.
    4. Summarise the result and what you'd verify next.

    Common mistakes

    • Launching straight into features of the pen.
    • Never asking for the sale.

    Likely follow-up questions

    • What if I say I don't need a pen?
    • How would you sell it to a CFO versus a student?
    Example strong answer

    Before I tell you anything about the pen, can I ask a few questions? When did you last use a pen? — Signing a contract this morning. — Is signing documents a big part of your role? — Most days, and with clients. — What does a pen say about you when you sign in front of a client? — Fair point, it should look professional. — So if you had a pen that writes smoothly first time, feels substantial and looks the part in a client meeting, would that be useful? This one is weighted metal, with a refillable cartridge, so you'll never be caught borrowing a cheap one. — Isn't that more than I'd pay for a pen? — It is more than a disposable one, but it's refillable, so over a year it costs less than the packs you keep replacing. Shall I put one aside for you, or would a box of two be better — one for the office and one for your bag?

    Practise this question and get feedback
  2. 2.

    How do you run a discovery call with a new prospect?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Consultative selling.

    Key points a strong answer covers

    • Prepare. Research the company and person first.
    • Open questions. Ask open questions about their situation and challenges.
    • Qualify. Qualify: need, budget, decision process, timeline (BANT/MEDDIC).
    • Listen & quantify pain. Listen and quantify the pain and its impact.
    • Agree next steps. End with a clear, agreed next step.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Talking more than the prospect.
    • Ending without a next step.

    Likely follow-up questions

    • How do you qualify out a prospect politely?
    • What's MEDDIC?
    Example strong answer

    I research the company and the person beforehand — their role, recent news, likely priorities — and set an agenda at the start of the call. Most of the call is open questions: how they handle the process today, what's not working, what that costs them, and what happens if nothing changes. I listen more than I talk and quantify the pain — 'so about 15 hours a week of manual reconciliation?' — because that builds the business case later. I also qualify: who else is involved in the decision, how they buy, budget and timing — using a framework like MEDDIC for complex deals. I finish by summarising what I heard and agreeing a specific next step in the calendar, or qualifying them out honestly if it's not a fit.

    Practise this question and get feedback
  3. 3.

    How do you handle the objection 'It's too expensive'?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Objection handling without discounting by reflex.

    Key points a strong answer covers

    • Acknowledge & explore. Acknowledge it and explore what's behind it.
    • Reframe on value. Reframe on value and the cost of the problem.
    • Options. Offer options — scope, phasing, terms — before discounting.
    • Avoid reflex discounting. If you discount, trade it for something.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Immediately offering a discount.
    • Arguing with the customer.

    Likely follow-up questions

    • What if their budget really is fixed?
    • How do you prevent price objections earlier in the process?
    Example strong answer

    I acknowledge it and find out what it means, because 'too expensive' can mean over budget, more than a competitor, or not yet convinced of the value. So I'd ask, 'Compared to what?' or 'If price weren't an issue, is this the right solution?' If it's value, I go back to the numbers we uncovered in discovery: they said the manual process costs around £60,000 a year in staff time, and our solution is £18,000, so it pays back in under four months. If it's genuinely budget, I'd look at options — a smaller starting scope, phasing, or different payment terms. If I do give a discount, I trade it for something, like a longer commitment or a case study.

    Practise this question and get feedback
  4. 4.

    Tell me about a time you missed a target. What did you do?

    IntermediateBehavioural

    What the interviewer is evaluating

    Accountability and resilience.

    Key points a strong answer covers

    • Ownership. Take ownership — no excuses.
    • Analysis. Analyse why with data.
    • Actions. The specific changes you made.
    • Result. The result afterwards.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Blaming the market, product or territory.
    • No concrete change in behaviour.

    Likely follow-up questions

    • What early warning signs did you miss?
    • How do you manage your pipeline now?
    Example strong answer (a fictional story — use your own)

    In my second quarter as an account executive I hit 72% of quota. Looking at my pipeline afterwards, the problem was clear: I had plenty of early meetings but too many deals stalled after the demo, because I hadn't identified the real decision-makers. I changed two things. I started mapping the buying group in discovery and asking explicitly who else needed to be involved, and I set aside two hours a day for prospecting so my pipeline had more coverage. I also asked our top performer if I could listen to her calls. The next quarter I closed at 108%, and my demo-to-close rate went from 18% to 27%. I now review pipeline coverage weekly instead of at the end of the month.

    Practise this question and get feedback
  5. 5.

    How do you deal with an angry customer?

    BeginnerRole knowledge

    What the interviewer is evaluating

    De-escalation and service recovery.

    Key points a strong answer covers

    • Listen without interrupting. Let them explain without interrupting.
    • Empathise & apologise. Acknowledge their frustration and apologise for the experience.
    • Own & solve. Take ownership and offer a concrete solution.
    • Follow up. Follow up to confirm it's resolved.
    • Stay calm / learn. Stay calm, and feed the root cause back to prevent repeats.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Arguing about whose fault it was.
    • Promising something you can't deliver.

    Likely follow-up questions

    • What if the customer is abusive?
    • What if you can't give them what they want?
    Example strong answer

    I let them explain fully without interrupting — people need to feel heard before they can listen. Then I acknowledge how they feel and apologise for the experience: 'I'm sorry — being charged twice and then waiting three days for a reply is really frustrating.' I take ownership rather than passing them around, and tell them exactly what I'll do and when: 'I've refunded the duplicate charge now; you'll see it in three to five working days, and I'll email you the confirmation.' I only promise what I can deliver, and I follow up to make sure it's resolved. Afterwards I log the root cause so the team can fix it. If someone becomes abusive, I stay calm, set a boundary and follow our policy.

    Practise this question and get feedback
  6. 6.

    Which metrics matter in customer support, and how would you improve them?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Operational understanding of support.

    Key points a strong answer covers

    • Satisfaction. CSAT, NPS, customer effort score.
    • Speed. First response and resolution times against SLAs.
    • Resolution quality. First-contact resolution, reopen and escalation rates.
    • Improvement levers. Knowledge base, better macros, training, fixing root causes.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Optimising handle time at the expense of quality.
    • Ignoring the reasons customers contact support.

    Likely follow-up questions

    • How do you reduce ticket volume without hurting satisfaction?
    • Why can average handle time be misleading?
    Example strong answer

    I look at satisfaction — CSAT after each interaction and customer effort score — speed — first response time and time to resolution against our SLAs — and quality — first-contact resolution, reopened tickets and escalations. Handle time matters for staffing, but pushing it down too hard hurts quality. To improve, I'd analyse contact reasons: the top few categories usually drive most volume, and many can be prevented by fixing the product or explained with a good help article. Then better macros and training for complex topics, and routing tickets to the right specialists so customers aren't transferred around. I'd share the top contact reasons with the product team monthly.

    Practise this question and get feedback
  7. 7.

    How do you build a pipeline through prospecting?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Outbound discipline: targeting, personalisation and consistent activity.

    Key points a strong answer covers

    • Ideal customer profile. Define the ideal customer profile and target accounts.
    • Research & personalisation. Research and personalise with relevant triggers.
    • Multi-channel cadence. A multi-channel cadence of calls, emails and LinkedIn.
    • Consistent activity. Consistent, time-blocked daily activity.
    • Measure & refine. Track reply and meeting rates; refine messaging.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Generic copy-paste messages to huge lists.
    • Prospecting only when the pipeline is empty.

    Likely follow-up questions

    • What does a good cold email look like?
    • How many touches before you stop?
    Example strong answer

    I start with a clear ideal customer profile — industry, company size, the role that feels the problem — and build a list of target accounts. For each, I do a few minutes of research to find a relevant trigger: a new hire, funding, expansion, or something they've posted. Outreach is a multi-channel sequence over two to three weeks — calls, short personalised emails focused on their likely problem rather than our product, and LinkedIn — about six to eight touches before I pause. I time-block prospecting every day, so the pipeline never runs dry, and I track reply and meeting rates by message and segment in the CRM, so I can keep improving what works.

    Practise this question and get feedback
  8. 8.

    Why do you want to work in sales (or customer support)?

    BeginnerHR

    What the interviewer is evaluating

    Motivation and self-awareness.

    Key points a strong answer covers

    • Genuine motivation. A genuine, specific motivation.
    • Relevant strengths. Relevant strengths like resilience and listening.
    • Evidence. Evidence from experience.
    • Link to this role. Link to this role and company.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Saying it's only about the money.
    • Generic answers like 'I'm a people person'.

    Likely follow-up questions

    • How do you handle rejection?
    • What do you know about our customers?
    Example strong answer

    I enjoy helping people solve a real problem, and I like that sales makes the result clear and measurable. In my retail job I was consistently in the top three for sales of premium accessories, and what I enjoyed most wasn't the closing — it was asking questions and figuring out what someone actually needed, then seeing them leave happy. I'm also resilient: a 'no' doesn't stay with me for long, and I treat it as information. Your product helps small businesses get paid faster, which is a problem I've seen first-hand in my family's business, so I could talk about it with genuine conviction.

    Practise this question and get feedback

Behavioural & HR questions you'll also get

These come up in almost every sales & customer support interview. Story questions are best answered with STAR — Situation, Task, Action, Result.

  • Tell me about yourself.

    BeginnerHR

    What the interviewer is evaluating

    Whether you can give a concise, relevant pitch that frames your experience around this job.

    Key points a strong answer covers

    • Present. Start with your current role and what you do.
    • Relevant past. Pick the most relevant past experience.
    • Strength / achievement. Include one strength or achievement with evidence.
    • Why this role. Finish with why this role is the next step.

    Suggested answer structure

    1. Present — your current role in one or two sentences.
    2. Past — the experience most relevant to this job.
    3. Proof — one achievement or strength with evidence.
    4. Future — why this role is the logical next step.

    Common mistakes

    • Reciting your whole CV chronologically.
    • Personal life story unrelated to the job.
    • Going over two minutes.

    Likely follow-up questions

    • Why are you looking to leave your current role?
    • What would your manager say is your biggest strength?
    Example strong answer

    I'm a front-end developer with four years' experience, currently at a fintech start-up where I build the customer dashboard in React and TypeScript. Before that I spent two years at an agency building e-commerce sites, which taught me to work fast with lots of different clients. The thing I'm proudest of recently is leading our move to a shared component library, which cut the time to build new screens by about a third. I'm now looking for a role where I can work on a larger product with a strong design system, which is exactly what drew me to this position.

  • Why should we hire you?

    BeginnerHR

    What the interviewer is evaluating

    Whether you understand the role and can match your strengths to its needs with evidence.

    Key points a strong answer covers

    • Role's needs. Show you understand what the role needs.
    • Matching strengths. Match two or three strengths to those needs.
    • Evidence. Back each with evidence.
    • Enthusiasm. Close with genuine enthusiasm.

    Suggested answer structure

    1. Name the two or three things the role needs most.
    2. Match each with your experience and evidence.
    3. Add what makes you different.
    4. Finish with genuine interest.

    Common mistakes

    • Generic claims like 'I'm hardworking' with no evidence.
    • Comparing yourself to other candidates you don't know.

    Likely follow-up questions

    • What would you do in your first 90 days?
    • What's one area where you'd need support?
    Example strong answer

    From the job description and our conversation, you need someone who can take ownership of the customer onboarding process, work with sales and product, and improve the numbers. I've done exactly that for three years: at my current company I redesigned onboarding for new accounts and cut the time to first value from 14 days to 6. I'm comfortable working across teams — I run a weekly session with sales and product on customer feedback — and I'm very data-driven, so I'd measure everything from day one. I'm also genuinely excited about your product, because it solves a problem I've seen customers struggle with.

  • Tell me about a time you disagreed with a teammate. How did you handle it?

    BeginnerBehavioural

    What the interviewer is evaluating

    Handling conflict constructively and keeping relationships.

    Key points a strong answer covers

    • Listened to their view. Show you listened to understand their view.
    • Used facts / common goal. Bring it back to facts or a shared goal.
    • Resolution & relationship. Resolve it and keep the relationship.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Making the other person the villain.
    • A story where you were simply right and they gave in.

    Likely follow-up questions

    • What if you couldn't reach agreement?
    • Have you ever been wrong in a disagreement?
    Example strong answer (a fictional story — use your own)

    On a website rebuild, a senior designer wanted an animated, image-heavy homepage, and I was worried it would hurt mobile load times and SEO. As the developer responsible for performance, I needed us to agree before the sprint started. I asked her to walk me through what she was trying to achieve — she wanted the brand to feel premium. I built two quick prototypes, one with her full design and one with lighter animations, and we tested both on a mid-range phone together. Hers took nearly six seconds to load. We agreed on a version that kept the key animation but lazy-loaded the rest. The page launched loading in under two seconds, and she later asked me to review designs earlier. I learned that testing together beats debating.

  • Tell me about a mistake you made and what you learned.

    BeginnerBehavioural

    What the interviewer is evaluating

    Honesty, accountability and learning.

    Key points a strong answer covers

    • Real mistake owned. Own a real mistake.
    • Fixed it. Show how you fixed it and who you told.
    • Changed behaviour. Show what you changed afterwards.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Choosing a fake mistake like 'I work too hard'.
    • Blaming others.

    Likely follow-up questions

    • How did your manager react?
    • How do you know you haven't repeated it?
    Example strong answer (a fictional story — use your own)

    In my first year as a marketing coordinator, I sent a promotional email to our whole list with the wrong discount code — I'd tested the email but not clicked the code itself. Within an hour customers were complaining that it didn't work. I told my manager immediately, set the wrong code to apply the discount too, and sent a short correction email with an apology. We lost very little revenue, and some customers replied thanking us for the quick fix. Since then I use a pre-send checklist that includes testing every link and code as a customer would, and I asked for a second person to check any campaign to more than 10,000 people.

  • Describe a situation where you worked under pressure or to a tight deadline.

    BeginnerBehavioural

    What the interviewer is evaluating

    Prioritisation, composure and delivery.

    Key points a strong answer covers

    • The pressure. Make the pressure concrete.
    • Prioritised. Show how you prioritised.
    • Communicated. Show how you kept people informed.
    • Delivered. Show the outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Glorifying working all night as the solution.
    • No mention of prioritising.

    Likely follow-up questions

    • What would you do if it was clear you couldn't make the deadline?
    • How do you stop pressure affecting quality?
    Example strong answer (a fictional story — use your own)

    Two days before a client presentation, our analyst fell ill and I had to finish the market research report she'd been leading. I listed everything left and asked the account director which sections the client cared about most — pricing and competitor comparison. I focused on those, reused verified data from our previous report, and moved the appendix to a follow-up email. I sent a short update each evening so nobody was surprised. We delivered the core report on time, the client approved the next phase, and the appendix followed two days later. I learned to ask early what matters most rather than trying to do everything equally well.

  • What would you do if you realised you were going to miss a deadline?

    BeginnerSituational

    What the interviewer is evaluating

    Transparency and problem solving.

    Key points a strong answer covers

    • Tell people early. Flag it as soon as you know.
    • Assess the gap. Work out how far off you are.
    • Options. Offer options: reduced scope, help, a new date.
    • Prevent repeats. Learn why it happened.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Waiting until the deadline to say anything.
    • Promising you'll just work all night.

    Likely follow-up questions

    • What if your manager is unavailable?
    • Has this happened to you?
    Example strong answer

    I'd tell the person depending on it as soon as I realised, not at the deadline. Before that conversation I'd work out how far off I am and why, so I could offer options: delivering the most important part on time and the rest a few days later, getting help from a colleague, or agreeing a new date. Then I'd let them decide what works best for them, and keep them updated. Afterwards I'd look at why it slipped — usually underestimating something — so I plan better next time.

Ready to answer them out loud?

Run a timed sales & customer support mock interview, type or speak your answers, and get a score breakdown with what to improve.

Interview questions for related roles