Skip to main content

Recruiting & Hiring Pipeline

Two halves of one job: the roles Finance has approved, and the candidates actually moving through interviews for them.

Written by Schae Lilley

Where to find them

Sidebar → Talent

Who can see them

Recruiting Pipeline — leadership, or anyone given the Planning grant. Note that being an Admin is not enough, because the page contains candidate names. Hiring Pipeline — leadership.

Can you change data here?

Recruiting: no. Hiring: yes — approving a role writes to Finance's sheet.

How fresh is it?

Cached about 15 minutes; both pages have a sync button

Why they're together

An approved role and the candidates filling it are one piece of work. Before this, roles, salaries and approvals lived in a Finance spreadsheet while all the candidate movement lived only in Greenhouse, and nobody could see both at once.

  • Hiring Pipeline is the demand side: which roles exist, what they cost, and whether the team actually needs them.

  • Recruiting Pipeline is the supply side: how far along each role's candidates are and when someone could realistically start.

Signal links them automatically by job title, and shows you honestly when it can't.


Recruiting Pipeline

What it's for

One dashboard answering: which roles are open, how deep is each pipeline, who is close to an offer, and when could they start?

What you'll see

  • Summary cards — open roles, active candidates, candidates in interviews broken down by round, offers out, hires, and an unlinked count that turns amber when it isn't zero.

  • A funnel chart of the whole company's active pipeline by stage: pre-interview → 1st → 2nd → 3rd or later → offer → hired.

  • A roles table — one row per role with its division, department, geography, stage, salary, target hire date, candidate counts per round, offers, hires, and a badge showing how confidently it's linked to the Finance sheet.

  • Matched and Unmatched tabs, so roles Signal couldn't link are visible rather than hidden.

  • Expandable rows — click any role to see that job's real Greenhouse stages in interview-plan order, plus the late-stage candidates: name, current stage, days since last activity, offer status, and target start date.

  • Filters, sorting on every column, CSV export, and a Sync button that bypasses the cache.

How to use it

  1. Weekly pipeline review. Read the summary cards, then scan the funnel for the stage where candidates are piling up. That's your bottleneck.

  2. See who's close. Expand the roles that matter. Late-stage candidates appear by name with days since last activity — a high number on a final-round candidate is the thing to chase today.

  3. Forecast start dates. Each late-stage candidate shows a target start date: the offer's real start date if one is set, otherwise the offer date plus two weeks. Roles without offers fall back to the Finance sheet's target hire date.

  4. Reconcile the two systems. Check the Unmatched tab. Anything there is either a title mismatch to fix or a genuine gap between what Finance approved and what's being recruited for.

Good to know

  • Candidate names appear only from the second interview onward. Early-funnel applicants stay anonymous by design — their names are never even requested. This is deliberate, not a data gap.

  • Roles are linked by job title, and Signal handles the usual variations — seniority abbreviations, "paid media" versus "paid advertising", SEO versus organic search, trailing location suffixes. Below a confidence threshold it refuses to merge and flags the role as Greenhouse only or Sheet only instead. Nothing is merged by guesswork.

  • "Days since activity" is not time in stage. It's the last activity on the candidate's record. Greenhouse doesn't expose when a candidate entered their current stage.

  • A "×N" badge on a role means the Finance sheet carries several openings of the same title.

  • If one source is having problems, the page still loads whichever source is healthy and shows a banner naming the one that failed. The degraded result isn't cached, so recovery is immediate.

  • The interview-round counts classify each job's own stage names. A stage past the second-interview boundary with an unfamiliar name counts under "3rd or later".

  • Prospects and candidates moved to a different job are excluded from the funnel.

Common questions

Why does a candidate show as a number instead of a name? The name lookup missed, which is rare. The number is their Greenhouse ID.

Why is a role unlinked, or listed twice? The Finance sheet title and the Greenhouse job name were too different to link confidently. Signal shows both rather than merging them wrongly.

Why can't I see this page? I'm an Admin. Admin isn't enough here — the page contains candidate names, so it needs the Planning grant specifically, which leadership already has. Ask a Signal admin.

We need a new field to track this. Before requesting one, check the Req ID column — Signal already reads it. Most requests of this kind turn out to be a data-entry gap rather than a missing feature.


Hiring Pipeline

What it's for

Every proposed role sits next to a calculated verdict on whether that team is actually at capacity — so headcount conversations start from revenue data rather than from who argues best.

What you'll see

  • Two tabs — Power Digital and Cardinal (Healthcare).

  • Summary cards — open roles, approved, proposed, total salary, projected revenue impact, and a US versus international split.

  • A roles table with stage, salary, division, department and geography.

  • A Hiring Need verdict per role:

Verdict

Meaning

Valid Hire

The team is at or above its revenue-per-head target — the hire is justified

Review

Nearing capacity (roughly 85–99% of target)

Questionable

The team has open capacity — the ask deserves scrutiny

No Data

No target-tracked employees matched that department

  • An Approve button on proposed roles.

  • A Sync Sheet button, filters and CSV export.

How to use it

In headcount review, work down the proposed roles and read the verdict alongside the salary. "Questionable" means the team is below its revenue-per-employee target and the ask needs a real argument. "Valid Hire" supports approval.

Then approve directly from Signal.

What you can change — and it leaves Signal

Approving a role writes to Finance's hiring spreadsheet, setting the stage to approved and stamping today's date. That sheet is the system of record, so the approval is immediately visible to everyone using it. This is not a Signal-only flag.

Sync Sheet is a read-only refresh.

Good to know

  • The verdict is an input, not the decision. It compares the role's department and division against official targets using real revenue. It knows nothing about strategy, client commitments or someone leaving next month.

  • A role you just added may not appear. The sheet is cached about 15 minutes — click Sync Sheet. Also check the stage filter: it defaults to proposed and approved only, so other stages are hidden until you widen it.

  • The targets behind the verdict come from KPI Targets. If those are stale, so is the verdict.

  • It depends on the sheet's structure. Signal reads tab names, headers and the stage naming convention. A restructure of the sheet changes what Signal shows — worth a heads-up to the Signal team before reorganizing it.

Common questions

Does approving here change anything outside Signal? Yes — it writes directly to Finance's sheet. That's the point.

What do Valid Hire / Review / Questionable mean? See the table above. They compare the team's actual revenue per head against the official target for that role.

The role I just added isn't showing. Click Sync Sheet, and widen the stage filter.

Why can't I open these pages? Both need leadership-level access; Recruiting additionally accepts the Planning grant. See Who can see what.

Related

Did this answer your question?