Candidate Stage

Last updated

Definition

A candidate stage is one defined step in a hiring process, such as Applied, Phone screen, Interview, Offer, or Hired. Each application sits in one stage at a time, and every move between stages is timestamped in the applicant tracking system. Those timestamps produce conversion rates and time-in-stage metrics.

How candidate stages work

Stages turn a hiring process into data. When a recruiter moves an application from Phone screen to Interview, the applicant tracking system logs the date and the person who moved it. Rejections are logged the same way, ideally with a reason. Each stage should have a clear entry rule and one owner.

StageEntry ruleTypical owner
AppliedApplication receivedSystem
Resume reviewRecruiter has opened the applicationRecruiter
Phone screenScreen scheduledRecruiter
InterviewPassed screen, panel scheduledHiring manager
OfferHire decision made, offer being preparedRecruiter
HiredOffer acceptedRecruiter

Most teams keep a standard stage set for all roles and add role-specific stages only where the process really differs, for example a work sample for engineering or a background check for regulated jobs. A standard set is what makes reports comparable across departments.

Two metrics come straight from stages. Conversion rate is the share of applications that move from one stage to the next. Time in stage is how long applications wait in each stage. Together they show where a process loses good candidates and where it stalls.

Example

Illustration: a sales team fills six account-executive roles in a quarter. Across the quarter the ATS shows:

StageApplicationsConversion to next stageMedian days in stage
Applied90015% (135)4
Phone screen13540% (54)3
Interview5422% (12)11
Offer1250% (6)5
Hired6n/an/a

Two numbers stand out. Applications wait a median of 11 days in the interview stage, the longest by far, so panel scheduling is the bottleneck. And only half of offers are accepted, which points to pay or speed problems at the end. Overall, 6 hires from 900 applicants is a 0.67% yield, so filling the same six roles next quarter needs about 900 applicants again unless conversion improves.

Related terms

Common mistakes

  • Stages that describe activity, not status. "Chatting" or "In progress" can mean anything. Name stages after a verifiable event.
  • Recruiters batch-updating stages. If stages are moved in bulk on Friday, time-in-stage data is wrong. Update when the event happens, or let scheduling integrations move them.
  • Different stage names per department. "Onsite" in one team and "Final round" in another can't be compared in a report. Standardize names.
  • No rejection reasons. Without reasons, a low conversion rate tells you where candidates drop but not why.
  • Leaving stale applications open. Applications that sit in a stage for months inflate pipeline counts and hurt candidate experience. Set an auto-reminder or close rule.

How many candidate stages should a hiring process have?

Five to seven covers most roles: applied, review, screen, interview, offer and hired, plus a stage for any assessment the role needs. More stages add tracking work without adding much insight.

What is a good stage conversion rate?

It depends on the role and the source of applicants, so compare against your own history. A sudden fall in one stage, such as screen-to-interview, is more useful than any external benchmark.

Related

Where Candidate Stage fits in your HR stack