Hiring guides
Customer support interview questions that actually predict performance
Most support interview questions test how well someone interviews. These six test the job. What to ask, what a strong answer contains, and the three questions to stop asking.
The Adarna Team
Editors
The standard support interview is a test of interviewing. It rewards people who have rehearsed a story about a difficult customer, which is a skill with almost no overlap with answering forty tickets a day. The fix is not better questions in the abstract. It is questions that make the candidate do a small piece of the actual job, in front of you, where you can score it. Six of those follow, along with what a strong answer looks like and why.
Score against something
Before the questions, the thing that makes them work. Decide what you are scoring before you meet anyone, and score every candidate against the bar rather than against each other. We use four axes, weighted equally: empathy and tone, problem ownership, accuracy and factual care, and written English. Everything below is designed to surface one or more of them.
The six questions
1. "Here is a real ticket from our queue. Write the reply."
Give them an actual message, lightly anonymised, ideally one that is slightly annoyed and slightly ambiguous. Fifteen minutes, written, no help. This single exercise tells you more than the rest of the interview combined, because it is the job. A strong answer acknowledges the emotion in one short sentence and then moves to the problem. It states what happens next with a timeline. It does not over-apologise, and it does not open with three lines of throat-clearing before reaching the point.
2. "What would you need to know before you could answer this one?"
Now give them a ticket that cannot be answered from the information provided. The candidate who confidently answers it anyway has told you something important and expensive. You are looking for the person who identifies the missing piece and says so. This is accuracy and factual care, and it is the axis that protects you from the worst failure mode in support: a confident wrong answer, sent quickly.
3. "Tell me about a time you gave a customer the wrong information."
Note the phrasing. Not "a mistake you made", which invites a rehearsed non-answer about working too hard. This asks about a specific, slightly embarrassing category of error that every experienced support person has committed. A candidate who cannot produce one has either never done the job or is not being straight with you. The good answer includes what they did once they realised, and how fast.
4. "When would you not answer a customer's question?"
Escalation judgement, which is mostly what separates a support hire you can leave alone from one you cannot. Strong answers reach for account security, anything touching another customer's data, refund-policy edge cases, and legal or medical territory. Weak answers treat every question as theirs to solve, which sounds like initiative and is actually risk.
5. "Five people asked the same thing this week. What do you do?"
The difference between a support person and a support ticket processor. The answer you want involves telling someone, not just answering it five times well. This is the trait that turns your support hire into a product feedback channel, and it is almost never tested.
6. "What do you think this company does?"
Blunt, and worth it. You are not testing knowledge, you are testing whether they spent ten minutes on your site. Someone who cannot describe your product in a sentence will not learn it fast enough to be useful in week four. It is also the kindest possible early exit for both of you.
What each one is actually measuring
| Question | Axis it surfaces |
|---|---|
| 1. Write the reply | Written English, empathy & tone |
| 2. What would you need to know | Accuracy & factual care |
| 3. Wrong information | Problem ownership |
| 4. When not to answer | Accuracy & factual care, ownership |
| 5. Five people asked | Problem ownership |
| 6. What do we do | Preparation, and little else |
Three questions to stop asking
- "Tell me about a difficult customer." Every candidate has this answer prepared. You are scoring their preparation, not their judgement. If you want the same information, hand them a difficult ticket instead.
- "Where do you see yourself in five years?" It selects for people who are good at answering it. It tells you nothing about whether they can hold a queue in month three.
- "Are you comfortable working UK hours?" Nobody says no. This is not an interview question, it is a contract term. Put the hours in the job ad, state them again in the offer, and stop pretending the question filters anything.
If a smart candidate could ace it without being able to do the job, it is not an interview question. It is a personality quiz.
The part interviews cannot reach
One honest limit. An interview is a performance under observation, and some of the job is not. Reliability, whether the fortieth ticket of the day gets the same care as the first, whether someone tells you when they are stuck rather than going quiet for two days: none of that shows up in an hour. The only real tests are a paid trial task, a reference from someone who managed them daily, and the first month.
Which is why we structure our own assessment around written work and a recorded live interview rather than a conversation, and score the content rather than the polish. The standard we score against is set out in what good looks like in first-line support.