Files
krow_backend/skills/hiring-pulse-analysis.md
2026-08-28 12:21:44 +05:30

89 lines
2.3 KiB
Markdown

---
id: hiring-pulse-analysis
name: Hiring Pulse Analysis
description: Read the recent rhythm of hiring — applications arriving, and how the funnel is converting.
category: hiring
pages:
- control-center
- analytics
status: active
version: 1
triggers:
- hiring pulse
- hiring velocity
- hiring rhythm
- application rate
owliver:
enabled: true
suggestions:
- label: What is the hiring pulse?
capability: summary
- label: Applications over recent periods
capability: flow
capabilities:
- summary
- flow
- stats
- insight
responses:
summary:
title: Hiring pulse
source: candidates.activity
periods:
- today
- last-7-days
- previous-month
flow:
title: Applications over time
source: candidates.activity
periods:
- today
- last-7-days
- this-month
- previous-month
stats:
title: Hiring performance
source: hires.performance
insight:
title: Hiring performance
source: hires.performance
---
# Hiring Pulse Analysis
## Purpose
- Report the recent rhythm of hiring: how many applications are arriving, and
how the funnel is converting them.
- Distinguish a quiet week from a broken pipeline.
## Capabilities
- Count applications arriving across recent periods.
- Report conversion, speed and quality of hire.
## Data
Reads `candidates.activity` for arrival counts over periods, and
`hires.performance` for conversion, time-to-hire and quality.
## Analysis
Arrival counts are reported per period rather than as a single rate, because a
rate averages away the shape — thirty applications in a month is a different
situation depending on whether they arrived steadily or all on one day.
## Output
Applications per period, and headline conversion, speed and quality figures.
## Limitations
- **This is the analysis definition only.** The Hiring Pulse card that appears
on Krow pages is a separate UI configuration with its own placement and
period settings; the two are deliberately not the same definition and changing
one does not change the other.
- Arrival counts are by application creation date, not by when a role opened.
- A period with no applications reports zero, which is a real reading — it does
not distinguish "nobody applied" from "the role was not advertised".