Line Cook 3 - Seasonal
Core
Leading meal preparation, training kitchen staff, and overseeing kitchen operations at Zion Lodge within Zion National Park.
Role type
Senior Line Cook (Kitchen Supervisor)
Builds
High-quality meals for guests and staff at a historic lodge resort
Domain
Hospitality / National Park 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 schema options, but context is clearly 'production of meals'. The schema options are rigid. Let's re-evaluate. The options are: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. None fit 'cooking'. However, 'physical/clinical work' is the closest physical output option often used for manual labor in these schemas if 'food production' isn't listed. But wait, the instruction says 'one of: ...'. I must pick one. 'physical/clinical work' is the only one involving physical labor. Let's assume the schema is slightly misaligned for culinary roles or 'physical/clinical work' covers manual service roles. Actually, looking at the list again, none fit perfectly. I will select 'physical/clinical work' as it is the only category for manual labor, or perhaps the prompt implies I should map 'cooking' to the closest available. Let's look at the instruction again: 'Deliverable: <one of: ...>'. I will choose 'physical/clinical work' as a proxy for manual service labor if no better option exists, but strictly speaking, this is a mismatch. However, to follow the constraint 'one of', I must pick. Let's reconsider if 'product features' could apply? No. 'client delivery'? No. I will use 'physical/clinical work' as the fallback for manual labor roles in this specific schema constraint, acknowledging it's a schema limitation for culinary roles.