Your Cook Job Post Is the Problem, Not the Market

You posted "Line Cook Wanted — Experience Required" eleven days ago. Four applications. Two were dishwashers with no kitchen experience, one never answered the phone, and one came in, looked at the kitchen, and said he'd think about it.

Meanwhile you're working doubles and the sous is doing prep on her day off.

The instinct is to say nobody wants to work in kitchens anymore. Some of that is real — Toronto kitchens compete with construction, warehouses, and delivery driving, all of which pay cash-adjacent and don't require standing next to a flat-top in August. But the part you control is the part most owners never touch. Your job post is an ad. It's competing against forty other ads on the same screen. And most restaurant job posts are written like a legal notice.

Treat it like marketing and the pool changes.

The four things a cook looks for before reading anything else

A cook scrolling Indeed on their phone between shifts gives your post about six seconds. In those six seconds they're hunting for four facts. If any of them are missing, they scroll past, because the next post has them.

Pay, as a number. Not "competitive wages." Not "based on experience." A range: "$19–$23/hour depending on experience, plus tip-out." Everyone knows "competitive" means "minimum wage and we're hoping you don't ask." The posts that get applications say the number. If your number is low, you've learned something important before you wasted two more weeks.

Hours, honestly. "Full-time" tells a cook nothing. "Tuesday to Saturday, 2pm to 10pm, closed Sundays and Mondays" tells them whether they can keep their kid in daycare. A cook with a second job or a family is filtering on schedule before pay. If your schedule is genuinely rough — late closes, split shifts — say so in the post. You will get fewer applicants and a much higher percentage who actually show up for shift two.

What the kitchen actually is. "Busy restaurant" means nothing. "40-seat Thai kitchen on Danforth, two cooks on the line, about 120 covers on a Friday, wok and grill stations" means everything. A cook reads that and knows whether they can do it. The specific detail also signals that a human wrote the post, not a template.

A name. "Apply within" and "send resume to info@" both say nobody is waiting for you. "Text Maria at 416-555-0144" says a person will read this. Put your name and a direct way to reach you in the post. Yes, you'll get some junk. You'll also get the cook who was walking past, saw the post on his phone, and texted instead of filling out a form.

Write the post like you'd describe the job to a friend

Here's the structural difference. A bad post lists what you require. A good post leads with what you're offering and then says what you need.

Flip the order. Open with pay, schedule, and what the kitchen is. Then the requirements, and keep them short and true. "Two years on a line" is a real requirement. "Red Seal certification preferred" on a $20/hour job just tells good cooks you don't understand the market.

Add one line that nobody else adds: what happens next. "I read every text the same day and I'll set up a trial shift within 48 hours." That single sentence beats a higher wage at a place that ghosts people, because every cook in this city has been ghosted after an interview.

The two-week interview loop is why you lose the good ones

A good cook who is looking is looking at five places at once. The job goes to whoever moves first, not whoever pays best. If your process is: application sits in an inbox for three days, you call on Thursday, you schedule an interview for next Tuesday, you "discuss it with your partner," you call back the following week — that cook has been working somewhere else for nine days.

Compress it to three steps and run it inside a week.

1. Reply within the day. Even just: "Got your message. Can you come by Thursday at 3?" Speed is the signal. It tells them the kitchen is run by someone who answers things.
2. Short conversation, in the restaurant, between services. Twenty minutes. Where have you worked, what stations, why are you leaving, when can you start, what do you need to make. You are not hiring a CFO. You're finding out if they can cook and if you can stand being near them for eight hours.
3. Paid trial shift within a few days. Four hours, on the line, during a real service, paid at the rate you offered. Nothing in an interview tells you what a trial shift tells you. You'll see how they handle a ticket rush, whether they clean as they go, whether they ask questions or guess.

Make the offer at the end of the trial, out loud, while they're still in the building. Same principle as asking for the Google review while they're standing there. The moment you let them leave undecided, you're competing with whoever calls them on the drive home.

Where to post it

Indeed is where most Toronto kitchen searches start, and it's worth the spend when you're genuinely short. But two cheaper channels do more work than owners expect.

Your own staff. A referral bonus paid in two parts — half when the person starts, half when they hit 60 days — gets your cooks recruiting for you. Your sous knows six cooks. She'll only send you the ones who won't embarrass her.

Your own window and your own website. A sign on the door reaches people who already know the neighbourhood and already eat at places like yours. A "We're hiring" page on your site, with the same honest details, catches people who googled you after seeing the sign. It costs nothing to leave up, and it gives you somewhere to point when a regular says their nephew is looking for kitchen work. If your site makes that awkward to add, that's a sign it's working against you in other places too — the restaurant pages we build treat hiring, menu, and ordering as things the owner can change the same day.

Culinary programs. George Brown, Humber, and Centennial all push out grads looking for a first real line. They won't be fast yet. Some of them will be very good in six months if you teach them.

The hire you don't have to make

The cheapest cook in Toronto is the one already on your schedule next Thursday.

Every time someone quits, you pay for the ad, the interviews, the trial shifts, the weeks of slower tickets while the new person learns your prep, and the overtime you cover in the gap. None of that shows up as a line on your P&L, which is exactly why it goes unexamined. We wrote about the real arithmetic in staff turnover costs more than the raise you skipped.

Three things hold cooks better than almost anything else you can do this month:

A schedule they get in advance. Posting Monday's schedule on Saturday night makes it impossible to have a life. Two weeks out, same day every week, and don't change it without asking. This is also a cost control, not just a kindness — see your staff schedule is a labour cost decision.

A tip-out they understand. Most kitchen resentment traces back to a split nobody explained. Write it down, explain it on day one, and keep it the same. A tip pool that doesn't start fights covers the Ontario rules and the structures that hold up.

A path that isn't imaginary. "Prep to line in six months, line to sous when Dan moves up" gives someone a reason to stay through a bad August. If there's no path, say so honestly and pay more instead.

The open role hurts right now, so fix the post today and run a trial shift this week. Then spend next month on the three people you already have, so you're not writing another post in April.