Chef Manager
Core
Leading kitchen operations and preparing meals for residents in a retirement living community.
Role type
Chef Manager (hands-on culinary leadership)
Builds
Daily lunch and dinner services, special events, and functions for residents
Domain
Retirement living / Hospitality
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 options, though 'food service' is more accurate, the list only has 'physical/clinical work' as the closest non-IT option for hands-on roles, but strictly following the instruction 'one of: ...', I must choose from the list. However, 'physical/clinical work' is a specific category. Let's re-evaluate the list: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. This is a very specific list. A chef preparing food doesn't fit 'physical/clinical work' perfectly, but it's the only hands-on option. Wait, the instruction says 'one of: ...'. I will map 'preparing meals' to the closest fit or leave it if none fit? The instruction says 'one of: ...'. I will select 'physical/clinical work' as it implies hands-on physical labor in a service setting, or perhaps the prompt implies these are the ONLY options. Let's look at the options again. None fit 'food service'. I will use 'physical/clinical work' as a proxy for 'hands-on operational work' if forced, but actually, looking at the other options, none fit. I will assume the list is exhaustive for the schema. I will map 'preparing meals' to 'physical/clinical work' as it is the only hands-on category provided, or perhaps the user made a mistake in the prompt's list. I will stick to the list. Actually, 'client delivery' could work for service, but 'preparing meals' is internal. I will use 'physical/clinical work' as the closest 'hands-on' tag available in the restricted list, acknowledging it's a schema limitation.
