Dashcipe
Back to recipes
Previous dashboardNext dashboard
OperationsIntermediateFree during launch

HR Recruiting Dashboard

A recruiting dashboard for candidates, interviews, offers, and time-to-hire.

50 minHTML / Tailwind / Chart.jsRecruiting lead

Recipe Workspace

Preview the layout, understand the KPIs, copy the starter

Review the dashboard at a practical desktop ratio first, then use the KPI rationale, code starter, and AI IDE prompt below.

Live Recipe Preview

HR Recruiting Dashboard

A recruiting dashboard for candidates, interviews, offers, and time-to-hire.

Free launch recipeOpen live view

Live Recipe

HR Recruiting Dashboard

A recruiting dashboard for candidates, interviews, offers, and time-to-hire.

Overview · Free launch recipe
Dark CRMdensesidebardark sidebarpipeline cardsactivity feed

Candidates

18,420+8.2%

Interview rate

34.8%+2.1%p

Offer rate

$84.2K+12.4%

Time to hire

ReadyTracked

Candidates trend

Nivo

Pipeline Activity

Visx
1

Candidates

Sample data

18,420
2

Interview rate

Sample data

34.8%
3

Offer rate

Sample data

$84.2K

Watch List

CandidatesWatch
Interview rateWatch
Offer rateWatch

Detail Table

Candidates

Sample data

18,420

상태

Interview rate

Sample data

34.8%

상태

Offer rate

Sample data

$84.2K

상태

Top

Four KPI cards

Middle

Primary trend and segment view

Bottom

Priority table and alerts

KPI Ingredients

Candidates

Candidates belongs in the primary row when an owner can act on it this week.

Alternative KPI: Candidates segment

Interview rate

Interview rate belongs in the primary row when an owner can act on it this week.

Alternative KPI: Interview rate segment

Offer rate

Offer rate belongs in the primary row when an owner can act on it this week.

Alternative KPI: Offer rate segment

Time to hire

Time to hire belongs in the primary row when an owner can act on it this week.

Alternative KPI: Time to hire segment

Code Starter

Copy component starter

const metrics = [
  { label: "Candidates", value: "18,420", change: "+8.2%" },
  { label: "Interview rate", value: "34.8%", change: "+2.1%p" },
  { label: "Offer rate", value: "$84.2K", change: "+12.4%" }
];

export function HrRecruitingDashboardPreviewCards() {
  return <section className="grid gap-3 md:grid-cols-3">{metrics.map((metric) => <article key={metric.label} className="rounded-xl border border-zinc-200 bg-white p-4"><p className="text-xs font-bold text-zinc-500">{metric.label}</p><strong className="mt-1 block text-2xl font-black">{metric.value}</strong><span className="text-xs font-black text-emerald-600">{metric.change}</span></article>)}</section>;
}

AI IDE Prompt

Paste into your AI IDE

Create a HR Recruiting Dashboard. Put KPI cards for Candidates, Interview rate, Offer rate, Time to hire, trend and segment charts, a priority table, and empty/loading/error states.

Decision System

Why this dashboard should exist before it is designed

AdSense-quality pages need original explanation, not only screenshots. This section documents the decision, data model, failure patterns, and implementation alternatives.

Operating decision

HR Recruiting Dashboard answers this operating question: Where does the recruiting funnel slow down?. The primary row is not a vanity summary; it decides what an owner should do this week.

The recipe is designed for Recruiting lead, Early product builders who need to choose data definitions, chart priority, and bottom-row actions quickly.

Data sources and event definitions

  • ATS candidates, interview stages, offers

Before implementation, define event names, owner, refresh cadence, and missing-data behavior for each source.

Required KPIs and removal rules

Candidates

Candidates belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Candidates segment

Interview rate

Interview rate belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Interview rate segment

Offer rate

Offer rate belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Offer rate segment

Time to hire

Time to hire belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Time to hire segment

Common failure patterns

Treat isolated movement in Candidates as a signal to inspect data definitions or operating bottlenecks.

Treat isolated movement in Interview rate as a signal to inspect data definitions or operating bottlenecks.

Treat isolated movement in Offer rate as a signal to inspect data definitions or operating bottlenecks.

Treat isolated movement in Time to hire as a signal to inspect data definitions or operating bottlenecks.

Alternative layout

For an MVP, keep Four KPI cards. As data matures, expand Primary trend and segment view into segment comparison or cohort analysis.

Implementation Blueprint

KPI audit protocol before implementation

Use this table before designing the UI. Without a formula, review cadence, and action trigger, a dashboard can look polished but still fail to support an operating meeting.

Candidates

Candidates = source event aggregate / comparison baseline. Start segmentation by Candidates segment.

Daily morning

If Candidates moves more than 10% week over week, inspect the causal segment and action table together.

Interview rate

Interview rate = source event aggregate / comparison baseline. Start segmentation by Interview rate segment.

Weekly review

If Interview rate moves more than 10% week over week, inspect the causal segment and action table together.

Offer rate

Offer rate = source event aggregate / comparison baseline. Start segmentation by Offer rate segment.

