Factory Assistant (Printing)
Core
Operate and maintain printing machinery, perform quality assurance, and support die cutter operators in a sustainable packaging production environment.
Role type
Machine Operator / Factory Assistant
Builds
Packaging solutions for food, beverage, healthcare, pet-care, beauty, home, and garden sectors
Domain
Printing and packaging
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 instruction's allowed list, but the actual category is 'physical/industrial work'. The instruction list is fixed. I will map 'physical/clinical work' as the closest match for manual labor if no better fit exists, but strictly speaking, the instruction says 'one of: ... physical/clinical work'. I will use 'physical/clinical work' as the only physical option provided in the prompt's allowed list, even though 'clinical' is a misnomer here, to adhere strictly to the 'one of' constraint. Wait, re-reading the prompt: 'Deliverable: <one of: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work>'. The role is clearly physical/industrial. I must choose from the list. 'physical/clinical work' is the only physical option. I will use it as the literal string required by the schema, despite the semantic mismatch, or I should interpret 'physical/clinical work' as a category label for 'physical work'. Let's assume the schema implies 'physical work' and 'clinical work' are subtypes, or it's a typo in the prompt's example list. Given the strict instruction 'one of', I will output 'physical/clinical work' as the literal string if no other physical option exists. However, looking at the other options, none fit. I will use 'physical/clinical work' as the required string value for physical labor roles in this specific schema context.
