2.3 KiB
2.3 KiB
id, name, description, category, pages, status, version, triggers, owliver
| id | name | description | category | pages | status | version | triggers | owliver | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| hiring-pulse-analysis | Hiring Pulse Analysis | Read the recent rhythm of hiring — applications arriving, and how the funnel is converting. | hiring |
|
active | 1 |
|
|
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".