Sous Chef, Restaurant
Core
Managing restaurant kitchen operations, food production, and staff in an upscale hotel setting.
Role type
Sous Chef
Builds
Restaurant food production and service
Domain
Hospitality / Fine Dining
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: Correcting to 'food production & service' based on context, but strictly following the allowed list 'physical/clinical work' is incorrect. Re-evaluating allowed list: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. None fit perfectly. 'physical/clinical work' is the closest for hands-on kitchen labor, but 'food production' is the actual domain. I will map 'food production' to the closest semantic fit or leave blank if strict. Actually, the prompt says 'one of: ...'. I must choose one. 'physical/clinical work' is the only one involving physical labor in a service context, though 'clinical' is wrong. Let's look at the list again. It seems the list is specific to tech/analysis mostly. However, for a Sous Chef, the work is 'food production'. I will select 'physical/clinical work' as a placeholder for 'hands-on physical work' if no better option exists, OR I will interpret 'product features' as 'menu items'? No. Let's stick to the literal list. 'physical/clinical work' is the only one that isn't abstract data. I will use it with the understanding it covers physical labor roles in this schema, or I will omit if strict. The instruction says 'one of'. I will choose 'physical/clinical work' as it implies physical labor, despite the 'clinical' misnomer, as it's the only non-abstract option for a chef. Wait, 'client delivery' could apply to food service? No. Let's assume the schema is rigid. I will use 'physical/clinical work' as the best fit for 'hands-on kitchen work'.