Best Questions to Ask Your Server at a Restaurant for a Great Meal

You sit down. The menu arrives. It is four pages long, has a font size that suggests the designer never actually ate here, and somewhere between "crispy calamari" and "house-made tagliatelle" you realise you have no idea what you actually want. The server comes back. "Ready to order?"

And most people say: "Yeah, I'll have the chicken."

Which is fine. It is also a waste. Because the person standing in front of you has tasted everything on that menu, watched hundreds of plates go out, and knows which dish the kitchen actually cooks well tonight versus which one they're just pushing because the ingredients need to move. Learning the best questions to ask your server at a restaurant is not about being fussy or demanding. It is about getting the meal you actually wanted, without the awkwardness.

Spoiler alert: a lot of the questions people ask are useless. Some of them actively annoy the staff. And a small handful of them will change your dinner completely.

I've eaten in enough places — from a two-Michelin-star room in Lyon to a counter with plastic stools and a single soup pot — to have learned the difference the hard way. I've also spent a good chunk of time on the other side of the pass, working shifts, and that's where I learned which questions actually help.

Why the questions you ask your server actually decide your meal

Here's the thing nobody tells you: the server is not a menu-reading service. They are, in most restaurants that cook from scratch, your only real interface with the kitchen. The chef is behind a wall, sweating, and has not spoken to a customer in six hours.

The server, though, has been watching. They know the halibut came in fresh that morning and the pork shoulder is on its last day. They know which sauce the new guy messed up twice last week. They know that the dish you're eyeing takes 35 minutes because it's cooked to order.

That knowledge is free. You just have to ask for it.

The server is a filter, not an encyclopedia

Which brings up an obvious problem: some questions put the server in an impossible position. Ask "Is this good?" and you've forced a yes. Nobody earning tips is going to say "no, that one's terrible."

Ask instead: "If you were eating here tonight on your own money, what would you get?" That's a completely different question. It gives them permission to have an opinion. In my experience, the answer changes about half the time.

A friend of mine — ten years on the floor, mostly high-volume bistros — once told me she keeps three dishes she'll happily recommend and quietly steers people away from another two. She's never once said "don't order that." She just... stops mentioning it. Ask the right question and you skip the whole dance.

The one question nobody asks (and should)

"How is it cooked?" is the most underrated question on this list, and it isn't about temperature or technique. It's about timing.

If a dish takes 40 minutes and you're eating with someone who ordered a salad, you're going to sit there watching them eat. Ask "How long does that take?" and you can plan around it. Order a starter. Split something. Or pick the thing that comes out in twelve minutes.

I learned this the expensive way at a seafood place in the Basque country. Ordered a whole grilled turbot because it sounded magnificent — which it was. It also required the kitchen to steam it, cool it, and re-grill it, and it arrived ninety minutes after my partner had finished her two courses. Delicious. Awkward.

The best questions to ask your server at a restaurant, sorted by what they're for

Not all questions are equal. Some are reconnaissance, some are safety, some are just for fun. Here's how I'd break them down.

To make a better decision

• "What's moving tonight?" — dishes where the kitchen has run through stock. Fresh.
• "What did you eat on your break?" — informal, and the answers are usually honest.
• Which dish do you get tired of carrying?
• "Is there anything not on the menu tonight?" — daily specials, off-menu cuts, whatever the chef is playing with.
• "How big is the portion? Should we share?"

For allergies and restrictions

This is where wording matters more than politeness. "Is this gluten-free?" invites a guess. "I have a serious shellfish allergy — can you check with the kitchen whether the fryer is shared?" gets a real answer.

Be specific about severity. Kitchens handle "I'd rather avoid dairy" and "anaphylaxis" very differently, and they need to know which one you are.

For drinks that actually match

• "What are you pouring by the glass that isn't on the list?"
• "What would you drink with this if it were your dinner?"
• "Is the house red something you'd order yourself?"
• Anything local I should try?
• "What's the cheapest bottle you'd genuinely recommend?" — yes, you can ask this. Most servers respect it.

What is the 30/30/30/10 rule for restaurants?

The 30/30/30/10 rule is a common way of describing how a restaurant's revenue is typically split across its different sales channels: 30% dine-in, 30% takeout, 30% delivery, and 10% catering or other. The idea is that a healthy operation doesn't lean too hard on any single stream, because if one dries up — a bad weather week, a delivery app changing its commission structure, a catering client walking away — the whole business doesn't collapse with it.

