One of the more persistent assumptions in recruitment is that good evidence should eventually produce a good hiring decision. If a candidate has the right experience, can demonstrate meaningful achievements and can articulate those achievements clearly, then the selection process should, in theory, recognise the capability.
In practice, it often does not.
Over the past eighteen months, much of the work behind FitGrid has involved trying to understand why capable people can present truthful, substantial and apparently relevant evidence and still fail to be read in a way that reflects what they could actually contribute.
The obvious explanations are familiar. Perhaps the résumé was poorly written. Perhaps the interview answer lacked structure. Perhaps the candidate chose the wrong example. Sometimes those explanations are correct. But they do not account for a more interesting class of failure: situations in which the evidence itself is good, the candidate is credible, and the underlying capability is genuinely relevant, yet the selector still reaches an interpretation that materially understates or misclassifies the person in front of them.
That problem is not primarily one of evidence. It is one of interpretation.
A selector never encounters a candidate as a neutral collection of facts. They encounter titles, companies, industries, tenure patterns, qualifications, achievements and career transitions through an existing set of expectations about what those things usually mean. “Retail leader”, “consultant”, “account manager”, “engineer”, “CFO”, “career changer” and “long tenure” are not simply descriptive labels. They arrive carrying associations.
Those associations are useful. Hiring would be impossibly slow if every piece of information had to be interpreted from first principles. Humans consolidate. We classify. We use prior experience to make rapid judgments about unfamiliar people and situations.
The problem begins when the consolidation becomes the candidate.
A person who has spent years developing commercial strategy, leading teams, negotiating complex relationships and improving operational performance may be interpreted predominantly through the sector in which those capabilities were most recently exercised. A candidate with a non-linear career may be read as inconsistent when the underlying pattern is actually one of increasing scope. Someone moving between industries may be treated as lacking relevance even where the cognitive and commercial problems they have solved are highly transferable.
The evidence can all be true while the conclusion drawn from it is incomplete.
This is the challenge I have come to name candidate frame control.
The phrase is not intended to imply control over another person’s judgment. A hiring manager is entirely free to interpret, question and reject a candidate’s case. The objective is instead to identify and reduce unnecessary interpretive friction between what the candidate has demonstrably done and what those facts reasonably suggest they could contribute in a new environment.
The distinction matters because most candidate representation remains heavily evidence-centric. Résumés catalogue experience. Cover letters explain interest. Interview frameworks such as STAR help candidates provide structured historical proof. All of these are useful, but they largely answer retrospective questions: What happened? What did you do? What was the result?
The employment decision is more ‘assumptive to prospective’ based largely on how the evidence is interpreted and seen to traverse the arc.
The organisation is not buying the candidate’s history as such for that is ‘spent effort’. The decisions orient around whether that work history supports a credible view of future performance within the role’s remit.
That creates an interpretive gap. Somewhere between “this person achieved X there” and “this person could create Y here”, in conventional recruitment, much of that translation is left to the selector/s (recruiter/hiring manager/panel).
That is a surprisingly large amount of cognitive work expected to be performed under hiring pressure.
The selector must decide which parts of the candidate’s experience are transferable. They must interpret titles whose meaning varies between organisations. They must determine whether an achievement resulted from the candidate’s judgment or from favourable circumstances. They must reconcile differences in industry, company size, operating model and organisational culture. They must decide whether the candidate’s previous behaviour is relevant to a problem that may look quite different on the surface.
Finally, they must construct some internal picture of what employing this person would actually be like. And all from a ‘snapshot’ of the applicant’s career conveyed in no more than 1000 words across 2-3 A4 pages, guessed by them from their interpretation of what is required to persuade from a job ad.
The more of that work we leave implicit, the greater the probability that an otherwise capable candidate will be reduced to the easiest available interpretation. And often, the ‘worst case’ the selector can attribute from the resume narrative.
This is particularly consequential for experienced professionals with dense or non-linear careers. Their problem is often not an absence of evidence but an excess of it. A thirty-year career can support multiple plausible narratives. The selector will not necessarily choose the one most relevant to the role. They will usually choose the one that becomes legible fastest.
Candidate-side strategy therefore cannot stop at presenting accurate information. It has to consider the path by which that information becomes meaning.
At FitGrid, this has progressively changed the way we think about evidence selection. The conventional question is whether an achievement is impressive enough to include. A more useful question is what the achievement permits the selector to understand about the candidate. Better still: what future contribution does that evidence make credible?
A revenue result, for example, has little interpretive value on its own. The number might be impressive, but what matters in a new hiring context is what produced it. Did the candidate identify an overlooked market? Rebuild an underperforming team? Change account strategy? Improve pricing discipline? Develop relationships that previously did not exist? Navigate regulatory or organisational complexity?
The mechanism behind the result is often more transferable than the result itself.
Once that mechanism is visible, a second question becomes possible: where might this pattern matter in the target organisation?
This is where historical evidence begins to become prospective.
Imagine a candidate has previously joined a business with fragmented customer ownership, inconsistent account planning and poor visibility of expansion opportunities. They introduced a disciplined account structure, improved stakeholder mapping and created a more systematic approach to identifying growth. The historical evidence is useful. But its real value in a new selection process emerges when the employer can see why that pattern may matter in their environment.
The candidate’s case therefore has to do more than say, “I have done this before.”
It should make it relatively easy for the selector to think, “I understand the pattern. I understand why it might matter here. I can begin to picture what this person could do with us.”
This does not require claiming knowledge the candidate does not possess. External applicants inevitably operate with incomplete information about the organisation. Pretending otherwise is counterproductive. The strongest form of candidate frame control is therefore hypothesis-led rather than declarative.
The candidate might say, in effect: based on what I understand about the role and the organisation, this appears to be one of the problems you may be trying to solve. I have encountered an analogous situation before. Here is what I did, here is what I learned, and here is how that experience would inform my thinking if the hypothesis is correct.
That is very different from claiming to know exactly what the organisation needs.
It creates a bridge without pretending the bridge is a certainty.
Most interview preparation focuses on improving answers to questions asked by the selector. Candidates are trained to produce better proof. But if the hiring decision ultimately contains a substantial prospective judgment, the candidate should also be capable of helping the selector articulate the future against which that proof is being assessed.
One question illustrates the difference:
“If we were sitting here six months after I joined and you felt you had made an excellent hire, what would be happening differently?”
The question is powerful because it moves the conversation beyond the abstract language of job descriptions. The hiring manager may describe stronger relationships with particular stakeholders, better commercial discipline, a team requiring less intervention, clearer reporting, increased customer retention or simply the disappearance of a recurring operational problem.
The desired future becomes more explicit.
Now historical evidence can be connected to something concrete.
The candidate may recognise an analogous situation and say: “That is useful context. Something similar existed when I joined X. The circumstances were obviously different, but the pattern was this…”
At that point the interview is no longer simply an examination of past behaviour. It becomes a joint exploration of whether demonstrated capability can plausibly produce value in a specific future environment.
That is the part of the selection process I think conventional interview models often leave unfinished.
STAR, for example, is an excellent framework for producing evidence. Situation, Task, Action and Result establish what happened and what the candidate contributed. But the selector still has to perform the final translation: what does any of this mean for us?
Candidate frame control is concerned with that final translation.
The goal is not to eliminate interpretation. That would be impossible and undesirable. The selector should interpret. They should test the candidate’s claims. They should introduce information the candidate does not have. They should challenge assumptions and consider alternative explanations.
The objective is to remove avoidable interpretive work.
A useful way of thinking about it is as interpretive distance: the distance between demonstrated capability and imagined future contribution.
When that distance is large, the selector has to infer too much. When it is artificially eliminated through exaggerated claims or overconfident projection, the candidate becomes less credible. The task is therefore to reduce the distance only as far as the evidence legitimately permits.
This produces a fairly simple operating principle.
Start with truth. Identify the candidate’s demonstrated capability. Understand the target environment sufficiently well to identify likely relevance. Anticipate the frames through which the candidate may be interpreted. Select evidence that helps the right capability become visible. Provide enough context for that evidence to mean what the facts justify. Then connect the evidence to a plausible future without pretending that future is known.
The result should feel less like persuasion and more like clarity.
The selector should not have to struggle from “they did this over there” toward “perhaps they could do something useful here”.
They should be able to arrive naturally at:
“I understand what this person has done. I understand why it matters in this context. I can picture what working with them might produce.”
That is ultimately what candidate frame control is trying to achieve.