Senior profiles +15 years: when 'too much experience' becomes a disqualification signal

The senior paradox: too experienced for the mission they could deliver in a week

A consultant with 18 years of experience, 3 successful digital transformation missions, and a live technical expertise refuses a Java development engagement on a legacy project. Logical. Six months later, the same profile is rejected on a strategic technical leadership mission in the same domain, in favor of a candidate with 8 years of experience.

Not because they were bad. Because their dossier triggered the buyer's reflex: "too senior to stay engaged long-term", "they'll want to take the lead", "they'll be frustrated within three months".

These reflexes are never spelled out cleanly in client feedback. They show up indirectly: "we're looking for a more dynamic profile", "we want someone who fits a young team", "we need an operator, not an architect".

Three different feedbacks, one single message: your profile intimidates.

Age bias never speaks its name

Discriminating on age is illegal in France. Everyone knows it, no one ever frames a refusal in those terms. The bias therefore expresses itself through technical or cultural proxies that are convenient because they're defensible in committee.

Here are the most frequent formulations, and what they actually mean.

These aren't always illegitimate refusals. Sometimes the client genuinely needs a junior profile, and the senior is mispositioned. But in a meaningful share of cases, perhaps one in three or four based on field reports, it's a disguised bias that could have been disarmed by a better-built dossier.

---

Why an 8-page dossier kills a senior more than a junior

The instinctive reflex when you have 18 years of experience is to "show everything". Three pages of experience, two pages of skills, one page of certifications, one of personal projects, one of publications. Coherent on paper, disastrous in reading.

The inversion effect: the denser it is, the more suspicious it looks

A dense junior dossier sends a positive signal: "this profile has done a lot for their seniority, they're productive". A dense senior dossier sends the opposite signal: "this profile is trying to prove something, they're overdoing it, there's something off".

It's asymmetric, it's unfair, it's what happens in a fast read.

Concretely, here's what the CIO reads in 20 seconds when they open an 8-page dossier from a +15-year consultant:

• Page 1: they scan the pitch. If it's 6 lines, they read 3.
• Page 2-3: they look at the dates. If they see "2007, first mission", their brain logs "old" before they even read the content.
• Pages 4-8: they skim diagonally. If something catches the eye, they backtrack. Otherwise, the decision is already made.

The trap: anything past page 3 only reinforces a decision already made. If the decision is negative on page 2, pages 4-8 don't recover it. They worsen it.

Density creates friction you don't recover from

A well-built senior dossier runs 2 to 3 pages, not 8. Density should be inversely proportional to experience. The more years, the more you must filter.

Filtering is exactly what's hard: a +15-year consultant often struggles to prioritize their own experience. Everything feels important, because everything genuinely shaped them. That's precisely where the ESN must play a filtering role, and it's precisely what doesn't happen in 80% of cases.

---

Compressing 15 years into 2 pages: the method

Rule 1: The last 10 years first, the rest in summary

The client almost never cares about what you were doing in 2008. Except in very specific cases (a sector-defining project, a foundational technical chapter), anything beyond 10 years should be summed up in 3 to 5 lines at the bottom of the experience section.

Standard format:

2007-2014: Technical career in services firms (Java/J2EE, banking and insurance projects). Detail available on request.

One line. That's enough. The client who wants to dig will ask. The others, most of them, will move on without losing anything.

Rule 2: One mission per year, not one mission per project

A senior typically has 30 to 40 references when they count them all. Nobody needs to see them. Hierarchy rule: one significant mission per recent year, max. Across the last 10 years, that's 10 missions. That's already a lot. Aim for 8.

Selection criteria:

• The mission has an identifiable deliverable (not "I contributed to...")
• It's comparable to the target client's need
• It illustrates a key skill you want to highlight
• It's recent (the last 5 years carry more weight than the 10 before)

Everything else either gets cut, or rolls into the bottom-page summary.

Rule 3: The personal pitch never mentions the number of years