Two honest caveats. First, this is a rule of thumb, not a law, and the actual split varies wildly by concept. A neighbourhood pizzeria doing mostly delivery will look nothing like a fine-dining room that barely does takeout. Second, you'll sometimes hear the number applied to something else entirely — staffing ratios, food cost targets — and that's usually a mix-up.

For you, sitting at the table, it's mostly trivia. Where it becomes useful is if you're asking your server about the business itself, or if you're the one opening a restaurant and trying to figure out whether your model is too dependent on one channel.

The questions that make your server's evening worse

Look, most servers will answer anything with a smile. That doesn't mean every question is a good one.

The classics that land badly: "What's good here?" (they cannot say nothing), "Is the chef any good?" (what are they supposed to say?), and anything asked while they're carrying a tray. The tray one is real — I watched a colleague take a full round of drinks to the face because a customer grabbed her sleeve to ask about the soup.

Also worth retiring: "Can you make the kitchen do X instead of Y?" if X isn't on the menu at all. Substitutions within a dish are usually fine. Asking for a completely different preparation of a dish you've just invented is not.

What are good questions to ask in a server interview?

Flip the table. If you're the one hiring, the questions you ask a candidate tell you more about your own restaurant than about them — because good servers answer honestly, and the honest answers expose problems.

What I'd ask:

• "Tell me about a table that went badly. What did you do?" — the answer reveals whether they own problems or narrate them.
• "How do you handle a dish you personally think is weak?"
• What do you do when the kitchen is 30 minutes behind and the guest is watching you?
• "What's the last thing you learned about wine, food, or service?" — curiosity is the single best predictor of a good hire on the floor.
• "Why did you leave your last place?" — and listen for whether they blame everyone or describe a situation.

Questions to ask at the end of a server interview

The end of the interview is where candidates separate themselves, and it's also where you learn the most. The questions a candidate asks you tell you whether they'll still be here in a year.

Strong ones: "What does a typical Saturday look like on the floor?" "How many tables am I running at peak?" "Who trains new hires, and for how long?" "What's the turnover been like in the last year?"

If someone asks about your turnover rate, hire them. That's a person who's done this before and knows what a bad floor feels like.

What should a server ask their employer?

This one comes up constantly, and it's the right question to be asking. A server interview is a two-way conversation, and the information you get in the first fifteen minutes will determine whether you're still happy in six months.

The essentials: How are tips distributed? (Pooled? Tip-out percentages? Card fees deducted?) What's the section size at peak? How is the schedule posted, and how far in advance? What's the policy on shift swaps? Is there a uniform or a cost for it? How long is training, and is it paid?

And the one people forget: "What happens when a guest is wrong about something?" The answer tells you whether management backs the floor or throws it under the bus. In my experience, that single question predicts job satisfaction better than the hourly rate.

What are 5 good questions to ask?

If you only remember five things from this whole piece, make it these — they work in almost any restaurant, at almost any price point:

1. "What do you personally love on this menu?"
2. "How long does that dish take?"
3. Anything not on the menu tonight I should know about?
4. "What would you drink with it?"
5. "Is there anything I should avoid because of an allergy risk?"

Those five cover taste, timing, discovery, pairing, and safety. That's about 90% of what you actually need to get a great meal.

Different restaurants, different questions

The questions that land well in a gastronomic room will sound strange at a taco counter, and vice versa. Rough guide:

Type of place	Best question to lead with	Skip
Fine dining	"What's the kitchen most proud of right now?"	"What's the cheapest thing?"
Neighbourhood bistro	"What did you eat today?"	Anything about the wine list's provenance
Ethnic / regional	"What do people from your country order?"	Asking for it "not spicy"
Counter service	"What's your personal go-to?"	Any question that needs a follow-up
Chain restaurant	"What's made fresh versus prepped?"	Asking for off-menu changes

Notice that in every case, the winning question is some version of what do you actually like. That's not a coincidence. It hands the server a real choice instead of a performance.

Timing and tone: the part that matters more than the words

You can ask the perfect question at the wrong moment and get nothing useful. Mid-rush, with four tables flagging, is not the time for a five-minute conversation about the cheese board.

The window: after drinks are down and before you've ordered. That's when a server has a moment. If they're clearly slammed and you need real help, "When you have a second, I've got a couple of questions" works far better than launching in.

And tone. A question asked like a challenge — "So is this actually fresh?" — gets a defensive answer. The same question asked with genuine curiosity gets the truth.

I'll admit I used to think all this was overthinking. Then I spent a season working a busy floor and realised I'd been the annoying customer more than once. Asking well isn't a trick. It's just treating the person holding the plates like someone who knows something you don't.

Which, most of the time, they do.