How to hire a kitchen manager for a small restaurant (job description, interview questions, screening workflow)

The obvious hire is your best line cook, the one who never misses a ticket. Running a great station and running the kitchen are different jobs, and the gap between them is exactly where this hire fails. A great line cook can plate fifty covers an hour and still have no idea whether your chicken order this week is running high, no instinct for writing a schedule that doesn't burn out your prep cook, and no track record of telling a friend on the line that their portioning is off. A resume, or even years on your own station, shows none of that. This guide is built to screen for cost judgment, scheduling and discipline, and line consistency under real volume, not for knife skills alone.

What a kitchen manager actually does at a small independent restaurant

At a restaurant group with a central kitchen team, a kitchen manager works off a food cost target set by a corporate chef, a scheduling tool that flags overtime automatically, and a compliance checklist someone else wrote. At a small independent restaurant, none of that exists unless the kitchen manager builds it. They set the order, watch the number, write the schedule, hold the line to a standard, and answer for the walk-in cooler if a health inspector shows up on a random Tuesday. There's no one behind them catching what they miss.

That's also what separates this role from a restaurant shift manager, a role we cover in a separate guide. A shift manager runs the floor and the pass for a block of hours and hands off to whoever's next. A kitchen manager owns the kitchen across every shift, whether they're personally there or not: this week's order, this month's food cost, who's on the schedule Friday, and whether the walk-in passes inspection. At a small restaurant those two jobs sometimes collapse into one person, but if you're hiring for the kitchen specifically, this is the role, and it carries more financial and operational ownership than a single-shift lead.

If you're hiring for other restaurant roles on the same cycle, our restaurant interview questions post has a broader bank of questions that work across servers, hosts, and cooks. This page goes deep on one role: the person who owns food cost, the kitchen schedule, and health code compliance in your kitchen specifically.

The core responsibilities, in practice:

• Ordering food and supplies against actual usage, and catching waste, over-portioning, or theft before it shows up as a bad food cost number at month end
• Building and adjusting the back-of-house schedule, including finding coverage when someone calls out with no bench of extra cooks to pull from
• Setting and enforcing line and plating standards so a dish looks and tastes the same at 6pm and at 10pm on a Saturday
• Coaching, correcting, and when necessary firing kitchen staff, including people they used to work beside on the line
• Owning health code compliance day to day: temp logs, storage, pest control, and being the person who walks an inspector through the kitchen
• Stepping onto the line themselves during a rush or a callout, because a small kitchen doesn't have the bench depth to absorb a gap without the manager cooking
• Hiring for their own team, since there's usually no separate HR function to lean on
• Reporting food cost, labor, and any compliance issues directly to the owner, who is often the only person they answer to

At a single-location independent, this person is the difference between a kitchen that's profitable and consistent and one that's bleeding money nobody can explain. That's worth naming clearly when you post the role, because it's a different pitch than "kitchen manager wanted, must be a team player."

Job description you can post today

Copy this, then adjust the specifics (your concept, your hours, your pay) to match your restaurant.

Kitchen manager
[Restaurant name] is looking for a kitchen manager to run the back of house. You'll own our food cost, build the kitchen schedule, hold the line to our standards, and keep us compliant with health code, all without a corporate team behind you.

What you'll do
Order food and supplies against actual usage and track food cost weekly. Build and adjust the BOH schedule, including finding coverage when someone calls out. Set and enforce line and plating standards so every plate matches, whether it's the first ticket of the night or the last. Coach and, when necessary, discipline or let go of kitchen staff. Own health code compliance: temp logs, storage, and walking an inspector through the kitchen if one shows up. Step onto the line yourself during a rush or a callout, since our kitchen doesn't have a deep bench.

What we're looking for
Real experience running a small kitchen, whether that's a previous kitchen manager or sous chef role, or a strong line cook ready to own scheduling and cost, not just a station. Comfort with basic kitchen math (food cost percentage, portioning, waste tracking). A [food protection manager certification, or willingness to get one] where required by your state and local health department. Someone who'll have a hard conversation with a cook directly instead of avoiding it, and who can still cook a full station themselves when the kitchen needs it.

