How to Screen Line Cooks: 9 Questions and What to Listen For Screening Interview Template

Tell me about your line cooking experience. What kind of kitchen was it (fine dining, high-volume casual, banquet, institutional or senior-living dining, quick service), which stations have you run (grill, saute, fry, garde manger, prep), and roughly how many covers did a busy service put out?

What this assesses: This is the calibration question, and it carries more weight here than anywhere else on the list because line cook covers four jobs that barely overlap. Listen for the kind of kitchen as much as the station. High-volume casual is repetitive and fast, built on the same dozen dishes, and those cooks are usually excellent on speed and shaky on anything off-menu. Fine dining is the opposite: smaller covers, longer tickets, more technique, more components per plate, and some of those cooks genuinely struggle when the ticket count triples. Banquet is a different trade entirely, where 400 plates leave at once out of a hot box or an Alto-Shaam and almost nothing is cooked to order, so a banquet cook may be outstanding on volume and production and have never worked a rail. Institutional and senior living dining is three meals a day, seven days a week, to a diet order rather than a guest order. None of these is a better cook than the others, they are differently useful, and a candidate who can say where they fit is more credible than one who claims all of it. Strong answers name the concept, name the station that was theirs, and give a real number: 280 covers on a Saturday, 140 tickets between six and eight, a 600-person plated banquet. They also distinguish what they owned from what the kitchen did. Be cautious with a candidate who says they helped in the kitchen, cannot name which station was theirs, or describes only prep and cold side and then assumes a full station during a rush is the same job. Do not screen on years alone either. Two years on a busy sauté station under a chef who actually taught beats eight years of portioning in a prep kitchen.

Walk me through how you keep your station moving when the tickets are stacking up, you are in the weeds, and the expo is calling for plates. How do you stay on top of a slam?

What this assesses: This is the question that predicts first-week washout, and the specific thing you are listening for is whether the candidate thinks in terms of the whole rail or one ticket at a time. Strong answers describe sequencing: reading the rail before touching a pan, counting the board all day so they are cooking six chicken rather than one chicken six times, firing by cook time so the longest item goes on first and everything lands together, and working two or three tickets ahead instead of reacting to whatever the printer just spat out. They talk about the pass as a deadline they are managing backwards from. They mention communication out loud, calling heard on a fire, telling expo what is thirty seconds out and what needs four minutes, and saying they are going down before they are buried rather than after, because a cook who asks for a hand at ticket eight is cheap and one who collapses at ticket twenty costs the whole service. The best answers also name what they stop doing during a slam: no deep cleaning, no side projects, hold the station together and catch up after the push. Be cautious with a candidate who describes no method at all and says they just work faster, because speed with no order is how tickets get sent incomplete and food sits under the heat lamp going cold. Be more cautious with one who blames the rush on servers, expo, or the kitchen being understaffed, and with one who cannot name a service where they genuinely got buried, since that usually means they have never worked a volume high enough to find out. Someone who tells you about a night they went down, and what they changed afterward, is giving you a better answer than someone who claims they never get in the weeds.

Give me your numbers without looking them up: what temperature do you cook chicken to, what about a burger, what is the danger zone, what do you hold hot food at, and how do you cool a big batch of soup or chili safely? Then tell me what food-handler card you hold with its expiration, how you keep allergens separated during a busy service, and whether you have cooked to therapeutic or texture-modified diets.

What this assesses: This is the closest thing to a skills test that fits in a written screen, because the numbers cannot be bluffed and a working cook knows them cold. Under the FDA Food Code the answers are poultry at 165 degrees, ground meat at 155, whole-muscle beef, pork, and fish at 145, a danger zone of 41 to 135, and hot holding at 135 or above. Reheating a previously cooked item for hot holding goes to 165. The cooling question is the one that separates people, because two-stage cooling is where most real violations and most actual outbreaks come from: 135 down to 70 within two hours, then 70 down to 41 within four more, six hours total, and the second half of that is impossible in a deep container, so strong answers immediately describe breaking the batch into shallow pans, using an ice wand or ice bath, and logging the temps rather than guessing. Listen for a calibrated thermometer and a habit of checking the thickest part rather than a claim that they can tell by eye. On allergens, the answer you want is separate pans, separate utensils, a hand wash and a glove change, an allergy ticket cooked first or cooked apart, and telling the chef or the server rather than handling it silently. Credit anyone who knows the list runs to nine majors now, since sesame was added under the FASTER Act effective January 2023 and plenty of cooks still work off the old eight. Date marking is a good tell: ready-to-eat items held over 24 hours get marked and run out at seven days at 41 or below. If the kitchen is senior living, long-term care, or a hospital, push on texture-modified work and look for IDDSI language, Level 4 pureed, Level 5 minced and moist, Level 6 soft and bite-sized, or thickened liquids, because a consistency error in that setting is an aspiration risk rather than a comped plate. Be cautious with a candidate who says you just know when it is done, who cannot produce a single temperature, who holds no card and has no plan to get one, or who treats cooling as leaving it on the counter to come down. Ask for the card with its expiration date and verify it yourself rather than taking the claim.

