All hiring guides
Retail & hospitality Line cook

How to hire a line cook (job description, interview questions, screening workflow)

A ready-to-post line cook job description, 11 interview questions built around working a rush without a big kitchen behind you, and a screening workflow sized for a small independent restaurant, not a chain.

Most line cook postings ask for years of experience and a list of cuisines. Neither tells you whether someone can hold a station alone when six tickets hit the rail at once. The line cook who wrecks your Friday isn't the one who's never made a beurre blanc. It's the one who falls behind the moment the pace picks up, cuts corners on temp checks when nobody's watching, or melts down the first time a plate comes back. A resume shows a list of past kitchens. It can't show whether someone stays fast and clean under real volume, owns a mistake instead of hiding it, or shows up for the Friday and Saturday nights that make or break your week. This guide is built to screen for speed, food safety habits, and composure under a rush, not for a list of restaurant names.

What a line cook actually does at a small independent restaurant

At a chain, a new line cook usually walks into a system built for them: a training binder with photos of every plate, a certification quiz on the fryer and the flat-top, a few shadow shifts next to a trainer, a sous chef and an expediter running the pass so no single station ever has to carry the whole ticket alone. At a small independent restaurant, most of that doesn't exist. The owner or the chef shows a new hire the station once, maybe tastes a few dishes with them, and by their second or third shift they're running that station solo during real service, with real tickets stacking up and nobody free to jump in if they fall behind.

That gap is what makes this hire different from a line on a resume. A line cook at a small restaurant isn't following a laminated plating guide with a manager double-checking every plate. They're remembering that table nine's order has a shellfish allergy, catching that the fryer oil is starting to smoke before it ruins a ticket, and keeping their station moving while also covering for whoever's out sick that night, because there's no float staff to call in. One line cook who falls behind on a busy Friday doesn't just slow their own station, it backs up the whole kitchen and shows up as a table that waited forty minutes for a burger.

You're also usually hiring someone who reports straight to the owner or the chef, not into a shift lead and a kitchen manager and a district chef the way a chain structures it. There's no layer between "how you cook tonight" and the person whose name is on the lease. That's worth being upfront about in your process: the job is more autonomy and more exposure than the same title at a bigger operation, and some candidates want that, and some don't.

The core responsibilities, in practice:

  • Running a station (grill, sauté, fry, prep, whatever the role covers) at full speed during a rush, without a sous chef or expediter absorbing overflow
  • Reading the ticket rail and prioritizing what fires first so a whole table comes up together
  • Following food safety basics without being told: temp checks, proper storage, avoiding cross-contamination, especially around allergies
  • Keeping plating and portioning consistent from the first ticket of the night to the last, when everyone's tired
  • Catching and fixing a mistake (an undercooked item, a wrong order, a missed allergy note) before it reaches the guest, or owning it fast if it doesn't
  • Communicating clearly with the rest of the kitchen and with servers during a rush, calling out times and shortages in real time
  • Keeping the station clean and organized through service, not just at close
  • Showing up reliably for the night and weekend shifts, since that's when most of a small restaurant's volume and revenue happens

Job description you can post today

Copy this, then adjust the specifics (your stations, your menu, your hours) to fit your kitchen.

Line cook
[Restaurant name] is hiring a line cook to run a station on our kitchen line. You'll be responsible for your section during service: prepping, cooking to our standards, and keeping pace when the tickets stack up, without a big brigade behind you.

What you'll do
Prep your station before service, cook and plate consistently to our standards, read the ticket rail and prioritize what fires first, follow food safety basics on temp, storage, and cross-contamination, communicate clearly with the rest of the line and with servers during a rush, and keep your station clean and organized throughout the shift, not just at close.

What we're looking for
Someone who's worked a real kitchen line before, fine dining or not. You should be able to keep your speed and your cleanliness up when things get busy, know or be willing to learn basic food safety practices, and speak up right away if something's wrong with an order instead of sending it out and hoping. Reliable availability for nights and weekends matters more to us than a specific cuisine background.

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

