Support hiring interview kit

A hiring kit for a frontline support role (associate, rep, or specialist). It covers the whole loop: define what "good" means before you meet anyone, screen fast, put candidates in front of a realistic ticket, probe the values that don't show up on a resume, and score everyone the same way so the decision isn't a vibe.

The centerpiece is the ticket-response exercise. Most support hires fail on judgment and tone under pressure, not on interview polish — so the best signal comes from watching someone actually do the work, not describe it.

Adapt the wording to your product and channels, but keep the shape: one scorecard, structured questions, a real work sample, and independent scoring before anyone talks.

The loop at a glance

Keep the whole loop under two weeks end to end. Good support candidates get hired fast; a slow loop loses your top pick, not your bottom one.

1. Role scorecard

Write this before you post the role. It's the single standard every interviewer scores against, so decide what matters now — not after you've met a charming candidate and started bending the bar.

Pick your three must-haves. These are the competencies you will not compromise on; a strong candidate weak in any one of them is a no-hire, however likeable.

Panel prep:

• Scorecard written and agreed before the role was posted
• The three must-haves are named and everyone accepts them as hard gates
• Each competency is owned by at least one interviewer who will probe it
• Product knowledge is treated as trainable — you're hiring for judgment and temperament, not for knowing your product on day one
• Panel agreed on the bar, not just the questions ("what would a 3 vs a 4 look like here?")

2. Resume / application screen (5 min)

You're filtering, not deciding. Spend five minutes and move on.

Look for:

• The cover note or application answers are clearly written — this is a writing job
• Any customer-facing or high-accountability experience (retail, hospitality, teaching, healthcare all count)
• Signs of ownership: "handled," "resolved," "was the person who…"
• They followed the application instructions (attention to detail is the job)

Don't screen out for:

• No prior support title — great reps come from everywhere
• Employment gaps or a non-linear path
• No degree, if the role doesn't genuinely need one

Real red flags (not cosmetic ones):

• Sloppy, error-riddled writing with no care taken
• Blames every past employer or customer
• Can't say anything specific about why this role or company

3. Screening call — questions (25 min)

A quick two-way filter: can they hold a clear conversation, and do they actually want this job? Ask the question, then stay quiet and listen for the italicised signal.

1. "Walk me through what a good day in a support role looks like to you." Listen for: helping people and solving problems, not just "quiet queue." A realistic picture of the work beats an idealised one.

2. "Tell me about a time you helped someone who was upset or confused. What did you do?" Listen for: a specific story, calming actions, and what the customer got — not just "I stayed calm."

3. "Describe something technical you had to learn on your own. How did you go about it?" Listen for: resourcefulness and self-teaching. Support is constant learning; you want someone who enjoys it.

4. "What do you do when you don't know the answer to a customer's question?" Listen for: find out, ask, verify — not guess. This is your first honesty check. A confident bluffer here is a warning.

5. "What's pulling you toward this role specifically?" Listen for: something real about the work, the product, or the team — not just "I need a job" or "I'm good with people."

6. Logistics, plainly: schedule and hours, comfort with written channels, notice period, salary expectations.

Advance if: clear communicator, at least one specific customer story, honest about not-knowing, and genuinely interested. Any two missing → don't advance.

4. Ticket-response exercise

This is where you get real signal. Give the candidate two tickets and ask them to write the replies they'd actually send, plus a one-line internal note on what they'd do behind the scenes. Take-home (45 min, sent back written) or live (share the ticket, let them type while you watch — better signal, more nerves; say "think out loud, don't rush").

Setup you give them:

"You've just joined our support team. Here are two tickets from your queue. Write the reply you'd send to each customer, exactly as they'd receive it. Under each reply, add a one-line internal note: what you'd check, do, or escalate behind the scenes. You can ask me clarifying questions — noticing what's missing is part of the job."

Ticket A — the frustrated billing customer

Tests tone under fire, honesty, and whether they read the account before reacting.

Subject: This is the THIRD time I've been charged

I cancelled my Pro plan back in March and you've charged me $49 AGAIN today. That's three months in a row now. I want all three charges refunded and this account closed for good. I've wasted enough time on this already.

Context you provide (in the account, or when asked):

• The customer downgraded to Free on March 3 — that part is done.
• A separate subscription, "Pro Analytics add-on" ($49/mo), is still active and was never cancelled. That's what's been charging them.
• You're authorised to refund up to 3 months without a manager.
• There are no prior tickets visible on the account.

What to look for:

• Acknowledges the frustration first and takes the hit — no defensiveness, no "actually you only cancelled the plan"
• Reads the account and correctly identifies the add-on as the real cause (or asks the question that would reveal it)
• Fixes it fully: cancels the add-on and offers the refund, without making the customer ask twice
• Honest about the mistake — doesn't hide that a second subscription was quietly billing
• Handles the "close my account" request thoughtfully — confirms rather than blindly closing, but doesn't argue them out of it
• Sets a clear next step so the customer knows exactly what happens and when
• Internal note shows they'd actually do the cancellation and refund, not just reply

