Skip to main content
Bluecoders

Hiring in defence: the sector's unwritten rules

Caroline FleuryNovember 19, 2026

France's BITD (Base industrielle et technologique de défense, its defence industrial and technological base) comprises more than 4,000 companies and over 210,000 jobs, and the national plan for employment in the defence industry, launched by the Ministry of Labour on 15 September 2026, targets 100,000 hires by 2030.

A surge of this size draws generalist recruitment firms overnight. That's logical, and it isn't a problem in itself.

The problem is that this sector has little patience for approximation. A clumsy approach doesn't just cost you a candidate — it can cost your client a business relationship, or worse, expose them.

Here are the 5 rules we apply, and that we've never seen written down anywhere.

Key takeaways

  • The client's ecosystem is both the best talent pool and the most slippery ground: approaching an engineer at a partner or prime contractor can cost them dearly.
  • Some roles are recruited for without being able to name the programme, sometimes without being able to name the company itself until a certain stage.
  • Two engineers with the same job title often do two different jobs. Without that precision in the brief, the search misses the mark.
  • The timeline isn't entirely in your hands: the administrative investigation ahead of a security clearance takes, in principle, 3 months at Secret level and 6 months at Très Secret level, under the IGI 1300 interministerial instruction.
  • Fake recruiters operate on the same ground as you. The DGSI publicly documents approaches by foreign intelligence services posing as headhunters.
  • The consequence: in this sector, a firm's quality is measured as much by what it refuses to do as by its ability to find candidates.

Why isn't hiring in defence like hiring anywhere else?

Because the 3 usual variables of a hire — the talent pool, the timeline and the information available — are all constrained by something other than the market.

The pool is constrained by clearability and by how scarce the skills are. The timeline is constrained by an administrative investigation that neither you nor the candidate control. The information is constrained by classification: you won't say everything, and neither will the candidate.

On top of that comes a dimension other sectors don't have: your searches are of interest to people whose job isn't recruitment. A firm that maps out the engineers on a programme produces exactly the same information an intelligence service is trying to obtain. The difference lies in what you do with it, and the rigour with which you handle it.

Rule 1: the client's ecosystem is the best talent pool and the worst hunting ground

When we open a search, the most qualified profiles are often one degree of separation from the client: at a partner, a subcontractor, a prime contractor, sometimes at a direct competitor on the same tender.

It's the most technically relevant pool. It's also the one that can do the most damage.

Approaching an engineer at an industrial partner of your client can potentially cost them a business relationship they spent years building. In a market where a few dozen players constantly cross paths on the same programmes, information travels fast, and it travels back.

Which is why the first thing we do on a defence mandate, before even discussing profiles, is map the client's ecosystem. Not their org chart — their ecosystem. Who are their partners, their clients, their competitors, their co-contractors on current programmes. And which companies are therefore off-limits for approach, even if they hold the best candidates.

This exclusion list is built with the client, never in their place. A firm that doesn't ask for it isn't measuring the risk it's putting them at.

Rule 2: some roles are recruited for without being able to name the programme

In a typical hire, the project is the selling point. Here, the project is precisely what you can't talk about.

We regularly recruit for roles where the programme can't be named, where the technical scope is described by allusion, and where even the company's name is only disclosed at an advanced stage of the process.

This changes the mechanics of the approach. You're not selling a project, you're selling a type of problem, a level of responsibility and a working environment. And you have to do it precisely enough for a senior engineer to agree to keep talking, without crossing the line into what can't be said.

In practice, this requires 2 things. First, knowing exactly what's shareable and what isn't — something to frame with the client's security officer, not to guess at. Second, accepting a lower response rate, because a deliberately vague approach puts off some candidates. That's the price to pay, and it's better to own it in the brief than to discover it mid-search.

Rule 3: two engineers with the same job title do two different jobs

It's the most common mistake, and the easiest to avoid.

