Cook (Restaurant) Interview Questions & Answers

1. Tell me about yourself.

Why they ask: To calibrate tone, warmth, and how you frame yourself in 45 seconds. A chef wants to hear a cook, not a résumé — where you've cooked, what you've run, what you're chasing next.

"I've spent the last two and a half years on the line at a 120-cover Italian trattoria in the neighborhood. I run sauté four nights a week and swing garde manger on Sundays. Peak Fridays we push around 180 covers with a full pasta menu — I own the pasta drop and the protein sauté side of the station, and my ticket time on the pass has been under nine minutes on average for the last quarter. Before that I did about a year at a breakfast-lunch café learning fundamentals. What I like about your restaurant is the wood-fire program — I want a station where I have to think about heat and timing at that level, and this is the room where I want to build that. Long term I'm chasing a sauté-lead or junior-sous role over the next eighteen months."

2. Why do you want to work in this kitchen specifically?

Why they ask: Chefs see a lot of "I need a job" applicants. They're trying to find out whether you'd have walked into the restaurant next door just as fast — and if so, they'd rather hire the cook who wouldn't.

"I ate here last Thursday, sat at the counter, ordered the pasta special and the pork chop. The pasta drop was tight and the pork chop had a real rest on it — you could see it on the plate. I know the room seats about eighty and you push 140 covers on a Friday, which is a step up from the concept I run now, and I want to work under a chef with a wood-fire program. On top of that, I know two of your line cooks from culinary school and both say the kitchen respects mise and doesn't tolerate shortcuts. Specific room, specific dish, specific reason — that's why I applied here first and not two blocks up."

3. Tell me about a shift you got weeded and how you dug out.

Why they ask: The single most important behavioral for a line cook. Chefs want to hear that you don't panic, that you name the problem out loud, and that you get back on time without dragging the rest of the line down with you.

"About four months ago, a Friday, we lost our garde-manger cook to a hand cut mid-service. I was on sauté and had to swing salads and cold apps while running six sauté tickets already fired. My task was to stay honest about time and stop the ticket window from stacking. I called it — 'garde-manger down, sauté is ninety-second delay for the next ten minutes' — so expo could talk to the front and stagger fires. I dropped my mise for the two cold apps into a hotel pan, brought them to my station, and ran the low-effort ones off the sauté rail while I fired proteins. The chef pulled a prep cook up to garde in about twelve minutes. My sauté drop stayed under a minute over standard, no tables got dragged, and we lost zero comps on that shift. What worked was calling the delay out loud early — nobody hides a weed on a real line."

4. Tell me about a time you disagreed with a chef or sous.

Why they ask: The chef's rule is the rule during service — but they want to know you have a real point of view and know when to raise it. They're testing whether you can push back cleanly and drop it when the answer is no.

"We were prepping a family-meal short-rib braise and my sous had us starting at high heat with the lid off for the first hour. My read was the fond was building too fast on a light-bottom pot. I said 'chef, quick — I'm reading this fond hot, want me to drop it forty degrees and lid it?' She looked, agreed, dropped it fifty. If she'd said no, I'd have run it hot — service isn't the moment to hold a stand — but the point is I flagged it while it was fixable, three minutes not twenty. The habit I keep is naming what I'm seeing in fifteen words or less and letting the chef make the call."

5. Tell me about a time you covered a station you had never run.

Why they ask: Kitchens are a game of gaps. Chefs want cooks who can slide into a hole without a full training block and without pretending to know what they don't.

"A Sunday brunch, our fry cook called out an hour before doors. I'd shadowed fry for two shifts but never run it live. My task was to hold the station through a 180-cover brunch without stalling the rail. Before doors I walked my chef through what I knew and what I didn't — 'I've got the fry times on the wings and the fritters, I'm not sure on the calamari sequence' — and she gave me a two-minute walk on the calamari. I asked the grill cook to shadow-call my first three fry tickets so I could adjust. First ninety minutes I ran two tickets slow, was on standard by cover 40, and we finished the shift under a minute over standard on fry. What made it work was flagging what I didn't know before it turned into a comp."

6. Tell me about a time you caught a food-safety violation.

