A rejection can be the right result in hiring. The dangerous case is a rejection that happens before anyone qualified to judge the work ever sees the candidate.
Recently, a story circulated about a frustrated team lead who applied to an open role on his own team under a fake name, only to be rejected in six minutes because his CV listed “React” while the screening filter required “React.js.” Whether that rejection comes from an AI model or a rigid keyword rule a recruiter configured years ago, the strategic problem is the same: a trivial difference in wording ended a file before anyone who actually understood the job looked at it.
Tech founder Chris Bakke wrote in Fast Company about running a different kind of test. About once a year, he applies to open roles at his own companies under an alias, simply to see how long it takes a strong application to reach a real person or receive a clear decision. His focus wasn’t a missing punctuation mark; it was bureaucratic delay.
Between rigid keyword rules and slow, multi-layered handoffs, most corporate front doors are quietly turning away the exact people leadership claims to be looking for.
The Blind Spot at the Top
When I sit down with board members and C-level executives, I find that the people with the biggest titles are always the last to feel a brittle front door.
If you are an executive or a director, you likely entered the company through a trusted network, an acquisition, or a dedicated executive search. You never had to feed your career history into your company’s automated careers portal. Because of that, it is easy to assume that your seat at the table is the natural result of merit, and that your hiring machine is equally good at spotting merit at every other level of the organization.
Often, it isn’t. If you stripped away your name, your reputation, and your internal sponsors, and submitted your actual track record (including the nonlinear leaps, the projects that taught you the most, and the skills you learned on the job) there is a very real chance your own system would screen you out before a human ever read the second page.
How to Stress-Test Your Pipeline
You do not need to play “undercover boss” or trick your HR team for the sake of a clever anecdote. A board that wants to know how its front door actually behaves can ask leadership to run a clean, structured audit:
- Submit synthetic test profiles: Create a small batch of realistic applications, mixing high-agency builders who have unconventional backgrounds with polished resumes that look compliant on paper but lack real substance.
- Define the verdict in advance: Before putting those files into the funnel, have the hiring executives write down which profiles should advance and which should be declined.
- Audit the rejections and the clock: Track how many days it takes for a strong builder to reach someone who understands the work—and inspect the exact rules that eliminated the candidates who never made it through.
When executives actually look at the files their system auto-rejects in the first ten minutes, the conversation in the boardroom changes immediately. You stop talking about “talent shortages” and start fixing the filter.
The question I ask boards is simple: if we stripped away your name, your title, and your internal advocates, would our current hiring process recognize a person who can do the job—or could a missing keyword end your file in minutes?
I advise companies on recruitment for a changing job market. Contact me to arrange an on-site workshop for your board and leadership team to stress-test your hiring pipeline.