FCAS — Système de combat aérien du futur, SCAF in French — is routinely described as "Europe's next fighter jet." That description is the main reason people misunderstand it, and misjudge the careers attached to it. FCAS is a system of systems: a crewed next-generation fighter is one component inside a networked architecture of uncrewed platforms, a combat cloud, new sensors and a new engine. Roughly speaking, the aircraft is the least novel part. The novel part is the software-defined connective tissue between everything — and that is where most of the hiring is.
This dossier does three things: explain the actual structure, state the risks honestly (there are serious ones, and pretending otherwise would be malpractice), and map the skill profiles being recruited today rather than in 2040.
The programme in one paragraph
France, Germany and Spain are co-developing FCAS with an entry-into-service ambition around 2040. The industrial leads are Dassault Aviation for the next-generation fighter, Airbus Defence and Space for Germany and for several system pillars, and Indra as the Spanish national coordinator. Engine development runs through a Safran–MTU Aero Engines–ITP Aero structure. Thales and other national champions hold sensor and connectivity scopes. Demonstrator work — the phase intended to fly a technology demonstrator before the operational design is frozen — was contracted in the early 2020s and is the phase the programme is executing now. Public cost estimates for the full lifecycle sit in the range of one hundred billion euros and above; no such figure should be treated as precise at this stage of a forty-year programme.
The seven pillars — and where the work actually is
The programme is organised into technology pillars. Understanding them is the difference between applying for the right job and applying for a job that will not exist for fifteen years.
- Next-Generation Fighter (NGF). The crewed aircraft, Dassault-led. Aerodynamics, structures, flight controls, low-observability shaping, certification. High prestige, comparatively small headcount, extremely long lead times.
- Remote Carriers. Uncrewed adjuncts — expendable and reusable — that carry sensors, jammers or effects forward of the crewed platform. This is where autonomy, guidance and low-cost manufacturing skills land, and where the fastest-moving work sits, because remote carriers can be fielded before the fighter exists.
- Air Combat Cloud. The distributed, contested-environment data fabric connecting platforms. Effectively a real-time, safety-critical, adversarial distributed-systems problem. The single largest software hiring pillar.
- Engine. A new high-thrust, high-thermal-load powerplant with adaptive characteristics and vastly greater electrical generation than a Rafale-class engine — because the sensors and directed-energy ambitions demand power. Turbomachinery, materials, thermal management.
- Sensors. Multifunction radar, electronic warfare, passive detection, sensor fusion. Where Thales, Indra and FCMS scopes concentrate; signal processing and RF engineering.
- Stealth / low observability. Shaping, materials, radar-cross-section modelling, signature management across bands.
- Simulation and the "digital twin" backbone. Model-based systems engineering, mission simulation, synthetic environments used to validate architecture choices before hardware exists. Structurally the earliest-hiring pillar, and the one most transferable to civil industry.
Read that list as a timeline. Pillars 2, 3 and 7 hire heavily now. Pillars 1, 4 and 6 hire steadily but in smaller numbers and with harder entry barriers. If you want to work on FCAS this decade, the honest answer is that you will most likely work on cloud, autonomy, simulation or sensors — not on an airframe.
Why the governance is the biggest risk, not the technology
Trinational combat aircraft programmes have a documented failure mode, and it is never the physics. It is workshare. The requirement to give each partner nation industrially meaningful work collides with the engineering need for single-point design authority. Europe has lived this before: the Eurofighter consortium delivered a capable aircraft at a cost and schedule that few would defend, while France's decision to leave and build Rafale alone produced a coherent programme at the price of a smaller market.
FCAS has repeatedly surfaced public friction between Dassault Aviation and Airbus over design leadership and the scope boundaries around the fighter pillar, with reporting through 2024 and 2025 describing disputes over the balance of authority and periodic questioning in Berlin of whether the current structure is viable. Treat these as programme risk, not gossip: leadership ambiguity in the pillar that defines the aircraft's configuration propagates into every other pillar's interface definition.
The second structural risk is competition. The UK, Italy and Japan are running GCAP on a comparable timeline with a different governance model. Two European next-generation combat programmes competing for the same export markets, supplier base and scarce engineering talent is not obviously stable. Whether they converge, coexist or one absorbs the other is the single most consequential open question in European defence industrial policy — and it will shape careers more than any technology choice inside either programme.
The third risk is budgetary sequencing. Defence budgets across Europe have risen substantially, and France's multi-year military programming law raised the envelope materially. But rising budgets are being pulled in two directions: replenishing stocks and fielding capability now, versus funding a capability arriving in the 2040s. In a squeeze, the 2040 programme is the one that slips. That is not pessimism; it is how procurement behaves under pressure.
What derisks the programme
Three factors argue the other way, and they are why this is still worth building a career around.
Sovereign necessity. A European combat air capability without dependence on non-European export licences is now treated as a strategic requirement rather than a preference. That political floor is unusually solid.
Spin-in and spin-out value. Almost everything in pillars 2, 3 and 7 has near-term application outside the fighter: uncrewed systems, secure tactical networks, autonomy stacks and mission simulation are being procured on their own merits, independent of FCAS milestones. Skills built here retain value even if the crewed aircraft slips a decade.
Demographic pressure. The generation that designed Rafale and Eurofighter is retiring. Combat aircraft competence is not documentable; it transfers by apprenticeship. Every partner company knows it must hire and pair juniors with that generation before it leaves — which is why entry-level defence engineering hiring is unusually strong for a programme whose product is fifteen years away.
The eleven profiles being hired now
Ranked by near-term demand rather than glamour.
- Real-time and embedded software engineers (C, C++, Ada, Rust; DO-178C or equivalent military assurance). The backbone requirement across pillars.
- Distributed-systems and secure-networking engineers. Combat cloud: intermittent links, contested spectrum, byzantine conditions, hard latency budgets.
- Autonomy, guidance and control engineers. Remote carriers: trajectory optimisation, collaborative behaviour, human-machine teaming.
- Model-based systems engineers (MBSE). SysML, architecture modelling, requirements traceability. Chronically short in supply across all three nations.
- RF, radar and electronic-warfare engineers. Antenna design, digital beamforming, signal processing, EW techniques.
- Sensor-fusion and applied-ML engineers. Multi-sensor tracking, classification, and — critically — verification of learned components in an assurance framework.
- Cybersecurity and cryptographic engineers. A networked combat system is an attack surface; national accreditation makes this competence non-optional.
- Propulsion, turbomachinery and thermal-management engineers. Engine pillar, plus aircraft-level power and cooling — an underrated bottleneck as electrical demand rises.
- Materials, composites and low-observability specialists. Signature management, high-temperature materials, manufacturability.
- Verification, validation and simulation engineers. Building the synthetic environments that decide architecture before metal is cut.
- Programme, configuration and supply-chain managers with export-control fluency. ITAR/EU dual-use, offset structures, multinational configuration control. Scarce, well paid, and structurally secure.
The entry barrier nobody mentions: clearance and nationality
This is the practical constraint that most career advice omits. Work on FCAS pillars generally requires national security clearance, which in turn generally requires citizenship of the relevant nation and a background investigation measured in months. Two operational consequences follow.
First, timing: apply early, because clearance lead time — not interview performance — often determines your start date. Second, positioning: candidates who already hold a clearance are disproportionately valuable, which makes an initial role in a cleared environment (defence supplier, national laboratory, armed-forces engineering branch) a rational first move even at lower pay, because it converts into access later.
The corollary is that dual nationality, publication history and prior foreign employment can complicate accreditation for the most sensitive scopes. This is not a judgement; it is a fact to plan around. Many candidates in that situation build careers in the adjacent, less restricted layers — simulation tooling, non-classified subsystems, civil-military dual-use suppliers — and move inward over time.
Our companion dossiers go deeper on the adjacent surfaces: the defence-tech résumé, clearances and ITAR covers accreditation mechanics, the Airbus dual-mission dossier examines one of the two prime contractors, and the Safran engine dossier covers the propulsion pillar's industrial base.
How to read the next three years
Four public signals will tell you whether FCAS is converging or fracturing, and they are more informative than any announcement: whether the demonstrator phase holds its schedule and produces flight hardware; whether the Dassault–Airbus design-authority question is resolved in writing rather than in interviews; whether German budgetary commitments are renewed at each parliamentary cycle; and whether any formal contact emerges between FCAS and GCAP. If the first two land well, the programme is real. If they slip together, expect the capability to be delivered incrementally — remote carriers and combat cloud first, crewed aircraft later — which, notably, is exactly the scenario in which the skills listed above are most valuable.
What the money actually buys, and in what order
A useful way to read any forty-year programme is to ask what each phase purchases. The demonstrator phase does not buy an aircraft; it buys decision quality. Its output is a set of validated answers to questions that are ruinously expensive to get wrong later: how much electrical power the platform must generate, how the crewed aircraft and its uncrewed adjuncts divide sensing and shooting, which interfaces are frozen and which stay software-configurable, and how much signature performance is affordable at production scale. Every one of those answers constrains thousands of downstream jobs.
This is why the simulation pillar is not a support function. In a programme where the operational aircraft flies a decade after the architecture is set, the synthetic environment is the design tool. Teams building high-fidelity mission simulations are effectively deciding the specification. Candidates who understand that inversion — that modelling work is upstream of hardware work, not downstream of it — position themselves far better than those chasing the airframe.
The second phase-ordering insight concerns openness. Both FCAS and its competitors have converged on the language of open, modular architectures: standardised interfaces so that mission systems, effectors and autonomy can be replaced on software timescales rather than airframe timescales. If that commitment holds, the durable career is in the mission-system layer, which refreshes every few years, rather than in the platform layer, which refreshes once a generation. If it does not hold — if integration collapses back into a bespoke, prime-owned stack — the durable career is with the primes. Watching which way interface governance settles is therefore a personal career signal, not just a procurement detail.
The supplier tier is where most people will actually work
Public attention fixes on three or four names. Employment does not. A combat air programme of this scale distributes work across hundreds of tier-two and tier-three suppliers: actuation, connectors, power electronics, thermal management, test benches, secure communications modules, composite tooling, machining, non-destructive inspection, and the software houses that build the ground infrastructure and test harnesses around all of it.
For a candidate, the supplier tier has three underrated advantages. Responsibility arrives earlier, because teams are smaller and one engineer owns a whole subsystem rather than a fraction of one. The work is more visible, because a tier-two delivery either passes qualification or does not. And mobility is higher: subsystem competence transfers across programmes — including to GCAP-adjacent, space or civil aviation work — whereas deep familiarity with one prime's internal processes transfers poorly.
The corresponding disadvantage is honest to state: less prestige, often lower pay in the first years, and exposure to programme milestones you do not control. The rational pattern many engineers follow is to build subsystem depth in the supplier tier for three to five years, obtain clearance and qualification experience there, and then move into a prime with a specific, demonstrable competence rather than a general aerospace degree.
A candid closing assessment
FCAS is a programme with an exceptionally strong strategic rationale and an unresolved governance problem. Both statements are true at once, and any career decision that ignores either half is naive. The strategic rationale means the underlying capability areas — autonomy, contested networking, sensor fusion, assured software, propulsion and thermal management — will be funded in Europe for the next two decades regardless of what happens to the specific programme structure. The governance problem means no individual should tie a career narrative to a single programme name or a single 2040 milestone.
The practical conclusion is straightforward: build competence in a capability area, not loyalty to a programme label. Acquire clearance early. Prefer roles where you own a verifiable deliverable. And read the four convergence signals above each year, because they will tell you where the work is moving long before any press release does.