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