Priya Nair
7 years · Java / Spring
85%Strong match
- Evidence to explore
- Java and Spring used in production API work.
- Still your call
- Confirm system-design depth and current notice period.
Your candidate poolYour next shortlist
Your next shortlist
may already be here.
You already spent time finding these people. Give their experience a fresh look against the next brief, before starting the search again.
Your workspace’s saved candidates. A new assessment for every role.
A pass for one role
can be a reason to call for another.
Change the brief below. The people stay the same; the evidence that matters changes.
Cedar Labs · fictional brief
Same pool · 3 sample peopleJava backend engineer
Java, Spring Boot, production APIs · 5+ years
Rahul Iyer
6 years · Python / SQL
61%Possible match
- Evidence to explore
- API and SQL experience is relevant to part of the brief.
- Still your call
- Spring Boot evidence is missing; ask before progressing.
Sneha Kulkarni
5 years · Java / Selenium
66%Possible match
- Evidence to explore
- Java is evidenced in automated test suites.
- Still your call
- Test automation does not establish production API ownership.
A different JD changes the question you ask of the same CV.Availability and interest still need a fresh check.
Helix Health · fictional brief
Same pool · 3 sample peopleData engineer
Python, SQL, ETL ownership · 5+ years
Priya Nair
7 years · Java / Spring
44%Needs review
- Evidence to explore
- SQL appears in the profile’s backend work.
- Still your call
- Python and ETL ownership need evidence for this role.
Rahul Iyer
6 years · Python / SQL
88%Strong match
- Evidence to explore
- Python, SQL and ownership of data pipelines align.
- Still your call
- Check the scale of those pipelines and current availability.
Sneha Kulkarni
5 years · Java / Selenium
49%Needs review
- Evidence to explore
- SQL checks appear in test automation work.
- Still your call
- Data validation is not evidence of owning ETL pipelines.
A different JD changes the question you ask of the same CV.Availability and interest still need a fresh check.
Northwind Systems · fictional brief
Same pool · 3 sample peopleQA automation engineer
Java, Selenium, Cucumber · 4+ years
Priya Nair
7 years · Java / Spring
62%Possible match
- Evidence to explore
- Java and API testing provide adjacent experience.
- Still your call
- Selenium and Cucumber ownership need verification.
Rahul Iyer
6 years · Python / SQL
50%Needs review
- Evidence to explore
- Automated data checks show relevant testing habits.
- Still your call
- The requested Java test stack is not evidenced.
Sneha Kulkarni
5 years · Java / Selenium
86%Strong match
- Evidence to explore
- Java, Selenium and Cucumber align with this brief.
- Still your call
- Confirm framework ownership and interest in this team.
A different JD changes the question you ask of the same CV.Availability and interest still need a fresh check.
Interactive illustration. Fictional people and briefs; these scores and explanations are authored examples, not live engine outputs. They demonstrate role-specific fit, not a candidate’s value or hiring outcome.
Look inward.
Then source what’s missing.
Before you accept a requirement, see the pool’s likely fits. On a job’s Source tab, bring that context into your sourcing plan.
Preview your starting point
Pool readiness gives you strong and possible fit counts, leading names and earlier-role context. A preview helps you plan; it does not save a screened shortlist.
Screen for this requirement
Run “Screen this pool” for the current job. Inspect its evidence, gaps and candidate history. An old score from another JD is not the new decision.
Search with a clearer gap
If the pool lacks the needed experience, source more people. The Resdex side panel can flag possible pool sightings while you review your own search results.
Pool-radar sightings need your confirmation. They do not prove identity. The side panel is installed by hand, runs beside your own Resdex account and requires your actions.
Less repeated searching.
What could that change for your desk?
Explore a monthly scenario. Count recruiter capacity separately from variable sourcing spend, and keep fixed subscriptions visible.
Your monthly scenario
60 of 240 candidate-role reviews use the saved pool.
10 hours
Recruiter capacity freed per month
Time available for other work. This is not a salary saving or a reduction in headcount.₹0
Potential variable sourcing spend avoided
Only when a profile purchase or paid credit really would be avoided under your contract. Unused bundled credits are not automatically cash savings.₹5,000
Fixed subscriptions stay unchanged
Includes whatever fixed software or portal bills you entered. This model does not cancel or reduce them, and it is not an ROI calculation.Source every profile anew72 h
Reuse where suitable62 h
Show the calculation and its limits
Candidate-role reviews = roles × reviews per role. One person considered for two JDs counts twice: the work is role-specific. This is not a count of unique people hired.
Reviews covered by the pool = total reviews × reuse percentage, rounded to the nearest whole review. Use the percentage you expect to remain suitable after checking fit, interest and availability.
Capacity hours = reused reviews × (new sourcing minutes − reuse minutes) ÷ 60
Both timings should include the work you actually do. Add fresh outreach, availability checks and role-specific review to the reuse time. If reuse takes longer, the result shows additional hours instead of hiding them.
Avoidable variable spend = reused reviews × avoidable cost per new profile
Use ₹0 if your existing plan is fixed or bundled and reuse will not reduce an actual payment. Fixed monthly subscriptions are shown separately and unchanged. No wages, placement revenue, taxes, conversion improvement or claimed customer results enter the calculation.
Scenario, not a forecast or measured product saving. Real results depend on pool quality, overlapping roles, candidate response and your sourcing contract. Reuse never removes the need for a fresh recruiting decision.
Keep the history.
Refresh the judgement.
A practical path from a saved CV to a considered new conversation.
Start with the brief, including what changed
Review the parsed requirements: must-haves, nice-to-haves, experience and the client’s answers. A title alone does not make two roles equivalent. Then inspect pool readiness before deciding how much new sourcing is needed.
Pool previews and reverse matching are read-only rankings. Run screening for the job when you need a saved evaluation and evidence to review. See how scoring works.
Carry the profile forward, not the old verdict
Sonder keeps earlier screening, pipeline and client feedback in context. A previous pass may have been about a different brief, budget or timing. Read the reason before treating it as a new rejection—or a new approval.
Start from a candidate to see which open roles they fit, or start from a role to inspect the pool. Each route points you toward a review; neither contacts or submits the person for you.
Reconfirm the person’s circumstances
- Are they still interested in a move and in this specific opportunity?
- Are notice period, expected compensation, location and work-mode preferences current?
- Is the CV up to date, and is there evidence for the new role’s must-haves?
- Do you have permission to share their profile with this client?
A saved CV or high fit score answers none of those questions automatically. Your own workspace pool is different from opted-in Sonder Jobs Talent Search, where job seekers confirm their availability.
Refresh scores when the inputs change
Changes to the brief, candidate scoring details or screening rules can make an evaluation stale. Sonder keeps saved decisions visible and asks you to re-screen before sharing. Update the record, screen against the current role and inspect the new evidence.
Uploading a full CV can add evidence beyond a sparse export row. Read the result again: more information can change the assessment in either direction.
Avoid paying to rediscover someone you already have
Check your pool first. When using the manually installed Resdex side panel, the pool radar can indicate that a visible result may already be known to your workspace. It uses a name sighting with supporting clues, not a verified identity match. Confirm the person before relying on it.
You run the search and choose the next step on your own account. Whether avoiding a CV view changes a bill depends on your plan; do not equate every unused view with money saved.
Bring existing records in with a review step
On paid plans, bring CV folders and candidate exports into the workspace through a preview and confirmation flow. Review mapped fields, duplicates and warnings before saving. Archived candidates stay out of normal pool screening.
The 14-day trial starts with a fresh workspace. Explore the four import paths or compare the plans.
Start with the people
you already know.
Open a fresh workspace, add a requirement and see how Sonder brings fit, evidence and the next decision together.
No credit card required. Sign up with Google or email.
Existing-desk imports are available on paid plans.