Skip to main content

Heart Aerospace

Integration Engineer

Los Angeles, CAFrom $176kmidAdded 1 month ago

About this role

Heart Aerospace seeks an Integration Engineer to oversee mechanical and electrical system integration for the ES-30 hybrid-electric aircraft. You'll coordinate across design, manufacturing, and assembly to ensure seamless subsystem integration from prototype through production.

What you'll do

  • Lead integration of propulsion, battery, avionics, and structural systems into the aircraft platform
  • Define build sequences, mechanical interfaces, fastener strategies, and cable/fluid line routing
  • Optimize aircraft assembly processes from first article through full-rate production
  • Provide design-for-assembly feedback to engineering teams
  • Collaborate with design engineers, manufacturing, and production floor technicians
  • Ensure complex systems meet certification and performance requirements

What they're looking for

  • Systems integration and aircraft assembly
  • Design-for-manufacturing (DFM) expertise
  • Mechanical and electrical integration knowledge
  • Problem-solving and attention to detail
  • Cross-functional collaboration
  • Production process optimization
  • Technical documentation and sequencing
  • Fast-paced execution capability
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Heart Aerospace

Heart Aerospace is developing the ES-30, a 30-passenger hybrid-electric regional aircraft, and is hiring engineers across propulsion, structures, software, and testing disciplines to design, integrate, and certify its innovative powertrain and airframe systems.

View all jobs at Heart Aerospace

Likely interview questions

  • Walk us through your experience integrating mechanical and electrical subsystems. How have you handled interface conflicts between different teams or disciplines?
  • Describe a time you identified a design-for-assembly (DFA) issue late in development. How did you communicate it to the design team, and what was the outcome?