scottwrites.things field notes  »  hiring

Field Notes · Explainer · ~9 min read

most résumés never actually get read

I want to explain what a "human capital intelligence platform" is, why that phrase sounds like marketing nonsense, and the one thing it changes about hiring that I think genuinely matters.

fair warning up front: I build one of these things, so I'm not a neutral party. I'm going to try really hard to explain it honestly anyway, including the parts it can't do.

okay, so here's a number that nobody ever puts on a slide. If you ran a busy job opening last quarter and a hundred résumés came in, your team probably gave a real look to about thirty of them.

The other seventy didn't get rejected. That's the part I want to be precise about. Nobody read them, decided "not a fit," and moved on. The pile just got too big and the clock ran out before anyone got to them. They sat there. Then the role closed.

100 résumés, one busy req
the part of hiring nobody likes to draw
got a real look  ~30
never read by anyone  ~70
100 résumés, one busy req. this is the part of hiring nobody likes to draw.

wait, isn't that just a volume problem?

That's what I thought too, for a long time. Too many applicants, not enough hours, end of story. But I don't think that's actually right, and the difference turns out to matter a lot.

A volume problem is something you fix by going faster or hiring more screeners. But silent rejection isn't really about speed. It's about reading. To make a decision you can stand behind, someone — or something — has to actually read the document and weigh it against the job. Seventy percent of the time, that step just… didn't happen. That's not a hiring decision. That's a queue that ran out of time and called it a day.

once I started thinking of it as a reading problem instead of a volume problem, a bunch of stuff clicked into place. so bear with me.

okay so what's a "human capital intelligence platform"?

The phrase is bad. I'll just say that. It sounds like three buzzwords in a trench coat. But there's a real thing underneath it, and the easiest way to get there is to say what it isn't.

Your company already has an ATS (applicant tracking system). It knows who applied, what stage they're in, who emailed them. It's basically a filing cabinet with a to-do list attached. It's good at that! A human capital intelligence platform doesn't replace it.

You've also probably been pitched a dozen point tools — a résumé parser, a scheduling bot, a chatbot on the careers page. Those are features. Each one automates one step. They don't change what your filing cabinet actually knows.

an ATS

stores who's in the pipeline. a filing cabinet that doesn't read the files.

a TIP

reads every file and turns the pile into something you can actually search and ask questions of.

^ this is the whole difference, really

So here's my plain-language definition. A human capital intelligence platform reads every application — not skims it for keywords, reads it — and turns the messy flood of PDFs into a clean, structured thing you can query. 200 inconsistent résumés become 200 comparable profiles, every skill mapped to the same vocabulary, every claim linked back to the exact line on the page it came from. The ATS stores the candidate. The TIP understands them. Then it does the actual hiring work on top of that.

the thing that quietly breaks most résumé scoring

Here's a question that I think breaks almost every automatic résumé scorer, and it's a question any recruiter already knows the answer to in their gut: are you scoring a graduate engineer, or a Chief Operating Officer?

