The Candidate Database (talent pool) and saved filters

How CVViZ's "Resume Pool" / Candidate Database works, and how to slice it with saved filters and tags.

The terminology

What people often call a "talent pool" is, in CVViZ, just the Candidate Database — every candidate in your workspace, whether or not they're attached to an active job. The internal code-name for this concept is Resume Pool, but the user-facing label is Candidate Database.

The database lives at the candidate database.

What's in the database

  • Candidates added directly via the Add Candidates modal with the "Candidate Database" target.
  • Candidates from past jobs — their data persists after a job is closed.
  • Candidates imported via CSV.
  • Candidates sourced via Find on web / Find on GitHub / Discover candidates.

Slicing the database with filters

Use the toolbar's quick filters and detailed filters to scope the database to whoever you care about right now:

  • Top grade — A or B from AI grading.
  • With email — only contactable candidates.
  • Has notes — candidates your team has already engaged with.
  • Last 7 days — recent inflow.
  • Plus structured filters: tags, qualifications, top skills, locations, visa types, etc.

See Searching and filtering the candidate database for the full filter reference.

Saved filters / persistence

Filter combinations persist across pagination via theRedux state. As you click through pages and into individual candidates, your filters stay applied until you reset them.

Building a "talent pool" with tags

CVViZ doesn't have explicit named talent pools as separate database objects, but tags do the job:

  1. Pick a name for your conceptual pool — e.g. Strong silver-medalists 2025, Senior PMs healthcare.
  2. Apply that tag to relevant candidates, individually or via bulk action.
  3. Filter the database by that tag whenever you want to revisit the pool.

This gives you the same effect as named pools without the overhead of a separate management screen.

Re-engaging from a "pool"

When a relevant role opens:

  1. Filter the database by the relevant tag (or filter combination).
  2. Select candidates, click Add Candidates to Job, pick the job. They enter the new job's pipeline as sourced applicants.
  3. Or, click Send Email with a re-engagement template.

Discover candidates: AI matching from the database

The Discover candidates tab in the Add Candidates modal does this re-engagement automatically: it matches the entire candidate database against the open job and surfaces likely fits. Requires AI ranking permission and a target job.

What you don't get

To set expectations:

  • No CRUD interface for named pools.
  • No automatic re-population of pools based on rules (the way some ATS platforms have "dynamic talent pools").
  • No notifications when new candidates match a saved filter — re-run the filter when you want fresh results.

Tips

  • Use a small, consistent set of tags for talent-pool segmentation. Too many tags becomes noise.
  • Document your tag conventions so the team uses them consistently.
  • Refresh / prune your "pools" quarterly — drop tags from candidates who have moved on or asked to be removed.
  • Always check candidate consent before re-engaging — see GDPR and compliance.