A 637-point Hacker News post this weekend told the story of a man who spent ages 14 to 16 in a maximum-security juvenile prison, picked up a felony at 19, lost nearly everything to addiction — and then taught himself to code, built open-source software, and got hired by people who looked at him rather than his record. The post, by a developer writing under the handle GavinRay97, is plainly moving. It is also, read at the right angle, an accidental indictment of the very policy framework that claims to help people like him.

Washington State’s expanded Fair Chance Act took full effect this year, layering new requirements on any employer who wants to consider criminal history in hiring. The law now mandates a two-step adverse action process, individualized assessments, written explanations, and waiting periods that give candidates time to respond before a decision is final. It is, by the standards of 2026 employment law, a model statute. The problem is that the model bears almost no resemblance to how the viral story actually worked.

The Statute Requires a Process; the Story Required a Person

Read the post carefully and you notice something. The turning points are not programs, not policies, not expungement laws, not fair-chance ordinances. They are individuals. “A few people who took a chance on me,” he writes. That is the entire mechanism. Someone with hiring authority looked at an applicant with a felony record and made a judgment call — discretionary, un-procedural, legally exposed.

Under Washington’s new framework, that same judgment call is now embedded in a compliance sequence designed to make it auditable. The employer must delay the background check until after a conditional offer. Must run an individualized assessment. Must issue a pre-adverse action notice, wait, then issue a final adverse action notice if the answer is no. Every step is documented. Every step is discoverable in litigation.

The law does not forbid hiring someone with a record. But it makes the act of choosing to do so feel like a liability — because now there is a paper trail showing you saw the felony and hired them anyway. If something goes wrong later, that trail will be Exhibit A in a negligent-hiring suit. The rational employer response is not to discriminate; it is to avoid the whole sequence by never reaching the conditional-offer stage for candidates the background check might complicate.

One founder of a 40-person SaaS company, reached via Slack on Sunday, put it plainly: “I’ve hired two people with records. Both worked out. I would not do it again under the new Washington rules. Not because I don’t want to — because my board would need to know, and their lawyers would need to know, and suddenly a hiring decision becomes a governance issue.”

What Compliance Culture Can’t Replicate

This is the tension the fair-chance movement has never fully confronted. Discretionary mercy — the thing that actually changes a life — is personal, informal, and un-standardizable. The law wants to make it procedural, transparent, and standardized. Those two things are in tension, and the law is winning.

The Clean Slate laws rolling out in D.C. and Virginia this year attempt a different approach: automate record-sealing so certain convictions never appear on background checks at all. That at least sidesteps the discretion problem by removing the information from the equation. But it raises its own question: if the goal is to make the record invisible, what are we saying about whether employers have a legitimate interest in knowing about it?

What is striking about the Hacker News post — and the hundreds of comments amplifying it — is that nobody is praising a statute. Nobody is saying “thank God for Washington’s individualized-assessment requirement.” The story resonates because it is about specific people doing something risky and human. The policy apparatus, for all its good intentions, is trying to eliminate the risk from that transaction. But the risk is the transaction.

The Uncomfortable Question the Post Raises

The post’s author rebuilt his life through software and open source — fields where demonstrable skill can, in theory, substitute for a clean background check. That is not true of most work. A warehouse supervisor, a home health aide, a school bus driver — these roles involve physical proximity to people and property, and the calculus is different. But the viral post is not about policy design for those roles. It is about the particular alchemy of someone seeing past a record and betting on a person.

The uncomfortable question is whether making that bet legally safer — which is what the Fair Chance Act claims to do — actually makes it less likely. The answer, if you ask people who do the hiring rather than people who write the laws, is not encouraging. The laws give employers a path to say yes while documenting every step. They also give employers a very clear reason to say no before the path ever begins.

Sources