How to hire a restaurant server (job description, interview questions, screening workflow)

Most server hiring advice tells you to look for restaurant experience. Nearly every resume has it, and it barely predicts whether the hire works out. The server who sinks your Friday is not the one who has never touched your POS. It is the one who ghosts the interview, no-shows the first shift, or quits two weeks in once the real pace sets in. A resume shows a list of past server jobs. It cannot show whether someone stays honest around the register when it is busy, tells you the truth after a mistake, or keeps their head when four tables need them at once. This guide is built to screen for reliability and composure under a rush, not for a stack of restaurant names.

What a server actually does at a small independent restaurant

At a chain, a new server gets a multi-day onboarding program: a manual, a POS certification quiz, a shadow shift with a trainer, maybe a corporate video on service standards. At a small independent restaurant, most of that doesn't exist. You or your GM walk a new hire through the POS once, point out the specials, and by their second night they're on the floor with real tables, real tickets, and real money, learning the rest as it happens.

That gap is what makes this hire different from a line on a resume. A server at a small restaurant isn't following a script. They're remembering that table six asked for no ice twice, catching a slow ticket before the guest has to flag it, and covering four to six tables at once with no expediter running interference for them. One slow or careless server on a busy Friday doesn't just cost their own tips, it slows the whole section and shows up in a review with your restaurant's name on it, not a franchise number.

You're also not hiring into a career ladder the way a chain can advertise one. Most people take a server job because it pays well for the hours and fits around school, another job, or a life outside work. That's fine, and it's worth being honest about in your process instead of pretending you're building years of tenure you can't actually offer.

The core responsibilities, in practice:

• Taking orders accurately and entering them into the POS the way the kitchen needs to see them
• Reading the pace of a table: when to check in, when to leave them alone, when to speed things up
• Handling a full section during a rush without dropping any one table
• Catching and fixing mistakes (a wrong dish, a missed allergy note, a slow ticket) before the guest has to complain
• Recommending specials, drinks, and add-ons without sounding like a script
• Handling cash, cards, and split checks accurately at the end of a shift
• Communicating clearly with the kitchen and other servers during a rush, not just with guests
• Showing up reliably for the night and weekend shifts, which is when most of your revenue happens

Job description you can post today

Copy this, then adjust the specifics (your menu, your hours, your service style) to fit your restaurant.

Restaurant server
[Restaurant name] is hiring a server to work our dining room and take care of our guests. You'll own a section during your shift: taking orders, running food and drinks, and making sure every table has what they need without being asked twice.

What you'll do
Greet and seat guests when needed, take accurate orders, enter them correctly in our POS, deliver food and drinks, check in on tables at the right moments, handle payment and split checks, and communicate with the kitchen and your fellow servers to keep tickets moving during a rush.

What we're looking for
Someone who's worked in a fast-paced, customer-facing role before, restaurant experience or not. You should be able to remember details without writing everything down, stay level-headed when several tables need you at once, and speak up honestly if you make a mistake instead of hiding it. Reliable availability for nights and weekends matters more to us than years of experience.

Schedule
[Insert shift days and hours, e.g. Wednesday-Sunday, 4pm-close, with some weekend lunch shifts]

[Insert pay, per your company's policy and any applicable state salary transparency requirements. Server pay is often a base wage plus tips, and tipped-wage rules vary by state, so confirm your state's tipped minimum wage and tip credit requirements before you post.]

10 interview questions, and what a good answer sounds like

1. Tell me about a shift where every table in your section needed you at the same time. What did you do first?

This is a triage question, sized for a small restaurant where there's no expediter or extra hand to absorb the overflow. A strong answer names a real sequence: which table they went to first and why, what they said to buy time with the others. A vague answer, or one that leans entirely on a manager to have fixed it for them, is a flag, because on a small floor that extra layer often isn't there.

2. A guest sends a dish back, or you realize you got an order wrong. Walk me through what you do next.

Listen for ownership before problem-solving. A strong candidate tells the kitchen right away, tells the guest honestly instead of dodging, and moves to fix it without being asked twice. Someone who describes quietly hoping the guest won't notice, or immediately blaming the kitchen to the table, is telling you how they'll actually handle a mistake when you're not standing there.