A generic scorer doesn't know. Worse, it doesn't know that it doesn't know — it'll spit out a confident number for both using the same rubric. But the things that make a great grad hire (a relevant degree, hands-on tools, learns fast) are not the things that make a great COO (scope of stuff they've run, years leading people, owned a P&L, credible in front of a board).

Weight "education" at 30% and a fresh grad scores like a plausible COO. Weight "leadership" at 30% and a CEO with rusty hard skills scores like a plausible junior dev. Both answers are wrong, and they're wrong for the same reason: the tool pretended the level of the job didn't matter.

The fix isn't a cleverer single rubric. It's letting the weights flip depending on how senior the role is. Same nine things measured every time, but the emphasis slides:

Same nine signals, weighted by the level of the role
how the emphasis slides from junior to C-level
junior / midcan they do the work?
hard 55
lead 10
dom 10
senior / leadcan they scale the work?
hard 45
lead 15
dom 15
director / VPcan they own the function?
hard 30
lead 20
dom 20
C-levelcan they stand behind it?
hard 15
lead 30
dom 25
hard skills leadership domain

A grad who scores 87 earned it on skills and recency. A COO who scores 87 earned it on leadership and scope. Same number, two totally different questions, both answered correctly. Which is exactly what a good recruiter does in their head when they read across levels — and exactly what single-rubric tools flatten into mush.

my favorite small example: someone with an "AWS Solutions Architect — Professional" cert almost certainly knows what EKS is. but if the letters "EKS" aren't literally on the CV, a dumb scorer says 0% match and tosses a strong candidate on a technicality. a good one knows the cert implies the skill.

what actually changes for a recruiter

The day-to-day change is smaller than you'd expect, which is sort of the point. No new system to log into. No "is everyone trained yet" meeting. A new feed just shows up inside the tool they already use.

What's in the feed is a ranked, explained shortlist drawn from all hundred applicants instead of the thirty that survived the queue. Each candidate comes with a scorecard showing matched skills, missing skills, and the exact sentence behind every claim. The recruiter's time moves off the boring bottom of the funnel (mechanical reading, copy-pasting, "did I miss anyone" dread) and onto the top: judgment, and the human conversation no model should be having.

And the speed is the human's call, not the robot's. The sane rollout has three gears:

Gear 01
shadow
it scores quietly in parallel, nobody acts on it, you just check it against what your team would've done.
Gear 02
gated
recommendations show up, but every one needs a human to approve / edit / decline. every override teaches it.
Gear 03
automate
only on the reqs you pick, only above a confidence line you set, and you can yank that line back any time.

There's no one-way door. Honestly, a tool that asks you to trust it on day one hasn't earned the word "intelligence."

the part where the lawyers show up

This is the part that went from "nice to have" to "you actually have to care about this" faster than most HR teams are ready for.

The rules around AI in hiring have changed. The EU AI Act flat-out classifies AI used in recruitment as high-risk — which comes with real obligations around documentation, human oversight, bias monitoring, and logging. (The big compliance deadline keeps sliding — it was August 2026, now it's being pushed toward late 2027 — but the high-risk label itself is settled, and the law gives a rejected candidate a right to an explanation.) In New York City, Local Law 144 has been enforceable since 2023: if an automated tool substantially helps make a hiring call, you owe an independent bias audit, a public summary of it, and notice to the candidate. And it reaches past the city — remote roles tied to a NYC office count too.

European Union
EU AI Act
Classifies recruitment AI as high-risk: documentation, human oversight, bias monitoring, logging — and a rejected candidate's right to an explanation. Deadline slid from Aug 2026 toward late 2027; the label is settled.
New York City
Local Law 144
Enforceable since 2023. If a tool substantially helps make a hiring call: an independent bias audit, a public summary, and notice to the candidate. Remote roles tied to a NYC office count too.
the question everyone's actually asking
"why was this candidate rejected?"

A regulator can ask it. The candidate can ask it. The hiring manager can ask it. They all want the same thing — where did this number come from? — and a scoring system that can't answer that has no business making calls about people's careers. The whole regulatory wave basically boils down to one demand: be able to show your work.

This is where a real platform pulls away from a black box. A black box that hands you a confident number is now a liability you carry. The other kind does the opposite: every score traces back through its version → a frozen snapshot of the inputs → the extraction → the OCR → the original PDF, each step hashed. Every claim is tied to a passage. Nothing gets overwritten — re-scoring makes a new version next to the old one, so "what did the system say six months ago?" has an exact answer. And you can hand an auditor a bundle they re-run on their own machine and get back one word: VERIFIED.

"show your work" — every score traces back, each step hashed
Score version Frozen input snapshot Extraction OCR Original PDF VERIFIED
Every claim is tied to a passage. Nothing is overwritten — re-scoring makes a new version next to the old one, so "what did the system say six months ago?" has an exact answer.

The sneaky-good part: compliance stops being a thing you survive once a year and becomes something you just… have, by default. The bias audit becomes continuous. The explanation becomes a button. The team that used to dread the audit becomes the team that's already ready for it.

the part I think is genuinely cool

Here's the bit that I think gets missed completely, and it's the one a CFO should care about as much as an HR lead.

In the old way, a job application is basically exhaust. It shows up, gets triaged or silently dropped, and the value evaporates the second the role closes. A pile of PDFs in an ATS is a depreciating asset — most of what you paid to attract never gets used, and what does is stale in six weeks.

But when every application gets read and structured, that same flood becomes a candidate data asset that appreciates. The senior engineer who just missed out on one role is already parsed and instantly re-scorable against the next one — in minutes, not from scratch. A pool you quietly built last quarter activates the day a new req opens. Internal mobility, re-discovery, succession — all of it turns into queries against something you already own, instead of starting from zero every single time.

the old way · exhaust
A depreciating asset
PDFs pile up in an ATS. Most of what you paid to attract never gets used; what does is stale in six weeks. Value evaporates the moment the role closes.
becomes →
the new way · an asset
A candidate data asset that appreciates
Every applicant is parsed and instantly re-scorable against the next req. Pools activate on demand. Internal mobility, re-discovery, succession — queries against something you already own.
this is why high-volume hiring — BPO, retail, logistics — gets the biggest win. the volume that used to be the burden becomes the raw material for the asset. funny how that flips.

what it does NOT do

I said I'd be honest, so: a human capital intelligence platform does not replace your recruiters, and it does not make the hiring decision. I know the category is loud with people promising exactly that. I think they're mostly wrong, and usually furthest from the actual work.

What a good one does instead is kind of unglamorous, and I'd argue more valuable. It does the reading no human has time for. It refuses to produce a confident number out of broken inputs — if a page failed to scan, it blocks the run instead of quietly guessing. And it hands a human a defensible starting point with the evidence still attached. It's built to be able to say "I don't know, and here's why" — which, when the cost of a confident wrong answer is somebody's career, is the most important sentence a system can be capable of saying.

The judgment stays with your people. The tool just makes sure their judgment gets applied to the whole field, on a footing they can defend — instead of to whatever 30% the clock happened to allow.

so… what does it mean?

Put it all together and the point of one of these isn't "we hire faster," even though you will. It's a change in what the job is for. Recruitment stops being the place good candidates go to be silently dropped, and becomes the layer the business actually runs on. HR stops bracing for the audit request and starts already having the answer.

The seventy you never read were never a volume problem to power through. They were a question you couldn't afford to answer — and now you can. That's the thing that changes. Everything else is downstream of it.

anyway — that's the honest version. if you build hiring tools and think I got something wrong, I genuinely want to hear it.
— scott