Chef: job description, interview questions, and screening workflow

The instinct is to hire whoever cooked the best tasting dish. A great tasting-menu audition, cooked alone in a quiet kitchen, proves almost nothing about whether someone can run your kitchen and hit food cost on a real Saturday night. A chef candidate can plate something beautiful in a calm test kitchen and still have no idea how to price that dish to hit your margins, no instinct for which three ingredients are quietly wrecking your food cost, and no track record of holding a small team together when six tickets land at once and there's no sous chef to lean on. Big-name kitchen pedigree doesn't fix this either. Working the fish station in a large brigade for five years is a different job from owning the whole menu and the whole kitchen at a restaurant with four cooks and no safety net. This guide is built to screen for menu judgment, food cost discipline, and kitchen leadership under real pressure, not for a resume of impressive kitchens or one good audition dish.

What a chef actually does at a small independent restaurant

At a restaurant group, a chef often works inside a system: a corporate culinary team sets recipe standards, a centralized purchasing team negotiates pricing, and a chef de cuisine executes a menu someone else largely designed. At a small independent restaurant, the chef is usually the one designing that menu from nothing, deciding what it costs, and personally answering for whether it works, both on the plate and on the P&L.

That's what separates this role from the two roles it gets confused with most. A line cook executes a menu someone else designed, running a station to a standard that's already been set. A kitchen manager owns the operations underneath the menu: ordering against usage, the back-of-house schedule, health code compliance. A chef owns the menu itself: what's on it, why, what it costs to make, how it's plated, and the culinary direction of the restaurant. At a small restaurant, a chef and a kitchen manager sometimes collapse into one person, and a chef sometimes cooks a full station like a line cook during a rush. But if you're hiring for the chef role specifically, this is the job, and it's a creative and financial role first, not primarily a scheduling or compliance one.

The core responsibilities, in practice:

• Designing and evolving the menu: what dishes go on it, what comes off, and how it holds together as a whole
• Pricing dishes to hit a food cost target, and catching when an ingredient price change or a popular dish is quietly eating margin
• Setting the plating and flavor standard for every dish, and holding that standard whether they're on the pass or a cook is
• Leading the kitchen through service, especially a real dinner rush, including calls on pace, sequencing, and when to step onto a station themselves
• Sourcing decisions: which purveyors and vendors to use, and adapting the menu when a supplier runs short or a price jumps
• Developing seasonal or occasional menu changes that fit both the restaurant's identity and the kitchen team's actual skill level
• Coaching cooks on technique and plating, and correcting a plate in the middle of service without stalling the line
• Balancing creative ambition against what a small team can consistently execute and what actually sells

At a single-location independent, this is the difference between a menu that's exciting and profitable and one that photographs well but quietly loses money on half its dishes. That's worth naming clearly when you post the role, because it's a different pitch than "chef wanted, must be passionate about food."

Job description you can post today

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

Chef
[Restaurant name] is looking for a chef to own our menu. You'll design what we serve, set our plating and flavor standards, and lead the kitchen through service, including a real Friday and Saturday rush, without a corporate culinary team behind you.

What you'll do
Design and evolve the menu, including seasonal changes that fit our concept and our kitchen's skill level. Price every dish to hit our food cost target and catch margin problems before they show up at month end. Set and hold plating and flavor standards across the kitchen, whether you're on the pass or a cook is. Lead the kitchen through service, including making real-time calls on pace and stepping onto a station yourself when the kitchen needs it. Make sourcing decisions and adapt the menu when a supplier runs short or a price changes. Coach cooks on technique and plating, and correct a plate mid-service without stalling the line.

What we're looking for
Real experience designing a menu and leading a small kitchen through service, not just working a station in someone else's kitchen. Comfort with kitchen math (food cost percentage, plate costing, portioning) and a track record of hitting a margin target, not just cooking well. Someone who can hold a plating and flavor standard under real volume, and who can teach that standard to a small team instead of just performing it themselves. Creative range balanced with commercial judgment: menu ideas that also sell.

Schedule
[Insert hours, e.g. Tuesday-Saturday, with close responsibility most service nights and menu and ordering work built into the week]

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

12 interview questions, and what a good answer sounds like

1. Walk me through designing a dish from concept to menu, including how you priced it to hit a food cost target.

