Server interview questions, and what a strong answer actually sounds like
A server interview is mostly about what happens when something goes wrong: a dish is late, an order was taken incorrectly, a table is unhappy and the kitchen is not at fault. Carrying plates and remembering a menu are trainable within a week. What is not is the instinct to tell a table the truth early, and the composure to keep the room pleasant while the pass is thirty minutes behind.
What the job actually involves
A server runs several tables at different stages at once — greeting one, taking an order at another, closing a bill at a third — while holding the kitchen's timing in their head. Most of the skill is sequencing and memory rather than charm, and the constraint on a busy night is almost always the order in which things are done.
The part that decides whether a table leaves happy is how bad news is handled. Dishes run late, items go off, orders get missed. A server who tells the table at minute five, with an accurate estimate, keeps a night recoverable. One who avoids the table until minute twenty has usually lost it.
The questions, and what a good answer sounds like
Ask these as written. Each one is paired with what a strong answer sounds like, so two people rating the same candidate reach the same conclusion for the same reason.
1. A main course is twenty minutes late and the table is visibly annoyed. What do you say?
A good answer: Goes to the table before being called over, gives an honest estimate instead of 'soon', and offers something concrete. Strong answers don't blame the kitchen in front of the guest. The failure mode this catches is avoidance. Servers who stop making eye contact with the table that's waiting.
2. You realise you put in the wrong order and the food is already cooked. What now?
A good answer: Tells the kitchen and the table immediately, and owns it without a story. Speed matters more than apology here. Candidates who would try to persuade the table to keep the wrong dish are describing a complaint you'll hear about later.
3. How do you decide which of your five tables to go to next?
A good answer: A stated basis (who is waiting on something, who is ready to order, who is ready to pay) and a habit of acknowledging the ones who wait. Experienced servers answer this immediately because it is the actual job.
4. A guest asks about an allergy. Walk me through exactly what you do.
A good answer: Never guesses. Checks with the kitchen, names the dish specifically, and comes back with a definite answer. Any answer containing 'I think' or 'probably' should end the process — this is the one question on the page with a safety consequence.
5. A table wants to split a bill six ways at the end of a busy service. What do you do?
A good answer: Does it without visible irritation and has a method. This is a small question that tests whether someone's pleasantness survives inconvenience, which is what the last hour of a shift is made of.
6. Tell me about a service that went badly.
A good answer: A real one, with their own part in it named. As with any hospitality role, the tell is whether any self-criticism appears at all. A candidate whose bad night was entirely the kitchen's fault will describe your kitchen the same way.
7. How do you sell a special without sounding like you're selling?
A good answer: Describes it in a sentence, says something true about it, and stops. Strong answers involve having tasted it. Servers who recite the description word for word are the reason specials don't move.
8. What does a good handover to the next section look like?
A good answer: Where each table is in its meal, what has been ordered, what has been promised. Candidates who describe the guest's position not the table number are thinking about the right thing.
A scorecard you can rate against
Rate every candidate 1 to 4 on each row, and write the rating down before you watch the next one. Ratings drift badly when they're relative to whoever you just saw.
| Criterion | What a 4 looks like |
|---|---|
| Delivering bad news early | Approaches the waiting table unprompted with an honest estimate. A 2 waits to be called over. |
| Sequencing under load | Orders five tables on a stated basis and acknowledges those who wait. A 2 describes moving faster. |
| Allergy discipline | Always checks with the kitchen and returns a definite answer. A 2 hedges or estimates. |
| Ownership of errors | Names a mistake and tells both kitchen and table immediately. A 2 manages the guest around it. |
| Composure late in a shift | Handles a six-way bill split without visible irritation. A 2 signals the inconvenience. |
How to run the screen
- Ask four of these, not eight. Hospitality candidates apply to several venues in an afternoon and a long screen loses good people to a shorter one nearby.
- Weight the allergy question as pass or fail. It has a safety consequence, and a hedging answer is disqualifying regardless of how strong the rest is.
- Cap answers at ninety seconds. Service is quick, clear speech under pressure and the format should look like the job.
- Go from the screen straight to a trial shift. The screen tells you about judgement. Only a shift tells you about pace and hands.
- Move in days. The best hospitality candidates accept the first reasonable offer, and a ten-day process systematically loses them.
Running this on a large applicant pool is where it gets expensive. VoxScreen sends these questions as a single link, transcribes and scores every answer against criteria you set, and hands back a ranked list. Free for 50 candidates a month, no card.
Common hiring mistakes for this role
- Testing menu knowledge. It is learnable in a shift and mostly selects for people who worked somewhere similar.
- Hiring on warmth alone. A server who can't deliver bad news early is pleasant right up until the night it matters.
- Skipping the allergy question because it feels like a formality. The answers vary far more than managers expect, and this is the one with real consequences.
- Using a recorded interview instead of a trial shift. Recordings show judgement and manner; they show nothing about carrying three plates through a full room, which is a real part of the job.
- Hiring the most talkative candidate. Good service is largely about reading who wants attention and who doesn't, which doesn't present as talkativeness in an interview.
Common questions
What should I ask a server in an interview?
Four questions cover most of it: the late main course, the allergy check, how they order five tables, and a service that went badly. Those test bad-news delivery, safety discipline, sequencing and self-awareness: the four things that actually vary. Menu knowledge doesn't need to be one of them.
Do servers need previous restaurant experience?
Less often than job ads suggest. Carrying, sequencing and the menu are learnable within a week or two. What is worth screening for is composure and honesty under pressure, and those turn up in candidates from retail, care work and call centres just as readily as from another dining room.
How do I screen a large pool of server applicants?
Ask everyone the same four questions with the same time limit, rate against written criteria before moving on, and go straight to a day of trial shifts with the strongest. The main benefit of recorded answers here is removing scheduling from the first round, which is where most of the calendar time goes in hospitality hiring.
Should I use a trial shift or an interview for servers?
Both, in that order: interview first, then trial. They test different things: the interview shows judgement about guests, allergies and mistakes. The trial shows pace, memory and how someone is in a full room. Neither substitutes for the other, and the interview's job is to get you to the trial with three candidates instead of ten.