Propulsion Valves Engineer (m/f/d)
Core
Design and procure valves for the propulsion system, managing requirements from prototyping to serial production.
Role type
Propulsion Valves Engineer
Builds
Propulsion system valves for rocket engines
Domain
Aerospace / Rocket Propulsion
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 strict label list, but context is clearly 'product features' or 'production ML models' is wrong. Let's re-evaluate the label list. The list is: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. None fit perfectly. 'product features' is the closest for a mechanical component. However, the instruction says 'one of'. I will use 'product features' as it's the standard for hardware components in this schema if 'hardware' isn't an option, or perhaps the schema implies 'physical/clinical work' for anything physical? No, that's specific. Let's look at the instruction again: 'Deliverable: <one of: ...>'. Since 'hardware' isn't there, and it's a valve, 'product features' is the most logical fit for a component within a system, or perhaps the prompt implies I should pick the closest. Actually, looking at the list, none are perfect. But 'product features' is often used for any tangible output. Let's stick to the list. Wait, is there a better fit? No. I will use 'product features' as it represents the valve itself as a feature of the propulsion system.