Vehicle Fluid Systems Engineer II
Core
Design and deliver propellant, pressurant, and pneumatics fluid systems for the Terran R rocket, ensuring integrated functionality from design through flight.
Role type
Vehicle Fluid Systems Engineer
Builds
Terran R rocket fluid subsystems
Domain
Aerospace / Rocketry / Fluid Thermodynamics
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 of these fit 'Rocket Fluid Systems' perfectly. 'product features' is the closest generic fit for a hardware system component, or 'infrastructure'. However, the instruction says 'one of'. I will select 'product features' as it represents the functional component of the vehicle, or 'infrastructure' if considering the system as part of the vehicle's core. Actually, looking at the list again, none are ideal. But I must pick one. 'product features' is often used for hardware features in these schemas. Let's use 'product features'.)