The Forty-Minute No

The Rejection and The Reveal

I applied for a role at 1:03 pm, in the afternoon. I was rejected at 1:43 pm.

Forty minutes. My skills were "impressive," the rejection email assured me, but they had decided to move forward with candidates who more closely fit their needs. I'd half-decided the role wasn't right anyway, and the outcome changed nothing about my afternoon. What caught my attention wasn't the *no*. It was the *forty minutes*, because forty minutes is not enough time for a human being to have read anything. The decision was made by a filter, and the filter's answer was dressed up in the language of considered judgment.

That gap, between what actually happened and the story told about it, is where my mind sits because it's a small, clean specimen of something I've spent three books trying to describe.

Can metrics tell a true story?

The Mission of Metric

The purpose of a hiring process is two-fold: to find the person who can do the work well and to find the person who best fits the team. Simple enough to state; however, no organization can read a thousand applications by hand, so it builds proxies for "can do the work," years-of-experience thresholds, salary bands, and keyword matches. Those proxies are reasonable. They are also not the same thing as the purpose. Under volume pressure, the proxy is what the system starts to optimize. The filter stops asking, "Can this person do the job?" and starts asking, "Does this record fall inside the boundary?" Those were never the same question, and somewhere in the drift from one to the other, a person who could plainly do the work gets removed because the measurement replaced the thing it was standing in for.

This is the pattern I call metric-as-purpose drift, and the unsettling part is that nothing malfunctioned. The system did exactly what it was built to do. Drift rarely announces itself as failure. Far more often, it arrives wearing the uniform of efficiency.

The Capability Argument

Here's the objection that usually defends the auto-reject: there are simply too many applicants, and filters are a necessary evil. But that defense collapses the moment you look at it honestly. The same speed that lets a system reject me in forty minutes would also let it rank every applicant in forty minutes. The calculation isn't scarce. Reading isn't the bottleneck. The reject filter and a prioritization engine are the same capability pointed at two different purposes, and the choice between them isn't technical. It's about what the organization actually decided to optimize for.

Imagine the version that served the purpose instead of the proxy. You tell the system: surface the top thirty candidates for a human to review. If none fit, then the next thirty. And so on until the role is filled, with the measurement ordering the reading rather than replacing the judgment. When someone's found, everyone else gets told the search has closed. And this is the part that costs almost nothing and changes everything: you tell candidates roughly where they landed.

You surfaced in the top hundred of nine hundred; we're advancing the top thirty in this round based on these criteria, and you may be contacted for later rounds.

That is not science fiction. It's a prompt and a willingness to be seen.

Transparency: Risk or Safety

Most institutions get this wrong, believing that hiding the metric protects them and disclosure exposes them. The opposite is true.

A defensible process is one whose criteria are stated, job-related, and applied consistently, which is very close to what the law already asks for. The opaque gate fails all three from the institution's own point of view: the criteria are unstated, so if the process is ever challenged, the company has to *reconstruct*, after the fact, why it rejected someone from a black box it deliberately kept dark. That reconstruction is precisely where the liability lives. Opacity doesn't remove the exposure. It just defers it to the moment you can least control it and strips away the contemporaneous record that would have been your defense.

The transparent version builds that defense in real time. "You reached the top hundred; we advanced the top thirty on criteria A, B, and C, drawn from these requirements" is, in a single sentence, a documented, job-related, consistently applied rationale generated at the moment of decision. You've written your own defense file. And the strongest objection left to a challenger shrinks to "the job description was underspecified," which, in an age where job descriptions have swollen to exhaustive lists by the minute, almost never holds.

Which leaves a fork, and neither branch flatters the institution that chose silence. Either they've badly misjudged their own legal exposure, mistaking felt safety for real safety, or their criteria are quietly encoding something that couldn't survive daylight, and the opacity isn't caution but cover. There is no third branch where the darkness reflects well on them. Requiring transparency, then, does more than make the process humane. It sorts the organizations that had nothing to hide from the ones that did.

Story: Orphaned Structure

I could stop there, and it would be a tidy analysis of forces, volume, fear, and risk. Those explanations share a convenient feature: they are owned by no one. They make the drift a weather system, and the weather is nobody's fault.

That's not quite honest. Underneath the structure is a person who could have built the better version and didn't. "The institution preferred opacity" is a tidy abstraction that launders individual inertia into systemic inevitability, and the passive voice is drift's native tongue. Nobody chose the broken process; it "emerged." Nobody is accountable, because responsibility got distributed across a structure until it evaporated.

So let me put the agent back in the sentence. Guarantee someone in that department a bonus tied to make this process bulletproof and humane, and it would exist within a fortnight. Not because people would suddenly grow conscientious, but because the incentive would finally point at the purpose instead of away from it. The capability was never missing. The reason to use it was there. Rejected, qualified candidates are invisible and silent; they don't illustrate a difference anyone can measure. So the effort to serve them is pure cost with no reward, and rational self-interest computes correctly: don't bother.

We need to honestly evaluate this, because "people are lazy" is as lazy a theory as "systems drift" and just as capable of explaining everything and therefore nothing.

The person who skips the fix usually isn't a villain. They're responding correctly to a structure someone above them declined to build well. Which means the accountability doesn't vanish; it climbs to whoever had the authority to tie reward to purpose and chose not to.

My Authored Why

I wrote three books on systems and their drift because diagnosis alone is insufficient. A person who can see the drift but has no method, no measurements, and no place to begin is only better-informed about their helplessness. So one book diagnoses the drift. One turns the diagnosis into practice: how to measure, where to start, and how to continue. And the third addresses the part the first two expose but cannot close: the person who has to hold the line after the meeting ends, when the incentives still haven't changed and everyone else has drifted back to the easy thing.

Because that's what it comes down to. Doing what shores up the foundation is always uphill. Drift is gravity, a constant pull toward the lower-energy state, and standing against it isn't a decision you make once. It's a posture you hold under continuous load, while your own fatigue and your own unaligned incentives quietly urge you to set the weight down.

It would be easy to end there, on the lone figure straining against the tide, admirable and doomed. But that's not how this works, and the truth is more hopeful. Standing against gravity is nearly impossible alone and becomes progressively sustainable in numbers because each person who holds the line lowers the cost for the next. Integrity compounds the same way drift does, only in reverse: each untaken action makes the next easier to skip, and each person who stands makes standing more normal, less lonely, and more defensible until, at some threshold, the posture stops being resistance to the culture and becomes the culture.

You don't have to defy gravity forever. You have to be the first stable point that makes a second one possible. The foundation gets shored up one person at a time, and the value of the first isn't that they fix it; it's that they prove it can be stood for and lower the price of the next person joining.

A forty-minute rejection is a small thing. But it's a clean window into a vast arena, and the way out isn't cleverer filters or better software. We already have the capability; we proved that in the first five minutes. The way out is someone deciding the foundation is worth standing for when it would be simpler not to.

The more of us who do, the easier it becomes.