Powertrain Responsible Engineer
Posted Mar 27, 2026·Open for 121 days (and counting)
Hiring for this role?
Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Function
Engineering
Workplace
On-site
Location
US
Job Description
Hermeus is a venture-backed defense aviation company reclaiming the lost art of rapid iterative prototyping to build the fastest aircraft in the world today. By prioritizing relentless hardware iteration, we deliver high-speed systems at the pace of the modern battlefield. We work with the Department of War to provide the high-speed capabilities our nation and its allies need to maintain a durable, asymmetric advantage.
About The Role:
As a Powertrain Responsible Engineer you will own the mechanical components and assemblies that generate and transmit power in all forms (fluid, mechanical and electrical) throughout our hypersonic vehicles. This includes gear boxes, generators, motors, and turbomachinery. This highly interdisciplinary role requires strong 1st principles in mechanics, fluid dynamics, thermal analysis, materials science, and manufacturing. You will need to be able to communicate requirements clearly and concisely in a rapidly changing environment while driving the development of cutting-edge hardware that will accelerate the future of hypersonic travel.
Audit details(provenance, verification trail, raw fields)
Core fields
Posting ID
hermeus:86943845-15c8-4299-b62b-6c184a0fbaefTitle
Powertrain Responsible Engineer
Function
Engineering
Location
Los Angeles, CA
Workplace mode
in_person
Posted at
2026-03-27 01:46:33Z
Compensation
undisclosed
Provenance
First seen (our tracker)
2026-07-20 21:46:45Z
Last seen
2026-07-26 06:00:49Z
Last updated
2026-07-26 06:00:49Z
Removed at
still open
Days open
Open for 121 days (and counting)
ATS adapter
lever
ATS slug
hermeusVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