[Insert pay, per your company's policy and any applicable state salary transparency requirements. Line cook pay varies by region, kitchen volume, and station, so check current local rates before you post.]

11 interview questions, and what a good answer sounds like

1. Walk me through the last time your station got slammed with no one around to help. What did you do first?

This is the core question for a small kitchen, where there's no expediter or extra hand to absorb the overflow when a station falls behind. A strong answer names a real sequence: what they triaged first, how they reset their mental order of tickets, what they said to the rest of the line to buy time. A vague answer, or one that assumes a manager or a second cook would step in to save them, is a flag, because on a small line that backup often isn't there.

2. A plate comes back from the dining room because it's wrong or undercooked. What do you do in the next thirty seconds?

Listen for ownership before excuses. A strong candidate takes the plate back, fixes it immediately without arguing about whose fault it was, and tells whoever's running the pass what happened so it doesn't repeat. Someone who describes getting defensive with the server, or quietly re-firing it without telling anyone, is showing you how they'll handle a mistake when the owner isn't standing right there.

3. Tell me about your food safety habits on a normal night, not just what you'd say if a health inspector asked.

You want specifics, not the textbook answer. A strong response describes an actual routine: checking temps at set points, using separate boards or bins for raw protein, rotating stock, washing hands between tasks without being reminded. A candidate who can only recite generic rules ("always wash your hands") without describing how they actually do it during a busy shift probably hasn't built the habit yet.

4. How do you keep your plating and portioning consistent between the first ticket of the night and the hundredth, when you're exhausted?

This tests discipline under fatigue, which is different from skill. A good answer names a concrete method: weighing or measuring key items instead of eyeballing late in the shift, checking their own plates against a mental standard, slowing down for a second on the ones that matter most. Someone with no answer here is telling you your food quality will drop off a cliff during your busiest, most profitable hours.

5. Describe a time you had to speed up without cutting a corner that mattered. How did you tell the difference?

Speed and consistency pull against each other on a small line with no slack in the schedule, and this question separates people who understand the tradeoff from people who don't. A strong answer names a specific corner they wouldn't cut (temp, allergy check, a key prep step) and one they would streamline (plating flourish, an extra garnish) when the rail is full. Someone who says they just "work faster" without naming what they protect hasn't actually thought about where the line is.

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

Reliability is one of the biggest things to screen for in this role, since restaurant 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 second job, a class schedule, childcare, is more trustworthy than one who agrees to everything and doesn't show up the first Saturday.

7. If you saw a coworker skip a food safety step, like not changing a cutting board between raw chicken and produce, what would you do?

This gets at whether someone will actually protect your kitchen when you're not standing there, not just follow rules when watched. Listen for whether they'd say something in the moment, to the coworker directly or to whoever's running the shift, versus letting it go to avoid friction. No single answer proves someone's reliable on this, so weigh it alongside the rest of the interview rather than as a pass or fail on its own.

8. What's the most physically demanding kitchen shift you've worked, and what got you through it?

You're checking whether they understand the real pace of a small kitchen on a packed Friday night: hours on your feet, heat, moving fast in a tight space, often with fewer people than the ticket volume would call for at a bigger operation. A strong answer describes real conditions and a real coping strategy. Someone who can't point to anything comparable may need an honest conversation about the physical demands before you hire them.

9. Tell me about a time you had to learn a new dish or a new station fast, with no formal training program to lean on.

Most small restaurants don't have a multi-week onboarding process, so you're testing self-directed learning, not just past knowledge. A strong answer describes an active approach: watching the chef plate it once, asking specific questions, tasting components to understand the balance, writing a quick note for themselves. Someone with no answer here is telling you they'll need more hands-on time from you or your chef than you may be able to give.

10. Describe working directly under a chef or owner, without a sous chef or kitchen manager in between. What was that like?

This surfaces whether someone can take direction and feedback straight from the top, which is the actual reporting structure at most small restaurants. A strong answer talks about communicating directly, asking clarifying questions instead of guessing, and taking correction without getting defensive. Someone who's only ever worked in a kitchen with layers of management between them and the chef may need an adjustment period you should ask about honestly.

11. Why are you looking for a line cook role right now, and what would make this the kind of kitchen you stick with?

Given how much turnover this role sees, listen for concrete, specific reasons over generic answers like "I love cooking." A candidate who names something you can actually deliver, a schedule that works, a chef they want to learn from, a menu they're excited to cook, is more likely to still be on your line in six months than one who can't say why this kitchen over any other.

A scorecard you can score candidates against

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

What you're scoringStrong signalWeak signal
Working a station alone under pressureNames a real triage sequence and how they reset their order of tickets, without assuming backup would appearAssumes a manager or second cook would step in, which on a small line often isn't there
Owning a mistakeTakes the plate back, fixes it fast, flags it to the pass so it doesn't repeatGets defensive with the server, or quietly re-fires it without telling anyone
Food safety habitsDescribes an actual routine: temp checks at set points, separate boards for raw protein, rotating stockOnly recites generic rules without describing how they actually work a shift
Speed vs. consistencyNames a specific corner they'd never cut and one they'd streamline when the rail is fullSays they'd just "work faster" with no sense of where the line is
ReliabilityNames a real availability conflict up front instead of agreeing to every shift"I'm flexible" with no specifics, the profile that no-shows the first Saturday
Protecting the kitchen when unsupervisedWould actually say something about a coworker skipping a food safety stepWould let it go to avoid friction

How to screen line cook candidates without losing a week to it

If you're hiring a line cook, you're probably also filling a restaurant server role or a restaurant shift manager role on roughly the same cycle, since small restaurants rarely lose just one position at a time. 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.

A workflow that fits a small independent kitchen:

  • Ask about availability before anything else. Line cook turnover runs high, and a lot of it comes from candidates who never intended to commit to the Friday and Saturday nights the role 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 a conversation.
  • Use light resume screening, not a filter for years of experience or fine dining pedigree. Our resume screening tool is useful here mainly to catch basic gaps, work authorization, any real line experience, not to rank candidates by which restaurants are on the resume.
  • Add a one-way video interview for communication and how someone talks through pressure. A line cook's job is staying calm and clear when the rail fills up, and none of that 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 hear how someone actually thinks through a rush before you spend an in-person slot on them.
  • Close with a paid trail shift on the actual line. For this role more than almost any other, a couple of hours cooking next to your current team during real volume tells you more than another round of questions ever could. Use it to confirm what the video already showed you about pace and composure, and to see the knife skills and cleanliness habits a conversation can't reveal.
  • Keep the whole process fast. This role pulls a high volume of low-commitment applicants, and the strongest candidates you find will often take whichever offer moves first. A screening workflow that gets from application to trail shift in days, not weeks, is the difference between hiring the person you wanted and losing them to the kitchen down the street.

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

Common hiring mistakes for this role

Weighting cuisine and pedigree over real line speed. A resume full of impressive restaurant names doesn't tell you whether someone can hold a station alone during a Friday rush with no expediter backing them up. Someone from a high-volume diner or fast casual kitchen can outwork a fine dining candidate who's only ever cooked in a controlled, well-staffed environment. Screen for pace and composure under pressure, not the restaurant names on the page.

Skipping the trail shift to save time. It's tempting to hire off a good conversation alone when you need the position filled yesterday, but a trail shift is the single best predictor of how someone will actually perform on your line. A candidate who interviews well can still fall apart the first time six tickets hit the rail at once. Pay for a short trail and watch them cook before you make the offer.

Assuming a confirmed start date is a real one. Line cook 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 at the station, 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. Line cook 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 current kitchen 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.

Running a heavy, multi-round process for a high-volume hourly role. Given the churn this role sees and how quickly a good candidate gets scooped up elsewhere, a slow process with three rounds of interviews for an hourly kitchen job will lose you candidates to whoever hires faster. A fast, consistent screening process, availability check, a short video, a trail shift, beats a thorough but slow one for this role every time.

Recommendation

What should your screening process look like?

Answer six quick questions about how you hire. We'll point you to the screening steps that fit, so you spend your time on the candidates worth a conversation.

How many applications does a typical position pull in?
How much can you tell from a resume for these roles?
Do you need proof of a specific skill before a live round?
How do first-round phone screens fit your week?
How big is the team doing the screening?
What matters most in how you compare candidates?

What each result looks like

Layer all three signals

Your hiring spans high volume and high stakes, so no single step covers it. Layer all three: score resumes first, hear candidates on a one-way interview, then confirm with an assessment. Each step narrows the field, and you make the call at every stage.

7-day free trial. No credit card required.

Built for small business hiring

Screen every role in this guide inside Truffle

Post the job description, run resume screening, a one-way interview, or an assessment, and get a ranked shortlist. Public pricing, 7-day free trial, no credit card.

Truffle is candidate screening software built for the AI age

Start free trial

7 days · 30 credits · no card required

Start typing to search 300+ pages on hiretruffle.com.