Pushing sourced candidates into a job

The four paths

Sourced candidates can flow into a job's pipeline through four built-in paths. All target a specific job (the destination is set when you start the import).

Path 1 — People Search import

From People Search (per-job):

1. Run a search.
2. Open a profile in the Detailed Profile Modal.
3. Import the person — the candidate is created with source and linked to the current job.

Path 2 — Find on web

From the Add Candidates modal's Find on web tab:

1. Confirm the target job at the top of the modal.
2. Pick a source tab (Resume Files, LinkedIn, GitHub, Behance, Stack Overflow).
3. Run the search; results render as profile cards.
4. Tick the candidates you want and click Import (the button has a cloud-download icon).

Imported candidates land in the selected job's pipeline.

Path 3 — Find on GitHub

From the Add Candidates modal's Find on GitHub tab (only available when adding to a specific job):

1. Search by query, location, language, repos, followers.
2. Pick the candidates you want.
3. Save / import them; they enter the target job's pipeline.

Path 4 — Discover candidates (AI matching from your DB)

From the Add Candidates modal's Discover candidates tab (requires AI ranking + a target job):

1. Confirm the target job.
2. Apply optional filters: Date Added, Tags, Jobs.
3. Click Find Candidates.
4. CVViZ scans your existing candidate database and surfaces candidates the AI thinks match this job.
5. Add the strong matches to the job's pipeline.

Bulk add from the candidate database

If candidates are already in your database (via past jobs, CSV import, etc.), use the bulk path:

1. Open the Candidate Database at the candidate database.
2. Filter to the candidates you want (tag-based filtering works well).
3. Bulk-select them.
4. Click Add Candidates to Job and pick the destination job.

How sourced candidates are marked

The frontend marks candidates imported via People Search with. Candidates from Find on web, Find on GitHub, and Discover candidates don't get an explicit "sourced" source tag in the frontend — the source on the candidate carries whatever value the backend assigned (usually based on the entry path).

What stays with the candidate

When you push a sourced candidate into a job:

• All previous notes, tags, and timeline activity carry over.
• Resume(s) on file stay attached.
• Stage automations on the destination job fire (e.g. an automation might send an introductory email).

If the candidate is already in another job

CVViZ doesn't block adding the same candidate to multiple jobs. They appear in each job's pipeline. Reporting can break this down per job.

Tips

• Tag sourced candidates with the campaign name for attribution and re-engagement later.
• Send an intro email manually right after importing — the automated stage-entry email (if you have one configured) may be too generic for a sourced reach-out.
• Check the candidate's existing record before importing — if they applied before, you don't want to send a duplicate cold email.