Why they ask: ServSafe on paper is one thing; the honesty to stop a plate on the line is another. Chefs are testing whether you'll hold the line under pressure.

"During a Saturday-night rush, our garde-manger cook plated a raw-bar tower with tuna crudo that had been sitting at room temp for what I counted at around eighty minutes — I'd been tracking on my station timer. My task was to stop the plate without escalating in front of the guest. I called quietly to the sous — 'chef, that tuna's out of temp, I want to swap it' — she checked her own timer, agreed, we plated fresh from the walk-in and I dropped the flagged tuna into the trash bin with the sous watching, per policy. The guest got their tower on time, we lost about ninety seconds and the cost of one portion of tuna, and we would have lost a lot more if it went out. I keep a fifteen-minute check on any protein sitting at pantry temp — the timer is on my station board, not in my head."

7. Tell me about a time you helped a struggling teammate.

Why they ask: A chef wants a cook who props up the line, not one who watches the sauté cook drown at cover 90. Kitchens run on the person next to you.

"A new grill cook was on his third week and stacking tickets during a Friday rush — he had eight fires up and was on his sixth minute over standard. I was on sauté with a lighter rail. I walked over, took his fire order sheet, called back his next four tickets so he could reset his rail sequence, and put two of his sides — the mash and the wilted spinach — onto my sauté rail so I could plate-drop for him. He caught up inside twenty minutes and finished on standard for the rest of the shift. I flagged nothing to the chef in the moment — that's not the point during a rush — and after service I told him the two things I'd change about how he was sequencing so he wouldn't need me next Friday. He didn't."

8. Tell me about a time you burned or dropped a dish during a rush.

Why they ask: Every cook drops food. The chef is testing whether you call it, refire clean, and don't hide it — because a hidden mistake becomes a returned plate becomes a public review.

"On a Thursday, mid-fire on a duck breast, I overshot the sear by about forty seconds — the skin was black, not crackling. I called it immediately — 'refiring duck on twelve' — pulled a new breast from my mise, dropped it, and told the expo we were ninety seconds late on that ticket. Expo talked to the front, the server dropped a comp appetizer, the guest got their duck three minutes over the standard drop and never wrote a review about it. What lost me forty seconds gained me back nothing worth hiding it for — a hidden overshoot becomes a plate coming back cold and the chef finding out from a comp report the next morning."

9. Tell me about a time you reduced waste or cost on your station.

Why they ask: Food cost is a chef's most-watched number. Cooks who think about yield without being asked are cooks who get moved up.

"On our pasta station, we were prepping fresh dough daily and consistently 86'ing about a pound and a half at the end of service — call it $6–8 in flour and eggs and about twenty minutes of prep labor. I noticed the loss happened on our slower Wednesday-Thursday shifts. I proposed to my sous we cut Wednesday prep by two hundred grams and run a smaller Thursday backup that we could scratch-make if needed. She agreed. Over eight weeks we cut Wednesday waste to almost zero and the Thursday backup got scratched twice — both handled inside seven minutes because the mise was clean. Net was around $70/month in flour and eggs and about eight labor hours saved. Small, but real, and it built trust with the sous for bigger asks."

10. Walk me through your last month of shifts — what did you miss, what did you cover?

Why they ask: The most direct reliability question chefs ask. They're looking for a specific answer and they've heard every excuse — the honest answer wins.

"Last thirty days I was scheduled twenty-two shifts. I worked all twenty-two. Two of them I picked up as covers when other cooks called out — one Sunday brunch and one Wednesday dinner. I've had one call-out in the last four months, a stomach bug on a Tuesday; I called four hours before shift and my sous had time to bring in coverage. My commute is a fifteen-minute bus and a five-minute walk, and I'm forty minutes before doors every shift. I'm not building this into an answer for you — that's actually how it runs. My last chef will confirm."

11. Where do you see yourself in three years?

Why they ask: Chefs invest training in cooks who plan to stay long enough to earn it back. A vague answer says you'll leave in six months.

"Three years from now I want to be running a station as a sauté lead or junior sous in a concept doing 150+ covers a night, ideally in a chef-driven room like this one. To get there I need another twelve to eighteen months owning sauté through peak with a menu that changes seasonally, then six to twelve months at expo learning to run a service. I'm not looking to open my own place — I'd rather deepen at concepts I respect than run my own. This restaurant is the room I want to build that in, which is why my second question when I walked in was how you promote from sauté to sous."