You're checking for a real process that connects creativity to margin, not just a story about inspiration. A strong answer names both sides: where the idea came from, and how they costed it out, adjusted portions or ingredients when the number didn't work, and landed on a version that still tasted like the original idea. A candidate who can only describe the creative side, with no mention of pricing or margin at any point, hasn't owned a menu, only contributed to one someone else priced.

2. Tell me about a dish you loved that didn't work once it hit the menu. What told you, and what did you do?

Every chef with real experience has one of these. Listen for a specific signal they noticed (it wasn't selling, the food cost was too high, it was slowing down the line) and a specific decision that followed: reworked it, repriced it, or pulled it. A candidate who can't name a real example, or who insists everything they've put on a menu has worked, is either inexperienced or not being straight with you.

3. How do you keep plating and flavor consistent across the kitchen when you're not the one plating every ticket?

This tests whether they can hold a standard through a team, not just perform it themselves. A strong answer names something concrete: a plate reference at the pass, a specific tasting or checking habit during service, a clear way they trained a cook on the standard rather than assuming it would transfer by watching. Someone with no answer here is telling you your food quality depends entirely on them being physically present at every station.

4. Walk me through a real Friday or Saturday dinner rush. What are you personally doing, as the chef, while your cooks work their stations?

You want to hear their actual role during service, not a generic description of a busy night. A strong answer names specific decisions: managing pace and ticket sequencing from the pass, deciding when to step onto a station versus staying at the pass to keep the whole kitchen moving, catching a plate that's off before it goes out. A candidate who describes themselves as just another cook on a station, with no mention of running the kitchen as a whole, may be strong technically but untested as the person actually leading service.

5. Tell me about a time a supplier ran out of something or a price jumped mid-week. How did you adapt the menu?

This tests sourcing judgment under a real constraint. A strong answer describes a specific fix: a substitution that kept the dish's integrity, a quick 86 with a clear alternative offered, or a menu adjustment that protected both quality and margin. A candidate who says they'd just absorb the cost without adjusting anything, or who has never actually had to solve this, may not have owned purchasing decisions before.

6. How do you approach a seasonal menu change, and how do you factor in what your current kitchen team can actually execute?

Listen for whether they design with their real team in mind, not an idealized one. A strong answer names both the creative direction and a concrete check on feasibility: testing a new dish with the actual cooks who'll run it, simplifying a technique that's too ambitious for the team's current skill level, or building in training time before a launch. A candidate who only talks about the food, with no mention of the team executing it, may design menus that look great on paper and fall apart during a real service.

7. Tell me about a time you said no to a dish idea, yours or a cook's, because it didn't make sense for the restaurant.

This surfaces commercial judgment, which matters as much as creativity in this role. A strong answer names a real reason: it wouldn't hit food cost, it required a piece of equipment or a technique the kitchen couldn't support, it didn't fit what the restaurant's guests actually order. A candidate who can't produce a real example may lead with ego over judgment when the two conflict.

8. Walk me through how you taste and adjust a new dish before it goes on the menu.

You're checking for an actual process versus a one-and-done gut check. A strong answer describes tasting at multiple points, getting a second opinion from someone on the team, and adjusting for consistency, not just flavor: can this be replicated by a cook other than the chef, at volume, under time pressure. Someone who says they just know when a dish is right, with no process for testing that it holds up outside their own hands, is a risk for a kitchen that isn't just them.

9. Tell me about a time you had to lead your team through executing something more ambitious than their current skill level.

This tests whether they can stretch a small team without breaking service. A strong answer names a specific gap they saw, how they simplified the execution, trained on it, or paced the rollout, and how it actually went once it hit real volume. A candidate who describes pushing an ambitious dish onto the menu without adjusting for their team's readiness, and having it fall apart during service, is telling you something about their judgment under real conditions.

10. How do you balance a signature or creative dish against a dish that's reliably profitable but less exciting?

Listen for a real philosophy about menu composition, not just "I make what I love." A strong answer names a specific approach: using a few high-margin, reliable dishes to fund more ambitious or lower-margin ones, or knowing which sections of the menu need to work financially versus which can carry more creative risk. A candidate with no sense of this balance may build a menu that's exciting to cook and hard to keep the restaurant open on.

11. Tell me about your relationship with purveyors or vendors. How do you decide who to buy from, and how has that changed a menu?

This surfaces real sourcing experience versus a hypothetical answer. A strong candidate names actual relationships or decision points: quality versus price tradeoffs, a vendor they moved away from and why, a specific case where sourcing shaped a dish or a menu change. A vague answer, with no real specifics about vendors or a sourcing decision, suggests they haven't owned this part of the job before.

12. Tell me about a dish or a menu you were proud of that didn't work commercially. What did you learn?

This tests self-awareness and whether they separate their own taste from what the restaurant actually needs. A strong answer is honest about the miss, names a specific reason it didn't work (didn't sell, cost too much to make, was too complicated for the kitchen to execute consistently), and describes what changed in how they think about menu design afterward. A candidate who can't name a real failure, or who blames the failure entirely on guests or staff, may be harder to work with when their next idea needs adjusting.

