Skip to main content

​
Overview

Resume review always runs when a job has requirements. What’s configurable is whether failing the review prevents the candidate from being contacted, and what counts as failing. When resume screening is on, an applicant who fails any one of the three failure modes below moves to Resume Rejected. When it’s off, the star rating and requirement matches still display — they just don’t prevent outreach.

​
Failure modes

When resume screening is on, any of these will move an applicant to Resume Rejected: All three are independent. A candidate only needs to fail one to be rejected. Failed required requirements — and 0-star ratings, which mean the AI found a disqualifying mismatch — replace the star rating with a red Missing Requirement badge. Ratings of 1–4 stars below the minimum star threshold use the greyed-out star treatment. Radius failure is its own separate badge.

​
How candidate location is resolved

When the radius filter is enabled, the system tries to establish a candidate location in this order:
  1. From the ATS — the location attached to the candidate record in your ATS.
  2. From the resume — if the ATS location is missing or doesn’t pass the radius, the resume is parsed for a location.
If no location is determined for a candidate, the candidate will be marked as RESUME_REJECTED.

​
Applicants vs sourced candidates

Resume review behaves differently depending on how the candidate arrived at the job:
  • Applicants (entered from your ATS) go through full resume review when they enter the job. Any of the three failure modes above can move them to Resume Rejected. Rejected applicants can receive a resume feedback email with a candidate-facing details page where they can request a re-review.
  • Sourced candidates (added to the job by a recruiter — via the Sourcing tab, a tearsheet, manual upload, or any other in-product flow) bypass applicant-side resume screening. Adding the candidate is itself an expression of recruiter intent to interview, so resume review does not block them regardless of star rating or requirement matches. The exception is Auto-match sourcing, where the configured minimum star rating and requirement gating still control which candidates the system auto-adds.

​
Settings reference

Org-level defaults can be overridden per job. When a job sets its own value, that value fully replaces the org default for that job.

​
Resume requirements are independent of sourcing requirements

By design, a job carries two separate sets of requirements: the resume-review set documented on this page, and the sourcing set used to search your candidate database. They are independent in both directions:
  • Editing one set never changes the other. Adding, removing, or rewording a resume requirement leaves sourcing untouched, and vice versa.
  • The same requirement can carry different importance in each set — for example “CDL Class A” can be Required for resume review while being only a nice-to-have signal in sourcing.
This is intentional: screening an inbound applicant and searching a database are different jobs, and they usually deserve different bars. See Sourcing vs Resume Requirements for how to steer each set from a template.

​
What happens after rejection

A candidate who does not pass resume screening sits in the Resume Rejected stage. From there:
  • If resume feedback emails are enabled, the candidate receives a feedback email pointing to a candidate-facing details page showing the requirements they did not meet (the star rating is not shown). They can submit additional context through the Request Review form.
  • A recruiter can click Progress to Interview on the candidate (or use the bulk action when multiple are selected) to override the rejection and move them into outreach immediately. Any queued rejection or resume-feedback email is cancelled.
For the email-side behavior, see Outreach → Other automated touches.