Oracle Recruiting Cloud —
100 Interview Questions & Answers

Oracle Recruiting Cloud (ORC) is Oracle's native talent acquisition module embedded within Oracle HCM Cloud. It provides end-to-end recruitment functionality from job requisition creation through to new hire onboarding hand-off — all on the same platform as Core HR, Payroll, and Talent Management.

• Single Data Model: Because ORC shares the same data model as Oracle Core HR, candidate-to-employee conversion is seamless — no integration required between ATS and HRMS
• Unified Workforce Structures: Departments, Jobs, Locations, Business Units, and Grade structures defined in Core HR are directly used in ORC requisitions without duplication
• Key Modules: Job Requisitions, Candidate Management, Candidate Pools, Job Offers, Career Sites, Interview Scheduling, Sourcing, Background Check Integration, and Onboarding hand-off
• Replaced product: ORC replaced Taleo Recruit for cloud customers; Oracle continues to invest in ORC as the go-forward cloud recruiting product

• Recruiter: Manages requisitions end-to-end — sources candidates, manages applications, schedules interviews, extends offers
• Hiring Manager: Raises requisition requests, reviews candidates, participates in interview evaluation, approves offers
• Recruiting Manager: Oversees team's requisitions, runs reports, manages workload assignment across recruiters
• Candidate: External or internal candidate who applies via Career Site or internal job board
• Recruiting Administrator: Configures ORC settings — pipeline phases, offer approval flows, career site branding, prescreening questions
• Interview Panelist: Participates in structured interview panels and submits interview feedback via questionnaires

These are two distinct objects in Oracle Recruiting Cloud:

• Job Requisition: The internal hiring request document that captures the business need — job title, grade, department, headcount, budget, hiring team, approval chain. It is the master record for the hiring process and is not visible to candidates
• Job Posting: The external (or internal) advertisement derived from the requisition. It contains the candidate-facing description, requirements, and apply instructions. One requisition can have multiple postings — e.g., one for external candidates and one for internal employees

The candidate pipeline is the structured workflow that tracks a candidate's progress through the hiring process. Oracle delivers standard phases that organisations can configure:

• New: Candidate has applied or been added to the requisition but not yet reviewed
• Review: Recruiter is screening the application — reviewing resume, prescreening answers
• Preselect: Shortlisting phase; candidates may be sent a questionnaire or phone screen
• Interview: Candidate is progressed to structured interview rounds
• Offer: Compensation and offer details are prepared and extended
• HR: Final pre-hire checks (background check, reference checks)
• Hire: Candidate is converted to a new hire / pending worker in Oracle Core HR

Each phase can have custom sub-states (e.g., Interview — Round 1, Interview — Round 2). Administrators configure the pipeline phases in Setup and Maintenance → Manage Recruiting Candidate Selection Process.

A Candidate Selection Process (CSP) defines the pipeline phases and states that candidates move through for a given requisition type. It is the backbone of how hiring workflows are structured in ORC.

• Configuration path: Setup and Maintenance → Manage Candidate Selection Process
• Phases and States: Each CSP contains ordered phases (e.g., Application, Assessment, Interview, Offer). Each phase has states (e.g., Under Review, Pending, Completed)
• Actions: Each state can trigger actions — send notification, move to next phase, require questionnaire completion
• Assignment to Requisitions: A CSP is linked to requisition templates or specific requisition types (e.g., Professional, Executive, Hourly)
• Required vs Optional States: States can be marked mandatory — the recruiter cannot skip them without completing defined criteria

• Requisition Title & Number: Auto-generated number; title describes the role
• Job Family & Job Function: Classification hierarchy that drives candidate matching and reporting
• Position: Optionally linked to a position from Oracle Core HR for headcount control
• Business Unit, Department, Location: Workforce structure attributes from Core HR
• Grade and Salary Range: Drives offer letter defaults and compensation benchmarking
• Primary Recruiter and Hiring Manager: Members of the hiring team responsible for the process
• Target Start Date and Number of Openings: Hiring timeline and headcount volume
• Requisition Type: Professional, Hourly, Executive, Contingent — drives which CSP and approval flow is used
• Prescreening Questionnaire: Linked questionnaire to filter applicants on apply

ORC uses Oracle Approvals Management (AME) or the built-in Recruiting Approval Configuration to route requisitions for approval before they go live.

• Approval Rules: Configured in Setup and Maintenance → Manage Approval Rules for Recruiting. Rules evaluate requisition attributes (Business Unit, Grade, Requisition Type, Salary Range) to determine the approver chain
• Approval Chain Types: Position hierarchy, Supervisory hierarchy, or Static approval lists
• Parallel vs Sequential: Multiple approvers can be configured in parallel (all must approve) or sequential (one after another)
• Delegation and Proxy: Approvers can delegate to colleagues during absence. Proxy access allows admins to act on behalf of approvers
• Notifications: BPM workflow sends email notifications and in-app bell notifications to approvers at each step
• Approval Actions: Approve, Reject (sends back to initiator), or Request Information (suspends until response)

A Requisition Template is a pre-configured requisition used as a starting point for frequently hired roles. It reduces data entry errors and ensures consistency.

• Contains pre-filled fields: Job Title, Department, Grade, Prescreening Questionnaire, Candidate Selection Process, Interview Questionnaire
• Recruiters select a template when creating a new requisition — all template fields are auto-populated and can be overridden
• Managed via Recruiting → Configuration → Requisition Templates
• Templates can be restricted by Business Unit or Location so recruiters only see relevant templates

When Oracle Core HR is configured to use Position Management, ORC can enforce that a requisition must reference an approved, funded position before it can be opened.

• Position Lookup: On the requisition, the recruiter selects a Position from Core HR. The position carries pre-defined attributes (Job, Grade, Department, Location) which auto-populate the requisition
• Headcount Validation: If the position's approved headcount is already fully filled, ORC can warn or prevent the requisition from being submitted
• Budget Integration: When Oracle Workforce Budgeting is enabled, ORC checks position budgets against the workforce budget before allowing a hire
• Position Override: Administrators can allow exceptions for over-hiring with appropriate approvals in the workflow

Multi-level conditional approval routing in ORC is configured through Recruiting Approval Rules in Setup and Maintenance:

• Condition Attributes: Define conditions using requisition fields — e.g., IF Requisition Type = Executive AND Grade ≥ 15 THEN route to CHRO first
• Rule Priority: Assign numeric priority to rules — lower number = higher priority. The first matching rule wins
• Approver Types: Use Job Role (dynamic — resolves to the person holding that role), User (static), or Position Hierarchy level (dynamic)
• Chaining Rules: Multiple rules can chain — Rule 1 triggers Line Manager approval; Rule 2 triggers Finance approval above a salary threshold; both rules apply simultaneously in parallel
• Bypassing Rules: Configure an "Auto-Approve" rule for low-risk requisitions (e.g., back-fill of Grade 5 role in same department) to avoid bottlenecks

A Candidate Profile is the central record of a candidate in Oracle Recruiting Cloud. It serves as the talent record that persists across multiple applications.

• Personal Details: Name, contact information, address, work authorization status
• Work Experience: Employment history with dates, titles, and descriptions
• Education: Degrees, institutions, fields of study, graduation dates
• Skills & Certifications: Competencies and professional qualifications
• Attachments: Resume/CV documents and cover letters
• Application History: All past and current applications across requisitions
• Source: Where the candidate originated — career site, LinkedIn, agency, referral
• Compliance Data: EEO/OFCCP data (for US customers) captured separately with data privacy controls

ORC has built-in duplicate detection to prevent multiple profiles for the same individual:

• Duplicate Detection on Apply: When a candidate registers, ORC checks for existing records using email address as the primary unique key. If a match is found, the candidate is prompted to log in rather than create a new profile
• Merge Functionality: Administrators can merge duplicate candidate records via Recruiting → Candidate Profiles → Merge. The master record is retained; duplicate application history is consolidated
• Internal vs External: An existing Oracle HCM employee applying through the internal career site is linked to their Person record — no duplicate profile is created
• Social Login: Candidates using LinkedIn or Google Sign-In are matched by the authenticated email, reducing duplicate creation

• External Candidate: Someone outside the organisation applying via the public-facing career site. They create a standalone candidate profile. Not yet an employee in Oracle HCM
• Internal Candidate: A current employee or contingent worker applying via the internal career site. They authenticate with their Oracle HCM credentials. Their application is linked to their existing Person record, so the recruiter can see their current role, grade, and tenure
• Internal Mobility: ORC supports configured internal job boards visible only to employees. Certain jobs can be designated "Internal Only" or "Internal First" before going external
• Referrals: Employees can refer external candidates via ORC's referral functionality — the referring employee is tracked against the candidate's source record

Candidate Pools are talent pipelines where recruiters group candidates who are not yet linked to a specific open requisition but are of interest for future hiring.

• Use Cases: Silver-medal candidates from past hiring; pipeline building for anticipated future roles; graduate/intern talent pools; executive succession pipelines
• Pool Creation: Recruiters create pools via Recruiting → Candidate Pools → Create Pool. Pools have owners and can be shared across the recruiting team
• Adding to Pool: Candidates are added manually, from applications, via sourcing campaigns, or through Candidate Pool subscriptions (candidates self-register interest)
• Pool Phases: Pools have their own phases (e.g., Prospect → Engaged → Ready to Hire) — configurable similarly to CSPs
• Moving to Requisition: When a requisition opens, pool members can be moved directly into the requisition pipeline with one click

