Requirements and priorities

Every requirement has a priority. The priority decides how much the requirement counts and whether missing it matters.

Keep must-haves few

Three to six must-haves is usually right. If everything is a must-have, nearly every candidate is "missing" something and the ranking loses its meaning.

How a requirement is found in a CV

• Skills are matched through the skills dictionary, which knows common spellings — React.js, ReactJS and React are the same skill.
• Related skills count for half: a Laravel developer is credited with PHP.
• Years are measured from the dates of roles that used the skill, overlapping jobs counted once.
• Education is compared by level, so a Master's meets a Bachelor's requirement.

Met, partial and missing

Each candidate's must-have table shows one of three results, with the evidence from the CV:

• Met — clearly shown.
• Partial — present but short of the requirement, for example two years against three.
• Missing — no evidence found.

A CV can describe a skill in words the engine does not recognise. Missing means not found, which is why HireMind asks for a human review instead of rejecting.

Changing requirements later

Edit the job and save. HireMind marks the ranking as out of date and offers Re-score, which recalculates every candidate from the stored CVs.