Head Chef (F/M/X)
Core
Plan, create, and develop menus aligned with brand concept and seasonal availability while ensuring quality, taste, and presentation standards for a California-inspired restaurant.
Role type
Head Chef
Builds
Production food and beverage experiences for hotel guests and local residents
Domain
Hospitality / Fine Dining
Deliverable
Production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: Corrected to 'physical/clinical work' based on strict label list, but context is clearly 'product features' or 'physical work'. Re-evaluating label list: 'physical/clinical work' is the only one fitting food prep. However, 'product features' is often used for software. Let's look at the list again: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. Food prep is best mapped to 'physical/clinical work' in this specific constrained list, though semantically awkward. Alternatively, if 'product features' implies the menu items, that might fit. But 'physical/clinical work' is the standard fallback for manual labor in this schema. Let's stick to the schema's intent. Actually, looking at the schema provided in the prompt, 'physical/clinical work' is the only non-digital/non-analytical option. I will use 'physical/clinical work' as the closest fit for manual food preparation in this constrained taxonomy, or 'product features' if interpreted as the menu. Given the 'physical' nature of a chef, 'physical/clinical work' is the intended bucket for manual roles in this specific schema design, even if 'clinical' is a misnomer for cooking. Wait, the prompt says 'physical/clinical work'. I will use that label for the chef role as it represents the physical labor aspect.