eVTOL Systems Engineer

EvTOL Mid-level (L4 equivalent) 2-5 years

1 Which company are you aiming at?

To generate precise rejection-prevention feedback and application strategy, tell us where you're targeting.

Joby Aviation

Archer Aviation

BETA Technologies

Lilium

Wisk Aero

Vertical Aerospace

2 Send your application

You need an account so we know where to send the feedback.

Create an account Sign in

The job description

Tech stack. MBSE, SysML, Cameo Systems Modeler, IBM DOORS, ARP4754A, interface control documents, functional hazard assessment, requirements verification planning

About the role

You will join an eVTOL aircraft company as the connective tissue between the propulsion, battery, structures, avionics, and software teams. The systems group owns the vehicle-level requirements that turn a concept configuration into a certifiable aircraft. Your work keeps every subsystem aligned to the same performance, safety, and certification targets from preliminary design through type certification. You will be the person who notices when battery weight growth ripples into hover performance, and you will drive the trade before it becomes a redesign.

What you will achieve

Decompose vehicle-level requirements into allocated subsystem requirements with full bidirectional traceability, closing 100 percent of open TBD items before preliminary design review and keeping the baseline stable through detailed design.
Author and maintain interface control documents across propulsion, battery, avionics, and airframe teams, resolving cross-team conflicts on paper months before they could reach hardware.
Lead functional hazard assessments for new vehicle functions, generating the safety-derived requirements that feed the ARP4754A development assurance process and anchor the certification safety case.
Drive the requirements verification matrix from analysis through ground and flight test, catching verification gaps in design reviews instead of discovering them on the flight line.
Deliver the systems engineering package for a major program milestone, walking into PDR or CDR with zero critical findings on systems content and a verification plan the authority accepts.

What you will bring

Must-haves

2 to 5 years of systems engineering experience on aircraft, spacecraft, or similarly complex electromechanical products with real hardware delivered.
Working knowledge of ARP4754A and how development assurance flows from aircraft level down to individual items.
Hands-on experience with a requirements management tool such as IBM DOORS or Jama Connect, including baselining and change control.
Ability to read and critique interface definitions across electrical, mechanical, and software domains with equal comfort.
Familiarity with MBSE practice and SysML modeling in tools like Cameo Systems Modeler for architecture definition.
Technical writing sharp enough that your ICDs and review packages need minimal rework before release.
Comfort presenting trade studies and requirement changes to chief engineers, defending systems decisions with data under challenge.

Nice-to-haves

Direct experience supporting an FAA or EASA certification program through at least one major milestone.
Background in electric propulsion or high-voltage aircraft power systems and their integration challenges.
Exposure to model-based safety analysis or formal methods for requirements verification.
Familiarity with configuration management tools and processes for development hardware baselines.