Most recruiters using Darwinbox tag a candidate as strong in the moment, right after an interview or a final review. That tag is what makes rediscovery possible later. Anyone who didn't get tagged, whether the role wasn't quite right or the recruiter simply moved on to the next application, has no path back into consideration when a similar opening comes up.
This expert guide covers what tools Darwinbox offers for finding candidates already in the database. It also covers their limitations and how an external AI integration addresses those to automate rediscovery, sourcing, and scoring past qualified candidates.
What Is Talent Rediscovery?
Talent rediscovery involves searching and matching stored candidates in Darwinbox's HCM for new job openings. This includes applicants from closed positions, those in the talent pool, and individuals who progressed partway through hiring before the role was filled or shelved.
With automatic checks against new openings, rediscovery transforms application history into an active sourcing channel, eliminating the need for recruiters to rely on memory.
Does Darwinbox Provide Candidate Rediscovery?
Partially, Darwinbox parses resumes automatically and lets a recruiter tag a strong past applicant, then sends an alert when that tagged candidate matches a future job opening. Its Talent CRM also lets a recruiter segment candidates by skill, interest, or readiness for a role, with periodic engagement emails to keep that group active between hiring needs.
Coverage depends on what gets tagged. A candidate who was not flagged as strong at the time, whether the original role fit poorly or a recruiter simply moved on, never generates a future alert. The alert itself carries no score or stated reason, nothing scopes a search by how long ago a candidate applied, and nothing records a hiring manager's decision on a match.
How to Rediscover Candidates in Darwinbox
Darwinbox's tagging and alert system already catches some past applicants automatically. Connecting Skima AI scores every qualified candidate in the database, not just the tagged ones, adds date scoping, and creates a hiring manager decision trail. Below is a 5-step workflow that starts with what Darwinbox already provides and builds on it:
Step 1: The Native Path, Start With Tagging and Alerts
When reviewing an applicant, tag strong candidates directly on their profile. Resume parsing keeps their skills and experience data current, and the system sends an alert when a tagged candidate's profile matches a future job opening.
This step catches a repeat match for a candidate someone already flagged as strong. It misses everyone who was not tagged, and the alert carries no score or stated reason. For a database-wide, scored, and tracked version of this same check, Skima AI builds on this next.
Step 2: Connect Your Darwinbox Account With Skima AI
Register an API client inside Darwinbox with scopes for Candidates, Employees, Positions, and Webhooks, then configure OAuth 2.0 using the client credentials and Darwinbox's token endpoints. This connection uses Darwinbox's own REST API directly, with no middleware required.
- Read access: candidate applications, resume text, source and referral data, employee profiles, and position requirements
- Write access: application custom fields, candidate tags, and employee profile fields
- Pulled data: candidate contact details, resumes, application status, position requirements, and employee skills and career interest data for internal matching
- Event triggers: application created, profile updated, and position opened, delivered through Darwinbox's webhooks
Step 3: Configure Custom Fields and Confirm the Connection
Add the custom fields Skima AI writes to on the Candidate Application and Employee objects: Match Score, Reasons, and an Internal Rediscovery Score for employee matches. Enable the three webhook events from Step 2, or fall back to scheduled polling if webhooks are not configured.
Before rolling this out further, submit a sample application in a sandbox or test environment. Confirm the Match Score and Reasons appear, check that an internal employee match surfaces correctly if one exists, and verify hiring manager feedback logs correctly before applying it to live roles.
Step 4: 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 opens with options to narrow the scan: select a specific candidate segment, or leave it open to every synced Darwinbox record.
Set the candidate created date range next: All time, Last 6 months, Last 1 year, or a custom window, and optionally check the location filter to restrict the scan geographically. Click Apply. A "Performing Rediscovery" notification appears while the scan works in the background, and turns green with a refresh option once it completes.
Step 5: Review, Filter, and Sync Feedback Back to Darwinbox
Refresh the page and open the Rediscovered source tab inside View Candidates. Each match carries a Skima AI score and reason bullets, tagged with a Rediscovery source label. Filter by Industry, Work Mode, Experience Level, Notice Period, Location, and Salary Range to narrow the list.
Once the shortlist looks right, generate a secure, no-login link and send it to the hiring manager. They click thumbs up, thumbs down, or maybe on each name, with an optional comment. Skima AI writes that decision back into Darwinbox as a custom field entry on the candidate application, keeping the feedback on the record without a second login.
What If Your Darwinbox Database Is Messy or Duplicated
Darwinbox does not offer a way to detect or merge two candidate records that belong to the same person, whether they applied under a different email address or a different name spelling the second time. A recruiter only catches that overlap by recognizing a name while reviewing a new application.
Skima AI treats this as ongoing maintenance rather than a one-time cleanup. It matches first on email, phone, or LinkedIn URL, then checks name, location, and company together as a backup signal.
When a match surfaces, a field comparison modal displays differences across Name, Title, Company, Location, Email, Phone, and LinkedIn, tagging each mismatched field as Differs. A recruiter picks which values to keep and merges the records, or adds the profile as new if the two genuinely differ. Every resolved case logs under the Duplicates tab, split into In Database, From Uploads, and Resolved sub-tabs for later audit.
5 Benefits of Candidate Rediscovery with Skima AI in Darwinbox
A documented 30-day pilot with Darwinbox reported 5 clear advantages once Skima AI starts scoring a company's full candidate and employee history:
- Faster Time-to-Screen: Rediscovered candidates arrive already matched and scored against the open role, reducing time-to-screen by 58% compared to starting a fresh search.
- Interviews Double From the Shortlist: The same pilot saw interviews booked from the shortlist double compared to the prior process.
- Every Candidate Scored, Not Just Tagged: Scoring covers the full database instead of only candidates a recruiter flagged as strong at the time, so a fit missed the first time still surfaces later.
- Employees Included Alongside Applicants: Scoring draws on employee skills and career interest data already stored in Darwinbox, so an internal candidate ready for a new role surfaces next to external ones.
- A Decision Trail for Every Name: A hiring manager responds through a no-login shortlist link, and that decision logs against the candidate record, building an audit trail the native alert system does not keep.
5 Best Practices to Rediscover Talent in Darwinbox
A few habits decide whether this connection turns into a steady source of candidates or a one-time setup:
- Keep Tagging, Then Widen With Skima AI: Continue tagging strong candidates for the native alert system's quick catches. Run a scoped Skima AI scan alongside it to reach candidates who were never tagged in the first place.
- Automate Rediscovery on Job Creation: Skima AI's setting under Preferences and General starts a database scan the instant a new job gets created inside the connected account, so no requisition goes live without a first look at existing history.
- Extend Reverse Search Beyond Tagged Candidates: Talent CRM segments group candidates by skill, interest, or readiness, but a candidate outside those segments can still fit a different role well. Reverse Search starts from any candidate's profile and returns every open job they match, ranked by score.
- Segment Scans by Candidate Created Date: Choose a 6-month or 1-year window when a role calls for someone recently active. Widen to all time for a niche or hard-to-fill role where the applicant pool has stayed thin for years.
- Review the Duplicates Tab on a Regular Schedule: Since Darwinbox has no way to catch a repeat applicant under a different email or name spelling, checking the In Database sub-tab regularly is the only way to keep this from piling up.
Is Candidate Rediscovery Worth It for Your Recruitment Team?
Darwinbox's tagging and alert system highlights the value of revisiting past candidates, as companies see genuine matches today. The effectiveness of this system relies on recruiters tagging candidates consistently; those who are untagged remain outside its reach.
A company with years of closed requisitions in Darwinbox provides Skima AI with a more extensive pool for scoring and deduplication than one with only a few roles filled. A shorter history yields a less comprehensive Rediscovered list, making early justifications for the setup more challenging.
Pilot Candidate Rediscovery in Darwinbox Now
For a company with a multi-year Darwinbox history, a pilot using Skima AI can deliver a high ROI. Start with two or three live requisitions, ideally roles the company has filled more than once before, so there is a real historical pool to score against.
Connect Skima AI to Darwinbox, configure the custom fields, and validate the connection in a sandbox before going live. Skima AI's own Darwinbox integration structures the rollout in phases: a validated pilot first, then a production rollout with defined success metrics and regular model reviews.
Track how many rediscovered candidates reach an interview and how the hiring manager responds to the shortlist link. Skima AI's documented 30-day pilot with Darwinbox reported a 58% drop in time-to-screen, interviews from the shortlist doubling, and hiring manager satisfaction rising 24 points on NPS. From there, expanding to more requisitions becomes a decision backed by the pilot's own numbers.
Frequently Asked Questions
1. Does Darwinbox have a built-in talent rediscovery feature?
Partially, Darwinbox tags strong past applicants and sends an alert when they match a future job opening, but coverage stops at candidates who were tagged, with no score, no date scoping, and no record of a hiring manager's decision.
2. How do I rediscover candidates in Darwinbox?
Start with Darwinbox's native tagging and alert system for candidates already flagged as strong. For a database-wide, scored, and auditable version, connect Skima AI through Darwinbox's API, configure custom fields, then launch Talent Rediscovery on a live requisition.
3. What are the benefits of candidate rediscovery in Darwinbox?
Based on a documented 30-day pilot, rediscovered candidates cut time-to-screen by 58% and doubled interviews from the shortlist. Scoring covers the full database rather than only tagged candidates, and hiring manager satisfaction rose 24 points on NPS.
4. Is Skima AI safe to integrate with Darwinbox for talent rediscovery?
Yes, Skima AI scores candidates using resume-based evidence only, with no automatic rejections, and logs every hiring manager decision and shortlist action for audit. Data stays encrypted in transit and at rest, in line with SOC 2 and GDPR practices.
5. Is candidate rediscovery useful for Darwinbox's typical customers?
Yes, especially for companies with several years of closed requisitions in Darwinbox, where past applicants who were never tagged for an alert have gone unchecked against newer openings. The value grows with the size of that history.
