HFor hiring teamsapplications open · summer 2026

Hire the human.Not the CV. Not the title. Not the keyword stack.

Describe the person who'd thrive on your team — how they work, the scope they own, the values you hold. Claude matches against rich candidate profiles, not keyword-stuffed PDFs. You see the match reasoning before you see the CV.

Request employer accessSee how matching worksEncrypted both sides · no resume mills
9.1
Match in your inboxprofile #4821
arrived 12 min ago
↑ your team
Sourcegraph · Cody team
staff IC slot · EU · 6-person crew
deep-focusasync-defaultships to usersscope: lead-IC
candidate ↓
Profile #4821
8 yrs · EU · lead-IC pattern
deep-focusasync-defaultships to usersB2B SaaS only
why a 9.1
Same working pattern. Both default to async. Their last three roles all shipped customer-facing LLM products to B2B teams under 500 people. The title gap is irrelevant.
human ↔ humanno CV pile
01 / describe

The person, not the JD

Working style, scope, team shape, what success looks like 6 months in.

02 / inbox

Matches come to you

Candidates surface with score + reasoning, anonymized until you both agree to talk.

03 / reach out

Warm intros, claim-traced

Reach out with a tailored note. Their experience claims are pre-verified against their profile.

04 / private

Both sides encrypted

Their profile and yours. The server can't read either. Even we don't see your hiring data.

describe(person, not role)match.attribute_by_attribute()candidate.profile → your.inboxclaim_trace · pre-verifiedanonymous until mutualno resume millsencrypted both waysscoped reasoning · auditeddescribe(person, not role)match.attribute_by_attribute()candidate.profile → your.inboxclaim_trace · pre-verifiedanonymous until mutualno resume millsencrypted both ways
01 Why hiring teams switch

You can't hire a human by skimming a PDF stack.

Three things every ATS gets wrong, and we built around. Profile-first, reasoning-first, mutual-consent-first.

01 / profile-first

Describe the person. Not the role.

A title and a bullet list don't describe who'd thrive here. Tell us the working style, the scope, the kind of decisions this person owns. Claude matches that — not your job description against their resume.

team6-person crew, async-first
styledeep-focus, ships > debates
scopelead-IC, owns a surface
valuescraft > velocity
roleStaff AI Engineer (one slot of many)
02 / reasoning

Match reasoning, not a CV pile.

Every match comes with a why — attribute-by-attribute. You see "their last three roles shipped customer-facing LLM products to B2B teams" before you see the CV. Lead with reasoning, dig into the resume when the match earns it.

profile #4821 · score 9.1
Async-default · last 3 roles fully remote EU
Shipped LLM product to 200k+ B2B users
Lead-IC pattern · no people management
Only B2B — passes on consumer roles
03 / mutual

Encrypted both ways. Anonymous until you both want to talk.

Candidate profiles are pseudonymous in your inbox. Your team's hiring profile is pseudonymous in theirs. When both sides green-light the match, you see each other. No resume mill. No recruiter spray.

your teamciphertext
server
candidateciphertext
02 How matching works

Four steps. The rest is in your inbox.

You don't post a job and wait. You describe the person, and matches stream in as candidates with that profile shape opt into being considered.

step 01

Write a profile, not a JD.

Skip the bullet-list job description. Describe who'd thrive — working style, the team they'd be on, what success looks like in their first six months. The role title is one slot among many.

↳ what most companies post
"5+ years experience, strong communication, must be proactive, fast-paced startup, ninja rockstar 10x, AI native, must love dogs…"
↳ what we ask you to write
team6 ICs, async-first, ships every two weeks
scopeLead the Cody indexing pipeline
valuesCraft over velocity, ships over debates
6moIndexer 2x faster, fewer P0 escapes
step 02

Matches surface in your inbox.

Candidates whose profiles match yours opt into being considered. They arrive with a fit score and a one-paragraph reasoning. No CV pile, no spray.

Inbox · Staff AI Eng, Cody14 new
9.1
Profile #4821
Async-default · shipped LLM to 200k B2B users · 8 yrs
12m
8.4
Profile #4750
EU remote · scope-lead pattern · craft-obsessed
3h
7.6
Profile #4612
Solid IC, B2B SaaS, no LLM yet but adjacent
1d
step 03

Read the reasoning.
Decide if you want to talk.

Open a match: you see the score, the reasoning, and the attribute-by-attribute breakdown — all before the CV. Claim-traced means every line in their experience summary points back to a verified profile claim.

match reasoning
9.1Profile #4821 · Staff AI Eng

Their working pattern matches yours on 7 of 8 attributes. Same async default. Last three roles all shipped customer-facing LLM products at companies under 500. The title gap (Manager → Staff IC) is irrelevant — their de-facto scope has been lead-IC for 3 years.

async-default — last 3 roles fully remote EU
ships-to-users — 200k+ B2B users at BetaCorp
lead-IC — no people-management since 2022
step 04

Reach out. Both sides agree.

Compose a short intro — the system suggests citation hooks from their profile so your note isn't generic. They get the message under their pseudonym. If they say yes, the masks drop on both sides and you start the real conversation.

anonymized · pseudonym until mutual yes
to profile #4821 · from sourcegraph · cody-hiring
Your indexing work at BetaCorp caught us
Saw your profile pattern matches what we're trying to do on Cody — async-default + lead-IC scope, customer-facing LLM. The piece I'd love to dig into: how you handled the GDPR migration in 2024. 30 min next week?
03 Inside the app