A big part of the job is making the same dish the same way every time. How do you stay consistent on portions, plating, and recipe spec when you are moving fast, and what do you do when a plate does not look right before it leaves your station?

What this assesses: Consistency is the whole difference between a line cook and someone who cooks well at home, and it is also where food cost lives. A six-ounce portion served at eight ounces is a 33 percent overage on the most expensive thing on the plate, and no amount of talent makes that back. Strong answers are unglamorous and specific: they work off a recipe card and a plate photo rather than memory, they use the tool the spec calls for, a portion scale for proteins, a numbered scoop, a ladle, a ring mold, and they scale the batch rather than eyeballing a double. They know their own station's specs by heart because they cook them two hundred times a week, and they can tell you one, which is a good thing to ask for. On the plate that does not look right, the answer you want is that it does not leave the station. They wipe the rim, remake the component, or re-fire and tell expo it is coming thirty seconds behind rather than sending something they know is wrong and hoping the server does not notice. The best answers mention tasting through service, checking the first plate of a new batch against the standard, and flagging a problem upstream when the prep is off rather than quietly compensating for it. Be cautious with a candidate who describes portioning by hand to save time, who says close enough or the guest cannot tell, or who gets defensive about following a recipe and wants to cook it their way. That last one is worth taking seriously: creativity is an asset in a chef and a liability on a line, where the job is to reproduce someone else's dish exactly. Also be cautious with anyone who says they have never sent a plate they were not happy with, because every cook has, and the useful answer is what they did about it.

Tell me how you set up and prep your station before a shift. How do you decide what mise en place you need, and how do you keep your station clean and organized during service?

What this assesses: Service is won or lost before the first ticket, and this question tells you whether the candidate understands that. Strong answers describe a routine with a sequence: check the prep list and the par levels, look at the reservation book or last week's numbers to decide how much to build, taste and temp what came off the previous shift, run a line check before the doors open, and get the station set so everything they touch most is closest to their hands. Listen for the forecasting part, because under-prepping and running out of a component at 7:30 on a Saturday is one of the most expensive mistakes on a line, and over-prepping walks straight into food cost and waste. The best answers describe a backup strategy: a second pan in the lowboy, par stock in the walk-in, knowing what they can fire from frozen if they get caught. On working clean, you want wiping and resetting continuously rather than at the end, keeping the rail and the pass clear, a sanitizer bucket with a towel in it, changing a cutting board instead of pushing on with a dirty one, and keeping raw proteins below and apart from ready-to-eat items in the lowboy. The detail that marks an experienced cook is that they clean during the lulls, not after the rush, because after the rush they are tired and the cleaning gets worse. They also hand off a station in the condition they would want to receive it, labeled, dated, rotated first in first out, and they tell the next cook what is low. Be cautious with a candidate who says they show up and figure it out, who treats cleaning as the dishwasher's job, or who describes a station where they are hunting for things mid-service, since a disorganized station slows every cook next to it and that cost shows up as ticket times across the whole kitchen.

Kitchens are tight, loud, and high-pressure. Tell me about a time you had a conflict with a coworker or a chef during service, or a night the kitchen was short-staffed and slammed. How did you handle it?

What this assesses: A line is a small team working shoulder to shoulder in heat and noise, and one cook who cannot absorb a correction or will not cover a station degrades the entire kitchen. What you are listening for is whether the candidate can separate the moment from the aftermath. Strong answers describe taking the direction during service without arguing, because a rush is not a negotiation, and then raising it with the chef or the coworker afterward when the food is out and everybody can hear. They distinguish between being corrected and being disrespected, and they have a sense of proportion about which was which. On the short-staffed night, the answers you want are concrete: they picked up a second station, moved to where the tickets were, simplified what they could, came in early or stayed through a double, and they describe it as what the night required rather than as a favor they are still owed. Credit a candidate who mentions helping the cook next to them without being asked, since that instinct is the single best predictor of whether a line holds together on a bad night. The best answers also include some self-awareness about their own worst moment, snapping at somebody, slamming a pan, and what they did about it. Be cautious with answers that escalate, that involve walking off the line or quitting mid-service, that blame every coworker and every chef they have ever had, or that describe kitchen culture as a reason yelling and personal abuse are acceptable, which tells you what they will bring to your kitchen. Be cautious in the other direction too, with a candidate who cannot name a single conflict or a single genuinely bad night, because that usually means thin real-service experience rather than unusual serenity.

