The brief is a candidate advocacy document. It deserves to be treated like one.
HC Brief is my answer — a way to give a hiring committee the same situational awareness the recruiter already has, so a strong candidate's case gets made clearly, fairly, and without anything getting lost in translation.
The Hiring Committee brief is the last mile before a hire. It's the document that determines whether a strong candidate gets through — and it's one of the most consequential things a recruiter writes.
The bar kept climbing. Every time I walked away from a Hiring Committee and came back to submit again, it felt like a new set of criteria — longer, more specific, harder to clear than the last round. It wasn't that watch-outs got scattered — you can't really scatter them — it's that low-signal concerns were easy to miss entirely. Committees also expect actual interview quotes as evidence for every claim, not paraphrase, and every brief needs a gender-neutral scrub to keep bias out. AI fluency became a requirement without much broad communication about how to actually assess for it, so recruiters had to figure that part out mid-process, often on a submission already in motion.
And there are real stakes to getting it right the first time: a brief goes through multiple layers of approval before it ever reaches Hiring Committee, and missing one HC date can push a process out multiple days. One week, three of my eight-hour working days went entirely to two HC documents — 24 hours of dedicated work — and even then, entries were questioned past that point, adding more time on top. That's not the exception; that's what these documents can cost.
I built HC Brief because getting a strong candidate through Hiring Committee shouldn't mean re-solving the same completeness, evidence, and formatting problem from scratch every time, against a bar that keeps getting harder to clear without help.
The bar kept climbing. The time cost kept rising with it.
A Hiring Committee brief isn't judged once — it's judged against a standard that gets more specific and more demanding every cycle. Low-signal concerns were easy to miss, not because they were scattered, but because there was no forcing function to catch every one of them. Add in the evidence requirements, the bias scrub, and an AI fluency bar that arrived without a clear playbook, and a single brief could take days — sometimes most of a week — to get right.
Low-Signal Concerns Were Easy to Miss
Not scattered — just easy to overlook without a structural check that forced every gap and tenure flag to surface somewhere.
Evidence Had to Be Verbatim
Hiring Committee expects actual interview quotes supporting every claim, not paraphrase. Tracking down and attributing the right quote for each point took real time.
AI Fluency Arrived Without a Playbook
It became a requirement for every hire at every level without much guidance on how to actually assess and document it — so recruiters had to figure it out mid-submission.
Every Brief Started From Zero
Without a canonical structure — including the gender-neutral scrub every brief needs — each recruiter rebuilt the same decisions from scratch, every time, while the bar kept climbing underneath them.
Every section has one job. When sections do their jobs, decisions get clearer.
The key insight was simple but had significant implications: a brief that tries to put everything everywhere ends up putting nothing anywhere well. The solution wasn't to add more content — it was to give every concern exactly one home.
When Watch-Outs is the single container for all flags — tenure, gaps, concerns, unassessed values — Job History can be a clean narrative. When AI Fluency has its own required section, it can't be glossed over. When each section has exactly one job, the committee reads the brief instead of decoding it.
"The brief is not a summary of scorecards. It's a structured argument for why this person should be hired — with full transparency about the risks."
Six sections. One job each.
The fix wasn't more guidance — it was fewer places for anything to hide. HC Brief is built around six required sections, each with exactly one job, so a concern either has a home or it's missing entirely. There's no third option. Before anything is finalized, a self-audit checks for gender neutrality, evidence mapping, and any claim that isn't backed by the scorecard.
From a draft to a canonical standard.
The First Brief
HC Brief started as a structured prompt — a way to translate raw scorecard notes into a coherent Greenhouse submission. The structure worked. The question became: could it scale to any candidate, any role, any PE?
Jessica Lopez as the Anchor
The Jessica Lopez brief became the canonical format example — the standard that all subsequent briefs were measured against. Having a concrete anchor made the format teachable and transferable to other partners.
Watch-Outs as Single Home
The most important structural decision: Watch-Outs became the one and only home for all concerns. This freed Job History to be a clean narrative, and ensured the committee could find every flag in one place — nothing buried, nothing missed.
AI Fluency Rationale
As AI fluency became a universal Gusto requirement, HC Brief was updated to include a mandatory standalone section. Every brief now documents the AI fluency assessment explicitly — there's no way to submit without addressing it.
Self-Audit Before Finalizing
Added an automated self-audit step: the tool checks for gender-neutral language, unsupported claims, missing Watch-Outs, and incomplete AI fluency rationale before delivering the final brief — catching issues before they reach the committee.
Pod-Wide Pilot, Expanding
HC Brief is in active pod-wide pilot. It originated as my own tool, was shared with my manager who asked me to pilot it formally, pressure tested live with Amy Thibodeau's team, stress tested with Ellen's L6 submission, and produced a brief the hiring committee called "GOAT level." Expansion across Invite is the next step.
Cleaner briefs. Fairer decisions.
Format is not a detail. Format is fairness.
HC Brief taught me that the quality of a hiring decision is partly determined by the quality of the document that frames it. A brief that buries watch-outs protects no one. A brief that skips AI fluency misses a required bar. A brief without a coherent narrative leaves the committee to do the synthesis work that the recruiter should have done.
This started as my own tool, built to solve my own problem. Then my manager asked me to pilot it. Then we pressure tested it with real submissions. Then a hiring committee called an L6 brief it produced "GOAT level." That's the proof of concept. Org-wide adoption is the next chapter.
Editorial Note: Names and identifying details have been changed to protect confidentiality. The work itself has not.