Take 2 systems engineers. The first works on a cloud architecture and deploys continuously. The second runs a satellite designed to operate for 15 years, with no possibility of a fix after launch. Same title, same skill family on paper, two engineering cultures that have almost nothing in common.

Same thing in propulsion. One designs a plasma thruster for a satellite, the other a jet engine certified for thousands of flights. Both are propulsion engineers. Neither can step into the other's role without serious retraining.

What sets these profiles apart isn't the technology, it's the relationship to irreversibility and certification. An engineer used to fixing things in production doesn't think the way an engineer does when the smallest error becomes permanent at lift-off.

This is why our defence briefs are written with a level of detail that sometimes surprises people: not "signal processing engineer", but on what kind of signal, in which chain, under what real-time constraint, against which certification standard. For a role as a PhD in applied mathematics specialising in signal processing at Wheere, or a Lead Industrialisation Engineer in radio frequency at Rubicon, this precision is what separates a useful shortlist from 15 irrelevant CVs.

Rule 4: the timeline isn't entirely in your hands

On a role exposed to classified information, hiring includes a step that nobody at the table controls: the administrative investigation ahead of security clearance.

The IGI 1300 interministerial instruction, issued by the SGDSN (France's General Secretariat for Defence and National Security), sets the framework: the investigation takes, in principle, 3 months for a Secret-level clearance and 6 months for Très Secret, from the date the file is received by the investigating service. Elementary and primary-level checks take 1 to 2 months.

The scale of the system explains why these timelines aren't negotiable. The DRSD (Direction du renseignement et de la sécurité de la défense, France's defence intelligence and security directorate), the investigating service for the defence sphere, reports having received 483,000 administrative investigation requests in 2024 and issued 436,000 security opinions, around 45,000 of which concerned clearance for people working in companies.

Two practical consequences, which we raise systematically from the brief stage.

  • Qualify the requirement before you search. Not every role billed as cleared actually is, and the level required isn't always the one the manager thinks it is. This is checked with the security officer, not by re-reading the job description.
  • Give the candidate an honest timeline, separating what depends on the company from what depends on the authorities. An engineer who discovers late in the process that their start date is slipping by several months will walk away, and they'd be right to.

We detailed the full mechanics, from the paperwork to the questions an employer isn't allowed to ask, in our article on hiring a defence engineer and security clearance.

Rule 5: fake recruiters operate on the same ground as you

It's the rule people talk about least, and the one that changes how you work the most.

