Every iCIMS account stores candidates faster than any single hiring team can track by memory. A retailer or hospital system operating iCIMS across dozens of locations can hold hundreds of thousands of candidate profiles, most tied to a requisition that closed months or years ago, and never checked against anything since.
Finding a specific person in that history depends entirely on a recruiter remembering they exist and deciding to look. Nothing in the platform makes that connection automatically.
This expert guide explains what tools iCIMS provides for finding qualified candidates already in the system. It also covers their limitations and how an AI integration addresses those to automate sourcing and scoring past applicants.
What Is Candidate Rediscovery?
Candidate rediscovery matches applications already stored in your iCIMS database with newly available roles. It includes applicants from closed requisitions, talent pool candidates, and those who started but didn’t finish the hiring process.
This feature automatically checks past candidates against new openings, turning your application history into a valuable sourcing channel. Unlike other tools that require manual searches, rediscovery ensures that every potential fit is considered as soon as a role opens.
Does iCIMS Provide Candidate Rediscovery?
No, iCIMS doesn't provide a candidate rediscovery tool or any way to automatically source and score past qualified applicants. The recruiting module includes a Person Search tool for finding specific candidates by name or search criteria. It also has Talent Pools under Candidate Relationship Management for grouping candidates that a recruiter wants to revisit later.
Talent Cloud AI adds several named matching features on top of that. Talent Discovery surfaces qualified candidates based on skills and experience. Talent Match returns candidates similar to a recruiter's ideal profile. Candidate Ranking sorts applicants for a specific job by fit.
Each of these tools requires a recruiter to open it and point it at a job. None of them automatically checks a candidate from a closed requisition against a new one as soon as that requisition posts. A recruiter still has to remember that a past candidate exists and then use Person Search, Talent Discovery, or a talent pool manually to find them.
How to Rediscover Candidates in iCIMS
Since iCIMS 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 iCIMS Account With Skima AI
Generate OAuth 2.0 credentials, or an API key and secret, in the iCIMS Partner Portal, scoped to Profiles, ApplicantWorkflows, BinaryFiles, and CollectionFields. This connection uses iCIMS's own REST APIs directly, with no middleware required. Skima AI needs both read and write access to function.
- Read access: candidate and person profiles, applications, job details, and resume attachments
- Write access: custom fields through the Collection Fields API, candidate tags, and activity notes
- Pulled data: candidate contact details, resumes, application stage, and job requirements for scoring context
- Event notifications: application creation and updates, stage changes, and attachment uploads
Real-time webhooks are not native to iCIMS, so Skima AI relies on safe polling every 10 to 15 minutes.
Step 2: Configure Custom Fields and Confirm the Connection
Create the custom fields Skima AI writes to through the Collection Fields API, or authorize Skima AI to provision them during setup. These are Skima AI match score, a number from 0 to 100, and reasons, a long text field listing reasons for the fit. A Skima Screened tag gets added at the candidate level, so screened applicants stay filterable inside iCIMS.
Optional HM Feedback and HM Comment fields capture manager responses once a shortlist goes out. If custom fields are restricted in your instance, Skima AI falls back to writing an activity note or attaching a SKIMA_Evidence.pdf instead.
Before rolling this out further, test it on two or three requisitions. Upload a resume, then confirm the Match Score and Reasons actually appear on that application.
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 iCIMS 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 matched poorly on an earlier Talent Discovery search but line up well against this requisition.
Step 5: Shortlist and Sync Feedback Back to iCIMS
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 iCIMS through the same API connection for the audit trail, updating the custom fields and logging an activity note. The feedback stays visible on the record without anyone opening a second tool.
What If Your iCIMS Database Is Messy or Duplicated
iCIMS manages duplicate candidates with a merge tool in Applicant Tracking, Onboarding, Offer Management, and Connect. However, only user admins can access it, and only two profiles can merge at once.
There’s no automatic flagging for duplicates; recruiters must identify them, often when candidates apply with different email addresses, as iCIMS primarily matches profiles by email.
In high-volume accounts like retail or healthcare, this issue escalates. Each new application under a different email creates split profiles, each with partial application histories. The merge process requires manual identification and combination of profiles.
In contrast, Skima AI treats this as ongoing maintenance. It first matches by email, phone, or LinkedIn URL, then checks names, locations, and companies. A comparison modal highlights differences before merging, while missing details are filled through contextual profile enrichment. A dedicated Duplicates tab tracks resolved cases, organised into In Database, From Uploads, and Resolved sub-tabs.
5 Benefits of Candidate Rediscovery with Skima AI in iCIMS
Talent rediscovery with Skima AI changes what an iCIMS 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 iCIMS 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, plus a Skima Screened tag for instant filtering inside iCIMS.
- Hiring Manager Engagement Without a New Login: The shortlist feedback loop keeps managers responding through a link, no iCIMS 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 iCIMS
None of these benefits happen automatically inside iCIMS without a few intentional habits. The 5 practices below cover search timing, data hygiene, and fitting rediscovery around a high-volume, multi-location account:
- Check Person Search and Talent Pools First, Then Widen the Scan: Person Search and Talent Pools already cover candidates a recruiter has actively searched for or grouped. 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 Brand or Location: A candidate who matched well for a role at one location or brand often fits an opening elsewhere in a multi-brand organization. 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.
- Coordinate the Duplicates Tab With Your Admin's Merge Process: Since merging duplicate profiles in iCIMS depends on a User Admin combining two records at a time, reviewing Skima AI's Duplicates tab on the same schedule catches records that the manual merge process was never built to reach at scale.
Is Candidate Rediscovery Worth It for Your Recruitment Team?
An iCIMS account that has processed high volumes of applications across multiple locations or brands for several years builds up a Person Search database most recruiters only ever touch through a single Talent Discovery search. That backlog holds significant value.
A candidate who matched well for a role at one location often fits a similar opening at another, and nothing in iCIMS connects those two facts unless someone searches for that person directly.
Setting up Skima AI requires OAuth 2.0 credentials scoped correctly in the iCIMS Partner Portal, a handful of custom fields provisioned through the Collection Fields API, and a short validation cycle on a couple of live requisitions. None of this needs a large implementation project, but it does need someone on the technical side to handle the setup correctly the first time.
For an organization with a single location and infrequent hiring, the backlog remains small, making the setup effort harder to justify. In contrast, a multi-brand or multi-location employer that processes thousands of applications each year has a Person Search database filled with more qualified candidates than any one recruiter can manually search. This is precisely the gap that rediscovery aims to close.
Final Verdict: Pilot Candidate Rediscovery in iCIMS Now
For multi-location or high-volume organizations hiring repeatedly on iCIMS, a pilot with Skima AI can deliver high ROI. The right move is not switching every brand or location over at once. Start with two or three live requisitions, ideally ones your company has filled more than once before.
Connect Skima AI, configure the custom fields, and launch Talent Rediscovery on those roles. Skima AI's own iCIMS integration structures 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 iCIMS pilot, expect something above and around 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, not a guess.
Frequently Asked Questions
1. Does iCIMS have a built-in talent rediscovery feature?
No, iCIMS does not have a built-in talent rediscovery feature or tool. Instead, it offers Person Search, Talent Pools, and Talent Cloud AI features like Talent Discovery, Talent Match, and Candidate Ranking, but each requires a recruiter to point it at a job manually. None of these scan or score closed requisitions automatically when a new role opens.
2. How to perform candidate rediscovery in iCIMS?
To perform candidate rediscovery in iCIMS, connect Skima AI to iCIMS through OAuth 2.0 credentials from the iCIMS Partner Portal, configure custom fields through the Collection Fields API, 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 iCIMS candidate rediscovery?
Rediscovered candidates arrive pre-scored, reducing 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 tag for filtering, and hiring manager feedback without a new login.
4. Is Skima AI safe to integrate with iCIMS for talent rediscovery?
Yes, Skima AI encrypts candidate data in transit and at rest, maintains a signed Data Processing Agreement with subprocessors listed, and follows SOC 2 practices. Scores rely on resume-based evidence only, with no automatic rejections, and every hiring manager decision stays logged in iCIMS for audit.
5. Is candidate rediscovery useful for iCIMS's typical customers?
Yes, especially for multi-location or multi-brand organizations processing high volumes of applications 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.
