Chef | Jiffy Lube Live
Core
Coordinate day-to-day operations of a live event venue kitchen, preparing food items, managing stock, and ensuring guest satisfaction.
Role type
Venue Chef (Live Event Operations)
Builds
Food and beverage service for live events and venue guests
Domain
Live entertainment venues / Hospitality
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: This is a physical service role, not ML/Software. The deliverable is actually 'food service operations' but the schema options are limited. I will map to the closest physical/operational nature or omit if strict. Let's re-read schema: 'physical/clinical work' is the only fit for non-digital physical labor. However, 'product features' or 'dashboards' are wrong. 'client delivery' is wrong. 'production ML models' is wrong. The schema seems to force a tech stack. Wait, the prompt says 'Deliverable: <one of: ...>'. This is a Chef. None of the options fit perfectly except perhaps 'physical/clinical work' as a stretch for physical labor, or I should interpret 'product features' as 'food items'. But the instruction says 'never infer'. Let's look at the options again: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. A chef does 'physical work'. I will use 'physical/clinical work' as the only option that acknowledges the physical nature, though it's a poor fit for a chef. Actually, looking at the other fields, 'Builds: food service' is better. Let's stick to the schema strictly. 'physical/clinical work' is the only one that isn't software/data. I will use it.