Monday, May 4, 2009

Chefs salaries revealed

Posted by Owen Morris on Mon, May 4, 2009 at 12:45 PM

chefdunechaser_thumb_225x168.jpg
There is a saying in the restaurant industry: You can't make a living but you can make a killing. That pretty much sums up the boom-or-bust attitude. Even so, for most restaurant workers things can be a little bit more even. The industry magazine Star Chefs has released its 2008 report on how much one can expect to make working in a kitchen.

"Chefs might be the new pop culture superstars, but this doesn't exactly translate to more money for the average culinary professional," the article notes. "Executive chef salaries headed south ... and pastry chef salaries took a veritable nosedive."

The national average for executive chefs is just under $75,000. For a pastry chef it's $46,228; for a sous chef it's slightly less at $44,205. Line cooks earned just under $13 per hour. And remember that the average executive chef has been working nearly 20 years and it takes the average line cook six years to earn that hourly wage.

But the numbers can be broken down even further. For instance, executive chefs at hotels can expect to make almost $10,000 more than the average, but the executive chef at a casual dining restaurant only makes $64,000 per year. In New York City, the average was in the $80,000 range. Not much considering the price of living there, but still more than Anthony Bourdain made after 20 years of working in the city. He claims never to have brought home more than $52,000 per year.

Where the numbers get really interesting is in education levels and salary. Culinary degrees are outrageously priced for the return students get (state-run programs like Johnson County's not included) and it turns out those years training and not working may even hurt. People with non-culinary degrees earn more than those with culinary degrees.

Also, don't expect to work 9 to 5. More than 80 percent of people in the kitchen reported working nine-plus hours a day. Chefs work on average more than 50 hours a week and 30 percent work more than 60 hours per week. What the article doesn't say is that's at least 51 weeks of the year, including all holidays and weekends.

So yes, chef may be a glamor job now but it still comes down to extremely hard, long work.

(Image via Flickr: Dune Chaser)

Tags: , , , , ,

Comments (1)

Showing 1-1 of 1

Add a comment

Hahahahaha! "...chef may be a glamor job..." This concept always makes me giggle a bit. My husband is "just" a kitchen manager, and always has been, and his stories have never given me any idea that there's glamour behind those kitchen walls. Yeah, the guys/gals on t.v. might have things a wee bit more glamorous than most chefs, but still...the burns, the cuts, the dealing with the whiney line cooks and serve staff! GAH! I'll take sitting in a chair all day looking at a computer over that shit. Blech.

(My husband, for the record, never earned more than $32,000 annually at KC Hopps for his "assistant" KM job, and he worked an avg of 60 hours a week there, and it took him a while to work into that position. Now he makes $12 an hour in his new position (morning KM at a CC in JoCo), but he works 40 hours a week, has a set schedule, and I get to see him every night. Works for me!)

report   
Posted by Faith on May 4, 2009 at 12:49 PM
Subscribe to this thread:
Showing 1-1 of 1

Add a comment

Latest in Fat City

Slideshows

All contents ©2012 Kansas City Pitch LLC
All rights reserved. No part of this service may be reproduced in any form without the express written permission of Kansas City Pitch LLC,
except that an individual may download and/or forward articles via email to a reasonable number of recipients for personal, non-commercial purposes.
Website powered by Foundation