Oracle Recruiting Cloud uses Oracle's embedded AI/ML capabilities to rank and match candidates to requisitions:

• Job Requisition Matching Score: ORC scores each applicant against the requisition's job profile using NLP analysis of the candidate's work experience, skills, and education versus the requisition's requirements
• Similar Candidate Suggestion: When a recruiter shortlists a candidate, ORC suggests similar profiles from the candidate pool or other active applications based on profile vectors
• Best Candidates: The Best Candidates tab on a requisition surfaces the top-ranked applicants, saving recruiters from reviewing all applications manually
• Prescreening Integration: AI scores are combined with prescreening questionnaire results and knockout question outcomes to produce a composite ranking
• Bias Mitigation: Oracle's AI model is designed to match on skills and experience, not on demographic attributes — EEO data is kept in a separate compliant data store

• Step 1 — Move to Offer Phase: Progress the candidate to the Offer phase in the candidate pipeline
• Step 2 — Create Offer: Click Create Offer. Enter compensation details (salary, bonus, allowances), start date, legal employer, and any additional offer components
• Step 3 — Offer Approval: Submit the offer for approval. The configured approval chain reviews and approves/rejects the offer amount
• Step 4 — Generate Offer Letter: Once approved, generate the BI Publisher-based offer letter PDF. The letter auto-populates candidate name, role, salary, and start date from the offer record
• Step 5 — Extend Offer: Send the offer to the candidate via email with a link to view and accept/decline through the candidate self-service portal
• Step 6 — Candidate Acceptance: Candidate accepts online. ORC records the acceptance date and electronic signature

Offer Letters in ORC are generated using BI Publisher (BIP) templates linked to ORC's offer data model:

• Data Model: ORC delivers the RecruitingOfferLetterDataModel in the BI Catalog containing all offer attributes — candidate name, job title, salary, start date, legal employer, manager
• Template Design: Download the standard RTF template from BI Catalog → Edit in Microsoft Word with BI Publisher Desktop Add-in → Add company branding, conditional clauses (e.g., part-time vs full-time language), and custom fields
• Upload Template: Upload the customised RTF back to the BI Catalog report. Set language and territory for multi-lingual support
• Link to ORC: In Setup and Maintenance → Manage Offer Letter Templates, link the BI Publisher layout to an ORC offer letter template. Map templates by requisition type or business unit
• Testing: Generate a test offer in ORC for a test candidate and review the PDF output for correct field population

After offer acceptance, the candidate transitions from the ATS into Oracle Core HR as a new hire:

• Move to HR Phase: Recruiter moves the candidate to the HR phase. This triggers any pre-employment processes (background check integration, reference checks)
• Initiate Hire: Recruiter clicks Initiate Hire. The offer data (start date, job, grade, department, salary) pre-populates the Core HR Hire flow, eliminating re-keying
• HR Completes Hire: HR Administrator completes the hire in Oracle Core HR — confirming work relationship, assignment details, bank account, and payroll information
• Onboarding Trigger: On the hire date (or configurable days before), Oracle Onboarding tasks are automatically assigned to the new hire and their manager
• Requisition Update: Once all openings are filled, the requisition status changes to Filled or Closed automatically

• Grade Rate Linkage: In Oracle Compensation, define Grade Rates with salary range (minimum, midpoint, maximum) for each grade. ORC reads these rates and displays the range when the recruiter enters offer salary
• Compa-Ratio Warning: ORC can be configured to warn or block offers above the grade maximum. Configure via Recruiting Settings → Offer Salary Validation
• Approval Escalation: In Recruiting Approval Rules, add a condition: IF Offer Salary > Grade Maximum THEN add VP Compensation as additional approver
• Offer Components: Configure additional offer components (signing bonus, car allowance, relocation) with their own validation rules and approval triggers
• Audit Trail: All offer changes and approval decisions are logged in the offer history — useful for pay equity audits and compliance reviews

• The offer status changes to Declined and the recruiter receives a notification
• The recruiter can record the decline reason (compensation, another offer, personal reasons) for reporting purposes
• The candidate's pipeline state returns to a pre-offer phase so the recruiter can either renegotiate or progress the next candidate
• A revised offer can be created and submitted through approval again if the organisation wishes to counter
• Declined offer reasons feed into standard ORC analytics reports to help identify pattern issues in compensation competitiveness

A Career Site is the candidate-facing web portal where external (or internal) candidates can search for and apply to open positions.

• An organisation can configure multiple career sites — one per brand, business unit, country, or candidate type
• Common configurations: one external site, one internal employee site; or one site per subsidiary brand
• Each site has its own URL, branding (logo, colours, imagery), language settings, and displayed job postings
• Configured via Recruiting → Configuration → Career Sites
• Job postings are selectively published to specific career sites based on requisition attributes or manual selection

• Site Builder: ORC provides a no-code Career Site Builder (drag-and-drop page editor) for branding and layout customisation
• Branding Options: Upload logo, set primary/secondary colours, configure hero banner images, add custom text blocks and video embeds
• Pages: Home page, Job Search page, Job Details page, Application Flow pages — each can be individually designed
• Custom Domains: The career site can be mapped to a custom domain (e.g., careers.yourcompany.com) via DNS configuration and SSL setup in ORC settings
• SEO Settings: Configure meta titles and descriptions for job postings to improve search engine visibility
• Accessibility: ORC career sites are designed to WCAG 2.1 AA standards — ensure custom imagery and text meet contrast ratio requirements

Prescreening questions are embedded in the application flow to assess candidate suitability before a recruiter reviews the application:

• Prescreening Questions: Open-ended or multiple-choice questions asking about experience, availability, certifications, or salary expectations. Answers are scored and contribute to the candidate's overall ranking
• Knockout Questions: Binary (Yes/No) questions for mandatory requirements. If a candidate answers incorrectly (e.g., "No" to "Do you have a valid UK work permit?"), they are immediately disqualified and the system shows a rejection message
• Question Library: Questions are maintained in a central library in Recruiting Configuration → Prescreening Questions and reused across requisitions
• Scoring: Prescreening scores are combined with AI matching scores to produce the Overall Score visible to recruiters in the pipeline

• Full Apply: Candidate completes a full application with profile creation, resume upload, prescreening questions, and EEO/OFCCP data (where applicable)
• Express Apply: Simplified 2-3 step apply flow — ideal for high-volume hourly roles. Captures minimal data upfront; full profile built over time
• LinkedIn Easy Apply: Candidates apply using their LinkedIn profile, which maps to ORC candidate profile fields
• Resume Parsing: ORC automatically parses uploaded resumes to pre-fill work experience, education, and skills fields
• Apply with Social Login: Google or LinkedIn SSO for profile creation, reducing registration friction

• Privacy Statement: Configure a Privacy Statement in Recruiting → Configuration → Privacy Statements. Link it to the career site — candidates must accept before creating a profile or applying
• Consent Versioning: When the privacy statement is updated, ORC prompts returning candidates to re-accept the new version on next login
• Data Retention Rules: Configure automatic purging of candidate data after a defined period of inactivity (e.g., delete candidate profiles inactive for 24 months) via Recruiting Settings → Candidate Data Retention
• Right to Erasure: Administrators can manually delete a candidate's personal data on request via Candidate Profile → Delete. This anonymises the record while retaining aggregate statistics
• EEO Data Separation: US diversity (EEO/OFCCP) data is stored separately from the application record and is not visible to recruiters or hiring managers during the selection process
• Cookie Consent: Use OneTrust or a similar CMP integrated with the career site domain to manage cookie consent banners per jurisdiction

• Career Site: Primary organic sourcing via the branded career site with SEO-optimised job postings
• Job Boards: Automated posting to Indeed, LinkedIn, Glassdoor, and other boards via Oracle's job distribution integrations (e.g., Broadbean, Multiposting)
• LinkedIn Recruiter Integration: Bi-directional integration with LinkedIn Recruiter — source candidates directly from LinkedIn into ORC pipelines via LinkedIn Recruiter System Connect (RSC)
• Employee Referrals: Built-in employee referral programme — employees share job links with unique referral tracking codes; referred candidates are automatically tagged
• Agency Portal: External recruitment agencies submit candidates through a dedicated secure agency portal
• Talent Community / Candidate Pools: Proactive sourcing from the organisation's own talent pipeline
• Social Sharing: Recruiters and employees can share job postings on LinkedIn, Twitter/X, and Facebook directly from ORC

The Agency Portal is a secure external-facing interface where approved third-party recruitment agencies can submit candidates for requisitions they have been engaged on:

• Agency Registration: Agencies are registered in ORC as external users with Agency role. They access the portal via a separate URL (not the candidate career site)
• Requisition Assignment: Recruiters explicitly share requisitions with specific agencies — agencies can only see and submit against requisitions assigned to them
• Candidate Submission: Agency users upload candidate CVs and enter candidate details. Submitted candidates appear in the recruiter's pipeline tagged with the agency source
• Terms & Fees: Fee arrangements and terms can be tracked against agency submissions for invoicing reconciliation
• Submission Tracking: Recruiters can see all agency submissions per requisition and track their progress, preventing duplicate submissions from multiple agencies

