When a search stalls, the common reflex is to raise the volume: more applications, faster, across a wider range. It rarely unblocks anything, because the limiting factor is not how many applications you send but the quality of the decision that precedes each one.
What an application actually costs
A properly worked application means reading the posting closely, understanding the company's context, choosing the relevant evidence, adjusting the opening line and sometimes preparing for a conversation. That effort is not elastic: it comes out of limited time, often alongside a current job.
So the question is not « how do I send more » but « where do I put the effort ». Targeting is not narrowing; it is deciding the allocation deliberately instead of leaving it to whatever appears first in a list.
A seven-dimension targeting grid
There is no universal score, and a single number out of a hundred would fake a rigour it does not have. A qualitative read across seven dimensions is more useful, because it also tells you what the application itself needs to work on.
- 1
The role
question 1Is this genuinely the role I am after, or a nearby role I would accept by default? A « by default » role shows through in the application, almost every time.
- 2
The problems to solve
question 2Have I worked on comparable problems? Comparable does not mean identical: same class of problem, same kind of constraint, same nature of data.
- 3
Must-have skills
question 3Which ones genuinely block you from holding the role in the first months, as opposed to those listed out of habit?
- 4
Transferable skills
question 4Where do I have credible adjacent experience I can defend through reasoning rather than through a CV line?
- 5
Expected level
question 5Does the role call for execution, ownership of a scope, framing, reference expertise, or leading people? It is the most often overlooked criterion and one of the most decisive.
- 6
Environment
question 6Product, consulting, startup, large enterprise, research, platform, production. The same title means different things depending on the environment, and experience in one does not automatically carry to another.
- 7
Available evidence
question 7What exactly can I show or recount to support this application? If the answer is vague, the application will be too.
The grid is not there to disqualify you. It tells you where the effort goes: on a strongly aligned application, into precision; on an adjacent one, into demonstrating the transfer.
Reasonable gap or structural gap
Nobody matches a posting one hundred per cent, and nobody expects that. What matters is telling a gap you can defend from a gap that sits on the core of the role.
Structural gap
It sits on the role's main responsibility: the posting is about owning a system in production and the experience stops at prototypes; the role is centred on leading a team and the experience is purely individual. No rewording closes that kind of gap.
Reasonable gap
It sits on a tool, a cloud provider or a sector context, while the underlying concept and the class of problem are mastered. That gap is defended by explaining what transfers and what will have to be learned.
The test: if you had to explain the gap out loud in an interview, would your explanation hold in two sentences without making anyone uncomfortable?
A few examples, from the most defensible to the heaviest: a missing tool where the concept is understood is recoverable; experience on a different cloud provider transfers provided you say so; an adjacent role takes demonstration work but stays playable; prototype experience against a production mandate is a serious gap once the role is about operating the system; no experience at all on the role's main responsibility is a structural gap.
Allocating effort across four categories
Rather than an arbitrary sending rhythm, it is more useful to sort opportunities by nature. The proportions depend on your situation; what matters is knowing which category you are in before you start writing.
- 1
Strongly aligned
maximum effortThe role you want, problems you have handled, direct evidence available. This is where deep preparation pays best: full reading of the posting, real personalisation, preparing for the conversation.
- 2
Adjacent but credible
focused effortOne or two reasonable gaps on a solid base. The effort goes into one precise point: making the transfer explicit, leaning on evidence that shows reasoning rather than tooling.
- 3
Exploratory
measured effortThe role interests you but alignment is uncertain, or the company is barely known to you. A short, honest application beats one that over-reads the posting.
- 4
Too far
no applicationThe gap sits on the core of the role. Time spent here is taken from the first three categories. Better to note the gap and treat it as a skill objective.
Adapting without reinventing yourself
Targeting implies adapting, and adaptation has a clear boundary: it applies to presentation, never to facts. The distinction is simple to state and easy to cross without noticing, especially under the pressure of a posting that almost fits.
What cannot be invented
A level of expertise, a responsibility you never held, a technology you never practised, an outcome, or your actual role in a collective project. These get checked in a technical interview, often on the first follow-up question.
What can legitimately be adapted
The title or opening line, the order of experiences, the skills brought forward, the projects selected as evidence, and the wording of the pitch. The same experience can be told from several angles without a single fact changing.
- Reuse the posting's vocabulary when it matches what you do, without adopting a title you have not held.
- Bring forward the two or three experiences that speak to the posting's problem, shortening the rest if needed.
- Choose evidence that shows the reasoning when the exact tool differs.
- Name the gap instead of hiding it: hidden it looks suspicious, named it becomes manageable.
Where this step ends
Targeting is a decision: where to apply and how to split the effort. Understanding what a posting really asks behind its wording is a reading exercise, and adapting your CV to a given role is execution. The three follow in that order, and confusing the decision with the execution is exactly what produces undifferentiated applications.
Before sending an application
Five minutes of checking before committing several hours of effort to an opportunity.
- I can say in one sentence why this role rather than a neighbouring one.
- I have identified the main responsibility expected, not just the technology list.
- I have found at least one comparable problem in my experience.
- I know which of the posting's skills are blocking and which are secondary.
- I can name my gaps and say which ones are reasonable.
- I have one precise piece of evidence to cite, tellable in two minutes.
- The expected level matches my actual level of responsibility.
- Nothing in my application asserts a fact I could not defend in interview.
Key points
- The limiting factor is available effort, not the number of postings you can reach.
- Seven qualitative dimensions beat a global score that would only simulate rigour.
- A tool gap can be defended; a gap on the role's main responsibility cannot be written around.
- Four categories are enough: strongly aligned, adjacent credible, exploratory, too far.
- Adaptation applies to presentation — title, order, selected evidence — never to facts.
- Naming a gap makes it manageable; hiding it makes it suspicious.
- Applications
- Targeting
- Opportunity search