12. Why are you leaving your current kitchen?

Why they ask: Chefs are looking for red flags — bad blood with the chef, a firing story you're spinning, a wandering career. The clean version wins.

"My current chef and I have a good relationship — she'd take a call from you. The reason I'm looking is the menu at my current room hasn't changed in fourteen months and I've been running the same three sauté fires the whole time. I'm ready for a concept where the menu moves seasonally and I have to keep learning. I gave my sous heads-up I was looking a month ago and I'll give proper two-week notice when I sign somewhere. That's the whole story."

13. Walk me through the temperature-danger zone and the four-hour rule.

Why they ask: Base-layer food safety. If you can't recite this cleanly, ServSafe on your résumé is decorative.

"The temperature-danger zone is 40°F to 140°F — anything held between those temps grows bacteria fast. The four-hour rule is cumulative: a protein or dairy item can spend a total of four hours in the danger zone across its life, not four hours per stop. Once it hits four cumulative hours, it goes in the trash — no exceptions. On my station I timer anything sitting at pantry temp, I don't temper proteins on the counter for more than forty-five minutes, and I recheck cold-side reach-in temps at the start of every shift with a calibrated probe. Cold-side reach-ins live under 40°F; hot-hold under a heat lamp lives over 140°F. I keep a calibrated thermometer in my apron and I calibrate it monthly in an ice bath."

14. What are the internal temperatures you'd hit for chicken, pork, ground beef, and fish?

Why they ask: Direct temp check. Chefs want the numbers, not "medium."

"Chicken and all poultry: 165°F, held for at least fifteen seconds. Pork: 145°F with a three-minute rest, though most operations still cook to 160°F+ for safety on wholesale pork. Ground beef and any ground meat: 160°F — grinding contaminates through the mass, so pink is not safe. Whole cuts of beef and lamb: 145°F for medium-rare, guest choice with menu-item consent. Fish: 145°F or until the flesh flakes and is opaque — I use flake plus probe. Reheated leftovers: 165°F for fifteen seconds before service. I probe every protein I plate and I calibrate weekly."

15. Walk me through your allergen protocol on a shellfish or nut ticket.

Why they ask: Allergens are the #1 kitchen liability. A cook who fumbles this answer will not touch the line.

"When an allergy ticket hits the rail, expo calls it out and it goes at the top of the fire order regardless of table sequence. I stop what I'm doing, wash my hands, change gloves, pull a clean cutting board and a clean pan from the sanitized rack — not from my station. I fire the allergen dish first before other fires so cross-contact risk is zero. I hand-carry it to expo instead of running it on the rail, and I verbally confirm to expo: 'shellfish-free chicken pasta for twelve.' Expo re-confirms with the server. For nuts, same protocol plus I check every component — the dressing, the finishing oil, the garnish — because tree nuts hide in emulsions. If I'm ever unsure whether an ingredient contains an allergen, I don't fire — I stop and ask the sous."

16. Walk me through your mise en place for a Friday-night dinner service.

Why they ask: Mise is the whole game. A chef learns more from this answer than from your résumé.

"On sauté for a 180-cover Friday, I'm in about forty-five minutes before doors. My par sheet from Thursday close tells me exactly what I need — I don't build mise from memory. I set my station left-to-right in fire order: proteins in the reach-in below me labeled and dated, aromatics and finishing herbs in ninth-pans up top, oils and butters at hand reach, three sauté pans stacked and one on the burner, tongs left of my burner, spider right. My par board is on the wall behind the burner. I run a mise check with my sous ten minutes before doors — she reads five items off my par sheet and I show her the pan. Cleanup is built into the setup — every pan I use has a return spot, and I break down clockwise from the burner so the next shift walks into a station they can find things in."

17. A four-top comes in with a soup, a salad, and two hot apps. How do you sequence?

Why they ask: Direct test of ticket-flow thinking. Chefs want to hear "all fours land together" without a beat of hesitation.