Source tracking records where each candidate originated from, enabling cost-per-hire and source effectiveness analysis:

• Automatic Source Tracking: ORC captures UTM parameters on career site URLs — job boards, campaigns, and social shares can have unique tracking links (e.g., ?src=linkedin_organic)
• Source Categories: Pre-defined source categories include Job Board, Employee Referral, Agency, Social Media, Career Site, Direct, Campus. Recruiters can also manually set/override source on a candidate profile
• Source in Reporting: Source data feeds into OTBI Subject Area Recruiting — Candidate Applications Real Time, enabling recruiters and HR to report on hire rate by source, cost per source, and time to fill by source
• ROI Analysis: Source tracking enables recruiters to identify which channels produce the most hired candidates versus cost, informing recruitment marketing budget decisions

• Prerequisites: Active LinkedIn Recruiter contract with RSC entitlement; Oracle HCM Cloud administrator access
• Step 1 — Enable RSC in ORC: In Recruiting Settings → LinkedIn RSC, enable the integration and generate the ATS Integration Token
• Step 2 — Configure in LinkedIn: In LinkedIn Recruiter Admin settings, navigate to ATS Integration → Add ATS. Select Oracle Recruiting Cloud and enter the ATS Integration Token
• Step 3 — Job Sync: Configure which ORC job postings sync to LinkedIn Recruiter — typically all active external postings. RSC syncs jobs every few hours
• Step 4 — InMail Sync: With RSC, InMail messages sent to candidates in LinkedIn Recruiter sync back to ORC candidate timeline, maintaining a single record of candidate interactions
• Step 5 — Apply Tracking: Candidates who apply via LinkedIn Easy Apply are tracked back to LinkedIn as the source automatically

• Employees access the internal career site and click Share on any eligible job posting to generate a unique referral link
• When a candidate applies using that link, their application is automatically tagged with the referring employee's details
• Recruiters can see the referral source on each candidate's profile and communicate the referral status back to the referring employee
• ORC does not natively manage cash referral bonuses — these are typically handled separately in Payroll or Compensation. However, ORC provides the referral tracking data needed to trigger those processes
• Referral eligibility rules (e.g., which jobs are eligible for referral, which employee levels can refer) are configurable in Recruiting Settings → Referral Program

• Schedule Interview Action: From the candidate record, the recruiter clicks Schedule Interview, selects interviewers from the hiring team, picks a time slot, and sends calendar invites
• Calendar Integration: ORC integrates with Microsoft Outlook/Exchange and Google Calendar to show interviewer availability in real time when scheduling
• Candidate Self-Scheduling: ORC supports a self-scheduling workflow where the candidate is sent a link to pick from available time slots, reducing back-and-forth scheduling
• Interview Types: Phone, Video (integrated with MS Teams, Zoom, or Oracle Video Interview), On-Site
• Notifications: Automatic email confirmations and calendar invites sent to candidate and interviewers. Reminders sent 24 hours before the interview

Interview Questionnaires are structured evaluation forms completed by interviewers after each interview, ensuring consistent and legally defensible hiring decisions:

• Configuration: Created in Recruiting Configuration → Interview Questionnaires. Each questionnaire contains questions with rating scales (e.g., 1–5 star) or text feedback fields
• Competency Linkage: Questions can be linked to Oracle Competencies from the Profile Management library, enabling structured competency-based evaluation
• Assignment: Questionnaires are assigned at the requisition level (one per interview round) or within the CSP configuration
• Completion: After the interview, interviewers receive a notification to complete their evaluation. Responses are captured in ORC and visible to the recruiter and hiring manager
• Aggregate View: The recruiter sees a consolidated evaluation summary comparing all interviewers' ratings for a candidate side-by-side

• ORC Assessment Integration Framework: Oracle provides a standard REST-based integration framework for connecting assessment vendors (e.g., SHL, Korn Ferry, Mercer Mettl, HireVue)
• Trigger: When a candidate reaches a configured pipeline phase, ORC automatically sends an assessment invitation to the vendor via REST API
• Results Callback: Upon completion, the vendor sends results back to ORC via REST. Scores appear on the candidate profile under the Assessments tab
• Score in Ranking: Assessment scores are factored into the candidate's Overall Score alongside prescreening and AI matching scores
• Configuration: In Recruiting Configuration → Assessment Partners, register the vendor's endpoint URL and authentication credentials

• MS Teams Integration: Enabled via Oracle's native Microsoft 365 integration. In HCM Settings, connect the Oracle tenant to the Microsoft 365 tenant using OAuth. Once connected, interview links automatically generate as Teams meeting links
• Zoom Integration: Similar OAuth-based connection in HCM Settings → Video Conferencing. Zoom meeting links are auto-generated when video interviews are scheduled
• HireVue (Async Video): Configure via the Assessment Integration Framework. When a candidate reaches the Video Interview phase, ORC triggers a HireVue invitation. The candidate records responses asynchronously. Results and video links come back to ORC for recruiter review
• Calendar Sync: Ensure Microsoft Exchange Web Services (EWS) or Google Workspace API is configured so interviewer free/busy availability is visible when scheduling
• Testing: Create a test requisition and test candidate to validate the full flow — scheduling → invite generation → candidate experience → results sync

• ORC integrates with background screening vendors (e.g., Sterling, HireRight, Checkr) via a REST-based integration
• Background check is typically triggered when the candidate moves to the HR phase of the pipeline (post-offer acceptance)
• ORC sends candidate personal details to the vendor's API. The candidate receives an email inviting them to complete consent and provide additional data directly with the vendor
• Results (Clear, Consider, Suspended) are returned to ORC and visible on the candidate's HR phase record
• The recruiter or HR administrator can then proceed with the hire (if Clear) or handle exceptions for Consider/Suspended results per company policy

ORC configuration is primarily done in Setup and Maintenance under the Recruiting functional area:

• Manage Recruiting Settings: Global on/off switches for features — referrals, agency portal, prescreening, AI matching, social apply
• Manage Candidate Selection Process: Configure pipeline phases and states
• Manage Requisition Templates: Create and manage default requisition templates
• Manage Offer Letter Templates: Link BI Publisher layouts to ORC offer templates
• Manage Career Sites: Create and configure career sites
• Manage Interview Questionnaires: Create structured evaluation forms
• Manage Prescreening Questions: Build the question library
• Manage Approval Rules for Recruiting: Configure requisition and offer approval chains

• Notification Templates: ORC uses Oracle Alerts (Alert Composer) and built-in email templates. Access via Recruiting Configuration → Notifications
• Trigger Events: Notifications are triggered by pipeline state changes — e.g., application received, moved to interview, offer extended, rejected
• Candidate Notifications: Automatic acknowledgement emails on application, status update emails when progressed or rejected, offer delivery emails
• Recruiter/Manager Notifications: New application received, approval pending, offer accepted/declined, background check result returned
• Template Customisation: Email templates support merge fields for candidate name, job title, recruiter name, and company name. Templates are managed in Oracle Alerts Composer
• SMS Notifications: ORC supports SMS via third-party SMS gateway integrations for mobile-first candidate communication

Lookups are configurable lists of values used to populate dropdown fields throughout ORC. They are managed in Setup and Maintenance → Manage Common Lookups filtered by the ORC module.

• Key ORC Lookups: Rejection Reasons (ORA_IRC_REJECTION_REASON), Withdraw Reasons (ORA_IRC_WITHDRAW_REASON), Sourcing Channels (ORA_IRC_SOURCE_MEDIUM), Decline Offer Reasons (ORA_IRC_DECLINE_REASON)
• Extensible Lookups: Most ORC lookups are extensible — you can add new values without Oracle SR. User-defined values are tagged as System Access = USER
• Effective Dating: Lookup values can be date-effective — set an end date to retire obsolete values without deleting historical data
• Translation: Lookup values support translations for multi-language career site deployments

• Purpose: DFFs allow organisations to capture additional data on ORC objects (Requisitions, Candidate Applications, Job Offers) that are not part of the standard data model
• Configuration Path: Setup and Maintenance → Manage Descriptive Flexfields → search for Recruiting objects (e.g., IRC_REQUISITIONS, IRC_SUBMISSIONS)
• Segment Types: Global segments (always shown) or Context-sensitive segments (shown based on a context value — e.g., show different fields for Professional vs Hourly requisitions)
• Value Sets: Attach value sets to restrict input — dropdown lists, number ranges, or validated lookups
• Deploy: After configuring, click Deploy Flexfield to publish changes. Requires a page refresh for users
• Reporting: DFF values are available in OTBI Subject Areas and can be included in custom analyses

Oracle Recruiting Booster is an add-on module for Oracle Recruiting Cloud designed for high-volume, hourly, and event-based hiring:

