Candidate Pipeline

Reqcore's pipeline gives recruiters a visual Kanban board to track candidates through hiring stages. Each job has its own pipeline view.

Pipeline Stages

Applications move through these stages:

New → Screening → Interview → Offer → Hired
                                     → Rejected (from any stage)

Kanban Board

Access the pipeline from any job's Pipeline tab. The board shows:

• Color-coded columns for each stage
• Candidate cards with name, email, and current status
• Drag-and-drop between columns to update status
• Click any card to open the candidate detail sidebar

Candidate Detail Sidebar

Clicking a candidate card opens a slide-over panel with:

• Status transitions — Move the candidate to the next stage
• Notes — Add recruiter/hiring manager notes
• Question responses — View answers to custom application questions
• Documents — View uploaded resumes and files
• PDF preview — Inline preview of PDF documents

Managing Candidates

Adding Candidates

Candidates can be added in two ways:

1. Public application — When someone applies through the public job page, a candidate record is automatically created (deduplicated by email within the organization)
2. Manual creation — Recruiters can add candidates directly from the Candidates section in the sidebar

Candidate Deduplication

Candidates are deduplicated by email within each organization. If a candidate applies to multiple jobs, a single candidate record is maintained with multiple application records.

Per-Job Candidates Table

The Candidates tab on each job shows a data table view (similar to Supabase's table UI) with:

• Sortable columns
• Click-to-open detail sidebar
• Bulk status overview

Applications

Creating Applications

Applications link a candidate to a job. They can be created:

• Through the public application form
• Via the "Apply candidate to job" modal from the job detail page
• Via the "Apply to job" modal from the candidate detail page

Unique Constraint

Each candidate can only have one application per job within an organization. This is enforced at the database level with a unique constraint on (organizationId, candidateId, jobId).

API Endpoints

Next Steps

• Application Forms — Configure custom questions per job
• Document Storage — Manage resumes and files
• Dashboard — At-a-glance hiring overview