"All four apps have to land at the pass at the same time — the table doesn't want two guests staring at empty plates. The soup and salad are pantry-owned and hit the pass fast, call it thirty seconds. The two hot apps are mine on sauté, call it four to five minutes depending on the fires. I signal expo I'm ready to fire, expo holds pantry, I fire the hot apps first, at the two-minute mark I signal expo to fire pantry, and everything lands at the pass at the four-minute mark plus or minus fifteen seconds. If the hot apps are wildly different times — say a tartare and a seared scallop — I'd tell expo up front so we sequence around the scallop. Rule: whoever cooks the longest fires first, and pantry chases."

18. Break down a whole chicken for me — walk me through the cuts.

Why they ask: Fundamental knife check. Chefs often ask this at the office interview and then hand you a chicken during the stage to confirm.

"Chicken on the board breast up. First, remove the wings at the shoulder — slice through the joint, not the bone. Second, pull the legs — cut through the skin between thigh and body, pop the joint out with your palm, then slice through. Separate drum from thigh at the joint you can feel. Third, remove the backbone — flip the bird, cut down each side of the spine with poultry shears or a heavy knife, save the backbone for stock. Fourth, break the breastbone — flip breast-side up, press to crack, split down the keel bone into two boneless-in-skin breasts. Trim any excess fat and cartilage, save the tender if you want it separate. Total time on a stage should be under three minutes and you should end with eight pieces plus a backbone and a bag of trim for stock."

19. How do you prevent cross-contamination between raw chicken and produce?

Why they ask: Direct safety check that ties to color-coded boards, hand-wash discipline, and pan handling.

"Color-coded boards — red for raw meat, green for produce, yellow for cooked meat, blue for fish, white for dairy and bread. Never cross them. Raw chicken lives on the red board, produce on green, and if I break down chicken I sanitize the board with quat-sani and rewash before switching. Hands: after raw poultry, I wash to my forearms with hot soapy water for twenty seconds, dry with a single-use towel, glove up. Reach-in order matters too — raw chicken goes on the bottom shelf so nothing drips onto ready-to-eat food. If I'm doing raw prep and cooked plating on the same station, I run raw prep first, break down, sanitize, then switch to plating. Never the other way."

20. How do you portion consistently on your station?

Why they ask: Portion consistency drives food cost, guest experience, and expo timing. A cook who eyeballs is a cook who blows the budget.

"Every portion on my station has a spec: sauté pasta is six ounces of dry pasta per plate, protein is a five-ounce sear, finishing oil is a half-teaspoon. I portion into deli containers or quart bags at mise, so during service I grab a pre-portioned bag instead of eyeballing off a hotel pan. I weigh — I don't guess. Every twenty tickets I spot-check a plate on the scale and adjust if I'm drifting. The portion sheet is on my wall, not in my head, and if a new item comes on the menu I ask the chef for the spec before I run it once. Consistent portions are how the guest gets the same plate on a Wednesday as on a Saturday."

21. Walk me through fixing a broken beurre blanc during service.

Why they ask: A live diagnosis test — do you know why sauces break and how to reset them under time pressure?

"Beurre blanc breaks when the fat separates from the reduction — usually because it got too hot, too cold, or you rushed the butter mount. Fix in two moves. First, off the heat, into a warm bowl with a splash — call it a tablespoon — of hot water or hot cream. Second, whisk hard while dribbling the broken sauce back in slowly to re-emulsify. If it's still broken after that, start fresh: new reduction of shallot and wine, and this time hold the sauce over a warm water bath at 140°F to 160°F — never on direct flame. Prevention on my station is a warm water bath at the sauté rail and a whisk in reach; a broken sauce mid-service is thirty seconds if you catch it and three minutes if you don't."

22. What is the difference between cleaning and sanitizing, and when do you do each?

Why they ask: Base ServSafe. If you conflate these, you've never actually opened a station.

"Cleaning removes visible dirt, grease, and food debris — soap and hot water on a scrub pad. Sanitizing kills the bacteria that cleaning doesn't reach — a quat-sani solution at 200 ppm, a chlorine bleach solution at 50–100 ppm, or a heat-sanitize dishwasher rinse at 180°F. You clean first, then sanitize — sanitizer on top of food debris does nothing. On my station: cutting boards get cleaned after every protein switch and sanitized before I switch to a new protein family. The full station gets a clean-and-sanitize break-down every close. Sani buckets on the line get changed every two hours because they lose potency."