• Use Case: Retail, logistics, healthcare, hospitality — industries needing to hire hundreds of candidates quickly with minimal recruiter effort
• Key Differentiators: Conversational AI / chatbot-driven apply flow; automated screening via SMS/messaging; virtual hiring events; interview self-scheduling at scale
• Chatbot Integration: ORC Booster includes an AI conversational assistant that guides candidates through the application and pre-screening via SMS or web chat — no recruiter involvement required for initial screening
• Event Hiring: Create hiring events (job fairs, campus days) where candidates register and are auto-scheduled for interview slots
• Licensing: Recruiting Booster is separately licensed from standard ORC. Standard ORC is required as the base platform

• Recruiting — Candidate Applications Real Time: Application volumes, pipeline status, candidate source, time in stage, prescreening scores
• Recruiting — Requisitions Real Time: Open/filled/cancelled requisitions, time to fill, cost per hire, hiring team details
• Recruiting — Job Offers Real Time: Offer status, accepted/declined rates, offer salary vs grade range, approval cycle time
• Recruiting — Interviews Real Time: Interview completion rates, interviewer feedback scores, no-show rates
• Recruiting — Candidate Pools Real Time: Pool membership, engagement rates, pipeline conversion
• Workforce Management — New Hires: Post-hire data once candidates are converted to employees — for time-to-productivity and source-of-hire analysis

• /hcmRestApi/resources/latest/recruitingCEJobRequisitions — Read and manage job requisitions
• /hcmRestApi/resources/latest/recruitingCEJobApplications — Manage candidate applications and pipeline movements
• /hcmRestApi/resources/latest/recruitingCECandidates — Read and create candidate profiles
• /hcmRestApi/resources/latest/recruitingJobOffers — Manage offer creation and status
• /hcmRestApi/resources/latest/recruitingJobPostings — Publish and manage job postings
• Use Cases: Pushing candidates from a third-party ATS or sourcing tool into ORC; automating requisition creation from a Workforce Planning tool; reading offer data into a Compensation analytics platform

• Data Store: In HCM Extracts, the Recruiting data stores include Candidate Application, Requisition, and Offer record groups. Navigate to Data Exchange → HCM Extracts → Create Extract
• Record Groups: Add the Candidate Application record group as the driving record. Add child record groups for Work Experience, Education, Prescreening Responses, and Offer Details
• Filter Criteria: Apply extract criteria — e.g., Application Status = Hired AND Last Updated Date > Extract Last Run Date for incremental extracts
• Delivery: Configure SFTP delivery in the extract's Delivery Options. Map the output file format (CSV or XML) to the target system's expected schema
• Scheduling: Schedule via ESS Scheduled Processes (daily, weekly, or triggered by event)
• Monitoring: Check extract job results in Data Exchange → Extract Process Results. Validate record counts against expected volumes

• Open Requisitions Report: All active requisitions with age, stage, and recruiter assignment
• Pipeline Summary Report: Candidates per stage per requisition — gives a funnel view
• Time to Fill Report: Average days from requisition open to hire by department, recruiter, or job family
• Source Effectiveness Report: Applications, interviews, offers, and hires by source channel
• Offer Acceptance Rate: Offers extended vs accepted vs declined, with decline reason breakdown
• EEO / Diversity Report: For US customers, OFCCP-compliant applicant flow log by race/gender/veteran status
• Recruiter Activity Dashboard: Per-recruiter metrics — requisitions managed, candidates progressed, offers extended, time to fill

• ATOM Feed Trigger: Oracle HCM publishes ATOM feeds for business events. The Recruiting "New Hire" event fires when a candidate is converted to an employee
• OIC Subscription: In OIC, create an integration with the Oracle HCM Cloud Adapter as the trigger. Subscribe to the Worker — New Hire Completed ATOM feed event
• Payload Mapping: Map the hire event payload (employee name, start date, job, department, location) to the target system's schema (e.g., IT provisioning system, Payroll vendor API)
• Error Handling: Configure OIC error handling to retry failed deliveries and alert the integration admin on persistent failures
• Authentication: Use OAuth 2.0 client credentials for HCM Cloud adapter authentication in OIC. Store credentials in OIC Connections as secure properties

• Delivered Roles: ORC ships with predefined job roles — Recruiter, Recruiting Manager, Hiring Manager, Recruiting Administrator, Agency User
• Recruiter Data Security: By default, recruiters only see requisitions and candidates where they are named as Primary Recruiter or Collaborator. Configure Recruiting Access Management profiles to expand or restrict this access
• Hiring Manager Access: Hiring Managers see only their own requisitions and the candidates in their pipeline phases. Configure via the Hiring Team membership on each requisition
• Sensitive Data: EEO/diversity data is secured separately. Only users with the View EEO Data privilege can access this — typically restricted to HR Compliance roles
• Aggregate Access: Recruiting Managers and HRBPs can be given access to all requisitions in their Business Unit or Department via Recruiting Management Hierarchy profiles
• Custom Roles: Use Security Console to copy delivered roles and create custom variants with adjusted function security privileges for unique business requirements

• Check Questionnaire Assignment: Verify the prescreening questionnaire is linked to the requisition under the Prescreening section. If using a template, check if the template has the questionnaire pre-assigned
• Questionnaire Status: Confirm the questionnaire itself is in Active status in Recruiting Configuration → Prescreening Questions
• Career Site Configuration: In the Career Site settings, confirm that the Enable Prescreening toggle is switched ON for the relevant site
• CSP Phase: Prescreening questions appear during apply if the CSP has prescreening configured as part of the Application phase. Check the CSP definition
• Candidate Already Applied: If the candidate previously applied to a different requisition using the same profile, the system may not re-display already-answered questions. Check the candidate's existing questionnaire responses
• Apply Flow Configuration: If using Express Apply, prescreening may be suppressed in the simplified flow. Switch to Full Apply and test

• Multiple Career Sites: Create separate career sites per country/language — e.g., one for UK (English), one for France (French), one for Germany (German)
• Language Settings: Each career site has a primary language and can support multiple display languages. Candidates select their preferred language from the site header
• Translated Content: Job posting descriptions must be entered in each required language. ORC supports per-language job description entry on each posting
• Translated Lookups: Rejection reasons, decline reasons, and other lookup values must be translated via Manage Common Lookups → Translation
• Translated Questionnaires: Prescreening questionnaire text needs translation entries for each configured language
• Legal Employer Mapping: Each country's requisitions should be linked to the correct Legal Employer to ensure offer letters, compliance data, and hire processing use the correct legal entity
• Privacy Statements: Country-specific GDPR/privacy statements must be configured and linked to the relevant career sites

• Supported HDL Objects: Oracle supports loading of Candidate Profiles (PersonProfile), and limited historical application data into ORC via HCM Data Loader. Full application pipeline history loading is limited — Oracle's recommendation is to load candidate profiles and use ORC APIs for application records
• Candidate Profile Load: Use HDL TalentProfile and PersonProfile business objects to load candidate work experience, education, and skills from legacy ATS exports
• API-Based Application Load: Use the ORC REST API endpoint /recruitingCEJobApplications to programmatically create application records for migrated candidates against migrated requisitions
• Sequencing: Always load in order — 1) Candidate Profiles → 2) Requisitions (if loading historical reqs) → 3) Applications → 4) Pipeline phase updates
• Data Cleansing: Legacy ATS data often has duplicate candidates and inconsistent source codes — cleanse before loading to avoid polluting the ORC candidate database

Key recruiting metrics and how to build them in OTBI:

• Time to Fill: Days from Requisition Open Date to Hire Date. OTBI: Requisitions SA → Requisition Open Date and Hire Date columns → calculated measure using TIMESTAMPDIFF
• Time to Hire: Days from Application Date to Hire Date. Applications SA → Application Create Date and Offer Acceptance Date
• Offer Acceptance Rate: Offers Accepted / Offers Extended × 100. Offers SA → count of accepted vs total offers
• Source Efficiency: Hires by Source / Applications by Source. Applications SA filtered to Hired status, broken by Source Medium dimension
• Pipeline Conversion Rate: Candidates advancing from each stage / candidates entering the stage. Applications SA → stage transition counts
• Requisition Age: Days since requisition was opened for all currently Open requisitions — identifies stale requisitions needing escalation
• Diversity Metrics: Applications, shortlists, and hires by gender and ethnicity (EEO SA — US only, restricted access) to monitor pipeline diversity

The Hiring Team is the group of people who collaborate on a requisition. Members can be added by the recruiter or hiring manager when creating or editing a requisition.

• Primary Recruiter: Owns the requisition and manages the pipeline — required field
• Recruiter Collaborators: Additional recruiters who can access and work on the requisition
• Hiring Manager: The business leader requesting the hire — required field
• Hiring Manager Collaborators: Additional managers who can view and action the pipeline (e.g., skip-level manager)
• Interviewers: Added when scheduling interviews; automatically get read access to the candidate profile during the interview phase
• Access to a requisition and its candidates is governed by hiring team membership — non-members cannot see the requisition by default

• Reject: Initiated by the recruiter or hiring manager. The organisation decides not to proceed with the candidate. A rejection reason is recorded and an optional rejection notification email can be sent to the candidate
• Withdraw: Initiated by the candidate themselves — they remove their own application. A withdraw reason can be captured (e.g., accepted another offer, personal reasons)
• Impact: Both actions move the candidate out of the active pipeline but the candidate profile and application record are retained for reporting and compliance purposes
• Re-consider: A rejected candidate can be un-rejected and moved back into the active pipeline if the recruiter decides to reconsider — this action is tracked in the audit history

