A marketing team hires a content strategist through Bob Hiring and closes the requisition. The other finalists, who interviewed well but didn't get the offer, moved into the closed pipeline along with everyone else who applied. Nothing marks that person as runner-up or different from someone who never showed up.
Five months later, a similar content role opens on a different team. Nothing in Bob Hiring checks those earlier finalists against it. A recruiter would have to remember that specific person and search for them directly, or the connection never gets made.
This expert guide covers what tools HiBob provides for finding candidates already in the system. It also covers their limitations and how an AI integration addresses those to automate rediscovery, sourcing, and scoring past applicants.
What Is Candidate Rediscovery?
Candidate rediscovery searches and matches candidates from your Hibob database with newly available roles. It includes applicants from past positions, candidates in a talent pool, and those who advanced partway through hiring. This automated process turns your application history into an active sourcing channel, ensuring that potential fits are identified without the need for manual searches.
Does HiBob Provide Talent Rediscovery?
No, HiBob doesn't offer a talent rediscovery feature or any way to automatically find and rank past qualified candidates. The Bob hiring module covers the core of a hiring pipeline: job postings, candidate stages, custom scorecards for evaluation, and a direct handoff into the new hire flow once someone is chosen.
Furthermore, recruiters can build and manage a pipeline for a specific requisition, but there is nothing to search or score candidates from a previous, closed requisition.
Once a job closes, its applicants stay tied to that job's pipeline. Nothing carries them forward or checks them against a different or nearly identical role that opens later.
How to Rediscover Candidates in HiBob
Since HiBob has no built-in way to source, score, or surface past applicants across open jobs, its users connect Skima AI to scan the database and rank matching profiles automatically every time a role opens. Below is a 5-step workflow, from connecting your account to a finished shortlist:
Step 1: Connect Your HiBob Account With Skima AI
Create API service credentials with the right permissions in the HiBob admin portal. This connection uses HiBob's own REST API directly, with no middleware required. Skima AI needs both read and write access to function.
- Read access: candidate profiles, job requisitions, application status, and resume attachments
- Write access: activity logs and candidate tags
- Pulled data: candidate contact details, resumes, application stage, and prior application history for scoring context
- Webhook subscriptions: candidate creation, updates, and stage changes
If webhooks are not configured, Skima AI falls back to safe polling every 10 to 15 minutes.
Step 2: Configure Fields and Confirm the Connection
Map candidate and job fields between HiBob and Skima AI using HiBob's API metadata tools. The Skima AI match score, (number from 0 to 100), and reasons (bullets explaining the fit), post as activity log entries on the candidate record. A Skima Screened tag gets added at the candidate level, so screened applicants stay filterable inside HiBob.
Optional hiring manager feedback and comments also log as activity entries once a shortlist goes out.
Before rolling this out further, test the connection on a sample requisition. Upload a resume, verify the score and reasons appear, submit manager feedback, and check the log entry before applying it to live roles.
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 HiBob 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 finalists from a closed pipeline who line up well against this requisition.
Step 5: Shortlist and Sync Feedback Back to HiBob
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 HiBob through the same API connection for the audit trail, logging it as an activity entry. The feedback stays visible on the record without anyone opening a second tool.
What If Your HiBob Database Is Messy or Duplicated
HiBob does not offer a dedicated duplicate-detection or merge workflow for candidate records inside Bob Hiring. When the same person applies for more than one role, or reapplies months after being rejected, each application exists inside its own job pipeline with no automatic check tying the two together.
That gap increases as a company's hiring volume rises. A growing company that posts similar roles across departments ends up with duplicate applications when someone applies more than once. This often goes unnoticed until a recruiter spots a familiar name.
Skima AI treats this as ongoing maintenance rather than a one-time project. It matches on email, phone, or LinkedIn URL first. It also checks matching names, locations, and companies together as a backup signal.
Furthermore, a field comparison modal appears before anything merges, flagging exactly what differs across the two records. Missing details get filled in through contextual profile enrichment instead of staying incomplete. A dedicated Duplicates tab logs every resolved case for later audit, split across In Database, From Uploads, and Resolved sub-tabs.
5 Benefits of Candidate Rediscovery with Skima AI in HiBob
Once Skima AI is connected, a Hibob recruiting team gets 5 clear benefits from an application database that was already there:
- Faster Time-to-Screen: Rediscovered candidates arrive already scored, so recruiters skip the raw resume pile entirely. In a documented 30-day HiBob 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 activity entry alongside a Skima Screened tag for instant filtering inside HiBob.
- Hiring Manager Engagement Without a New Login: The shortlist feedback loop keeps managers responding through a link, no HiBob 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 HiBob
A few intentional habits turn this integration into real results inside HiBob. The 5 practices below cover search timing, data hygiene, and integrating rediscovery around a growing company's hiring pace:
- Check Closed Pipelines and Scorecards First: Scorecards from a closed pipeline already tell you how a candidate performed for that specific role. Use Skima AI's Talent Rediscovery to reach the much larger set of past applicants that no scorecard ever gets revisited for.
- 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 Finalists Who Did Not Get an Offer: A strong finalist for one role often fits a different opening that comes up later. 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.
- Review the Duplicates Tab as Hiring Picks Up Across Departments: A growing company hiring for similar roles across multiple teams accumulates duplicate applications quickly. Checking Skima AI's Duplicates tab on a regular schedule keeps that from turning into a backlog.
Is Candidate Rediscovery Worth It for Your Recruitment Team?
A company that has hired consistently through HiBob for a year or more builds up an application history spread across various closed pipelines that nobody revisits. That backlog holds significant value. A finalist who didn't get one offer often fits a similar role that opens later, and nothing connects those two facts unless a recruiter searches for that person directly.
Setting up Skima AI takes some coordination on the technical side. Someone needs to create API service credentials in the HiBob admin portal, map the relevant candidate and job fields, and test the connection on a sample requisition before going live.
For a small company with only a handful of open roles a year, that backlog stays thin and the setup effort is harder to justify. In contrast, for a growing company hiring repeatedly across departments, the candidate history building up behind each closed pipeline is exactly what rediscovery is built to put back to work.
Pilot Talent Rediscovery in HiBob Now
For growing companies hiring repeatedly on HiBob, a pilot with Skima AI can deliver a high ROI. Don’t switch every department over at once. Start with a few pilot roles, ideally ones your company has filled more than once before.
Connect Skima AI, map the relevant fields, and launch Talent Rediscovery for those roles. Skima AI's HiBob integration sets this up as a 30-day pilot, with weekly ROI reports to track progress.
Track time-to-screen, how many rediscovered candidates reach an interview, and the hiring manager's response. Based on a documented 30-day HiBob pilot, expect about a 58% drop in time-to-screen and double the interviews from your top shortlist. From there, expanding to more requisitions becomes a decision supported by your own data.
Frequently Asked Questions
1. Does HiBob have a built-in candidate rediscovery feature?
No, HiBob does not have a built-in candidate rediscovery feature. Bob Hiring covers job postings, pipeline stages, scorecards, and the handoff into onboarding. None of these search or score candidates from a previous, closed requisition against a new one.
2. How to conduct candidate rediscovery in HiBob?
To conduct candidate rediscovery in HiBob, connect Skima AI to HiBob through API service credentials from the HiBob admin portal, map the relevant 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 HiBob 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 HiBob for talent rediscovery?
Yes, Skima AI secures API tokens and webhook endpoints with OAuth 2.0 and HTTPS encryption, enforces role-based access, and follows GDPR and SOC 2 practices. Scores rely on resume-based evidence only, with no automatic rejections.
5. Is candidate rediscovery useful for HiBob's typical customers?
Yes, especially for growing companies hiring repeatedly across departments 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.
