Recruiting tracks the whole funnel — requisitions, candidates, stage targets, scorecards, offers — and puts a number on what goes wrong: days open per req, candidates past their stage target, and a drop-risk score on every live offer.
The most expensive row on the overview is not a hire. It is an offer out 11 days with no reply, scored 72% drop risk and priced at $128K. Pipelines fail quietly; this one says so.
recruiting.cedxsystems.com — live build
Runs on demo data. The workspace names itself Northline Talent · Q3 2026 on screen.
36 open requisitions60 openings left across them · 13 flagged P0
249 active candidatesof a 320 total pool · average score 68 of 100
22 offers out10 scored high drop risk · top of board 86%
What it is
Reqs, stages, and the offers that wobble.
Every req shows fill, pipeline and age
Forty-eight requisitions with department, level, status, fill, pipeline count, days open, priority and owner on every row. An SDR req at 0 of 2 with 96 days open reads next to a Staff Platform Engineer at 0 of 1 with 12 in pipeline — and 13 reqs carry a P0 flag.
Open · Filled · On hold statuses with owner
Average 42 days open across open reqs
P0–P2 priority on every row
recruiting — screen-2
Stage targets, not stage vibes
Each of the 249 in-process candidates shows days in stage against that stage's target — 20 days against a 6-day phone target, 17 against 5 at onsite. Eighty-six are past target and flagged for advance or reject, which is where pipelines usually hide their dead weight.
86 candidates past stage target, flagged
Average 6 days in stage across all active
Candidate list or by-stage view, one toggle
recruiting — screen-4
A drop-risk score on every live offer
The offer-drop predictor scores all 22 live offers against base salary — 86% on a $106K base at the top of the board. Beside it, the alerts price the rest of the funnel: an interviewer at 158% of load cap, a P0 req open 67 days, 47 scorecards past due.
22 offers out · 10 high drop risk
Interview load 9.5h booked against a 6h cap
Hire target health ring at 100% filled
recruiting — overview
Product tour
Four screens, captured from the running build.
Not a mockup and not a concept deck. This is what opens at /app/recruiting.
recruiting.cedxsystems.com
01 — Overview
The funnel brief, with its failures priced
Thirty-six open reqs, 249 active candidates, 62 filled against the QTD target, a 26-day average time-to-hire, 22 offers out and an interview load flagged overloaded. The stage bars read Applied 47, Screen 48, Phone 49, Onsite 44, Offer 61.
249 active by stage, five bars
Offer-drop predictor with base salary and drop %
47 scorecards past due, called out as an alert
02 — Reqs
48 requisitions, aged and owned
Search and filter by department chip across 48 reqs. The columns that matter are all on one row: fill, pipeline, days open, priority, owner — so a P0 req with 18 in pipeline and 87 days open is a row you can act on, not a report you request.
60 openings left across the 36 open reqs
Level from M2 to Director, IC4 to IC5
CSV of the filtered view
03 — Candidates
A 320-person pool, scored
The full pool with stage, score, days in stage, rating and owner per candidate — average score 68 across actives. Source chips split inbound, referral, agency and sourcing, and 40 candidates ageing past 10 days in stage are flagged for a nudge.
The pipeline view sorts by days in stage against target: 20 days against a 6-day target at phone, 19 against 5 at applied. Eighty-six candidates sit past target — the screen's own label is “need advance or reject”.
In-stage shown as days vs target, e.g. 20d/6
86 past stage target in view
Stage chips from Applied to Offer
Who runs it
Three roles keep the funnel honest.
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Talent operations
Owns the req board: 36 open, 13 at P0, average 42 days open. The 47 overdue scorecards are their chase list.
36 reqs · 13 P0
Hiring manager
Reads the pipeline by stage target, not by feel — and gets the nudge when their candidate sits 20 days in a 6-day stage.
86 past stage target
Recruiting coordinator
Lives in the interview load: 9.5 hours booked against the 6-hour cap is why scorecards go overdue.
load 158% of cap
The shape of it
What the demo workspace actually looks like.
Every figure below is legible in the captures above. Nothing here is a projection of your funnel — it is the state of the demo data.
36open requisitions48 total · 60 openings left
320candidates in the pool249 active · average score 68
26daverage time-to-hirehired this quarter
40candidates ageing >10 daysflagged “need nudge” in the pool
Active candidates by stage249 in process · overview stage bars
Applied47
Screen48
Phone49
Onsite44
Offer61
Offer-drop predictor, highest in viewbase salary · drop risk %
$106K base86%
$161K base76%
$128K base72%
$137K base68%
$170K base62%
Hire target health42 roles QTD · filled 62 · openings left 60
100%
Filled QTD 62 against the 42-role target
Aging in stage >10d: 40 · high-drop offers: 10
How it runs
A hire's life, in the order it actually happens.
01
Open
A requisition starts with level, priority and owner — 13 of the 36 open reqs carry P0 — and starts counting days open immediately.
02
Source
Candidates enter tagged by source — inbound, referral, agency, sourcing — and join a pool scored 0–100 with an owner on every row.
03
Advance
Each stage carries a target in days. Slip past it and the pipeline flags the candidate for advance or reject — 86 in the current view.
04
Close
Offers go out with a drop-risk score attached. The 86% risk on a $106K base is a prompt to act, not a post-mortem.
One record
The hire becomes the person the estate already knows.
Recruiting does not end at offer-accept. The record hands forward into the products that run the employee.
Finding this out on the third call is worse for you than reading it here, and worse for us.
Recruiting is not generally available. What opens today is the live build on demo data — Northline Talent · Q3 2026 in the captures is the demo workspace, not a customer.
We have no named customers to show you, so this page shows none. Candidates and owners in the captures are synthetic demo records.
The offer-drop predictor and candidate scores are demo models over seeded data. We are not claiming a validated prediction of your offer outcomes.
Source chips in the captures — inbound, referral, agency, sourcing — are demo data. We are not claiming live job-board distribution from these screenshots.
Scorecard and interview-load tracking is visible; no claim is made here about structured-interview bias auditing or any certification.
No audit or compliance certification has been issued for Recruiting. What we can evidence about hosting and access is on the security page.
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/recruiting. It runs on demo data, which the workspace labels on screen.
What does the offer-drop predictor actually show?
A risk percentage per live offer next to its base salary — 22 offers in view, 10 flagged high risk. It is a demo model over seeded offers, shown because it is legible in the capture, not because we claim it predicts your outcomes.
How does the pipeline stop candidates stalling?
Every stage has a target in days. Candidates past target — 86 of 249 in the demo — are flagged “need advance or reject” and sortable by days over, so a stalled funnel is a list, not a feeling.
What counts as interview load?
Hours booked against a cap, per interviewer. The demo alert shows 9.5 hours booked against a 6-hour cap — 158% — alongside the 47 scorecards sitting past due because of it.
Is Recruiting audited or certified?
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
The pipeline is running. Go and look at it.
Live build, demo data, no card. Then check the drop-risk score on the offer you sent last week.