• Internal Mobility in ORC allows existing employees to search and apply for internal job openings through the internal career site
• Internal Career Site: A separate career site (or a toggle on the main site) is configured for internal candidates — accessible after Oracle HCM authentication
• Job Posting Visibility: Postings can be set as Internal Only, External Only, or Both. Internal-only jobs are not visible on the public career site
• Employee Profile Pre-fill: When an employee applies internally, their current HR profile (current role, tenure, grade, competencies) auto-populates the application — reducing friction
• Manager Notification: Configurable whether the current manager is notified when their direct report applies internally. Some organisations suppress this notification to avoid retaliation concerns
• Talent Review Integration: High-potential employees flagged in Oracle Talent Review can be proactively surfaced to recruiters for internal roles

• OTBI (Oracle Transactional Business Intelligence): Real-time, self-service reporting tool. Recruiters and managers build ad-hoc analyses from current ORC data. Best for operational reporting — today's pipeline, open requisitions, current offer status
• Oracle Fusion Analytics Warehouse (FAW) — Recruiting Analytics: A pre-built analytics cloud product with a dedicated data warehouse. Provides pre-built KPI dashboards, trend analysis, and predictive insights for recruiting. Data is loaded from ORC into FAW on a configurable schedule (typically daily)
• Key FAW Advantage: Historical trending and benchmarking — FAW stores snapshots over time, enabling year-on-year comparison of time to fill, hire rates, and source mix. OTBI only shows current state
• When to use which: OTBI for daily operational queries; FAW for strategic workforce analytics and executive dashboards

• Contingent Workers (contractors, temps, consultants) can be sourced and tracked through ORC using a separate Contingent Worker requisition type
• The offer and hire flow for contingent workers differs from employees — they are onboarded as Contingent Worker work relationships in Oracle Core HR rather than Employee relationships
• Statement of Work (SOW) details (contract start/end dates, billing rate, vendor) are captured in the requisition and offer for contingent roles
• Integration with Vendor Management Systems (VMS) like Fieldglass or Beeline is common for organisations with large contingent workforces — ORC handles the requisition and approval; the VMS handles vendor sourcing

• Enable Position Management: In Core HR, enable Position Management for the relevant Business Units or the entire enterprise in Enterprise HCM Information
• Position Required on Requisition: In Recruiting Settings, enable the Require Position on Requisition option — recruiters cannot save a requisition without selecting a valid position
• Position Vacancy Check: Configure ORC to display a warning or hard stop if the selected position has no remaining headcount (all FTE slots filled)
• Auto-populate from Position: When a position is selected on the requisition, configure ORC to auto-fill Grade, Job, Department, Location, and Legal Employer from the position record, reducing data entry errors
• Budget Integration: Link Oracle Workforce Budgeting to enforce that positions must have approved budget before requisitions can be submitted for approval

• Check Data Model Output: Run the BI Publisher Data Model in Report Builder → View Data to see the raw XML being passed to the template. Identify which fields are null in the data model output
• Verify Offer Record Completeness: Check the offer in ORC for the candidate — are all required fields (Start Date, Grade, Legal Employer, Salary) populated? Empty offer fields produce blank placeholders
• Template Field Names: Open the RTF template in Word with BI Publisher Desktop. Verify that field codes like <?FIRST_NAME?> exactly match the field names in the data model — case-sensitive
• Data Model Parameter Mapping: Check the data model's bind parameters — ensure the Offer ID parameter is being passed correctly when the letter is generated
• Run in Preview Mode: Use BI Publisher's View Report with a test offer ID to isolate whether the issue is template or data model
• Check Character Set: Non-ASCII characters (e.g., accented characters in Indian or European names) may cause RTF parsing issues — ensure the template is saved with UTF-8 encoding

• A Job Profile (managed in Oracle Profile Management) defines the required competencies, skills, qualifications, and responsibilities for a specific job
• In ORC, a job profile linked to the Job on a requisition provides the AI matching engine with structured criteria to score candidates against
• When creating a requisition, the recruiter can pull in the job profile requirements to auto-populate the job description sections and required skills
• Well-maintained job profiles improve the quality of AI candidate matching scores — requisitions with minimal or generic job profiles produce less useful matching results
• Job Profiles are maintained in My Client Groups → Profiles → Job Profiles by HR or the Recruiting team

• The requisition status changes to Closed or Cancelled
• All active job postings linked to the requisition are automatically taken down from career sites and job boards
• Candidates still in active pipeline stages receive rejection notifications (if configured) — the system can auto-reject all remaining active candidates on close
• The requisition and all associated application data is retained for reporting and compliance purposes — it is never deleted
• A closed requisition can be re-opened if approved — useful when a hire falls through after offer acceptance
• Filled vs Cancelled: Filled = all openings hired. Cancelled = requisition withdrawn before filling (budget cut, reorg)

• Recruiting Events in ORC support structured hiring events — campus job fairs, open days, virtual hiring events, and graduate assessment centres
• Event Creation: Create an event in Recruiting → Events → Create Event. Define event name, date, location, interview slots, and linked requisitions
• Candidate Registration: The event is published to the career site. Candidates register and self-schedule interview slots
• Bulk Pipeline Processing: After the event, recruiters can batch-move all attending candidates to a specific pipeline phase (e.g., Interview Complete) in a single action
• Event Reporting: Track registration rates, attendance, interview completion, and subsequent hire rates per event in OTBI
• Available as standard in ORC; expanded functionality available with Recruiting Booster for high-volume event hiring

• Campus Requisition Type: Configure a dedicated Candidate Selection Process (CSP) for campus/graduate hiring with phases like Application Review → Assessment → Group Interview → Individual Interview → Offer
• Candidate Pools: Create a Graduate Talent Pool to nurture campus candidates throughout the year, moving them to active requisitions when intake opens
• Recruiting Events: Campus events (career fairs, on-campus assessment days) are managed via the Events feature
• Offer Management: Graduate offer letters often differ from experienced-hire letters — configure a dedicated offer template with internship/graduate-specific terms
• Onboarding Integration: Graduate joiners often have longer onboarding — trigger Oracle Onboarding checklist tasks well in advance of start date (typically 4–6 weeks prior)

• Enable OFCCP: In Recruiting Settings, enable the OFCCP compliance features. This activates the separate EEO data collection flow on the application
• EEO Questionnaire: ORC displays an optional self-identification form (race/ethnicity, gender, veteran status, disability) separately from the application — candidates cannot be required to answer, and responses are not visible to recruiters
• Applicant Flow Log: ORC automatically maintains an Applicant Flow Log per requisition, recording each candidate's progression through selection stages — required for OFCCP desk audits
• Disposition Codes: Configure standardised disposition codes for each rejection reason — OFCCP requires that all non-selected applicants have a documented, non-discriminatory reason for rejection
• Internet Applicant Definition: Configure the OFCCP Internet Applicant definition — only candidates who meet all four criteria (expression of interest, qualifications, consideration, unwithdraw) count as official OFCCP applicants
• EEO Reports: Run the delivered OFCCP reports in BI Publisher for annual AAP (Affirmative Action Plan) reporting

• ORC includes the ability to send candidate satisfaction surveys at key points in the hiring journey (application submitted, interview completed, offer received, rejection)
• Survey responses capture candidate feedback on the process — communication quality, interview experience, and overall impression of the organisation
• Results are aggregated into a Candidate Experience score/dashboard visible to Recruiting Managers
• The surveys are configured via Recruiting Configuration → Candidate Experience Surveys and linked to pipeline phase transitions
• Candidate experience data helps identify bottlenecks (e.g., slow communication, poor interview scheduling) impacting employer brand and offer acceptance rates

• After a candidate is hired in ORC and the hire action is completed in Oracle Core HR, Oracle Onboarding (OO) is automatically triggered
• Oracle Onboarding is a separate Oracle HCM module that manages pre-boarding and onboarding tasks — form completion, policy acknowledgements, IT requests, buddy assignments
• The handoff from ORC to Onboarding is seamless — no data re-entry needed since both modules share the same Oracle HCM data model
• Onboarding checklists can be triggered by hire date or a configurable number of days before start date (pre-boarding)
• New hires complete onboarding tasks via the Oracle HCM Cloud self-service interface or Oracle Journeys (a modern guided experience layer)

• ORC auto-generates requisition numbers using a configurable sequence. Navigate to Setup and Maintenance → Manage Recruiting Settings → Requisition Numbering
• Prefix: Configure a text prefix (e.g., REQ-, ORC-24-) to make requisition numbers identifiable and year-specific
• Sequence: Define the starting number and increment (typically 1). ORC increments sequentially for each new requisition
• Format: Define zero-padding (e.g., REQ-00001 vs REQ-1) and maximum digits
• Once a requisition number is generated, it cannot be manually overridden — this ensures uniqueness and auditability across all requisitions
• Multi-country organisations sometimes use a country code prefix per Legal Employer to make requisitions identifiable by geography

