hiring

An interview loop, rubrics with anchored levels, debriefs with evidence before votes, and the profile of the person who takes over the platform.

• Version 0.1.0
• 4 skills
• 1 gate check
• Running on this site: No public page yet

What it does

Structured hiring for engineering roles. A loop for a role is built from the outcomes the person must deliver: the outcomes give a short list of signals, and each signal is collected once, in one stage. Each signal has a rubric dimension with fixed questions and four levels, and each level has an anchor that describes observable behaviour. The rubric is written before the first interview. In the debrief, every interviewer submits evidence and a level before seeing other scores, the discussion starts with the evidence, and the decision comes last with its reasons on record.

The module also writes the profile of the next platform owner: the systems in the repository that person will own, the skills each system needs, and where in the loop a candidate shows each skill.

The skills prepare, check and record. Interviewers score and the panel decides; no skill scores a candidate.

Install

Add the marketplace at release v0.1.0 once, then install the plugin and restart Claude Code.

claude plugin marketplace add uncovertechtalent/cto-powersuit#v0.1.0
claude plugin install hiring@cto-powersuit

Skills

• /hiring:hiring-debrief

  Run a hiring debrief with evidence before votes: each interviewer writes evidence and a level per rubric dimension before seeing other scores, the debrief goes through the evidence first, the levels after it, and the decision comes last and is recorded with its reasons and any dissent.

• /hiring:interview-loop

  Design the interview loop for one role and write hiring/loop.md: the outcomes the role must deliver, the signals that predict them, the stages, the interviewer role in each stage and the signal each stage collects, with each signal collected once, in one stage.

• /hiring:interview-rubric

  Write the structured scoring rubric for a role in hiring/rubrics/<role>.json: one dimension per signal in the loop, each with its stage, fixed questions and levels 1 to 4 whose anchors describe observable behaviour, plus the hire bar, all written and frozen before the first interview.

• /hiring:successor-profile

  Write docs/successor-profile.md, the profile of the person who takes over the platform: the systems they will own, read from the installed modules and the docs in the repository, the skills each system needs, and the interview stage and rubric dimension where a candidate shows each skill.

Gate checks

The checks this plugin adds to the deploy gate of the gate module, each with a pass fixture and a fail fixture:

• hiring.rubric-anchors

Source

The CTO powersuit is a set of agent skills, one module per CTO function from the deploy gate to the hand-over, that one person uses to run a company's whole engineering platform. hiring is one of its 18 plugins, published by Stefan Coetzee.

The skills, templates, checks, fixtures, and the full README of hiring at release v0.1.0: github.com/uncovertechtalent/cto-powersuit/tree/v0.1.0/plugins/hiring. License: MIT. Every plugin of the powersuit: CTO powersuit.