Skip to content

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.

Interactive example: from opening a role to the hiring process. Example with fictional data.
  1. A recruiter opens a role
  2. Explained matches
  3. The candidate applies — on purpose
  4. The recruiter runs the process
Senior DevOps Engineer · remote
Example with fictional data

New opening

Senior DevOps Engineer · remote

Required

Nice to have

Ordered by fit

Payment never changes the score.

Candidate

Recommended

91
Senior DevOps Engineer
Example Company (fictional)

✓ Kubernetes — on your profile
– Terraform — required, not on your profile

Applied

Recruiter

New

Screening

Interview

Offer

Team notes — private

1/4A recruiter opens a role

01 · Opening and matching

In beta

Say 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 beta

Stages, interviews, decisions — and notes that stay with your team.

Interview invitation

In beta

The candidate picks a slot and accepts.

Team notes

In beta

Private to your organisation; never shown to the candidate.

Structured notes Planned

Concept · not available yet

Requirement → 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.

PlannedConcept · not available yet

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

  1. You post an ad
  2. You wait for applications
  3. You sift through CVs

JobUnblock

  1. You describe who you need
  2. You see explained matches
  3. You ask to get in touch — the candidate decides

Two sides. One rule: consent.

Recruiter

  1. Verified organisation
  2. Visible requirements
  3. Explained matches

Contact only after the candidate accepts

Before that — only a pseudonymous card.

Candidate

  1. One profile, reviewed by you
  2. Visibility — off by default
  3. 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.

Looking for a job? See how JobUnblock works for candidates