Rebuild searchable profiles
Parse historical resumes into stable, traceable experience and skill evidence.
Talent pool reactivation
Rediscover people you already know before starting every search from zero
A talent pool is valuable when a new role can surface relevant people from prior recruiting work—not when it merely stores many resumes. Aimme re-evaluates historical candidates against current criteria, retains relationship history, and separates evidence ready for review from information that needs refreshing.
The recruiting problem
Most talent pools are searchable only by names, tags, and keywords. Candidate experience changes and role definitions change. Old labels cannot explain why someone fits today’s role, so recruiters often return to external platforms and repeat the search.
How Aimme handles it
Break recruiting judgment into inspectable steps
Apply current criteria
Use today’s confirmed responsibilities and gates rather than past job labels.
Preserve relationship context
Consider prior communication, interviews, and rejection reasons before proposing renewed contact.
Identify stale facts
Mark company, role, location, and contact details that may require refresh.
From question to reviewable result
Preserve context—and the opportunity to stop and review
-
01
Define the pool
Choose teams, role families, time windows, and candidate data that may be used.
-
02
Clean and resolve
Handle duplicate resumes, multiple versions, and incomplete identity records.
-
03
Rematch
Create a new evidence matrix for the active role instead of reusing an old score.
-
04
Confirm reactivation
Review relationship history, match reasons, and contactability before outreach.
Why the result is reviewable
Fluent model output is not treated as fact
- Resume versions and last-updated dates prevent old and new facts from being mixed.
- A prior rejection is separated from the current role decision instead of becoming a permanent label.
- Rediscovery results explain which current requirements created relevance.
- Before outreach, the workflow checks opt-outs, invalid contact details, and existing team communication.
Operating boundaries
Be explicit about what the system does—and does not do
- Aimme does not recommend candidates based on protected traits such as name, gender, age, or ethnicity.
- Model output is recruiting support, not a hiring, rejection, or compensation decision.
- Missing evidence, conflicting sources, and unknown hard requirements are surfaced for human verification.
- Customers control candidate data. It is not used to train public models, and teams remain responsible for lawful, platform-compliant use.
Frequently asked questions
Answer the important questions first
How is reactivation different from resume search?
Resume search returns keyword matches. Reactivation applies current criteria, resolves identity and freshness, and considers the prior relationship.
Can previously rejected candidates be reconsidered?
Yes, but the prior role, rejection reason, and current requirements must remain distinct. The recruiting team decides whether renewed contact is appropriate.
How should reactivation be measured?
Track matchable-candidate coverage, valid contact rate, review acceptance, outreach response, and the number of rediscovered candidates who enter interviews.
Aimme
Start with one real role
Describe an active role. Aimme clarifies the requirements, searches and matches candidates, and organizes the evidence. Your recruiting team confirms every progression decision.