3. How do you recommend a special or a higher-priced item to a table without sounding like you're upselling them?

You're checking for genuine, specific language over a memorized script. A good answer references something real, what they'd actually say about a dish they've tried, and shows they read the table first: a couple on a date versus a family watching a budget get different recommendations. Someone who can only describe generic phrases ("would you like to add fries") hasn't thought about the guest at all.

4. Describe a time the kitchen was running behind and you had a table getting impatient. What did you say to the kitchen, and what did you say to the table?

This tests front-of-house and back-of-house teamwork, which matters more at a small restaurant where everyone's working a few feet apart all night. A strong answer treats the kitchen as a partner, checks in respectfully, and buys the table honest time without inventing excuses. Someone who throws the kitchen under the bus to make the guest happy is trading a short-term win for a floor that turns on itself during every rush.

5. Tell me about your availability for nights, weekends, and holidays. Which shifts would actually be hard for you to make?

Reliability is the single biggest thing to screen for in this role, since server hiring runs on ghosted interviews and no-shows more than almost any other job. Push past "I'm flexible" and get specifics. A candidate who names a real conflict up front, a class, a second job, a custody schedule, is more trustworthy than one who agrees to everything and doesn't show up the first Friday.

6. If you noticed a coworker giving away free food or drinks to friends, or shorting the register, what would you do?

This gets at honesty around comps and cash handling, one of the harder things to verify from a resume alone. Listen for whether they'd actually say something, to a manager or to the coworker directly, versus looking the other way. No single answer proves someone's honest, so weigh this alongside the rest of the interview rather than treating it as a pass or fail on its own.

7. What's the most physically demanding job you've had, and what made it manageable?

You're checking whether they understand the real pace of a small restaurant on a packed Friday night, which is different from most retail or office work. A strong answer describes actual conditions (being on your feet for hours, carrying heavy trays, moving fast in a tight space) and what helped them get through it. Someone who can't point to anything comparable may need a more honest conversation about the physical side of the job before you hire them.

8. Tell me about a guest who was difficult, not because of a mistake you made, but because they were just having a bad night. How did you handle them?

This is different from the mistake question above. It tests composure with a guest who isn't necessarily right. A good answer stays patient, doesn't take it personally, and keeps service moving without escalating. Someone who matches the guest's tone or gets visibly rattled is telling you what a bad table will look like on your floor.

9. How do you like to be trained on a new menu or system, and what actually helps it stick?

Since most small restaurants don't have a formal training program, you're testing self-directed learning, not just past knowledge. A strong answer describes an active approach: tasting the menu themselves, asking questions, writing quick notes. Someone with no answer here is telling you they'll need more hands-on time from you or your team than you may have to give.

10. Why are you looking for a server role right now, and what would make this the kind of job you stick with?

Given how much of this role is about retention, listen for concrete, specific reasons over generic answers like "I love people." A candidate who names something you can actually deliver, a schedule that fits, steady tip income, a team they'd want to be part of, is more likely to still be on your floor in six months than one who can't say why this job over any other.

A scorecard you can score candidates against

Ten questions only help if everyone doing interviews is listening for the same thing. Score every candidate on the same six signals, so you are comparing evidence instead of a vague sense of who seemed friendly. Keep it to one page and fill in a row per candidate.

How to screen server candidates without losing a week to it

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, built for exactly this kind of hiring: a role you refill often, with a pile of applicants who mostly come from Indeed, walk-ins, and word of mouth rather than LinkedIn. If you're hiring across multiple restaurant roles at once, not just servers, our restaurant interview questions guide covers questions spanning servers, hosts, line cooks, and managers. This page is built for when you're filling server shifts specifically, as part of a broader look at restaurant hiring.

A workflow that fits a small independent restaurant:

