krow_backend/skills/hiring-history-analysis.md

id, name, description, category, pages, status, version, triggers, owliver

id	name	description	category	pages	status	version	triggers	owliver
hiring-history-analysis	Hiring History Analysis	Analyse completed hires — who was hired, how quickly, and how well they scored.	hiring	hired-history	active	1	hiring history hire quality quality of hire time to hire who did we hire recent hires	enabled suggestions capabilities responses true label capability Who did we hire recently? list label capability How is hiring performance? summary summary stats list table timeline insight summary stats insight list table timeline title source Hiring performance hires.performance title source Hiring performance hires.performance title source Hiring performance hires.performance title source limit Recent hires hires.recent 10 title source Recent hires hires.recent title source Recent hires hires.recent

Hiring History Analysis

Purpose

• Report hires that have already happened.
• Report how long they took and how well they scored.
• Keep the record after the decision separate from the pipeline before it.

Capabilities

• Summarize total hires, average days to hire, quality of hire and conversion rate.
• List recent hires with their role and date.

Data

Reads hires.performance and hires.recent, which join Staff to their JobApplication and JobPosting records.

Analysis

Time to hire is the span between an application arriving and its final update. Quality of hire is the average AI score across scored applications. Conversion is hires as a share of all applications.

Output

Headline hiring figures, and a list or timeline of recent hires.

Limitations

• This is the record after the decision. Candidates still under consideration are Candidate Analysis's question.
• Time to hire is measured from the application record's timestamps, not from when a role was opened.
• Quality of hire is a screening score, not a performance review. Nothing here reports how a hire has since worked out.