Senior Material Flow Engineer
Core
Optimizing material movement, storage, and presentation within manufacturing and logistics operations to enhance efficiency and support lean manufacturing.
Role type
Senior IC material flow engineer
Builds
Optimized material flow systems, line-side delivery, supermarket designs, and kitting solutions for manufacturing sites
Domain
Manufacturing / Industrial Engineering / Supply Chain
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: Correcting to 'physical/clinical work' is incorrect based on the schema options. The schema options are: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. None of these fit 'material flow systems' perfectly, but 'infrastructure' or 'product features' are closest. However, the instruction says 'one of'. Let's re-evaluate. The role builds physical systems and processes. 'Infrastructure' usually refers to software/cloud. 'Product features' refers to software. 'Physical/clinical work' is for nurses/doctors. This is a tricky mapping. Let's look at the responsibilities: designing layouts, implementing systems. It's closest to 'infrastructure' in a broad sense or perhaps the schema is limited. I will select 'infrastructure' as it involves building the physical/logistical framework, or 'product features' if considering the 'solution' as a product. Actually, looking at the list again, none fit perfectly. However, 'infrastructure' is often used for physical systems in some contexts, but usually not. Let's stick to the most literal interpretation of the options. If I must choose, 'infrastructure' is the least wrong for 'systems', but 'physical/clinical' is definitely wrong. Wait, the prompt says 'one of: ...'. I will choose 'infrastructure' as it implies building the underlying system, even if it's physical/logistical, as opposed to software code. Alternatively, if the role is about 'solutions', maybe 'product features'. Let's go with 'infrastructure' as it's the standard bucket for 'building systems' in these schemas when 'physical' isn't an option for non-clinical roles. Actually, re-reading the options: 'production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work'. This role builds physical layouts and systems. 'Infrastructure' is the best fit among the limited choices for 'building systems'.