• Ask about availability before anything else. Server turnover runs high, and a lot of it comes from candidates who never intended to work the Friday and Saturday nights the job actually needs. A short set of qualification questions on nights, weekends, and holiday availability up front screens out the mismatch before you spend time on an interview.
• Use light resume or application screening, not a filter for years of experience. Our resume screening tool is useful here mainly to catch basic gaps, work authorization, any relevant customer-facing history, not to rank candidates by tenure at other restaurants.
• Add a one-way video interview for communication and composure. A server's job is talking to guests and staying steady under pressure, and neither shows up on a resume. Our one-way video interview tool lets candidates answer two or three of the scenario questions above on their own time, so you see how someone actually communicates before you book a table-side interview.
• Layer in a behavioral assessment for judgment calls. Have finalists work through Truffle's behavioral assessment to get a structured read on how they handle pressure, honesty, and guest situations, the same territory as the rush and comps questions above, before your final conversation.
• Close with a short interview or a trail shift. For an independent restaurant, a quick in-person conversation or a paid trail shift tells you more in twenty minutes than another round of questions. Use it to confirm what the video and assessment already showed you, not to start from scratch.

AI surfaces the evidence. You review it and make the call. None of these steps replace your judgment, they just make sure you're not starting from a bare resume every time this role opens.

Note that this is a different hire from a restaurant shift manager, the role a strong server might report to or grow into. A server owns their section during a shift. A shift manager owns the floor. Screen for guest-facing composure and reliability here, and save the leadership and delegation questions for when you're hiring or promoting into the manager role.

What the behavioral assessment surfaces for this role

The behavioral assessment is the one we'd point you to for a server, but it works differently from a right-or-wrong skills test. There are no universal correct answers. Instead it surfaces job-relevant behavior tendencies you define against the role. Three of them matter most on a busy floor.

Stress tolerance and emotional regulation. A strong signal is someone who stays composed when several tables need them at once and does not take a bad guest personally. A weak signal is someone who matches an angry guest's tone or gets visibly rattled the moment a shift gets loud.

Service orientation. A strong signal is anticipating what a table needs before they flag it and reading the room, a date night versus a family watching the check. A weak signal is treating every table the same and only reacting once a guest complains.

Integrity and ethical judgment. A strong signal is someone who would speak up about a coworker shorting the register or comping friends, and who owns a mistake instead of hiding it. A weak signal is looking the other way, or quietly hoping a wrong order goes unnoticed. No single answer proves honesty, so weigh this alongside everything else rather than as a pass or fail.

The assessment surfaces these tendencies as structured signal against the criteria you set. You still make the call, and a short paid trail shift is still the best final confirmation of what the assessment points to.

Common hiring mistakes for this role

Assuming a confirmed interview or start date is a real one. Server hiring runs on ghosted interviews and no-shows on the first shift more than almost any other role in a restaurant. Treat every candidate as a maybe until they're actually standing in front of you, and don't cancel your other options the moment one person confirms. It costs you nothing to keep a backup warm, and it costs you a shift when you don't.

Posting only where you'd look for a corporate hire. Server candidates mostly aren't on LinkedIn. If your only posting lives on a generic professional job board, you're missing the Indeed applicants, walk-ins, and word-of-mouth referrals from your own staff, who often know a former coworker looking for shifts. Sourcing built for a salaried, resume-driven hire doesn't reach the workforce that actually applies for this job.

Building a process for right now instead of next month. A single opening can pull dozens of low-quality, one-time applicants, and it's easy to put together a manual process, read every resume, call everyone back yourself, that works once and burns out whoever's doing it the next time the role opens. A process with saved qualification questions and a repeatable workflow matters more than getting through this one posting.

Having no backup ready when someone doesn't show. Given how common no-shows are for this role, running your shortlist down to one final candidate and stopping there leaves you exposed. Keep two or three people warm through the later stages instead of one, so a single no-show doesn't turn into an open shift with no coverage.

Running a heavy, multi-round process for a high-volume hourly role. The flip side of building nothing repeatable is over-building: four interviews and a working trial for a role you need filled by next week. Given the volume and the churn this role sees, a fast, consistent screening process beats a thorough but slow one, because the strongest candidates you find will often take whichever offer comes first.