Tech talent scarcity: what buyers scan first (and what they never read)

How a buyer actually processes your dossiers

A technical lead on the client side receives between three and eight dossiers for the same opening, sent by as many different ESNs. They do not read them. They scan them between meetings, phone in hand or a tab wedged between Jira and Teams.

Their real attention window on a first pass: fifteen to twenty seconds. Not out of laziness, but out of volume.

What they look for in those twenty seconds

• The tech stack visible immediately, without scrolling
• A comparable assignment to the current need: same sector, same scale, same type of deliverable
• Date consistency that does not force them to reach for a calculator
• A reusable context snippet they can use as-is when they present the profile in an internal committee

If your dossier forces them to reconstruct these four elements themselves, they move on to the next one. Not because the profile is weak, but because the dossier next door has already done the work for them.

The internal committee test

The buyer almost never decides alone. They must defend the profile in front of a project manager, an architect, sometimes a technical director. What they actually do: they copy-paste a chunk of your dossier into an email or Slack. If your formatting does not produce a self-contained, understandable summary out of context, you depend on their goodwill to rephrase. And they do not have time to rephrase for eight profiles.

The dossier that wins is not the best developer’s. It is the one the buyer can pass on with zero effort.

---

The mobile reality most ESNs ignore

Field numbers

According to feedback from ESN sales directors, between 30 and 50% of first dossier opens happen on a narrow screen. Phone between trips, tablet in a waiting room, 13-inch laptop on a train. This is not an edge case: it is nearly half your audience.

What breaks on mobile

Dossiers optimised for A4 printing are the worst on the move. Tight margins, reduced fonts, tables tuned for landscape, everything that works on a printed sheet becomes friction on a 6-inch screen.

What works everywhere

• A mission title in bold, on one line
• A short list of technologies (5–7 items max, not 25)
• Context in one sentence: sector, team size, main deliverable
• Visually separated blocks: the eye knows where to go without effort

The rule: if it works on an iPhone SE, it works everywhere.

---

Where time disappears in the document chain

Invisible friction

An ESN’s slowness versus the market rarely comes from sourcing. A good sales rep spots a relevant profile in a few hours. What drags time-to-submit is the document chain that follows:

1. Raw CV intake: PDF, Word, sometimes a LinkedIn capture
2. White-label formatting: in-house PowerPoint or Word template
3. Adaptation to the client brief: picking relevant missions, rephrasing
4. Internal validation: manager review, sometimes the consultant themselves
5. Send: final PDF by email, sometimes upload to a supplier portal

The real cost of each step

Realistic total: 2 to 6 hours between the moment you identify the profile and the moment the client receives the dossier. Sometimes a full day when validation stalls.

Why those hours matter

While your chain is running, another ESN has already sent. The buyer has their first name in mind. Psychologically, later profiles are compared to that first one, not evaluated from scratch. Arriving second is already playing on the back foot.

On tight roles (lead dev, senior DevOps, cloud architect) the window to position a profile is measured in days, not weeks. Every hour lost in the document chain mechanically lowers your placement rate.

---

Anatomy of a dossier that will not be read

Certain patterns show up again and again in dossiers that never get a reply. They are not obvious mistakes: they are structural flaws nobody fixes because “we have always done it this way.”

Sections regularly skipped

• Long paragraphs without subheadings: the eye has no anchor and drops off after three lines
• Lists of 20+ skills with no link to the current mission, Java, Python, C++, VBA, HTML, CSS, Angular, React, Vue… the signal drowns in noise
• Reverse chronology without visual hierarchy: same weight for a six-month mission in 2019 and a three-year mission in progress
• Generic “soft skills” paragraphs: “strong communicator, team player, rigorous” (who writes the opposite?)
• Education listed before experience: relevant for a junior, counterproductive for an 8+ year profile

What triggers a callback

Conversely, here is what buyers cite as action triggers:

• A “mission context” block at the top: stack, sector, duration, main deliverable, four lines max
• Short lists instead of walls of text, information is consumed without effort
• Identical formatting from one profile to the next: the reader does not restart decoding from zero on every open
• An actionable profile summary: not “passionate full-stack developer” but “7 years React/Node in fintech, latest mission: payment funnel redesign at X”
• Concrete deliverables on each mission: not “feature development” but “migration from monolith to 12 microservices, deployment time cut from 4h to 20min”

---

The problem of poorly executed white-label branding

When branding hurts the profile

Every ESN does white-label work. Logo at the top, colour palette, footer with contact details. So far, so normal. The trouble starts when the template overpowers the content.

Common symptoms:

• Half-page header with logo, tagline, certifications, full address, before the reader even sees the consultant’s name
• Corporate colours that hurt readability (light grey on white, navy links on dark blue)
• Rigid template that forces empty sections: “Publications,” “Patents,” “Languages” with a single item
• Legal footer eating 15% of every page

Branding should frame the content, not swallow it. The buyer does not care about your tagline: they want the stack and the latest mission.

Consistency as a competitive edge