Schedule
[Insert hours, e.g. Tuesday-Saturday, with close responsibility most nights and weekly ordering on Mondays]

[Insert pay, per your company's policy and any applicable state salary transparency requirements. Kitchen manager pay varies a lot by region and concept, so check current local rates before you post.]

10 interview questions, and what a good answer sounds like

1. Walk me through how you decide what to order for the week, and how you catch waste before it shows up in your food cost.

You're checking for an actual system, not a vibe. A strong answer names a real process: checking usage against last week's numbers, walking the walk-in and dry storage before ordering rather than guessing, and having a specific habit for catching over-portioning or spoilage on the line. A candidate who says they "just order what feels right" or has never looked closely at a food cost report is telling you they'll learn this on your dime, which is a real cost at a small restaurant with thin margins.

2. Tell me about a time your food cost came in high for a period. What did you find, and what did you change?

Every kitchen manager with real experience has a story here. Listen for a specific diagnosis (a supplier price jump, over-portioning on one dish, waste from a menu item that wasn't selling) and a specific fix, not a vague "we tightened up." A candidate who can't produce a real example probably hasn't owned a food cost number before, only worked near one.

3. It's Friday night, you're slammed, and one of your line cooks doesn't show. What do you do in the next fifteen minutes?

This is the no-bench-depth question. A strong answer moves fast: assess who can cover the station, decide whether they step onto the line themselves, adjust the ticket pace or the menu if needed, and communicate the change to the rest of the kitchen and front of house. A candidate who says they'd call the owner and wait for instructions, or who has no plan beyond "figure it out," isn't ready to run a kitchen without a safety net.

4. How do you keep plating and portioning consistent across a whole shift, especially on nights you're cooking yourself instead of just directing?

Consistency is the job, and this tests whether they have an actual method versus hoping the team remembers the standard. A strong answer names something concrete: a plate photo taped at the pass, spot-checking a percentage of tickets, tasting components at set points in the shift. Someone with no answer here is telling you your food quality will drift the moment they're not standing over every plate.

5. Tell me about a time you had to give a cook hard feedback about their work. How did you say it, and what happened after?

Listen for a direct, specific, private conversation, not a story about hinting at the problem or venting to someone else about it. A strong answer names what they actually said and whether the behavior changed afterward. A candidate who can't produce a real example, or whose instinct is clearly to avoid the conversation, will struggle the first time they need to correct someone they like.

6. What's your process for a health inspection, planned or not? Walk me through what you actually check.

You want specifics, not the textbook answer. A strong response names real checkpoints: temp logs current and accurate, raw and cooked storage separated, labels and dates current, pest control documentation on hand, and a habit of walking the kitchen with that lens regularly, not just before an inspection is expected. A candidate who can only recite generic food safety rules without describing an actual routine probably hasn't owned compliance before, only followed someone else's checklist.

7. When do you decide to step onto the line yourself instead of directing from the pass?

A small kitchen needs a manager who can do both, and this tests judgment about when each is the right call. A strong answer names a real threshold: when a station is genuinely underwater and stepping in is faster than reassigning, versus staying at the pass to keep the whole kitchen's pace and communication intact. Someone who says they'd always jump on the line, or never would, hasn't thought through the tradeoff between fixing one station and running the whole kitchen.

8. Tell me about a time you had to let someone on your kitchen team go. How did you handle it, and what led up to it?

This tests hiring and firing judgment for their own team, not just their own performance. A strong answer shows a pattern before the decision (documented issues, a real conversation or two first) and a clean, respectful handling of the actual conversation. A candidate who describes firing someone impulsively, or who's never had to make this call despite years in kitchen leadership, is worth a follow-up question about how they'd actually handle it here.

9. How do you build the weekly kitchen schedule, and what do you do when someone requests time off during a week you're already short-staffed?

Listen for a real process: balancing experience levels across shifts, accounting for peak nights, and a specific approach to the time-off conflict (first-come, first-served, seniority, direct conversation about coverage) rather than "I just figure it out." A vague answer here predicts a schedule that leaves you short on your busiest nights.

10. What's your own attendance and reliability record like, and what happens on your kitchen when you're out unexpectedly?

Ask this directly. A strong answer is honest about occasional absences and specific about backup: a sous or lead line cook who can run the kitchen for a shift, a clear handoff process. A candidate who claims a perfect record with no plan for coverage is harder to read, and at a small restaurant, one unplanned absence from the person who owns ordering and scheduling can stall the whole operation.

A scorecard you can score candidates against

Ten questions only help if everyone interviewing listens for the same thing. Score every candidate on the same six signals instead of comparing gut feelings from separate conversations.

How to screen kitchen manager candidates without losing a week to it

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, so you can build a process around what this role actually rewards: cost judgment, scheduling and discipline, and consistency under volume, not just years on a resume. This is the same labor pool you're sourcing for line cooks and restaurant servers, more Indeed, walk-ins, and industry word of mouth than polished resumes and LinkedIn, so the workflow needs to fit how these candidates actually apply, not how a corporate hire would.

A workflow that fits a small independent restaurant:

• Light resume screening, weighted toward real kitchen leadership over polish. Our resume screening tool is useful here mainly to confirm someone's actually run a kitchen, ordering, scheduling, a team, not to rank candidates by formatting or which restaurants are on the page. Make the resume helpful, not a hard gate, since a lot of strong candidates in this labor pool source through a walk-in or a call rather than an online application.
• A one-way video interview before you commit an in-person slot. Ask 2-3 of the scenario questions above, especially the no-show question and the food cost question, so you can hear how someone actually thinks before you spend a working interview on them. A one-way video interview surfaces judgment and communication style, which are hard to read from a resume and much easier to hear on video.
• A leadership assessment for your shortlist. Have finalists work through Truffle's leadership skills questionnaire before the final interview. It rates observable behaviors across competencies like delegation, decision-making under pressure, and conflict management and candor, which map directly onto the scheduling calls, no-show decisions, and hard conversations this role requires. It gives your last conversation something specific to talk through instead of a generic gut check.
• A working shift on the actual line before an offer. Once someone's cleared video and the assessment, bring them in for a real shift, paid, alongside your current team. This is where you confirm what the earlier steps only hinted at: whether their line standards hold up under real volume, and whether they actually step in and cook when the kitchen needs it.

AI surfaces the evidence. You review it and make the call. It doesn't decide for you, and for a hire this close to your food cost and your compliance risk, that judgment should stay yours.

Common hiring mistakes for this role

Promoting a strong line cook without checking scheduling and leadership judgment. Being the fastest, cleanest cook on the line doesn't predict whether someone can write a schedule that doesn't burn out your prep cook, watch a food cost number, or fire a friend when it's warranted. If you're promoting from within, test those specific skills directly in the interview instead of assuming they come with the title.

Sourcing only where you'd look for a corporate hire. This workforce mostly isn't on LinkedIn. If your only posting lives on a generic professional job board, you're missing the Indeed applicants, walk-ins, and referrals from your own kitchen staff, who often know a former sous chef or lead line cook looking for the next step. A sourcing plan built for a salaried, resume-driven hire doesn't reach the people who actually run kitchens like yours.

Underestimating turnover and flaky candidates in this labor pool. Restaurant hiring runs on ghosted interviews and no-shows on day one more than almost any other industry, and that doesn't disappear because the role has "manager" in the title. Treat a confirmed start date as a maybe until someone's actually standing in the kitchen, and build a paid working shift into your process so you're not finding out about a bad fit on a real Friday.

Moving too slowly and losing a strong candidate to the next offer. Kitchen managers who can actually run a food cost number and a schedule are hard to find, and they don't sit in your inbox waiting. A process that stretches interviews across two or three weeks reads as disorganized and costs you the hire to whoever calls back first. Verify interest fast, screen fast, and don't let a strong candidate go cold while you get around to scheduling the next step.

Writing a posting that blurs kitchen manager with shift manager or general manager. A vague "manager wanted, kitchen experience a plus" posting undersells the financial and compliance ownership this role actually carries, and pulls in applicants expecting a single-shift job. Be specific about food cost, scheduling, and compliance ownership in the first few lines, so the person who applies understands the scope of what they're signing up for.