After campaign end

If Offer rate moves more than 10% week over week, inspect the causal segment and action table together.

Time to hire

Time to hire = source event aggregate / comparison baseline. Start segmentation by Time to hire segment.

Monthly report

If Time to hire moves more than 10% week over week, inspect the causal segment and action table together.

Event and table starter

When starting from an AI IDE, lock event and table names first. It makes generated components and queries much more consistent.

hr_recruiting.viewed

Source event for Candidates. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

hr_recruiting.converted

Source event for Interview rate. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

hr_recruiting.risk_flagged

Source event for Offer rate. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

hr_recruiting.resolved

Source event for Time to hire. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

Weekly review sequence

  1. 1Separate whether the Candidates movement is a real operating issue or short-term noise.
  2. 2Read it with Interview rate to narrow the cause to acquisition, conversion, quality, or throughput.
  3. 3Use the bottom table to choose one owner, one segment, and one action for this week.
  4. 4At the next review, adjust the layout based on recovery after the action, not on the same chart alone.

Frequently asked questions

Which KPIs should HR Recruiting Dashboard prioritize?

HR Recruiting Dashboard should prioritize Candidates, Interview rate, Offer rate, Time to hire. Keep Candidates in the primary row only when an owner can act on it this week.

What data sources are required?

ATS candidates, interview stages, offers are the baseline sources. Define event names, refresh cadence, owner, and missing-data behavior before implementation.

Can this layout be used for an MVP?

For an MVP, start with Four KPI cards and Primary trend and segment view. Add bottom tables and alerts when operating actions become clear.

Which metrics should be removed?

Remove metrics that cannot trigger an action within one weekly review cycle, have unstable definitions, or behave like vanity metrics without adjacent context.

How should the AI IDE prompt be used?

Use the prompt as a starting point, then add real field names, table names, state UI requirements, and accessibility requirements for your project.

Market Pattern

Marketplace-proven dashboard pattern, rewritten for Dashcipe

This section documents the public preview pattern behind the layout and how Dashcipe changes it into original KPI guidance.

dark-crm-suite / dark
dark sidebarpipeline cardsactivity feeddeal table

Observed pattern

CRM and project templates often use dark sidebars, pipeline cards, activity feeds, and priority tables for dense workspaces.

Dashcipe adaptation

This recipe maps those ideas to bottlenecks, owners, and next actions for the vertical.

Originality guard

It extracts general CRM patterns visible in public previews without pixel-copying any original layout.

Free Resources

What you can use for free

Use the KPI logic, layout, code starter, prompt, Figma SVG, schema, and tokens directly.

requestRequest/VotepromptAI PromptKPI logicAI promptRequest queue

Use this recipe when

  • The vertical metrics are already roughly known
  • You need to prioritize charts and tables quickly

Skip this recipe when

  • No events or data definitions exist yet
  • You only need a marketing landing page

Expert Notes

How a real operator should read these KPIs

These notes turn each metric into an operating decision, data source, and removal rule.

Recruiting lead

Why it matters
Candidates is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Candidates as a signal to inspect data definitions or operating bottlenecks.
Data source
ATS candidates, interview stages, offers
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Recruiting lead

Why it matters
Interview rate is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Interview rate as a signal to inspect data definitions or operating bottlenecks.
Data source
ATS candidates, interview stages, offers
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Recruiting lead

Why it matters
Offer rate is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Offer rate as a signal to inspect data definitions or operating bottlenecks.
Data source
ATS candidates, interview stages, offers
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Recruiting lead

Why it matters
Time to hire is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Time to hire as a signal to inspect data definitions or operating bottlenecks.
Data source
ATS candidates, interview stages, offers
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Recipe Flow

Move through recipes without returning to the list

All recipes
Previous recipeSupport Ticket DashboardA support starter kit for SLA, backlog, first response, and repeat issues.Next recipeLMS Course DashboardAn LMS dashboard for enrollment, completion, assignments, and churn risk.

Related Recipes

Similar dashboard recipes

Recipes from the same category or stack.

bootstrap-analytics
Free resourceBeginner

AdMob Revenue Dashboard

Is a revenue drop caused by traffic, pricing, or placement?

Free downloadQuality checkedStarter KitNext.js3 screensSchemaFigma SVGNext.jsTailwindChart.js
Market patternbootstrap-analytics
Layout: topbarSurface: lightstat cardsbar chart
4 KPIsDetails
enterprise-suite
Free resourceIntermediate

GA4 App Analytics Dashboard

Where do users come from, convert, or drop off?

Free downloadQuality checkedStarter KitNext.js3 screensSchemaFigma SVGNext.jsTailwindRecharts
Market patternenterprise-suite
Layout: splitSurface: hybridKPI rowtrend chart
4 KPIsDetails
ops-workbench
Free resourceBeginner

Play Console Operations Dashboard

Where does store quality change appear first?

RequestableHTMLTailwindChart.js
Market patternops-workbench
Layout: sidebarSurface: darkstatus wallmap/list panel
4 KPIsDetails