• Phase 1 — Assessment: Document current Taleo configuration — requisition types, CSPs, approval flows, career site structure, integrations, reports. Map to ORC equivalents
• Phase 2 — Configuration: Build ORC configuration in sandbox — CSPs, career sites, offer templates, approval rules, prescreening questions, interview questionnaires
• Phase 3 — Integration Re-platforming: Re-build Taleo integrations (job board feeds, background check, assessment) on ORC's integration framework
• Phase 4 — Data Migration: Extract active candidate profiles from Taleo and load into ORC via HCM Data Loader or REST API. Agree with business on historical data migration scope
• Phase 5 — UAT: End-to-end testing by recruiters, hiring managers, and candidate journey testing on the new career site
• Phase 6 — Cutover: Redirect DNS from Taleo career site URL to ORC career site URL. Drain in-flight Taleo requisitions before cutover or handle parallel operations during transition
• Phase 7 — Hypercare: 4–6 week intensive post-go-live support period with Recruiting admins and functional leads on standby

• The Candidate Timeline (Activity Feed) on the candidate profile records a chronological log of all significant events and interactions
• Events logged include: application submitted, stage transitions, interview scheduled/completed, offer created/extended/accepted/declined, notes added, emails sent, recruiter comments
• Recruiters and hiring managers can add manual notes directly to the timeline — useful for recording phone call outcomes or verbal feedback
• The timeline is the single source of truth for the candidate's engagement history, supporting compliance requirements and enabling knowledge transfer when requisitions change hands between recruiters
• LinkedIn RSC InMail messages (if integrated) also sync to the timeline

• Attachments in ORC include candidate resumes/CVs, cover letters, portfolio documents, and compliance documents (e.g., right to work evidence)
• Accepted Formats: Configure accepted file types in Recruiting Settings — typically PDF, DOC, DOCX. Restrict executable files for security
• File Size Limits: Oracle HCM has attachment size limits (typically 10MB per file). Advise candidates on optimal file size in the career site guidance text
• Virus Scanning: Oracle HCM Cloud scans uploaded attachments for malware automatically
• GDPR Consideration: Attachments are personal data. The data retention purge policy must cover attachment deletion when candidate profiles are purged
• Recruiter Attachments: Recruiters can also upload internal documents (e.g., background check results, reference letters) to the candidate profile — these are separate from candidate-submitted attachments

Scenario: Automatic requisition creation from an approved Workforce Plan in a third-party system.

• Trigger: When a Workforce Planning tool (e.g., Anaplan, OneModel) approves a new headcount request, it calls ORC's REST API to create the requisition automatically
• API Call: POST to /hcmRestApi/resources/latest/recruitingCEJobRequisitions with payload containing job title, department, grade, location, number of openings, target start date, and hiring manager ID
• Authentication: Use OAuth 2.0 Client Credentials flow — the WFP tool authenticates with a service account's client ID and secret to obtain a bearer token
• Response Handling: ORC returns the created requisition ID. The WFP tool stores this ID to enable status tracking via subsequent GET calls
• Approval Trigger: If the requisition needs approval, the API call can also submit it for approval (set status to Pending Approval) in the same call
• Benefit: Eliminates recruiter manual data entry, ensures requisition data matches workforce plan exactly, and reduces time from approved headcount to open requisition by 1–2 days

• Oracle Journeys is Oracle's guided employee experience layer — a configurable checklist/task management experience designed for key employee lifecycle moments
• In the context of recruiting, Journeys is used for pre-boarding and onboarding: when a candidate is hired, a Journey is automatically assigned containing all new joiner tasks
• Journey Tasks: Can include Oracle HCM transactions (complete personal details, enrol in benefits), third-party links (complete background check, e-sign offer letter), learning courses, and document uploads
• Manager Journeys: A parallel Journey can be assigned to the hiring manager — set up workstation, order equipment, plan day-one agenda
• Pre-boarding: Journeys can be triggered weeks before start date — giving new hires tasks like submitting bank details, completing tax forms, and watching welcome videos before they step in the office
• Journeys are configured in My Client Groups → Checklists → Journey Templates

• Job Offer (ORC): The formal offer of employment created and tracked within Oracle Recruiting Cloud. Contains compensation details, start date, job title, and forms the basis of the offer letter. It is a transactional record in the ATS
• Employment Contract (Oracle Core HR): The legal contract of employment managed in Oracle Core HR under the worker's assignment. It records contract type (permanent, fixed-term), contract duration, probation period, and notice period
• Linkage: When the hire is completed in Core HR, contract details are entered as part of the assignment. The ORC offer data (salary, start date, job) pre-populates the Core HR hire flow, but the employment contract is a separate HR record

• A re-hire is a former employee who applies through ORC as a new candidate
• ORC and Oracle Core HR have re-hire functionality — when the candidate is moved to the Hire phase, Core HR checks if a Person record already exists for the individual (matched by National ID or name/DOB)
• If a match is found, the recruiter is prompted to confirm this is a re-hire. The existing Person record is reactivated with a new Work Relationship rather than creating a duplicate person
• Previous employment history (tenure, role history) is preserved on the person record, which is important for benefits re-instatement and re-hire eligibility checks
• Configure Re-hire Eligibility rules in Core HR — certain employees may be flagged as ineligible for re-hire (e.g., terminated for cause). ORC can display a warning during the hire step if the person is re-hire ineligible

Design approach for a strategic TA leadership dashboard:

• Page 1 — Portfolio Overview: Total open requisitions by status (Pending Approval, Open, On Hold), total candidates in pipeline, requisitions by Business Unit heat map, monthly hires vs target
• Page 2 — Efficiency Metrics: Average time to fill by job family (bar chart), average time to fill trend over 12 months (line chart), pipeline conversion funnel (% progression per stage)
• Page 3 — Quality Metrics: Offer acceptance rate by recruiter, source-of-hire mix (pie chart with drill-through to individual hires), 90-day retention rate of new hires (cross-SA with Core HR)
• Page 4 — Team Performance: Per-recruiter scorecard — requisitions managed, open days average, candidates progressed, offers extended/accepted
• Filters: Global prompt filters for Date Range, Business Unit, Recruiter, and Requisition Type
• Delivery: Schedule the dashboard to email to the TA Head weekly as a PDF burst report using BI Publisher

• A Pending Worker is a person record created in Oracle Core HR before the employee's start date — typically when the offer is accepted and the start date is several weeks away
• Purpose: Allows IT provisioning (email, laptop, access cards) to be requested and ready on Day 1. Enables onboarding tasks and Journeys to begin before the start date
• The Pending Worker status means the person does not appear in active headcount, payroll, or HR operational reports until their start date
• Conversion: On the actual start date, the system automatically converts the Pending Worker to an active Employee work relationship
• Triggered from ORC's Initiate Hire action when the selected start date is in the future — a toggle lets the recruiter choose Pending Worker vs immediate hire

• Mobile-Responsive Career Site: ORC career sites are mobile-responsive — candidates can search, apply, and track applications from any smartphone browser
• Oracle HCM Mobile App (Recruiter): Recruiters can review candidates, progress pipeline stages, approve requisitions, and receive notifications via the Oracle HCM mobile app
• Hiring Manager Mobile: Hiring managers review candidate profiles, submit interview feedback, and approve offers from the mobile app
• Candidate Notifications: SMS and push notifications (where configured) keep candidates informed of status updates without needing to log in
• Recruiting Booster: Offers an advanced mobile-first candidate experience with conversational AI-driven apply via SMS for high-volume hourly roles

• Approval Delegation: Approvers can delegate their approval authority to a colleague during absence. Navigate to Settings → Manage Worklist → Delegation Rules in Oracle BPM Worklist
• Vacation Rules: In the BPM Worklist, approvers set a date range and delegate — all pending approval tasks are auto-reassigned to the delegatee during the period
• Proxy Access: HR Administrators can be granted proxy access to take approval actions on behalf of an approver in exceptional circumstances — set up via Security Console → Manage Proxy Access
• Escalation Rules: In Recruiting Approval rules, configure escalation — if an approver does not act within X days, automatically escalate to their supervisor
• Admin Override: The Recruiting Administrator role can manually reassign approval tasks from the Pending Approvals queue for cases where an approver is unreachable

• Salary Range Display: ORC supports displaying salary range on job postings. Enable in Recruiting Settings → Pay Transparency. The salary range on the job posting is populated from the Grade Rate linked to the requisition's grade
• Conditional Display: Configure by country or business unit — e.g., show salary range only for US job postings (where Colorado, New York, California laws require it) but not for UK or India postings
• Manual Override: Recruiters can manually enter a posting-specific salary range on the job posting if the grade rate does not reflect market positioning
• Grade Rate Maintenance: Ensure Oracle Compensation grade rates are maintained and current — stale grade ranges displayed on postings can create legal and pay equity risks
• Audit: Track which job postings displayed salary ranges via OTBI Requisitions subject area — useful for compliance documentation

• Job Requisition Template: Pre-fills internal requisition fields (Department, Grade, CSP, Hiring Team, Approval Chain) to speed up requisition creation for frequently hired roles. Not visible to candidates
• Job Posting Template: Pre-fills the external job posting content — job description text, required qualifications, benefits sections, company description boilerplate. Used to maintain consistent brand tone and formatting across postings for similar roles
• Both template types are managed separately in ORC configuration. A single requisition template can have a linked posting template so creating a requisition from a template also pre-populates the posting content

