Candidate Selection Process Configuration: Phases That Fit Your Hiring

The candidate selection process, the phases and states a candidate moves through, is the spine of Oracle Recruiting Cloud. Get it aligned to how your teams genuinely hire and the system feels natural. Force everyone through a generic template and recruiters will find workarounds that corrupt your data within a month.

Map phases to real hiring stages

Screen, assess, interview, offer, these should reflect your actual funnel, including the industry-specific bits. A high-volume retail hire and an executive search do not follow the same path, and one selection process rarely serves both well. Consider separate processes by requisition type.

Automate movement where it's safe

Some transitions can be automated: a candidate who fails a knockout question moves to rejected, a completed assessment advances the state. Others need human judgement. Configure automation for the mechanical steps and leave the judgement calls to people. Over-automating selection is how good candidates get binned by a rule.

Design the rejection reasons deliberately

Rejection reasons feed your reporting and your compliance position. A vague set gives you useless analytics and a weak audit trail. A well-designed set tells you why candidates fall out and where the funnel leaks.

Real scenario: a client ran every role through one 9-stage process, including seasonal warehouse hires who needed three stages. Recruiters were skipping stages manually, which broke reporting and slowed everything. We built a lean process for high-volume roles and kept the detailed one for professional hires. Data quality recovered and recruiters stopped fighting the system.