Criteria tell Nova what evidence matters for a role. Good criteria make scores useful because they turn a hiring team’s priorities into clear, resume-verifiable screening requirements. Nova generates a first draft using these best practices, so you do not need to start from a blank page or become a criteria expert. Your main job is to add the hiring context Nova cannot infer from the job description, then review whether the draft matches how your team wants to screen.Documentation Index
Fetch the complete documentation index at: https://nova.dweet.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Criteria are configured per job. You need at least one criterion before Nova can score candidates.
What Criteria Should Do
Good criteria are:- Specific to the role: They reflect the actual job, not generic traits.
- Verifiable: Nova can check them from a resume or application answer.
- Flexible where appropriate: Equivalent tools, domains, or backgrounds can count when the role allows them.
- Focused: A typical role works best with 5-8 high-signal criteria.
- Separated by importance: Must have, Preferred, and Nice to have mean different things.
How Setup Works
From the Jobs page, click Add Criteria or Edit Criteria.Add role context
Include intake notes, hiring manager priorities, non-negotiables, flexibility, deal-breakers, target backgrounds, or application questions that matter. Nova uses this context to draft criteria for you.
Confirm priorities
Before the first draft, Nova asks setup questions to confirm priorities, flexibility, deal-breakers, and trade-offs that would change the criteria. It skips questions already answered clearly by the job description, intake notes, or existing application questions.
Review the criteria
Check the generated criteria, importance levels, and wording. Most roles only need light edits: tighten anything too broad, soften anything too strict, and remove duplicated or hard-to-verify criteria.
Importance Levels
| Level | Use it for | How it affects scoring |
|---|---|---|
| Must have | Requirements the role cannot work without. | A clear contradiction is a serious concern. Missing evidence creates important uncertainty. |
| Preferred | Strong differentiators that improve confidence. | Helps separate strong candidates from acceptable ones. |
| Nice to have | Bonus signals. | Adds context, but should not drive the score by itself. |
Writing Useful Criteria
Write criteria around evidence Nova can actually see.| Weak | Better |
|---|---|
| Strong communicator | Has led customer-facing discovery, demos, or stakeholder presentations |
| Startup mindset | Experience working in early-stage or high-ownership product environments |
| Good culture fit | Evidence of cross-functional collaboration in product, engineering, or customer teams |
| Knows Python | Backend development experience with Python or a similar production language |
| Senior enough | Has owned technical design or delivery for complex projects |
Requirements That Need Application Answers
Some requirements are important but hard to verify from a resume. Examples:- Work authorization.
- Required licenses or certifications.
- Location or onsite availability.
- Travel requirements.
- Willingness to work specific shifts.
- Specific required experience that is not usually visible on a resume.
If a requirement cannot be verified from a resume or application answer, it usually should not be a scoring criterion. Keep it for interview evaluation instead.
Deal-Breakers And Exclusions
Use normal Must have criteria for direct eligibility requirements, such asActive RN registration or Right to work in the UK.
Use exclusion wording only for objective, verifiable boundaries that are genuinely required for the role. Prefer neutral wording, such as:
Exclude candidates whose experience is only academic research, with no production engineering work.Exclude candidates who do not hold the required active license.Exclude candidates who cannot meet a stated location, shift, or work-authorization requirement.
Testing On Sample Candidates
Before starting scoring, test the criteria on a small set of real candidates when possible. Look for:- Candidates you expected to review scoring below 7.
- Candidates with limited relevant evidence scoring above 8.
- One criterion driving too many concerns.
- Repeated
Partialresults caused by unclear wording. - Must have criteria that should be Preferred.
Editing Criteria
All edits save automatically:- Edit text: Click a criterion and update the wording.
- Change importance: Use the importance dropdown.
- Delete: Remove criteria that are duplicated, vague, or no longer relevant.
- Add new: Add a missing requirement.
- Add from library: Reuse company-approved criteria across jobs.
- Refine with Nova: Select criteria, describe the change you want, then approve or reject the proposed edits.
Criteria Library
Save reusable criteria to the company library when the same requirement applies across roles. Good library candidates:- Work authorization requirements.
- Location or hybrid work requirements.
- Role-family requirements that repeat across jobs.
- Company-specific eligibility rules.
Reprocessing After Changes
Criteria changes apply to future scores. Existing scores are not automatically recalculated. If reprocessing is enabled for your workspace, a Nova admin can use Reprocess Applications from the job actions menu when you want previous candidates scored against the updated criteria.Best Practices
- Keep the final list to 5-8 high-signal criteria for most jobs.
- Use Must have sparingly.
- Prefer capabilities over brand names or vendor names unless the exact one is required.
- Split compound requirements when one part could pass and another could fail.
- Remove duplicated criteria so the same gap is not counted twice.
- Avoid school prestige, employer prestige, geography, or background proxies unless they are clearly tied to the role. See Bias Testing Methodology for how Nova checks scoring patterns.
- Test on sample candidates before launch for high-volume or high-stakes roles.
How many criteria should I set?
How many criteria should I set?
5-8 works well for most jobs. Sparse roles may need fewer. More criteria only help when each one adds a distinct screening signal.
How specific should criteria be?
How specific should criteria be?
Specific enough to verify, broad enough to allow equivalent evidence. “Backend development with Python, Go, or similar production languages” is usually better than “5 years of Python at a Series B company.”
Can I weight criteria differently?
Can I weight criteria differently?
There is no separate numeric weighting setup. Use Must have, Preferred, and Nice to have to show importance.
What if I change criteria mid-search?
What if I change criteria mid-search?
Changes apply to future scores. If reprocessing is enabled for your workspace, a Nova admin can use Reprocess Applications to update existing candidates.
Should I include interview-only traits?
Should I include interview-only traits?
No. If Nova cannot verify the trait from a resume or application answer, keep it for interviews instead of scoring.
Understanding Scores
Read and interpret Nova assessments
Enabling Nova
Start scoring on your job postings