Creating and editing Hiring Pipelines

Build custom hiring workflows from the master stage catalog and reuse them across jobs.

Where to manage

Settings β†’ Hiring Pipelines. Permission required: matching settings access.

The page header is Hiring Pipelines β€” "Create and manage custom hiring workflows for your recruitment process". The icon is a chart symbol.

Creating a pipeline

  1. Click Add Hiring Pipeline in the top-right.
  2. The modal title reads New Hiring Pipeline.
  3. Fill in:
    • Workflow Name β€” e.g. "Engineering β€” IC track", "Sales β€” closer".
    • Department β€” optional scoping.
    • Location β€” optional scoping.
    • Steps β€” pick from the master stage catalog and order them.
    • Default β€” checkbox; one pipeline can be default.
  4. Save.

Building the steps

The pipeline editor (the WorkflowEditor component, with a PipelineStages sub-editor) lets you select stages from the master catalog. You can:

  • Add stages in any order.
  • Include sub-stages (parent_progress_id-based) for fine-grained tracking.
  • Re-order via drag.

You don't invent new stages here β€” they come from CVViZ's catalog so reporting stays comparable across pipelines. (See Pipelines explained for the catalog.)

Editing an existing pipeline

  1. From the Hiring Pipelines list, click the pipeline.
  2. Modal title becomes Edit Hiring Pipeline.
  3. The "View Pipeline Stages" expansion panel shows the current stage list.
  4. Update stages, name, or scoping.
  5. Save.

Deleting a pipeline

Click the delete icon on a pipeline row. CVViZ asks for confirmation: "Are you sure you want to delete this hiring pipeline?" with the line "Hiring Pipeline: {workflow_name}".

Be careful β€” deleting a pipeline that's in use can affect existing jobs.

System default vs user default

  • is_system_default β€” CVViZ's shipped baseline pipeline. Always present, can't be deleted.
  • is_default β€” your custom default; saved with localStorage key. New jobs use it unless overridden.

Scoping by department / location

Each pipeline can be scoped via and location. Scoped pipelines surface for jobs matching that department or location, making the right pipeline easier to pick when creating a job.

Common pipeline shapes to start with

  • Generic β€” New β†’ Phone Screened β†’ Interviewed β†’ Job Offered β†’ Offer Accepted β†’ Joined.
  • Engineering β€” adds a Take-home and a Tech Interview between Phone Screened and Interviewed.
  • Sales β€” adds a Mock Pitch round in the interview block.
  • Volume / hourly β€” collapse to: New β†’ Phone Screened β†’ Interviewed β†’ Job Offered β†’ Joined.

Best practices

  • Don't create one pipeline per role β€” group similar roles under shared pipelines.
  • Tighten over time β€” drop sub-stages your team doesn't actually use.