23. Your sauté rail has six fires up, expo just fired three more, and you're four minutes behind. What do you do?

Why they ask: Testing the moment of truth. Chefs want a specific playbook, not "I'd just push through."

"Call it out loud immediately — 'sauté is four minutes down, don't fire the next round yet.' That stops expo from stacking me deeper. Second, re-sequence what's on my rail — combine any two tickets with the same protein onto one sauté pan and split at plating, drop pantry-side items to another cook if allowed. Third, ask the sous or the chef for a hand — most chefs will pull a prep cook to my station in ninety seconds if I ask early. Fourth, protect the two oldest tickets first and eat the delay on the newest three. What kills you is hiding the delay; naming it gets you help and lets the front control guest expectations."

24. A ticket comes in marked "dairy allergy — anaphylaxis." How do you handle it?

Why they ask: Anaphylaxis-level allergen tickets are the highest-stakes fires in a kitchen. Chefs are testing full protocol.

"Stop the rail. Wash hands, change gloves, pull a fresh cutting board and a fresh sauté pan from the sanitized rack. Read the ticket twice out loud with expo to confirm exactly what needs to be excluded — 'no butter, no cheese, no cream, and I'll check the bread and the finishing oil.' Fire the allergen ticket first before anything else, ahead of table sequence. Use fresh olive oil or a dairy-free fat, not the butter block. Plate on a clean plate not from the plate stack under the butter warmer. Hand-carry to expo. Verbally confirm with the server: 'dairy-free pasta for table twelve.' Server confirms with the guest. If I'm ever unsure about an ingredient — like whether the pesto has parmesan — I stop and ask the sous. When in doubt, don't fire."

25. A steak comes back overcooked. What do you do?

Why they ask: Testing whether you'll own it, refire clean, and get it to the guest without losing the table.

"Read the ticket for original temp — say the guest wanted medium-rare and it came back medium-well. I take the return, don't argue about it, and refire immediately as a top-of-rail priority. Pull a fresh cut from the reach-in, season, sear, rest, plate. The refire is under seven minutes if I have inventory. Meanwhile expo talks to the front so the guest knows their steak is being remade. When the plate goes up, I probe it in front of the sous — 128°F for medium-rare — and it goes to the pass. Then, after service, I look at the original fire: was my sear time off, was the steak thicker than spec, was I probing shallow. Own the error, don't blame the guest, fix the process."

26. You drop a plated dish on the floor during a rush. What do you do?

Why they ask: Testing honesty and speed. The wrong answer is picking it up.

"Drop stays on the floor, food goes in the trash — always. Call it: 'dropped a fourteen on tuna, refiring.' Grab a fresh plate, refire the components. If any components are still salvageable (a garnish in a ninth-pan, a sauce that never touched the floor), reuse them; anything that touched the floor or the plate is trash. Notify expo so the front can update the table on timing. Clean the drop immediately if it's grease so no one slips — even mid-service, that's a safety thing. Refire is usually under three minutes if my mise is set. And write it on the comp sheet after service — hidden drops become auditing problems."

27. You get in for a Friday shift and realize you're short on a key mise item. What do you do?

Why they ask: Testing whether you problem-solve or panic. Chefs want you to have solved half the problem before you knock on their office door.

"First, quantify — exactly how short, and what tickets in the first hour depend on it. Second, look at what I can do in the forty minutes before doors: can I prep more from scratch, can I substitute an in-house item, can I pull from the walk-in from a component that's not being used tonight. Third, if none of that works, tell the sous: 'we're short thirty portions of the ravioli filling, I can scratch fifteen by doors, we'll need to 86 the ravioli after that unless we cross-pull from prep.' Give the chef a problem plus two options, not a problem. That's how you become the person the chef trusts with the station."

28. A coworker shows up to shift visibly sick and coughing over the line. What do you do?

Why they ask: ServSafe requires reporting; chefs want to know you'll act, not look away.

