Hadrian
Factory Simulation Engineer
About this role
Hadrian seeks a Factory Simulation Engineer to design and deploy precision simulation systems supporting autonomous aerospace and defense manufacturing. You'll develop low- to high-fidelity simulations, collaborate cross-functionally, and build scalable toolchains that enable faster, cheaper production of critical components.
What you'll do
- Develop and refine discrete event and 3D simulations at varying fidelity levels for factory optimization
- Convert conceptual layouts into executable simulations with actionable insights
- Collaborate with engineering, operations, and leadership teams to deliver data-driven recommendations
- Maintain and enhance simulation toolchain infrastructure for scalability
- Build and manage library of parametric, reusable simulation assets
- Debug and optimize simulation models while balancing rapid prototyping with codebase health
What they're looking for
- Python (object-oriented programming)
- Discrete event simulation (DES)
- Visual Components or equivalent simulation software
- Kinematics and PLC interfaces
- CAD platforms (SolidWorks, NX)
- Systems thinking and technical communication
- Industrial engineering principles
- Plugin development (Python/C#)
Benefits
- Medical, dental, vision, and life insurance
- 401(k) retirement plan
- Equity compensation
- Flexible vacation policy
- Relocation support (based on business need)
Opens the official application on the employer’s site. No login required.
Hadrian
Hadrian builds aerospace and defense manufacturing systems, offering enterprise software platforms, advanced tooling design, and highly automated production capabilities for the sector. The company is hiring full stack engineers, manufacturing and tooling specialists, infrastructure and identity management experts, and workforce systems architects to support its rapid scaling.
View all jobs at HadrianLikely interview questions
- Walk us through your experience building simulations in Python and Visual Components. How have you approached converting rough layout concepts into executable DES models?
- Describe a time when you had to balance rapid prototyping with maintaining long-term codebase health. How did you make those trade-offs?