Interview Questions For A Server

What Actually Matters When You're Asking Interview Questions For A Server

The hiring manager at a place I used to consult for asked me to help them screen candidates because they were losing people within two weeks. Their original process was just asking if the person "worked here before" and whether they seemed like a nice person. Within a month they had three no-shows and a complaint about a server who didn't know how to run a side work sheet. So we rebuilt the question set from scratch. Here is the framework we landed on, and why each piece exists. Section one: operational awareness. Ask the candidate to walk you through what happens from the moment a table of four sits down to the moment they leave and get their check. You are not looking for theater terminology. You want to hear whether they think about sequencing, timing, and who they need to communicate with. The people who answer well will mention greeting, water, menu delivery, order-taking, expediting, check presentation, and resetting. The ones who skip the check or the reset are usually the ones who leave work half-done and make your closing staff miserable.

I had a candidate once who described her entire flow but completely forgot about modifications or allergies. When I pressed her on it, she said "we just tell the kitchen what they wrote down." That is not a dealbreaker on its own, but it told me she would need heavy supervision during her first month. I moved her to a slower lunch-only position instead of the dinner rush she wanted, and she lasted six months instead of six days. Section two: stress handling. Do not ask "how do you handle stress?" Everyone gives the corporate answer. Instead, give them a specific scenario and make them talk through it in real time. Try this one: it is Friday at 7:30 PM, two tables in have been waiting twenty minutes for their food, one of them is a regular who is visibly frustrated, and your expo guy just called in sick. What do you do first, second, and third? The right instincts show up as prioritization, not heroics. You acknowledge the regular table immediately. You check with the kitchen on the hold. You communicate with the other waiting table about wait times. You do not dump all your anxiety on the host stand or pretend nothing is wrong. Candidates who say they would "just work harder" are usually the ones who burn out by month three.

Section three: sales and product knowledge. Ask them to describe three items on your menu like they are recommending them to a guest who has never been here. Listen for specificity. Generic answers like "it's really good" or "it's popular" tell you nothing. You want to hear about ingredients, preparation method, flavor profile, or pairing suggestions. This reveals whether they actually read the menu when they worked before or just memorized prices. Section four: teamwork and conflict. Ask for a specific example of a time a coworker or manager gave them feedback they did not agree with. How did they respond in the moment? What did they do afterward? The candidates who say they completely agreed right away and never thought about it again are usually either lying or lack self-awareness. The ones who describe genuine pushback handled with professionalism tend to stay longer and lift the standard for everyone else. There is a specific edge case here that trips up a lot of interviewers. Some candidates will describe a conflict where they were clearly in the wrong but frame it as someone else being unreasonable. In my experience, if they cannot acknowledge even a small part of their own role in the situation, they are going to struggle with accountability on the floor. I started using that as a filter, and our turnover dropped noticeably over the next quarter.

Section five: logistics and reliability. This is the unglamorous part that destroys places faster than anything else. Ask directly about availability, transportation, ability to lift fifty-pound cases, ability to be on your feet for ten-hour shifts, and whether they have conflicts like school or second jobs that could interfere with late nights. Do not soften these questions. Get the answers in writing during the interview, not after they have already started showing up late.

Common Mistakes People Make When Hiring Servers

The biggest one is treating the interview like a personality check instead of a skills assessment. Charm matters, obviously, but a charming server who cannot manage a section under pressure will tank your covers and your tip pool. I have seen managers hire for vibes and fire within thirty days because the person could not handle a simple rush. Another mistake is asking the same generic questions for every shift and experience level. A candidate applying for a slow brunch position does not need the same depth of scenario testing as someone for Saturday night. Tailor the intensity. Use the full framework for dinner service and cut it down to operational awareness plus availability for lighter roles. A third mistake is not doing a working interview. No one learns whether they can actually handle the job by sitting in a chair and talking. A thirty-minute shadow during an actual shift, even just watching and asking questions while the candidate tries to run one table under supervision, will tell you more than any number of polished answers. It also lets the candidate evaluate whether your place is somewhere they actually want to work, which reduces offer rejections.

What the Data Actually Shows

Across the restaurants I have worked with, the structured interview approach above typically cuts first-90-day turnover by roughly a third compared to unstructured hiring. It does not eliminate turnover entirely. The restaurant industry has structural issues around pay, hours, and culture that no interview process can fix. But it does help you separate the people who are going to survive the learning curve from the ones who are not. The metric I track is not just retention. It is also first-month guest complaints related to service gaps, side work completion rates, and how quickly a new hire reaches full section capacity. Those three data points, combined with a structured interview, give you a much clearer picture than attendance records alone.

A Few Practical Notes

Keep the interview to about forty-five minutes. Go longer and you lose signal. Take notes during the interview itself so you can compare candidates objectively later. Score each section on a simple one to five scale and add them up. It sounds bureaucratic but it prevents recency bias, which is the real reason most hiring decisions go wrong. Have the candidate complete a brief side work assignment as part of the process. A folded napkin stack, a coffee station restock, a simple table reset. It takes five minutes and it reveals hand speed, attention to detail, and whether they understand that service work does not stop when the guest leaves. I added this after a candidate who sounded perfect in the interview completely failed to reset a section properly during a shift and caused a backup that cost the restaurant a reservation. If you are running a small operation without HR support, this framework still works. You do not need a formal scoring sheet. You just need to ask the same questions in the same order every time and write down what you heard. Consistency is what makes it useful, not complexity.