Done well, branding creates a recognition effect. When a buyer regularly receives dossiers from the same ESN and the format is always clean, structured, predictable, they build a trust reflex. They know where to find information. They save time. And when they must choose between two equivalent profiles, the readable dossier wins.

---

What buyers do not say (but behaviour reveals)

First-profile bias

Buyers never put it this way, but the first dossier received frames the whole evaluation. It is anchoring: later profiles are compared to it, not judged independently.

Concrete consequences:

• If the first profile is senior and expensive, the next ones look “less experienced” even if they fit the real need better
• If the first dossier is well structured, less readable ones feel “less serious”, regardless of the profile underneath
• If the first profile comes from a known ESN, the others start with an implicit credibility deficit

Being first and readable stacks two cognitive advantages.

The three-dossier threshold

Field observation: beyond three dossiers received, the chance a fourth is read carefully drops sharply. The buyer already has favourites. They have already started scheduling interviews in their head. The fourth dossier must be meaningfully better, or meaningfully better presented, to flip the shortlist.

Format fatigue

A buyer who receives five dossiers in five formats faces cumulative cognitive load. Each new format demands decoding effort: where are the missions? how is the timeline organised? what is emphasised?

ESNs that standardise their output format reduce that fatigue. The buyer recognises the structure, knows immediately where to look, and can compare profiles without mental translation work.

---

Prioritisation mistakes in the dossier

Leading with the wrong information

A common reflex: open the dossier with degrees and certifications. For a cloud architect with 12 years of experience, their 2013 engineering degree is not what books an interview. Their latest large-scale AWS mission is.

Order that works for experienced profiles (5+ years):

1. Actionable summary: one sentence, not a paragraph
2. Current tech stack: what they use today, not what they touched in 2016
3. Recent missions: the last 2–3, detailed with context and deliverables
4. History: the rest in condensed form
5. Education / certifications: at the bottom, as validation

For juniors (0–3 years), the order logically flips: education matters more when experience is thin.

The exhaustiveness trap

Listing every technology ever touched does not make a profile more attractive. It makes it suspicious. A developer who lists 30 technologies over five years reads as a shallow generalist to the buyer, not a versatile expert.

Better 5–8 technologies mastered with usage context than a list of 25 keywords with no hierarchy.

---

Structuring for reading speed

The three-level rule

A well-structured dossier reads at three speeds:

• Skim (5 seconds): summary at the top + stack = the buyer knows whether to continue
• Scan (20 seconds): mission titles + associated techs = they grasp the trajectory
• Read (2 minutes): mission detail, deliverables, context = they prepare interview questions

If your dossier only works at the third level, you lose every buyer who does not have two minutes at that stage of the process.

Visual cues that speed up scanning

• Bold on technology names in the body, the eye catches them on a fast scroll
• Dates aligned right or at the start of a line, not buried in a sentence
• Clear separation between each mission, a line, spacing, alternating background
• Action verbs at the start of bullets: “Migrated,” “Designed,” “Automated” rather than “Participation in the migration of…”

A well-structured dossier reads like a dashboard, not a novel.

---

Turning the document chain into an advantage

The real issue is not the tool: it is the flow

Many ESNs hunt for a magic tool that fixes everything. Reality: the problem is rarely a single tool. It is the number of tools in the chain and the manual handoffs between them.

A CV that goes Word → PowerPoint → PDF → Email → Client portal undergoes five format conversions. At each step, information is lost, alignment breaks, fonts change. The final output rarely matches the starting template.

Fewer steps, not more automation

The best optimisation is not to automate every step: it is to remove them. A flow where the profile is imported once (PDF, Word, or LinkedIn), structured in one format, adapted to the brief without starting from scratch, and exported directly in the right shape: that is three steps instead of five. Betterfolio is built on exactly that principle: one import, one structure, per-mission adaptations, a clean export.

Measure to improve

Few ESNs track time-to-submit, the time between identifying a profile and sending to the client. Yet it is as important an indicator as time-to-hire.

Useful metrics to track:

• Average time-to-submit per sales rep
• Response rate by send delay (before / after 24h)
• Number of back-and-forths before the final dossier is approved
• Conversion rate dossier sent → interview obtained

No measurement, no improvement. And without improvement, you stay dependent on individual sales talent to absorb process friction.

---

Checklist: does your dossier pass the 20-second test?

Before sending a dossier, check these points:

• The tech stack is visible without scrolling
• The profile summary fits in one concrete sentence (not “passionate and rigorous”)
• The latest mission is at the top, with context and deliverable
• Each mission mentions a measurable outcome or tangible deliverable
• Listed technologies match the client need (not an exhaustive inventory)
• The dossier is readable on mobile without zoom
• Branding uses no more than ~10% of the space
• A non-technical reader can understand the summary and forward it
• The format matches your other dossiers sent to the same client
• The dossier can be forwarded as-is internally by the buyer

If three or more boxes are unchecked, the dossier is probably not competitive, whatever the level of the profile behind it.