How scoring works
- Your job description sets the criteria. Huzuri turns it into a short list with weights, such as React and TypeScript 30%, three or more years 20%, shipped products 25%. The weights are visible, so everyone knows what a score means.
- Every CV gets a score per criterion: yes, no or not sure for a must-have, a level for a skill, or “not in the CV” when it isn’t mentioned. A “not sure” is left for a person to check.
- Developers get a GitHub check. When a CV links a GitHub profile, Huzuri looks at the public repositories and recent activity and scores that too.
- You decide. Shortlist from the ranked list, book the interviews, read each interviewer’s feedback, then make the offer or reject. Nothing is rejected automatically.
What it reads
PDF and Word files, uploaded from your computer. Contact details are pulled out of each CV, so you can reach the shortlist from the same screen.
Fair by construction
The criteria come from the job description you wrote, the weights are visible, and every criterion shows its answer, with “not sure” where the CV is unclear. A score is an argument you can check, not a verdict.
Where CVs are kept
On Oracle Cloud in Mumbai, India, with the rest of your Huzuri data, visible to the people on your team who run hiring under the same role rules as the rest of Huzuri.