Weak answer: corrects the customer, quotes policy, offers one month "as a courtesy," leaves the add-on running so it charges again next month.

Ticket B — the vague, urgent one

Tests diagnosis, not-guessing, and grace under deadline pressure.

Subject: Export not working

The export button doesn't do anything. Please fix ASAP — I have a board meeting at 2pm and need this data.

Context you provide: No error message, no mention of browser, file type, or what "doesn't do anything" means. That's the whole ticket.

What to look for:

• Doesn't guess a fix for a problem they can't see yet — resists the urge to send a generic "clear your cache" reply
• Asks the one or two highest-value questions (what happens when you click it? any error? which report/browser?) instead of a ten-question interrogation
• Names the deadline and works with it — offers a fast path (e.g. "if you can send me the data you need, I'll export it for you before 2")
• Tone is calm and helpful, not flustered by the urgency or annoyed by the vagueness
• Internal note shows a plan: reproduce it, check for a known issue, have a manual fallback ready

Weak answer: fires off a canned troubleshooting list, ignores the 2pm deadline, or promises "this is fixed now" without knowing what's wrong.

Scoring the exercise

Score each ticket 1–5 on the three must-have competencies, then average. This is the heaviest-weighted stage — trust it over interview charm.

5. Values & empathy interview (30 min)

Behavioural questions — past behaviour predicts future behaviour far better than hypotheticals. Ask for a real example every time; if they answer in the abstract ("I would…"), push once: "Can you give me a specific time that happened?"

1. "Tell me about a time you made a mistake with a customer or on the job. What happened, and what did you do?"

   • Strong: owns it plainly, describes the fix and what they changed after.
   • Weak: can't think of one, or the "mistake" is secretly a humblebrag ("I cared too much").

2. "Tell me about the angriest customer you've dealt with. How did it end?"

   • Strong: de-escalation through listening, a real resolution, empathy for why the person was upset.
   • Weak: "some people are just impossible" with no reflection.

3. "Describe a time you got feedback you disagreed with. What did you do?"

   • Strong: listened, tried it, formed a view from evidence — coachable without being a pushover.
   • Weak: defensive, or dismisses the feedback outright.

4. "When have you gone off-script or bent a rule to do right by someone? How did you decide?"

   • Strong: judgment about when it's warranted, and awareness of the trade-off.
   • Weak: either "rules are rules, always" or "I ignore rules I don't like."

5. "You've told a customer their problem is fixed, then realise you were wrong. What now?"

   • Strong: tells them immediately, no burying it. This is a core honesty check.
   • Weak: waits to see if they notice.

6. "What's a time you didn't know how to help someone? Walk me through what you did."

   • Strong: escalated or researched, kept the customer informed, followed up.
   • Weak: made something up, or dropped it.

Empathy scan across the whole interview:

• Talks about customers as people, not "tickets" or "users being difficult"
• Curious about why someone was upset, not just how to close the ticket
• Shows real accountability without over-apologising or self-flagellating
• Listens to the actual question and answers that one

6. Scoring rubric

Every interviewer scores independently, on the same anchors, before the debrief. Score each competency 1–5, multiply by weight, and total. The weights put more than half the score on the three must-haves.

Convert to a recommendation:

• Weighted total ≥ 80 and no must-have below 3 → Strong hire
• 65–79 and no must-have below 3 → Hire, with a note on what to coach first
• Any must-have (clarity, empathy, judgment) scored 1 → No hire, regardless of total
• Below 65 → No hire

The gate matters more than the average: a candidate who scores 5 on everything but guesses confidently when they don't know is a no-hire, because that's the one habit that quietly burns customer trust.

7. Debrief & decision (20 min)

• Every interviewer submitted independent scores before anyone spoke — no anchoring on the loudest voice
• Scores reviewed competency by competency, starting with the biggest disagreements
• Decision checked against the scorecard, not against "I liked them" or "she reminds me of…"
• Bias check: would we score this answer the same from a candidate we found less charming?
• The ticket exercise was weighted heaviest — real work beats interview performance
• For a hire: named the top one or two things to coach in their first 30 days (hand this to onboarding)
• For a no-hire: recorded a specific, kind reason — so feedback is possible and the loop improves

Reminders that keep the loop honest:

• Hire for judgment and temperament; train the product. Product knowledge is the fastest thing on this list to teach.
• The queue is written work. If someone can't write clearly under mild pressure in the exercise, no amount of warmth fixes it.
• A confident bluffer is more dangerous than someone who says "I don't know." Weight honesty accordingly.
• Same tickets, same questions, same rubric for everyone. Consistency is what makes the comparison — and the decision — fair.