• Multi-language Career Sites: Build country-specific career sites in local languages with translated job descriptions and lookup values
• Data Privacy by Country: Different countries have different data privacy laws (GDPR, PDPA, LGPD) — configure country-specific privacy statements, consent mechanisms, and data retention rules
• Compliance Fields: Some countries require specific data collection (EEO for US, BBBEE for South Africa, Age/Gender self-ID for India) — configure country-specific prescreening and compliance questionnaires
• Legal Employer Mapping: Requisitions and offers must be linked to the correct Legal Employer for each country to ensure correct offer letter terms and hire processing
• Background Check Vendors: Use vendors with coverage in all hiring countries — validate that the ORC integration supports multi-country check types
• Time Zone Handling: Interview scheduling respects each user's time zone. Verify recruiter and candidate time zones are correctly set in user profiles
• Global vs Local CSPs: Decide whether to use one global CSP with optional phases or country-specific CSPs that reflect local hiring norms and notice periods

• Check CSP State Rules: Navigate to the CSP configuration and identify if the current state has mandatory completion criteria — e.g., an interview questionnaire must be submitted before moving to the Offer phase
• Interview Feedback Pending: A common blocker — one or more interviewers have not submitted their questionnaire. Identify and chase outstanding feedback, or waive the requirement if the CSP allows
• Prescreening Not Complete: If the phase requires prescreening completion, check whether the candidate's questionnaire answers have been saved. Sometimes technical errors during apply leave the questionnaire in an incomplete state — an admin can mark it complete
• Approval Pending: If the move to the next stage triggers an approval (e.g., moving to Offer), check the BPM Worklist for a pending approval task that has not been actioned
• Offer Not Approved: Candidate cannot be moved to HR phase until the offer is in Approved status — check the offer approval chain
• System Error: If none of the above, check the ESS Scheduled Process log for any background process errors. Raise an Oracle SR with the Application ID and error message if a system defect is suspected

• The Candidate Self-Service Portal is the authenticated area of the career site where candidates manage their own profile and track applications
• Candidates can update their personal details, work experience, and skills; upload a revised CV; and view the status of all active and past applications
• Offer acceptance, decline, and e-signature actions are completed by the candidate via the self-service portal — not via email alone
• Candidates access the portal via the career site login using their registered email/password or social login (Google, LinkedIn)
• The portal reduces recruiter admin — candidates self-serve status updates instead of emailing the recruiter for progress information

• Posting Audience: Each job posting has an audience setting — Internal (visible only on internal career site), External (public career site), or Both
• Internal-First Configuration: Create the initial posting as Internal only with a 2-week posting period. Create a second posting for External audience with a start date 2 weeks later — ORC will automatically publish the external posting on that date
• Automation: In the posting, set Internal Posting End Date and External Posting Start Date to automate the transition without recruiter intervention
• Job-Level Override: For senior or confidential roles, mark the requisition as Confidential — the job title is hidden from the career site listing even for internal employees until explicitly unblocked
• Business Rule Enforcement: Some organisations enforce internal posting as a policy — configure a CSP state or approval step that requires HR to confirm internal posting was live for X days before approving external posting

• Oracle's ORC AI matching algorithm is designed to match candidates on skills, experience, and qualifications — not on demographic attributes like name, age, gender, or race
• EEO/demographic data collected during apply is stored in a separate, restricted data store that is not accessible to the AI matching engine
• Oracle tests the matching model for adverse impact patterns and publishes model cards describing the training methodology and fairness testing approach
• Customers are responsible for ensuring their prescreening knockout questions and job requirements do not create unintentional adverse impact — Oracle recommends legal review of all screening criteria
• The AI matching score is a recommendation tool, not a decision engine — the final hiring decision always rests with the recruiter and hiring manager
• Oracle maintains compliance documentation for GDPR Article 22 (automated decision-making) — ORC AI is framed as decision support rather than automated decision-making

• Bulk Requisition Creation: Use HDL or REST API to bulk-create requisitions for all seasonal roles rather than manual creation — saves days of recruiter effort pre-campaign
• Express Apply Flow: Configure an Express Apply flow on the career site — 2-3 screens maximum. Remove non-essential fields to minimise candidate drop-off
• Knockout-Heavy Prescreening: Use knockout questions to auto-filter candidates who don't meet basic criteria (availability, location, minimum age) — auto-reject ineligible applications without recruiter review
• Bulk Actions: Train recruiters on ORC's bulk action capability — select 50 candidates at once and move them all to the Interview stage, or bulk-reject with one rejection reason
• Recruiting Booster: For very high volume (thousands of applications/day), deploy Recruiting Booster's SMS-driven chatbot screening and self-scheduling to handle initial pipeline stages without recruiter involvement
• Reporting: Create a live OTBI dashboard showing applications received per day vs target, so the TA team can adjust sourcing channels mid-campaign if volumes lag

• Taleo Connect Client (TCC) is a bulk data import/export tool for legacy Oracle Taleo Recruit — it is not used with Oracle Recruiting Cloud (ORC)
• ORC is a completely separate product from Taleo and uses its own integration framework — HCM Data Loader (for person/profile data), ORC REST APIs (for recruiting objects), and HCM Extracts (for outbound data)
• Customers migrating from Taleo to ORC must re-build any TCC-based integrations using ORC REST APIs or HCM Extracts
• Knowing this distinction is important in interviews — using "TCC" in the context of ORC indicates confusion between the two products

• Oracle Alert Composer (accessible via Tools → Alerts Composer) is used to customise ORC email and in-app notification templates
• ORC delivers pre-built alert templates for all key recruiting events (application received, stage changed, interview scheduled, offer extended, rejected)
• Administrators can modify the subject line, body text, and merge field tokens (e.g., {CandidateName}, {JobTitle}, {RecruiterEmail}) in each template
• Notification delivery channels: Email, In-App Bell notification, or both. SMS requires additional gateway configuration
• Disable vs Suppress: Individual alert types can be disabled if the organisation does not want certain notifications sent — e.g., suppressing automatic rejection emails for confidential roles where the hiring manager wants to make personal calls
• Language: Notification templates can be translated for multi-language deployments — the system sends the notification in the candidate's or user's preferred language

• Unit Testing: Test each configured component individually — CSP phase transitions, approval rule triggering, offer letter generation, prescreening scoring
• End-to-End (E2E) Scenario Testing: Run complete scenarios for each requisition type (Professional, Hourly, Executive, Internal) from requisition creation through to hire in Core HR
• Candidate Journey Testing: Use incognito browser sessions to test the full candidate experience on the career site — search, apply, questionnaire, confirmation email receipt
• Integration Testing: Validate each integration — job board feed, background check trigger/callback, LinkedIn RSC sync, calendar integration, OIC flows
• Security Testing: Log in as each key role (Recruiter, Hiring Manager, Recruiting Manager, Agency User) and validate correct access — can see their own requisitions, cannot see others' data
• Performance Testing: Simulate concurrent user load on the career site — especially important for high-volume roles with advertising campaigns driving traffic spikes
• Regression Testing: After each quarterly Oracle patch, run the E2E scenarios to catch any regression issues from the update

• ORC supports multi-location job postings — a single requisition can have postings that display multiple acceptable work locations for the role
• The primary location is set on the requisition for HR/payroll purposes; additional work locations can be listed on the posting for candidate visibility
• For roles that are department-agnostic (e.g., a central shared services function), the Department field can be left as the shared services department with a note in the job description about team placement
• Some organisations create one requisition per location/department for clean reporting and tracking, while others use a single requisition with multiple openings. The right approach depends on reporting granularity needs and approval flow requirements
• Remote/hybrid roles: A dedicated "Remote" location can be configured in Oracle Core HR's Location hierarchy and used on requisitions for fully remote roles

• Trigger: When a candidate is hired in ORC and the hire is completed in Oracle Core HR, an ATOM feed event fires for the new employee
• OIC Integration: Oracle Integration Cloud subscribes to the New Hire ATOM event. The OIC integration maps the new hire data (employee ID, job, department, start date) to the SuccessFactors API payload
• SuccessFactors API Call: OIC calls the SuccessFactors Learning OData API to create a User record and auto-assign the relevant onboarding learning curriculum based on the employee's Job Code or Department
• Error Handling: If the SuccessFactors API call fails, OIC logs the error and sends an alert email to the HR Systems team for manual intervention
• Reconciliation Report: Run a weekly comparison report of new hires in ORC vs Learning users in SuccessFactors to identify any missed assignments from integration failures
• Alternative: If OIC is not available, schedule a daily HCM Extract of new hires in SFTP file format and configure SuccessFactors Learning to SFTP-pull the file and auto-process user creation

• Talent Community: A self-service sign-up on the career site where prospective candidates express interest in the organisation and specific job categories — without applying for a specific open role. Candidates submit their profile and are added to the organisation's talent community
• Candidate Pools: Internal recruiter-curated lists of specific individuals that have been screened and are considered for future roles. Pools are built and managed by recruiters
• Key Difference: Talent Community is inbound and candidate-initiated; Candidate Pools are recruiter-managed and curated. Talent Community members can be invited to move to a Candidate Pool when a relevant role opens
• Communication: Organisations can send email campaigns to Talent Community members about new job openings in their areas of interest — a proactive sourcing strategy