An inbox, not a pipeline. Matches come to you.

You spend hiring time reading reasoning, not sorting through resumes. Every candidate arrives scored, anonymized, and with their experience already claim-checked.

Preview · employer side opens after seeker launch · join the waitlist

hunt.work
S Sourcegraph employer
Encrypted both sides · candidates are pseudonymous until mutual yeslast audit · 14:02

Cody · Staff IC slot

14 matches · 3 new in last 24h · avg score 8.4
9.1
Profile #4821
8 yrs · EU · lead-IC pattern · last role: PM Director, BetaCorp
asyncdeep-focusships-to-usersscope-leadB2B SaaSLLM
12m ago
8.4
Profile #4750
6 yrs · EU remote · scope-lead · craft-obsessed
asyncdeep-focusscope-leadplatform teamML infra
3h ago
8.0
Profile #4691
10 yrs · EU · staff IC at Series-C B2B SaaS
asyncships-to-usersteam-leaddeveloper tools
5h ago
7.6
Profile #4612
7 yrs · EU · solid IC, B2B SaaS, no LLM yet but adjacent
asyncscope-leadB2B SaaSno LLM
1d ago
01 / inbox, not pipeline

Matches come to you

Candidates whose profile matches yours opt into being considered. You receive a scored, reasoned match — not a stack of resumes to sort.

02 / anonymous by default

Names hidden until mutual

Score is computed on working pattern, scope, and verified claims — not on names, photos, schools, or other protected attributes.

03 / claim-traced

Pre-verified experience

Every "shipped X" or "led Y" in their summary points back to a verified profile claim. No more "did this actually happen?" interview question.

04 Privacy model

Hiring is sensitive — for both sides.

A candidate's job search can cost them their current job. A startup's hiring plan can leak strategy. Encrypting one side and not the other only solves half the problem. We do both.

Both profiles encrypted at rest. Cross-tenant isolation enforced by the database itself.

  • Your team's hiring profile is encrypted at rest. The server enforces per-account row-level isolation — there is no query that returns another team's data.
  • Candidate profiles are encrypted at rest the same way. Their CV, their reasoning notes, their other matches — invisible outside their account.
  • Match computation happens in a scoped, audited Claude call. The two relevant slices are decrypted just long enough to score — then discarded.
  • Anonymization is a feature, not a setting. Identifiable attributes (name, photo, school, etc.) are surfaced only after both sides agree to talk.
two-sided encryptionaudited
your team
Sourcegraph · Cody
7b3a92f1c4e8a05d…
a09c41dd6e7b3a92…
matches
via scoped
decrypt
candidate
Profile #4821
f1c4e8a07b3a92dd…
3e9c41dd6e7b3a92…
hunt.work server sees
ciphertext only. Match scores returned. Plaintext profiles never stored.
05 Early access · private beta

The numbers we care about. Not the vanity ones.

8.2
Average match score for surfaced candidates
48h
Median time from match to first reply
3:1
Match-to-conversation ratio (industry avg: 40:1)
0
Names, photos, or schools shown until mutual yes
06 Early access

A short waitlist. A real conversation first.

We're onboarding 20 hiring teams in summer 2026. Drop your details and we'll reach out for a 20-minute call to understand what you're hiring for.

Request employer access

Free during private beta. Cohort 2 pricing estimated at €280 / role / month — free while we're onboarding founding teams.

Free during betaFounding-employer pricing lockedHands-on white-glove setup
07 FAQ

Hiring-team questions, in order of frequency.

If you've got more, write us — [email protected].

01

How is this different from a sourcing tool or an ATS?

Sourcing tools find people who match your job title and spam them. ATSs filter incoming applications by keyword overlap. We do neither. We match the person you describe against the person each candidate is — working style, scope, values, the things that actually predict thriving on your team. The role title is one slot among many.

02

Where do the candidates come from?

Active job-seekers using hunt.work for their own search. They've already built a rich profile of who they are. When a hiring profile matches theirs, both sides get notified. No scraping, no LinkedIn cold-outreach. Candidates opt in to being considered, role by role.

03

What if our hiring profile is sensitive?

It's encrypted at rest and isolated by per-account row-level policies the database itself enforces. Candidates only see your pseudonym + the working-pattern attributes — your company name surfaces only after they say yes.

04

Do you support DE&I / bias-free hiring requirements?

Anonymous scoring is on by default and can't be turned off during the match phase. Names, photos, schools, and other protected attributes are not visible to you (or to Claude) until both sides agree to talk. Match scores explicitly avoid those signals.

05

Can we integrate with our ATS?

Today: export matches as structured candidates (Greenhouse, Lever, Ashby) once both sides agree to talk. Bi-directional sync (read JDs from your ATS) is on the roadmap for cohort 2 — please flag this on your access request.

06

What does it cost?

Free during private beta (20 hiring teams, summer 2026). For cohort 2 we're testing a per-role flat fee (€280 / role / month estimated) — no per-candidate / per-message / per-hire spam fees. Founding employers get pricing locked in for 24 months.

Stop posting JDs. Describe the person.

20 minutes to write a hiring profile. Matches start surfacing the same day. Free during private beta — founding-employer pricing locked when we open cohort 2.

Encrypted both sides · anonymous by default · audited
hunt.work for employers — hire the human, not the CV