Sous Chef
Core
Manage daily kitchen operations, prepare and cook dishes, and oversee station production for clients in various hospitality settings.
Role type
Sous Chef
Builds
Dishes and menus for clients in offices, stadiums, cathedrals, and universities
Domain
Hospitality / Catering
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 the allowed list, but the actual deliverable is food. The allowed list is fixed. I must choose from the list. 'physical/clinical work' is the closest fit for hands-on food prep in this specific taxonomy, or I should omit if none fit. However, the instruction says 'one of: ...'. Let's re-read the allowed list: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. Food preparation is not explicitly listed. 'client delivery' might fit if it's catering, but 'physical/clinical work' is often used for hands-on roles. Given the strict constraint, I will map 'kitchen operations' to 'physical/clinical work' as it's the only hands-on option, or omit if strict. Actually, looking at the list, none fit perfectly. But 'client delivery' could work for catering. Let's assume 'physical/clinical work' is the intended bucket for hands-on manual labor in this schema, or I should just pick the closest. Let's pick 'physical/clinical work' as it implies hands-on execution. Wait, the prompt says 'one of: ...'. I will use 'physical/clinical work' as the proxy for hands-on kitchen work in this specific constrained list, or better, 'client delivery' if it's about serving. The role is 'Sous Chef' doing 'Food Preparation'. I will use 'physical/clinical work' as the closest manual labor category in the provided list, acknowledging it's a schema limitation.