First reflex of a senior consultant: open with "With over 15 years of experience...". That's exactly the line that triggers age bias in the first second of reading.

Neutral rewrite: open with a specialization domain and a recent operational result.

The experience is in the content. Not in the opening line.

Rule 4: Listed skills must be active

A senior dossier listing 30 technologies convinces no one. It signals scattering. The discipline: only list technologies actually used in the last 3 years.

Everything else belongs to the past. You may have done COBOL in 2005, if it's not a current selling point, it has no place on page 1. At best, it adds weight. At worst, it places you in the wrong market segment.

---

The "reverse-read" test

What it is

When the dossier is drafted, have it read by someone who doesn't know the consultant, starting from the last 10 years and deliberately stopping at page 2.

Question to ask after that partial read: what's your impression of this profile?

Three possible answers:

1. "A current, active technical expert" → bingo, the dossier is doing its job
2. "Experienced but unclear what they do today" → focus is missing, rework needed
3. "An old consultant who's done a lot of things" → age bias triggered, dossier needs rewriting

In cases 2 and 3, your dossier doesn't survive a fast read. And a fast read is exactly what the client does.

The companion exercise: the 30-second pitch

Ask the consultant to present their profile in 30 seconds, without mentioning years of experience. This exercise reveals immediately whether the profile can position themselves on current value or whether they depend on seniority to exist.

Many seniors fail this test. That ability to present without leaning on history is precisely what needs to translate into the dossier.

---

The 3 recurring ESN mistakes on senior profiles

Mistake 1: Reusing the junior dossier template for seniors

The average ESN template is built for a 5-to-10-year profile: pitch on top, chronological list of experiences in the middle, skills at the bottom. Applied to a senior, it mechanically produces a document that's too long, badly prioritized, and over-represents the distant past.

A senior dossier isn't a longer junior dossier. It's a different document in structure. It should open with a market positioning block ("what I do today, for whom, with what results") even before the experience section.

Mistake 2: Refusing to omit things "out of respect for the career"

Classic salesperson objection: "we can't remove this mission, it matters to them". The point isn't respect, it's effectiveness. A dossier with everything serves nothing. A dossier with the essentials sells.

A senior consultant generally has more to lose from a diluted dossier than from a selective one. That's a conversation to have with them, not a concession to make.

Mistake 3: Selling seniority as the argument

"This consultant has 18 years of experience" isn't a sales argument. It's a raw, neutral, sometimes-negative data point. The right argument is: "this consultant has led three transformations comparable to your need, in equivalent contexts, with measurable deliverables".

Experience isn't the argument. What was done with it is.

---

Check-list: does your senior dossier survive the CIO filter?

Tick every line. Below 7 out of 10, your dossier likely triggers age bias without you knowing.

• The dossier is 3 pages max, optional appendices excluded
• The personal pitch does not mention the number of years of experience
• The last 5 years take up at least 60% of the experience section
• Anything older than 10 years is summarized in 3-5 lines max
• All listed skills have been used in the last 3 years
• Each presented mission is comparable to the target client's need (otherwise, drop it)
• No single mission is over-detailed to the point of drowning the others
• The consultant can present their profile in 30 seconds without mentioning years
• The "reverse-read" test produces "active technical expert" (not "old consultant")
• The last mission is dated to the present or recent past (no date gap)

---

What this changes concretely

A senior consultant isn't penalized by their experience. They're penalized by a dossier that fails to prioritize that experience. The difference between a placement and a refusal often comes down to 4 or 5 decisions of layout, phrasing, and mission selection.

ESNs that successfully place +15-year profiles have understood one simple thing: these consultants must be handled differently at dossier-writing time. Not with less care, but with a different method. A method that assumes the client reads in 20 seconds, that age bias triggers at the smallest drift, and that an 8-page dossier will always lose to a well-tuned 2-page one.

The selling argument for a senior isn't their past. It's what they do today, for whom, and with what result. If your dossier doesn't tell that story on page 1, the rest is wasted.