• When the recruiter clicks Initiate Hire in ORC, the system launches the Add a Pending Worker or Hire an Employee flow in Oracle Core HR depending on the start date
• Future Start Date (Pending Worker): If the start date is in the future, ORC defaults to creating a Pending Worker. The person record exists in Core HR but the work relationship status is Pending until the start date
• Same-Day or Past Start Date (Active Employee): If the start date is today or in the past, the hire flow creates an active Employee work relationship immediately
• Automatic Activation: A scheduled process (Convert Pending Workers) runs nightly and automatically activates Pending Workers whose start date has been reached
• Payroll: Pending Workers are not included in payroll processing. The assignment is activated in payroll only once the person becomes an active employee

• Evergreen Requisition: A requisition kept permanently open to continuously collect applications for a role that is always hiring (e.g., call centre agents, warehouse operatives)
• Configuration: Set the requisition with a high number of openings (e.g., 999) so it never auto-closes when a hire is made. Set the posting with no end date so it remains live permanently
• Pipeline Management: Use CSP automation to auto-reject applicants who fail knockout questions immediately on apply, without recruiter review — keeping the pipeline clean in high-volume scenarios
• Batch Processing: Recruiters use ORC bulk actions to progress groups of candidates through stages simultaneously — interview scheduling in batches, bulk offers, bulk hires
• Child Requisitions: Some organisations create an evergreen "parent" pool requisition and then create specific "child" requisitions when a specific location or team needs to fill a slot — candidates from the parent pool are moved to the child requisition for the final offer/hire steps
• Reporting: Track evergreen requisition aging carefully — without a close date, these requisitions can accumulate thousands of applications. Set up monthly purge processes for old, unqualified applications per data retention policy

• Architecture: ORC is natively embedded in Oracle HCM Cloud (single data model); Taleo is a separate acquired product integrated via middleware — separate databases, separate security, separate UX
• Candidate-to-Employee Conversion: ORC converts candidates to employees within the same system with no data transfer; Taleo requires an integration to pass hire data to Oracle or SAP HCM
• User Experience: ORC has a modern, responsive UI aligned with Oracle HCM Cloud design language; Taleo has an older UI (though updated versions exist)
• AI Capabilities: ORC includes Oracle's embedded AI matching and candidate recommendations; Taleo has limited native AI
• Reporting: ORC uses OTBI/BI Publisher natively — same tool as all Oracle HCM reporting; Taleo has its own separate reporting module (Oracle Analytics for Taleo)
• Oracle's Direction: ORC is Oracle's strategic cloud ATS — ongoing investment; Taleo is in maintenance mode for existing on-premise/hosted customers

• Authentication: Obtain an OAuth 2.0 access token using Resource Owner Password Credentials or Client Credentials grant depending on the use case
• API Call: GET /hcmRestApi/resources/latest/recruitingCEJobRequisitions?fields=RequisitionId,Title,Status,PrimaryRecruiterId,OpenDate,NumberOfOpenings&limit=100
• Filtering: Use OData-style query parameters to filter — e.g., ?q=Status=OPEN to return only open requisitions; ?q=PrimaryRecruiterId=12345 to filter by recruiter
• Pagination: ORC REST uses limit/offset pagination. Implement a loop that fetches pages of 100 records until hasMore=false in the response
• Child Resource Queries: Expand child resources to get application counts — e.g., include expand=Applications to get candidate counts per requisition in one call
• Dashboard Build: Feed the API response JSON into your dashboard tool (Power BI, Tableau, custom React app). Refresh the data feed every 15–30 minutes for near-real-time visibility

• Oracle releases quarterly updates (February, May, August, November) to Oracle HCM Cloud, including ORC. The update is applied by Oracle automatically to production environments
• Preview Environment: Oracle provides a preview environment approximately 4 weeks before the production update. Use this to test the new release against your configuration
• Release Notes: Download the ORC-specific release notes from Oracle Support (My Oracle Support). Review new features, changed behaviours, and deprecated items
• Opt-In Features: Many new ORC features are delivered as opt-in (switched off by default). Review opt-in features and plan which to enable after testing
• Regression Testing: Run end-to-end test scripts in the preview environment covering all configured CSPs, approval flows, offer letter generation, integrations, and career site flows
• Change Communication: Communicate significant UI or process changes to recruiters and hiring managers before the production update goes live — avoid surprises

• Oracle Sourcing (formerly known as Oracle Taleo Sourcing / Sourcing Cloud) is a separate Oracle product focused on candidate marketing and attraction — not to be confused with "sourcing" as an activity within ORC
• Oracle Sourcing provides landing page builder for job campaigns, employee referral programme management, talent community management, social media job distribution, and candidate relationship marketing (CRM)
• It integrates with ORC — candidates sourced via Oracle Sourcing campaigns are pushed into ORC as candidates, with the sourcing campaign tracked as the source
• Not all ORC customers use Oracle Sourcing — many use ORC's built-in sourcing features (career site, referrals, LinkedIn) without the separate Sourcing module
• In an interview, distinguish clearly between Oracle Sourcing (the product) and sourcing activities (the function) to demonstrate product knowledge depth

• Enable Integration: In ORC Recruiting Settings, navigate to Background Checks and select Sterling as the vendor. Enter the Sterling API credentials (API Key, Client ID) provided by Sterling
• Package Mapping: Map Sterling screening package codes to ORC requisition types or job levels — e.g., Executive roles use a comprehensive package; Hourly roles use a basic package
• Trigger Configuration: Configure which CSP phase/state triggers the background check initiation — typically the HR phase post-offer acceptance
• Candidate Consent: Sterling's API sends a consent invitation email to the candidate. Ensure the invitation email text and sender address align with your employer branding
• Results Callback: Sterling sends results back via webhook to ORC. Verify the webhook URL registered in Sterling matches ORC's callback endpoint. Check firewall rules allow Sterling's IP range to reach Oracle HCM Cloud
• Testing: Use Sterling's sandbox environment with test candidate data. Trigger a background check on a test candidate in ORC UAT, verify the invitation is sent, simulate a result (Clear / Consider), and verify the result appears correctly on the ORC candidate profile

ORC data is stored in Oracle HCM's underlying schema. Key entities and their relationships:

• IRC_REQUISITIONS: Master requisition record — contains requisition ID, title, status, dates, workforce structure attributes
• IRC_JOB_POSTINGS: Job posting records linked to requisitions — posting text, dates, career site, audience
• IRC_SUBMISSIONS: Candidate application records — links Person ID (candidate) to Requisition ID. Contains pipeline phase, state, scores, dates
• PER_PERSONS / HRC_PERSON_CANDIDATES: Candidate person records — linked to Oracle's central Person entity in Core HR for employee-candidate continuity
• IRC_OFFERS: Offer records linked to submissions — compensation details, offer status, approval history
• IRC_QUESTIONNAIRE_RESPONSES: Prescreening and interview questionnaire responses linked to submissions
• Direct SQL access to these tables is not available in Oracle HCM Cloud (SaaS) — access recruiting data via OTBI Subject Areas, HCM Extracts, or REST APIs

• Check Posting Status: Navigate to the requisition → Postings tab. Confirm a posting exists and its status is Posted (not Draft, Expired, or On Hold)
• Posting Dates: Verify the posting start date has passed and the end date has not expired. A posting with a future start date will not yet appear on the site
• Career Site Assignment: Confirm the posting is associated with the correct career site. A posting on the Internal site won't appear on the External site
• Posting Audience: Check if the posting audience is set to Internal only — which would be invisible to external visitors
• Career Site Status: Confirm the career site itself is in Active status in Career Site configuration
• Cache: Career site job listings may be cached for up to 15–30 minutes. Wait and retry before escalating
• Requisition Status: If the requisition was moved to On Hold or Closed after approval, postings are automatically taken down. Confirm requisition status is Open
• SR to Oracle: If all of the above are correct and the posting is still not appearing, raise an Oracle SR with the Requisition ID, Posting ID, and Career Site URL for investigation

A strong Oracle Recruiting Cloud Consultant brings depth across these core areas:

• ORC Configuration Mastery: Deep knowledge of CSP design, career site building, prescreening, offer templates, approval rules, and descriptive flexfields
• Oracle HCM Core HR Knowledge: Understanding of Workforce Structures, Position Management, Grade Rates, and the hire/onboarding process — ORC doesn't operate in isolation
• Integration Skills: REST API fluency, OIC integration design, HCM Extracts, and third-party connector configuration (LinkedIn, background check, assessment, job boards)
• OTBI Reporting: Ability to build recruiting dashboards and custom analyses using ORC OTBI subject areas and BI Publisher offer letters
• Security Design: Configuring recruiting roles, data access profiles, and EEO/OFCCP compliance data controls
• Compliance Awareness: Understanding of GDPR, OFCCP, pay transparency laws, and how to configure ORC to meet these requirements across different geographies
• Change Management: Ability to train recruiters, hiring managers, and TA leadership on new processes — technical configuration alone does not deliver business value
• Business Acumen: Understanding of TA metrics, recruiting process best practices, and the ability to translate business requirements into ORC configuration decisions