Turn role requirements into a shared standard.

AI proposes criteria from your job description and assesses each CV against them. Adjust the priorities and inspect the reasoning behind each result.

Criteria, extracted from your job description.

AI reads your job description, extracts the requirements that matter and proposes them as weighted criteria. Auto-detect is on by default, and you decide what stays.

  • Clearly labelled as AI-proposedExtracted criteria sit under From the description, apart from the ones you add. Edit the description and refresh to update them.
  • Include or excludeExclude anything that does not belong and it is left out of screening from then on.
  • Templates and a saved libraryReuse the criteria you trust across roles, and add your own on top.

Criteria

5
React, 5+ yearsProduction React experience, recent.
Must-have
TypeScriptTyped codebases, not just familiarity.
Must-have
Design systemsBuilt or maintained a component library.
Important
EU work permitAdded by you from the saved library.
Must-haveYours
AccessibilityWCAG work, keyboard and screen readers.
Nice-to-have
Add criterionTemplatesLibrary: Senior engineering

Weight what the role actually needs.

Mark each criterion Must-have, Important or Nice-to-have. Together they form the role's rubric: the weighted criteria every CV is assessed against. A candidate who clearly fails a must-have is scored well below those who meet them all.

Try it. Design systems is
Illustrative example
RankCandidateReactMust-haveTypeScriptMust-haveDesign systemsImportantTestingNice-to-haveRecommendation
#1
Ava BennettFrontend engineer, 6 years
✓✓✓✓Highly Recommended
#2
Mateo AlvarezSenior developer
✓✓✗✓Recommended
#3
Hana SatoUI engineer
✓?✓✗Recommended
#4
Jonas WeberFull-stack developer
✓✗✓✓Not Recommended
Design systems counts, but missing it does not sink a strong candidate.

An assessment of every criterion, with the reason.

Pass, fail or unknown, each with the reasoning written out. Then a summary and an overall recommendation you can check line by line.

84

Hana Sato

UI engineer · 4 of 6 criteria met
Recommended
✓ReactMust-have

Six years of React across two product teams; owns the booking flow.

?TypeScriptMust-have

The CV lists JavaScript and Flow but does not mention TypeScript. Worth asking.

✓Design systemsImportant

Led the move to a shared component library used by three teams.

✓AccessibilityNice-to-have

Ran a WCAG 2.1 audit and fixed the findings on the patient portal.

✗TestingNice-to-have

No automated testing mentioned in any role.

✓EU work permitMust-have

Based in Lisbon with EU citizenship.

?

Unknown means the CV does not say.

When there is no evidence either way, Rycuta marks it unknown instead of guessing. You see exactly what to ask in the interview.

✗

Fails are explained too.

A fail says what was missing, so a person can overrule it with context the CV does not hold.

Senior Frontend Engineer

Applicants, newest first
64
Arjun MehtaApplied via the public page
Not RecommendedScreened
93
Chloé DuboisApplied via the public page
Highly RecommendedScreened
88
Leo MartinApplied via the public page
RecommendedScreened

Screening starts as they apply.

With auto-screen on, screening starts automatically when an application arrives through your public page. Each one is assessed against the role's criteria, then joins the ranked list.

  • On by default, per postingOne switch in the posting's options.
  • Your uploads, on your scheduleCVs you add yourself are screened when you choose to screen them.
  • Re-screen in bulkChanged the criteria? Select applicants and re-screen them together.

Same criteria, every applicant.

Everyone who applies to a role is assessed against the same criteria, one CV at a time. Nobody is measured against a different list.

1Job description4 requirements

We are hiring a frontend engineer with 5+ years of React, strong TypeScript, and experience building design systems. You care about accessibility and ship with tests.

2Proposed criteria4 proposed

Proposed from the description. Select one to trace it to every applicant.

3Every CV, assessed4 assessed
Against TypeScript
AB
Ava BennettTypeScript in every role since 2019, in strict mode.
✓Pass
MA
Mateo AlvarezMoved a large JavaScript codebase to TypeScript.
✓Pass
HS
Hana SatoLists JavaScript and Flow, but doesn't mention TypeScript.
?Unknown
JW
Jonas WeberDescribes TypeScript as a skill still being learned.
✗Fail
Sample data
ComingCriteria history: see exactly which version of the criteria each score was made with.