This job means standing on a hot line for an eight to twelve hour shift, lifting cases and stock, and working straight through a rush without a real break. Can you perform that with or without a reasonable accommodation, and what is the longest, busiest stretch you have actually worked on a line?

What this assesses: A real share of first-week quits are not about skill at all. They are a cook discovering that ten hours in front of a flat top in a kitchen that sits above 100 degrees in August is harder than the job they imagined. Ask it as a job-demands question with the with or without a reasonable accommodation framing, and keep it there. Do not ask about health conditions, injuries, prior workers compensation claims, or limitations, because those questions are off limits pre-offer under the Americans with Disabilities Act, and you do not need them: what you need to know is whether the person can do the posted job, which is exactly what this phrasing asks. Strong answers are matter of fact rather than heroic. They name a real shift length and a real volume they have already worked, ten hours on grill, a double on a holiday weekend, a 400-cover banquet push, and they describe habits that show they have done it: hydrating through service rather than after, slip-resistant shoes, long sleeves or a side towel for the oven, pacing the prep so the rush is not a sprint, eating before service instead of at midnight. Credit anyone who mentions the specific physical realities that catch people out, lifting a full stock pot or a case of oil, carrying sheet pans to the walk-in, the fryer, and standing on a rubber mat with no real break between four and nine. Be cautious with a candidate whose entire kitchen history is prep, cold side, pantry, or four-hour shifts and who assumes a full line is the same work at a different speed. Be more cautious with one who sounds surprised that the job is physical, or who answers only that they are a hard worker without naming a single shift they have actually stood through, because the line is an expensive place to find that out in week one.

Restaurant volume is heaviest on nights, weekends, and holidays, and shifts can run long or turn into doubles when someone calls out. What days and shifts can you work, and are nights, weekends, and holidays a problem for you?

What this assesses: Availability is the binding constraint in food service and the most common reason a genuinely good cook is still the wrong hire. Ask it early, because no amount of station skill fixes a candidate who cannot work when the kitchen is busy, and finding that out in week two costs you the whole search. Strong answers are specific and volunteered rather than extracted: actual days, actual earliest and latest times, a clear yes on Friday and Saturday nights, a clear answer on holidays, and an honest note on the one night they cannot do and why. Credit a candidate who raises a constraint unprompted, since someone who tells you up front that they have a class on Tuesdays or pick up a kid at six is far more reliable than someone who agrees to everything and then starts declining shifts. Push on the specifics that quietly break schedules: a second job and whether its shifts are fixed or variable, childcare coverage for a close that ends at eleven, school terms, and whether the stated availability is theirs to control. Weak answers want a weekday daytime schedule a restaurant cannot offer, which is worth noting rather than discarding, because an institutional or senior living dining kitchen running breakfast and lunch may be exactly where that person fits even though your restaurant line is not. Be most cautious with vagueness, with the candidate who says they are flexible or open to anything and gives no hours at all, since flexible almost always narrows the moment a real Friday, Saturday, and holiday rotation lands. Get it in writing here and compare it against the schedule you actually need to fill before you spend an hour on a working interview.

A no-show on a busy night means the rest of the line covers your station on top of their own. How is your attendance record, how do you get to work, and what is your backup plan if your ride falls through for a closing shift that ends after transit stops running?

What this assesses: Attendance is the single largest reason a line cook hire fails inside 30 days, and it beats skill as a predictor. A cook who is merely competent and always there is worth more to a kitchen than a talented one who misses two Saturdays a month, because every absence lands on the people who did show up and that is how a good crew starts leaving. Transportation is the mechanical cause more often than motivation is. A close ends at eleven or midnight, buses in most cities have stopped, rideshare surge after last call is real money against an hourly wage, and a cook who was fine for a 3 p.m. start quietly becomes unreliable on the shifts that matter most. Strong answers are concrete on both halves. On attendance they give a real record, including the honest version, and they describe the mechanics of calling out: how much notice, who they call, and whether they try to find coverage first, because a cook who calls the chef at nine the night before is a different employee from one who texts at four for a five o'clock start. On transportation they name the actual method and a real fallback: a car plus a coworker who lives nearby, a partner on a predictable schedule, a bike with a plan for January, cash set aside for a ride home after close. Credit anyone who has already thought through the late ride specifically, since that means they have worked closes. Be cautious with a candidate who treats showing up as conditional on how they feel or on whether they like the shift, who has no fallback at all and a single point of failure for getting to work, or who is evasive about a gap. Ask about gaps plainly and listen to the explanation rather than assuming the worst, because the hospitality labor market churns for structural reasons and a short gap is common. What should concern you is a pattern of leaving jobs without notice, which is the behavior most likely to repeat.