A scorecard you can score candidates against

Twelve questions only help if everyone in the room is listening for the same thing. Score every candidate on the same six signals, so you're comparing evidence instead of comparing how much you liked their audition dish.

How to screen chef 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: menu and food cost judgment, and the ability to lead a kitchen through real service, not just a resume of impressive kitchen names. This is often the same hiring cycle where you're also filling line cook or kitchen manager roles, and this labor pool sources more through Indeed, industry word of mouth, and direct referrals than through polished resumes on a professional network.

A workflow that fits a small independent restaurant:

• Light resume screening, weighted toward real menu ownership over kitchen names. Our resume screening tool is useful here mainly to confirm someone's actually designed a menu and led a kitchen, not to rank candidates by which restaurants appear on the page. A well-known kitchen on a resume tells you where someone worked, not whether they ever owned the menu there.
• A one-way video interview before you commit an in-person slot. Ask 2-3 of the scenario questions above, especially the dinner rush question and the food cost question, so you can hear how someone actually thinks about running a kitchen and a menu before you spend a working trail on them. Our one-way video interview tool surfaces judgment and communication style that a resume can't show, and gets you there before you've cleared your calendar for an in-person conversation.
• An in-person interview built around the questions above, not a general conversation about their cooking philosophy. Use the scorecard to keep the conversation anchored to menu judgment, food cost discipline, and leadership under pressure, the things a resume and a friendly chat both tend to hide.
• A paid trail against your actual menu and your actual team, not a standalone tasting dish cooked alone. Ask them to develop or adjust something for your menu against a rough food cost target, and watch how they communicate a plating standard to your current cooks. This tells you far more than a beautiful dish cooked in a quiet kitchen with no pressure and no team to lead.

AI surfaces the evidence, resume matches, interview answers, patterns worth a closer look. You review it and decide. For a hire this close to your menu, your food cost, and your kitchen's culture, that judgment should stay yours.

Common hiring mistakes for this role

Hiring off one great tasting dish instead of testing how they think about a menu. A single audition dish, cooked alone with no pressure and no team, shows technique but hides almost everything that actually predicts whether this hire works out: pricing judgment, leadership during service, and whether they can hold a standard through other people's hands. Build the trail around your actual menu and your actual kitchen, not a showcase dish.

Weighting kitchen pedigree over real ownership of a menu. A candidate who worked five years at a well-known restaurant, but only ever ran one station in a large brigade, hasn't necessarily owned pricing, sourcing, or leading a small team through a rush. Probe directly for what they actually owned, not just where they worked.

Blurring this role with kitchen manager or line cook in the posting. A vague "chef wanted, must love food" posting undersells the menu and margin ownership this role actually carries, and pulls in candidates who expect either a pure cooking job or an ops-heavy management job. Be specific about menu design and food cost ownership in the first few lines, so the person who applies understands the scope.

Underestimating how expensive a bad culinary hire is. A chef who can't hold a food cost target or design a menu your kitchen can actually execute doesn't just cost you a bad hire, it costs you wasted food cost every week, a menu that doesn't sell, and a kitchen that can't get through a Friday night clean. Treat this hire with the financial weight it actually carries, not as a role you'll figure out once someone's in the door.

Sourcing only where you'd look for a corporate hire, and moving too slowly once you find someone strong. Like most of this labor pool, strong chef candidates often come through Indeed, industry referrals, and word of mouth rather than a generic professional job board, and they don't wait around for a slow, multi-week process. A tight, fast process, a video screen, a scenario-based interview, a paid trail against your real menu, beats a drawn-out one that costs you the hire to whoever calls back first.