By Reginal Campbell · October 17, 2026 · 4-minute read
The Job Requirement You Learn About After the Interview
You can do everything the interview invitation asks and still lose to a test nobody announced.
Your interview was strong. Someone else got the job. The explanation tells you what made them stand out, and you find yourself wondering when you were supposed to know that counted.
Consider a hypothetical customer operations leadership role. The job calls for someone who can improve service delivery, manage a team, and resolve recurring operational problems. The invitation asks candidates to discuss their relevant experience.
One candidate prepares carefully. They bring specific examples of improving processes, coaching employees, and handling difficult customer situations. The conversation goes well.
Another brings something extra: a one-page outline of how they would investigate an operational backlog during their first month. What they would examine. Whom they would consult. How they would set priorities.
The manager selects that applicant. The outline helped them picture the person doing the work.
The first candidate prepared for the interview they were invited to attend.
In the feedback, they hear that their interview was strong. In the same conversation, they learn how much the other applicant’s outline mattered.
The reassurance arrives carrying a reason to doubt it.
Should they have brought something? Would a page of notes have made their experience more convincing? Was discussing their accomplishments not enough?
They are left second-guessing a preparation decision they did not know they were making.
Prepared for what?
Next time, be more prepared. Go above and beyond. Find a way to stand out.
That puts the burden in the wrong place.
The question isn’t how the first candidate could have won. It’s whether they had a reasonable opportunity to provide the evidence the manager ultimately found most persuasive.
None of this means the second candidate didn’t earn the offer. Discussing past accomplishments and explaining how you would approach a new problem are different kinds of evidence. A thoughtful outline can show whether someone investigates before prescribing, considers whom a problem affects, and sets priorities without pretending to know everything on day one. A manager should notice those qualities.
But a polished outline can make sound thinking visible. It can also make ordinary thinking look convincing. The manager still has to distinguish good judgment from good presentation.
And noticing valuable evidence is not the same responsibility as designing an interview that gives everyone a chance to provide it.
What the manager knew
There are two ways this could have unfolded.
In the first, the manager already knew they wanted to see a proposed approach, not just hear about past performance. That demonstration mattered, but the invitation never asked for it.
The omission became the candidate’s problem.
If the manager knew the demonstration would carry weight, they should have requested it.
In the second, the manager hadn’t thought to ask. The unsolicited outline revealed something useful and changed what they looked for in everyone else.
Interviews should leave room for discovery. But discovering useful evidence in one candidate’s answer does not establish that the others lack the capability it reveals.
Did they have a comparable opportunity to show it?
The outline is not the capability. It is one way of making the capability visible.
The test nobody announced
We put considerable effort into describing what people will do once they’re hired: responsibilities, qualifications, technical skills, leadership expectations.
Then we ask them to discuss their experience and leave them to work out what will make it convincing.
Doing the work. Showing you can. Guessing which demonstration will persuade this manager.
Three different tasks.
One candidate explains their operational judgment through specific accomplishments. Another sketches a plan. Both may provide meaningful evidence of the same ability. One may also fit the manager’s preferred way of seeing it.
Hiring involves judgment. The point is not to eliminate it. The point is to distinguish capability from success at anticipating which evidence we wanted.
Letting people distinguish themselves is one thing. Making them guess part of the evaluation is another.
When an unrequested demonstration becomes decisive, we risk mistaking unequal opportunities to show capability for differences in capability.
If a demonstration will decide the hire, it belongs in the invitation.
That doesn’t require five pages of instructions or a script for impressing the manager. If an approach to an operational problem will carry substantial weight, tell candidates they’ll have an opportunity to show one. Let them choose how.
One person may walk through their reasoning. Another may sketch an approach. Someone else may bring a page of notes. The manager can examine the substance: their assumptions, their questions, their priorities.
Keep the preparation proportionate. The purpose is to understand how someone works, not to obtain a free consulting engagement.
Leave room for initiative, too. Someone who identifies an issue nobody else considered should get credit for it. A comparable opportunity does not require identical answers.
It requires that candidates know which capabilities they will need to demonstrate, without having to guess which evidence will matter most.
What a clearer invitation changes
The first candidate may still have lost. A clearer invitation would not guarantee better judgment, a stronger demonstration, or a different decision.
But it would change what they were left trying to understand.
They could examine how well they had shown their capability, rather than wonder whether they should have guessed what evidence to bring.
That is the difference between being disappointed by a decision and being left to reconstruct an undisclosed test.
You were asked to discuss your experience. You did. Then the feedback explained how much a proposed approach had mattered.
You learned what the manager needed to see when you no longer had a chance to show it.
About the author
Reginal Campbell writes about enterprise technology, AI governance, leadership, and the systems organizations build to make consequential decisions.