Oracle Recruiting Cloud can tell you whether two candidate profiles belong to the same person, using national identifiers, name, date of birth, address, education, and work history all at once. That same system has nothing to say about whether a candidate from a closed requisition fits the different role that opened this morning.
The two problems look related but aren't. Oracle solves the first one: confirming whether one person accidentally applied twice. It leaves the second one, whether a qualified person from your own history fits today's opening, entirely up to a recruiter's memory.
This expert guide covers what tools Oracle Recruiting Cloud provides for finding candidates already in the system. It also covers their limitations and how an AI integration addresses those to automate rediscovering, sourcing, and scoring past applicants.
What Is Candidate Rediscovery?
Candidate rediscovery involves searching and matching existing profiles in your Oracle Recruiting Cloud with newly opened roles. This includes applicants from closed requisitions, candidates in a talent pool, and those who partially completed the hiring process.
By automating checks against past candidates, your application history transforms into an effective sourcing channel. Unlike most platforms that require manual searches, rediscovery ensures this process happens automatically whenever a role becomes available.
Does Oracle Recruiting Cloud Provide Candidate Rediscovery?
No, Oracle Recruiting Cloud doesn't provide a candidate rediscovery feature or any way to automatically source and score past qualified applicants. Its candidate search lets recruiters filter the database by skills, experience, and location, with LinkedIn search built directly into the same page.
Recruiters can also organize people into candidate pools categorized by skill or qualification, and use AI-based matching to compare a specific candidate against a specific job requisition.
Additionally, a separate similar candidates feature, once enabled through a profile option, applies machine learning to return up to 30 candidates who share traits with one candidate that a recruiter is already viewing.
All of these tools start with a recruiter choosing a candidate, a pool, or a set of search terms. None of them checks a closed requisition's full applicant list or database against a job that just opened, and none of them operates automatically. Rediscovery still depends on a recruiter remembering someone exists and going to look for them.
How to Rediscover Candidates in Oracle Recruiting Cloud
Since Oracle Recruiting Cloud has no built-in way to automatically source, score, or surface past applicants across requisitions, its users connect Skima AI to scan that history every time a role opens. Below is a 5-step workflow, from connecting your account to a finished shortlist:
Step 1: Connect Your Oracle Recruiting Cloud With Skima AI
Create an integration user with read privileges on requisitions, candidates, and applications, and write privileges on assessments and comments. Register an OAuth 2.0 client, or configure the connection through Oracle Integration Cloud. This connection uses Oracle's own HCM REST APIs directly, with no additional middleware required for cloud instances.
- Read access: job requisitions, candidate profiles, job applications, and resume attachments
- Write access: candidate assessment results, application comments, and custom attributes
- Pulled data: candidate contact details, resumes, application stage, and requisition requirements for scoring context
- Event notifications: application creation and updates, stage changes, and attachment uploads, delivered through Atom feeds where available
If Atom feeds are not configured, Skima AI falls back to safe delta polling every 10 to 15 minutes.
Step 2: Configure Custom Attributes and Confirm the Connection
Define custom attributes in HCM for matchScore, reasons, skimaScreened, and shortlistLink, or authorize Skima AI to provision them during setup. The match score shows a number from 0 to 100, and the reasons field explains the fit. A Skima Screened flag gets added at the application level, so screened candidates stay filterable inside Oracle.
Optional manager feedback and comments capture responses once a shortlist goes out, logged as application comments.
Before rolling this out further, test it on sandbox requisitions. Upload a resume, verify the match score and reasons appear, approve a candidate through the shortlist link, and confirm the feedback shows up correctly in HCM.
Step 3: Launch Talent Rediscovery Against a Live Requisition
Open the job inside Skima AI, from the Jobs list or from within the job itself. Click the three-dot Actions menu and select Rediscover Candidates. A modal lets you scope the scan two ways. Limit it to a saved candidate segment, or leave it open to every synced Oracle record.
Set the Candidate Created Date range next: All time, Last 6 months, Last 1 year, or a custom window, then click Apply. Skima AI scans the selected pool against this requisition's specific requirements and sends a notification once the scan finishes. Refresh the page to see the results.
Step 4: Review and Filter the Rediscovered Matches
Open the View Candidates tab to see a ranked list pulled from across your entire application history. Each candidate carries an AI match score and reason bullets explaining the fit. Filter by Industry, Work Mode, Experience Level, Notice Period, Location, and Salary Range.
Start broad and tighten the filters gradually. Narrowing too fast hides good candidates, including people who never surfaced through a manual Candidate Search but line up well against this requisition.
Step 5: Shortlist and Sync Feedback Back to Oracle Recruiting
Build your shortlist from the ranked matches Skima AI surfaced. Generate a secure, no-login link and send it to the hiring manager. They can click a thumbs up, thumbs down, or maybe on each candidate, with an optional comment.
Skima AI writes that decision back into Oracle through the same API connection for the audit trail, logging it as an application comment. The feedback stays visible on the record without anyone opening a second tool.
What If Your Oracle Cloud Database Is Duplicated
Oracle Recruiting Cloud offers a robust duplicate check. It assesses a match score based on national identifiers, name, date of birth, address, education, and experience, alongside simpler identifiers like email and phone.
Recruiters can activate this check from Candidate Search, candidate pools, job applications, or prospect records. They may select up to ten candidate files to view a pre-merge report that compares name, address, email, phone, application history, and screening status. The system advises which file to keep, prioritising the most up-to-date information.
This solution tackles a specific issue but does not resolve rediscovery. It identifies when one person mistakenly creates two records. However, it does not highlight distinct, qualified candidates from closed requisitions who may suit new roles. Additionally, it only checks selected records rather than conducting routine scans of the entire database.
Conversely, Skima AI handles this as ongoing maintenance. It begins matching with email, phone, or LinkedIn URL and checks name, location, and company as secondary signals.
Furthermore, a field comparison modal appears before any merging occurs, pinpointing differences between records. Missing information is completed via contextual profile enrichment. A dedicated Duplicates tab tracks each resolved case for future audits, divided into In Database, From Uploads, and Resolved sub-tabs.
5 Benefits of Candidate Rediscovery with Skima AI
Talent rediscovery with Skima AI changes what an Oracle Recruiting Cloud team can do with its own application history in 5 specific ways:
- Faster Time-to-Screen: Rediscovered candidates arrive already scored, so recruiters skip the raw resume pile entirely. In a documented 30-day Oracle pilot, a team reduced time-to-screen by 58%.
- More Interviews From the Same Shortlist: The same pilot saw interviews from the top shortlist double compared to the prior process.
- Explainable Match Scores With an Audit Trail: Every rediscovered match carries reason bullets tied to skills and experience, logged as an application comment alongside a Skima Screened flag for instant filtering inside Oracle.
- Hiring Manager Engagement Without a New Login: The shortlist feedback loop keeps managers responding through a link, no Oracle credentials required. Manager satisfaction rose 24 points on NPS in that same pilot.
- Lower Cost Per Hire on Repeat Roles: Rediscovered candidates were already sourced once, so filling a role you've hired for before needs zero new job board spend.
5 Best Practices to Rediscover Talent in Oracle Recruiting Cloud
None of these benefits happen automatically inside Oracle without a few intentional habits. The 5 practices below cover search timing, data hygiene, and fitting rediscovery around a large, multi-module HCM environment:
- Check Candidate Search and Similar Candidates First: Candidate Search and Similar Candidates already cover people a recruiter has actively searched for or viewed. Use Skima AI's Talent Rediscovery to reach the much larger set of closed-requisition applicants that neither tool checks again.
- Turn On Automatic Rediscovery for Every New Requisition: Skima AI's setting under Preferences and General starts a database scan the instant a new job is created. Enable it so no requisition slips through without a first look at your existing applicant history.
- Use Reverse Search for Candidates From a Different Business Unit or Region: A candidate who matches well for a role in one part of a large organization often fits an opening in a different division or country. Reverse Search starts from that profile and returns every open job they match, ranked by score.
- Segment Scans With the Candidate Created Date Filter: Choose a 6-month or 1-year window when a role needs someone who was recently active. Widen to All time for a niche or hard-to-fill role where the applicant pool has always been thin.
- Pair the Duplicates Tab With Your Team's Manual Dupe-Check Habits: Since Oracle's duplicate check only reviews the records a recruiter actively selects, checking Skima AI's Duplicates tab on a regular schedule catches records nobody thought to select for a manual check.
Is Candidate Rediscovery Worth It for Your Recruitment Team?
A company that has operated Oracle Recruiting Cloud across multiple business units or countries for several years builds up a candidate history far larger than any single Candidate Search or Similar Candidates lookup ever touches.
That backlog holds significant value. A candidate who matched well in one region often fits a similar opening elsewhere in the company, and nothing connects those two facts unless a recruiter searches for that person directly.
Setting up Skima AI takes real coordination on the IT side. Someone needs to create an integration user with the correct privileges, register an OAuth 2.0 client or configure Oracle Integration Cloud, and define the fields Skima AI writes back to. None of this is unusual for an Oracle HCM rollout, but it is not a same-day setup either.
For a smaller division inside a larger Oracle rollout, with only a few open roles a year, that backlog stays thin, and the setup effort is harder to justify. For a large enterprise using Oracle Recruiting Cloud across many business units, the candidate history building up behind each closed requisition is exactly what rediscovery is built to put back to work.
Pilot Talent Rediscovery in Oracle Recruiting Cloud
For large organizations hiring repeatedly on Oracle Recruiting Cloud, a pilot with Skima AI can deliver high ROI. The right move is not switching every business unit over at once. Start with two or three live requisitions, ideally ones your company has filled more than once before.
Connect Skima AI, define the custom attributes, and launch Talent Rediscovery on those roles. Skima AI's own Oracle integration organizes this as a 30-day pilot, with checkpoints at day 15 and day 30.
Track time-to-screen, how many rediscovered candidates reach an interview, and hiring manager response. Based on a documented 30-day Oracle pilot, expect over a 58% drop in time-to-screen and double the interviews from your top shortlist. From there, expanding to more requisitions becomes a decision backed by your own data.
Frequently Asked Questions
1. Does Oracle Recruiting Cloud have a built-in talent rediscovery tool?
No, Oracle Recruiting Cloud does not have a built-in talent rediscovery tool. It offers Candidate Search, candidate pools, AI-based matching against a specific job, and a Similar Candidates feature for finding people like one candidate already on screen. None of these scan closed requisitions automatically when a new role opens.
2. How to perform candidate rediscovery in Oracle Recruiting Cloud?
To perform candidate rediscovery in Oracle Recruiting Cloud, connect Skima AI to Oracle through an integration user and OAuth 2.0 credentials, define custom attributes for scoring fields, then launch Talent Rediscovery on a live requisition. Skima AI scans your application history, ranks candidates, and syncs hiring manager feedback back automatically.
3. What are the benefits of Oracle Recruiting Cloud candidate rediscovery?
Rediscovered candidates arrive pre-scored, cutting screening time by over 58% in a documented 30-day pilot and doubling interviews from the top shortlist. Matches carry explainable reasons, a Skima Screened flag for filtering, and hiring manager feedback without a new login.
4. Is Skima AI safe to integrate with Oracle Recruiting Cloud for talent rediscovery?
Yes, Skima AI encrypts candidate data with TLS in transit and AES-256 at rest, follows GDPR and SOC 2 practices, and logs every AI decision and manager response as an application comment for audit. Scores rely on resume-based evidence only, with no automatic rejections.
5. Is candidate rediscovery useful for Oracle Recruiting Cloud's typical customers?
Yes, especially for large enterprises operating across multiple business units or countries that refill similar roles over time. The value grows the more often the same kinds of positions, and sometimes the same candidates, come back into play.
