Early access for employers
Describe who you need. We'll show matching professionals — with their consent.
Candidate discovery instead of a job board. Describe the role, see explained matches and decide whom to contact.
Early stage: we're still building the candidate community, starting with technical specialists. We don't promise a particular number of candidates.
- A recruiter opens a role
- Explained matches
- The candidate applies — on purpose
- The recruiter runs the process
Senior DevOps Engineer · remoteNew opening
Required
- Kubernetes
- Terraform
Nice to have
- 5+ years of experience
- English B2
Ordered by fit
Payment never changes the score.
- 0Candidate 7F3A2C · DevOps EngineerSenior · 6–9 years · PolandKubernetes — statedTerraform — stated
- Experience closely matches the requirements
- Skill set fits the role
- 0Candidate B21E90 · Platform EngineerSenior · 10+ years · PolandKubernetes — statedTerraform — not stated
- 0Candidate 4C7D11 · Systems AdministratorMid · 3–5 years · PolandLower fit — review yourselfKubernetes — not statedTerraform — not stated
Candidate
Recommended
✓ Kubernetes — on your profile
– Terraform — required, not on your profile
Applied
Application sent
Apply to Example Company (fictional)
Applying shares your full profile and contact details with this company only. You can withdraw at any time.
Recruiter
New
Screening
Interview
Offer
Team notes — private
1/4A recruiter opens a role
01 · Opening and matching
In betaSay what's required. See who fits — and why.
- Order depends only on fit.
- Payment never changes a score or the ranking.
- Missing requirements are shown — nobody is rejected automatically.
- Until the candidate agrees — only a pseudonymous card.
02 · Pipeline
In betaStages, interviews, decisions — and notes that stay with your team.
Interview invitation
In betaThe candidate picks a slot and accepts.
Team notes
In betaPrivate to your organisation; never shown to the candidate.
Structured notes Planned
Concept · not available yetRequirement → observation. Notes record what was observed — they don't verify a CV.
From screening onward — only after the candidate applies or accepts a contact request.
03 · Feedback
Useful feedback — without the extra hour.
A draft built from the role's requirements and structured notes. You edit and approve it — nothing goes out unreviewed.
Developmental guidance, not a verdict. Private notes are never passed on verbatim.
04
Where we're heading
The goal: you describe in natural language whom you need, and the system returns ranked, explained matches among people who chose to be discoverable.
For many industries — starting with technical specialists.
Job board
- You post an ad
- You wait for applications
- You sift through CVs
JobUnblock
- You describe who you need
- You see explained matches
- You ask to get in touch — the candidate decides
Two sides. One rule: consent.
Recruiter
- Verified organisation
- Visible requirements
- Explained matches

Contact only after the candidate accepts
Before that — only a pseudonymous card.
Candidate
- One profile, reviewed by you
- Visibility — off by default
- Accept or decline
Principles we build on
Principles we build on
- Payment never changes a score or the ranking; there are no paid boosts in the beta.
- The index supports a decision; it doesn't make it.
- Inferred skills are never treated as verified.
- Candidate data — only for recruitment, within their consent.
Honestly, about early access
- Employers join by invitation, after their organisation is verified.
- At first there will be few candidates, focused on selected technical specialisms; we will widen the scope over time.
- Payments are disabled during the beta; we'll describe the rules for later stages before they apply.
Early access for employers
Early access for employers
We'll invite the first organisations where there are enough candidates.
A contact form for employers will be available soon.