The DGSI (Direction générale de la sécurité intérieure, France's domestic intelligence service) publishes an unambiguous warning on its own website: foreign intelligence services run online approaches and remote recruitment attempts targeting professionals across every sector, on professional social networks and job sites. Among the methods described: direct contact while posing as a recruiter interested in the target's profile, and posting fake job ads designed to draw applications from people working in the fields of interest. The appeal of the method is explicit: since the target initiates contact, their guard is down.

Its Flash Ingérence n°116, published in November 2025, fills out the picture with real cases of fake profiles, including bogus investment intermediaries and consulting firms with no legal existence.

In other words: the job we do is also a cover used by others. This has 3 direct effects on how we work.

Engineers on sensitive programmes are rightly wary of a cold approach. A vague pitch that doesn't name the firm, that pushes towards an encrypted messaging app, or that asks for technical details before any real conversation, ticks exactly the boxes the DGSI trains them to spot. A serious firm does the opposite: it names itself, stays traceable, and accepts being checked out.

Companies in the sector, for their part, pass information back up the chain. We've had a client give us names of candidates not to re-contact.

"In this business, the best prospecting sometimes starts with the morning news. A budget shifts, an alliance is redrawn, a conflict drags on, and our clients' needs change overnight."

Caroline Fleury, Account Executive, Defence, Industry & Hardware practice

What does this change when you choose a firm?

In this sector, the right questions to ask a firm aren't about the size of its database.

  • Ask for its exclusion list. If it doesn't ask you which companies are off-limits, it isn't measuring the relationship risk it's putting you at.
  • Ask how it presents itself when approaching candidates. A firm that approaches sensitive profiles under cover of anonymity exposes you.
  • Ask what it refuses to do. We turn down mandates we can't deliver on, and we explain why. On a role whose clearance requirement hasn't been qualified, the honest answer is to qualify it first.
  • Ask it to separate the 2 timelines — the company's and the authorities' — from the proposal stage.

It's roughly the opposite of a standard sales pitch. It's also what tells apart a firm that knows this ground from one that just arrived on it.

In summary

From a distance, hiring in defence looks like any other engineering recruitment. Up close, it's governed by constraints that don't show on the surface: a talent pool you can't hunt freely, a project you can't name, a timeline you don't control, and a profession others use as cover.

These rules aren't learned from a brief. They're learned by working with companies that have a great deal to lose if you ignore them.

Hiring for a sensitive programme or a clearable role? Let's talk about your need. Caroline Fleury leads hiring for the Defence, Industry & Hardware practice, on roles that demand both clearance and discretion.

FAQ

Why is hiring in defence different from other sectors?

Because the 3 variables of a hire are constrained there by something other than the market. The pool is limited by clearability and skills scarcity, the timeline by an administrative investigation nobody at the table controls, and the information by classification. On top of that comes a risk specific to the sector: searches for sensitive profiles also interest people whose job isn't recruitment.

Can you approach an engineer at a partner of your client?

Technically it's the best talent pool, and commercially the riskiest ground. In a market where a few dozen players constantly cross paths on the same programmes, a clumsy approach at a partner or prime contractor can cost your client a relationship built over years. The list of companies that are off-limits for approach is defined with the client at the brief stage, never in their place.

How long does the administrative investigation take before a security clearance?

Under the IGI 1300 interministerial instruction issued by the SGDSN, the investigation takes, in principle, 3 months for a Secret-level clearance and 6 months for Très Secret, from the date the file is received by the investigating service. Elementary and primary-level checks take 1 to 2 months. These durations cover the investigation itself, not the total time between an accepted offer and the clearance decision, which also depends on how the file is put together on the employer's side.

How do you spot a fake recruiter in the defence sector?

The DGSI publishes the warning signs on its website: a recently created profile, an incomplete or inconsistent background, few connections, a stock-photo picture, pushing to switch to encrypted messaging, and asking for technical details early on. A legitimate firm names itself, stays traceable, and accepts being checked out. A reverse image search and a first video call clear up most doubts.

Are two engineers with the same job title interchangeable?

Rarely, in this sector. A systems engineer who deploys on a cloud architecture and a systems engineer who runs a satellite designed to last 15 years with no possibility of a fix after launch don't share the same engineering culture. What separates them is the relationship to irreversibility and certification, not the technology. A defence brief therefore needs to specify the environment and the standard, not just the job title.

How do you recruit for a role when you can't name the programme?

By selling a type of problem, a level of responsibility and a working environment rather than a project. What's shareable is framed upfront with the client's security officer, not guessed at during approaches. You also need to accept a lower response rate, since a deliberately vague approach puts off some candidates: better to plan for it in the brief than discover it mid-search.

What should you ask a recruitment firm that specialises in defence?

Four things, and none of them is about the size of its database: its list of excluded companies, how it presents itself when approaching candidates, what it refuses to do, and its ability to separate the company's timeline from the authorities'. A firm that approaches sensitive profiles under cover of anonymity exposes you, because it adopts exactly the patterns intelligence services train engineers to spot.

Do you need to follow geopolitical news to recruit in defence?

It's a condition of doing the job, not an extra. A budget decision, a realigned alliance or an escalating conflict can change a defence company's hiring needs within weeks. A firm that doesn't track these shifts finds out about its client's priorities a quarter late, in a market where the hiring window is short.

A recruitment need?

Describe what you need. A recruiter from your sector will call you back within 24 business hours.