"Talk to them first, quietly, out of respect: 'you look rough, do you want to talk to chef about going home?' If they push back, I tell the sous or the chef directly — a coughing cook on the line is a code violation and an outbreak risk. Not my job to send them home, but it is my job to raise the flag before service starts. Meanwhile I'd offer to cover their opening prep if they can go on the schedule for a covered shift later. It's not a snitch move — it's the exact protocol the health inspector expects from anyone in the kitchen."

29. A chef is yelling at you during service and you disagree with the correction. What do you do?

Why they ask: Kitchens are still loud rooms. Chefs want cooks who can absorb heat during service and take the conversation offline.

"Yes chef. Hear it, execute what they asked, drop the argument until after service. During service is not the moment to hold a stand — the ticket window is running and the guest doesn't care who was right. After service, when things are quiet, I'd approach: 'chef, on that fire on twelve, my read was different than yours, can I walk you through what I was seeing?' That's the right time to discuss and it usually earns respect. If a chef is regularly yelling in a way that's abusive rather than about service, that's a different conversation and a different kitchen — but a hot moment on the line is not that."

30. You see a coworker plating a fish that fell on the floor. What do you do?

Why they ask: Integrity check. There is only one right answer here.

"Stop the plate before it hits the pass — 'chef, that fell, we need to refire.' Tell the sous immediately after. I don't confront the coworker in the middle of service — that's expo's or chef's job — but the plate does not leave the line. Full stop. A guest eating something off the floor is a lawsuit, a Yelp fire, and every job in the kitchen at risk. If the chef doesn't act, that's a conversation about whether I want to keep working here — but the first move is always stopping the plate."

31. The convection oven goes down mid-service. What do you do?

Why they ask: Equipment failures are routine. Chefs want cooks who reroute without panicking.

"Call it — 'oven is down, we need to re-route the roasted-veg side and the finishing pass on the salmon.' Then triage: what's already in the oven that we can finish another way (transfer to the second oven or the salamander), what's on the fire order in the next fifteen minutes that needs the oven, and what can we sub or 86. Give the chef options: 'we can push roasted veg to the range with a sear-and-cover, or we can 86 and swap for the sautéed greens.' Meanwhile someone calls maintenance. The station keeps running, the guest keeps eating, chef makes the call on subs, and after service we do a full postmortem on prep-list impact."

32. Chef changes a dish on the menu at 4pm the day of service. What do you do?

Why they ask: Kitchens change on the fly. Chefs want cooks who take the update, run it back to prove they got it, and don't grumble.

"Yes chef. Write down the new spec on my station board — new components, portions, plating. Repeat it back so I know I heard it right. Check my mise: what do I have, what am I short on, can I prep the delta in the ninety minutes before doors. Ask the chef to run one live for me at the pass so I plate it the way they want the first time, not the third. During service, first three fires I probe or check portion visually so I don't drift. After service, I write the change into my par sheet and my next-shift notes so nobody comes in tomorrow running the old spec."

33. A guest walks into the kitchen to compliment the chef, but chef is deep in service. What do you do?

Why they ask: Testing hospitality reflex and boundaries. Guests should not be behind the pass, and the answer has to protect both the guest and the line.

"Smile, thank them warmly, and walk them back to the pass or the front of house within about ten seconds — 'thank you so much, chef is at the pass on a rush, I'll let her know the moment she comes off, can I walk you back to your table?' I don't leave my station for more than a minute, and I get someone from the front to take over the escort as soon as I can. Then I tell the sous or the chef after service — 'table twelve came back to say the pasta was the best they've had this year.' Guest heard, chef informed, station protected."

34. You cut yourself deeply during a rush. What do you do?

Why they ask: Injury protocol has to be automatic, not improvised. Chefs are testing safety habits.

"Stop, step off the line, put pressure on the cut with a clean towel. Tell the sous or the nearest cook. If it's a deep cut — bone-deep, spurting, or won't stop after five minutes of pressure — I'm going to urgent care and someone else is finishing my shift. If it's shallow but bleeding, glove up with a fresh nitrile glove over a bandage and cover with a finger cot, then only if the sous clears me — some kitchens require any cut cook off the line entirely. I don't hide a cut. I don't cook with a bleeding wound under a glove. Blood in food is a nuclear health-code violation and everyone in that kitchen loses their job."