Role Matching
A percentage
that earns its place.
Rook scores every candidate against the roles you selected. Timeline logic, must have skills, and trajectory. Strengths, gaps, and the reasons underneath each number.
- Eight years shipping iOS, latest role at a B2C at scale
- Deep Swift Concurrency and SwiftUI, with open source proof
- Led a migration from UIKit in a team of six
- Limited Android exposure, role is iOS only so acceptable
- Has not managed reports for the last two years
How the number is built
Math you can defend.
A match score is only useful if you know what it read. Rook shows the math on every profile.
Timeline logic
Rook checks overlap, gaps, title inflation and depth. A title is not a skill until the time behind it adds up.
Must haves and nice to haves
Tag the skills that are non negotiable. Nice to haves add to the score without blocking it.
Trajectory, not just rank
Rook reads the arc, not just the latest title. A fast riser beats a flat senior on a role that needs one.
Multi role scoring
One candidate, many jobs. Rook scores against every role they could fit, not just the one they applied to.
Strengths, in a list
The three reasons to say yes, pulled from the resume, the links, and the social signals.
Gaps, honest
What is missing, what is thin, what to probe. Plainly stated, not buried.
In the profile
The number, and the reasons.
Open any candidate. The match sits at the top, next to the score. Strengths and gaps stack below, each tied to the resume line or the public source that earned them.
- Percentage shown on every card and list
- Strengths and gaps on the profile, cited
- Editable weights per role when you need them
- Eight years shipping iOS, latest role at a B2C at scale
- Deep Swift Concurrency and SwiftUI, with open source proof
- Led a migration from UIKit in a team of six
- Limited Android exposure, role is iOS only so acceptable
- Has not managed reports for the last two years
FAQ