How to Screen Executive Candidates

Screening at executive level has almost nothing in common with screening at other levels, and treating it as the same activity is where most of the errors come from.

Lower down, the CV is roughly the artifact. Someone lists what they did, you check it against requirements, and the gap between description and reality is usually small. At executive level that relationship breaks. Titles are inconsistent across company sizes. Scope is compressed into a line. The CV is a positioning document written to survive exactly the kind of scan you are about to perform, and it will survive it.

So executive screening is reconstruction: working out what someone actually ran, from sources other than their own account of it.

Screen against a rubric, not an impression

Before any candidate is assessed, the brief has to become a rubric — a list of requirements each of which can produce a result when held against evidence.

“Experience scaling a manufacturing operation” cannot. Every candidate passes it if you are inclined to like them. “Has taken a site from single-shift to multi-shift operation, or opened a second production facility” can — it is either supported by something you can point at, or it is not.

Sort the rubric into must-haves and preferences, and put them in the order the client actually cares about rather than the order they appeared in the job description. Then screen against that list, in that order, one criterion at a time. If this feels mechanical, that is the point: the mechanism is what makes the result reviewable later. Getting the brief specific enough to support this is the upstream half of the job.

Read scope, not title

The single highest-yield habit in executive screening is refusing to let the title do the work.

A Director of Operations at a €2B manufacturer may carry more scope than a VP Operations at a €200M one. A “Head of Supply Chain” might own procurement, logistics, and planning across six countries, or might own vendor contracts for one business unit. The words are the same. The jobs are not.

What to reconstruct instead:

• Span. How many people, sites, plants, or countries, and did that number change while they were there?
• P&L. Did they carry one, what size, and was it a real P&L or a cost center with a budget?
• Depth. Direct reports who are themselves leaders, or individual contributors? Two layers below or six?
• Constraint set. Regulated or not. Unionized or not. Capital-intensive or not. These shape how someone operates more than sector labels do.
• Direction of travel. Growing an operation, stabilizing one, and shutting one down are three different skills that produce the same title.

Most of this is not on the CV. It comes from announcements, filings, org structures, the way the company describes its own footprint, and occasionally from what the person said at a conference three years ago. That is normal — screening at this level is triangulation, not reading.

Titles are the cheapest thing on a CV to acquire and the most expensive thing to misread. Filter on scope; treat the title as a hint.

Three verdicts, not two

For each criterion, a candidate lands in one of three states:

Confirmed. The requirement is met and there is a specific, nameable source for it. Not “public sources.” An actual location a colleague could open.

Unconfirmed. Nothing was found either way. This is not a fail. Plenty of capable executives have a thin public footprint, and collapsing “unconfirmed” into “no” systematically screens out people for being quiet.

Flagged. There is evidence, and it is ambiguous. The title matches but the scope detail is missing. The dates overlap oddly. Two sources disagree. Flag it, say what the ambiguity is, and let it stay ambiguous.

The instinct to resolve every flag into a yes or a no is the instinct to make the document look decisive. It is worth resisting. A flagged criterion with the reason attached tells the reader exactly what to probe in the first call. A resolved-by-guess criterion tells them something that might be wrong, in the same voice as everything that is right — which is what makes the confirmed-versus-asserted distinction load-bearing rather than pedantic.

Screening for what is not on the CV

Some of the most useful screening signals sit outside the employment history entirely, when they are relevant to the specific role:

• Regulatory exposure — has this person operated under the regime this role sits in?
• Board seats and advisory roles, which often reveal scope the day job title hides.
• Conference talks and published work, which show how someone frames the problem.
• Named projects and patents, where the role is technical enough for it to matter.
• Integration and turnaround history, which rarely makes it into a title.

The discipline is relevance to the brief. A patent matters in an engineering search and is noise in a finance one. These signals go into the record when they bear on a requirement, with a source, like everything else.

Where screening goes wrong

Halo from the logo. A recognizable employer makes every subsequent claim easier to believe. Company brand is not evidence of individual scope.

Recency weighting. The most recent role dominates the read, even when the more relevant experience sits several roles back.

Inference dressed as fact. “VP Operations at a company that did an ERP migration during their tenure” becomes “led the ERP migration.” It might be true. It is not confirmed, and once it is written in the same voice as the confirmed claims, nobody downstream can tell the difference.

Merged identities. Two people, same name, same sector, one record. The resulting candidate looks exceptional and does not exist. Any claim that seems surprisingly strong deserves a second check that it belongs to the person you think it does.

Screening for the person you already found. A few strong impressions in, the rubric quietly reshapes itself around the profile of whoever impressed you first. Screening against a written rubric in a fixed order is the defense against this, which is most of the reason to write it down.

Where screening stops

Screening establishes what is true about someone and which requirements that satisfies. It does not establish whether they are right for the role.

That judgment needs what the research cannot reach: the temperature of the last client conversation, how the executive team is currently balanced, what the board has already ruled out, whether this hire is meant to sit beside the CEO or eventually replace them. Screening’s job is to hand over a clear, sourced, honestly-flagged picture so that judgment gets made on good information rather than on a persuasive CV.

The line is worth holding explicitly, because the tooling available now makes it easy to blur — a screening pass that outputs a ranking has quietly made a decision it had no standing to make.

Related reading: what to ask once they are in the room, what changes when the role is an operations one, how the three verdicts hold up when a model applies them, executive search best practices for candidate research, how to shortlist candidates for an executive role, how executive search researchers find candidates, and what candidate sourcing tools are actually built for.