Hiring,
on the record.
What if hiring were honest? Every message encrypted. Every key change published. Every decision preserved.
Why I built this.
It starts the same way every time.
A candidate sends a resume. Then silence. No response, no feedback, no record. Someone, somewhere, made a decision about that person's career — and didn't write it down. Or if they did, it died when the req closed, buried in a spreadsheet nobody will open again.
Agencies live the same nightmare from the other side. You prep a candidate. You write notes. You brief the hiring manager. Then the candidate crosses into the company's system and every piece of context you built — gone. You start from zero. Every single time.
And the hiring manager? They're making a six-figure decision from a PDF and whatever they remember from a thirty-minute call. No structured reasoning. No record of why they passed. Just a gut call that nobody can audit, nobody can question, and nobody will ever learn from.
Everyone knows it's broken. Everyone has a story. Nobody fixes it because the opacity serves the people who built the system.
Then there's LinkedIn — the thing that was supposed to be the answer. A platform that promised to connect professionals and instead became a feed of humblebrag posts, recruiter spam, and engagement-bait that has nothing to do with getting hired. You maintain a profile for years. It serves you ads and connection requests from people you'll never talk to. The jobs are the same jobs you find everywhere else, just with more sponsored noise. The “network” is a vanity metric. It's not a tool for hiring. It's a tool for LinkedIn.
I got tired of pretending it worked. Candidates deserve a space that isn't a performance. Recruiters deserve tools that don't tax every interaction. Hiring managers deserve a process that doesn't start with “create an account.”
So I started asking a different question. Not “how do we make hiring faster?” Not “how do we make it cheaper?” Those are the questions the industry keeps asking, and hiring keeps getting worse.
The question was: what if hiring were honest?
What if every message between a candidate and a recruiter was encrypted — so the platform couldn't read it, couldn't train on it, couldn't leak it? What if the server stored math, not messages?
What if every key change was published to a public log — hash-chained, tamper-evident, verifiable by anyone? So when we say we didn't change your encryption keys, you don't have to take our word for it. You can check.
What if every decision in a hiring pipeline was written down — structured, timestamped, preserved? So when a req closes, the reasoning doesn't vanish. It stays. Auditable. Transferable. Defensible.
What if a hiring manager could review a candidate without creating an account? No login. No dashboard. No training. Just a link. Because the friction of getting someone into a system is what kills most placements — and it's friction that exists only to serve the platform, not the hire.
And what if AI did the work it's good at — matching, surfacing, summarizing — but a human always made the call? Every output traceable to its prompt, its model, its provenance. The AI assists. The human decides. That's not a feature. That's the whole point.
That's Recruiter1.
Hiring, on the record.
Adrian Samak
Founder, Chief HITL OfficerBuilt different.
Three surfaces.
One pipeline, zero friction. Context flows between agencies and hiring managers in real time.
Every decision, preserved.
When a pipeline closes, the reasoning disappears with it. Recruiter1 keeps a structured record of every evaluation step — so hiring decisions are auditable, transferable, and defensible.
How the security architecture worksOne pipeline, zero friction.
Candidate reviews, secure share links, and structured evaluations flow between agencies and hiring managers in real time. No more lost context across organizational boundaries.
Browse the job boardCandidates, not resumes.
A private candidate network with encrypted DMs, signal-based social proof, and AI-matched job recommendations. Talent gets a persistent identity — not a PDF that goes stale.
Explore SignalsTrust by construction.
Three properties that make R1 trustworthy without trusting us.
Ledger by default.
Every evaluation step, every decision rationale, every pipeline move is structured and preserved. Nothing vanishes when a req closes.
Encrypted by design.
AES-256-GCM with X25519 key exchange. The server stores math, not messages. Device keys are tracked in a public transparency log.
Transparent by contract.
Key changes are published to a tamper-evident, hash-chained log that anyone can verify. Trust is verifiable, not claimed.
We are always interested in meeting exceptional people.
Remote-first. High agency. Meaningful equity.
View open positionsHire(d) better.
