Pyro writes down what good looks like for a role, once. Everything that follows is measured against that line, and everything that happens is written to a record you can open. Here is what you do at each stage, what Pyro does, and what you are left holding.
Every role starts with one document: what good looks like. Pyro drafts the posting with you, grades it section by section, and turns the essentials into a short list of criteria. That list is the line every later stage is held to.
Describe the role in your own words, or paste what you already have.
Drafts, grades and fixes the posting. Refuses to publish a line the bias gate catches. Writes the criteria down once.
A posting you can publish, and a standard the rest of the process will be measured against.
Connect the shared drive your CVs already live in. Pyro reads them for what they say, not for keywords, so a search for someone who has run production Kubernetes finds the engineer whose CV never used the words in your job title.
Connect the drive. Ask for the person you need, in a sentence.
Reads every CV for meaning, ranks the matches and highlights the exact line that qualifies each one.
Candidates you already had, surfaced with the sentence that makes the case.
For each criterion the standard set, Pyro either quotes the line from the CV that evidences it, or marks it unanswered. Nothing is inferred from a missing word. An unanswered criterion becomes a question for the interview, not a rejection.
Read the evidence, not just the number. Decide who goes forward.
Scores against the criteria, quotes its sources, turns the gaps into interview questions.
A shortlist where every score can be checked, and a question list for the next round.
ARIA is Pyro's first-round interviewer. It asks the questions the screen left open, and it does not accept a thin answer: what was the metric before, what was it after, what did you change. The score moves only on a quoted, timestamped answer.
Invite the candidate. Set the scope they are asked to consent to.
Runs the round, transcribes it, updates the evidence, and writes the round to the record.
A first round for every shortlisted candidate, with the answer that moved the score and the minute it moved.
A person interviews. The copilot sits beside them, visible only to them: questions retire as they are asked, follow-ups are drafted from what the candidate just said, and the case is assembled while the conversation is still going.
Interview. Decide.
Keeps the question list, drafts the follow-up, tracks which criteria are now evidenced.
A case assembled in the room, and a decision that is yours and recorded as yours.
Every action on an application is a row: who decided, on what evidence, which model, and the candidate's consent as a signed row at the top. It is one screen, not a reconstruction after the fact.
Open it when a candidate, a client or a regulator asks why.
Writes every row as it happens. Cannot be talked into skipping one.
An answer to “why” for every decision, kept for as long as you need it.
Candidates get one profile that follows them to every role on Pyro. They see the same evidence the recruiter sees, where they stand, and what changed after their interview. Consent is theirs to sign and theirs to withdraw.
Nothing extra. The portal is the same record, shown to the other party.
Tells the candidate on every stage change. Honours a withdrawal at the database.
Candidates who know where they stand, and fewer “any update?” emails.
Book a demo. We run the whole line on a real role of yours, in front of you.
The shared drive your CVs already live in. There is nothing to re-type.
Write the standard, search, screen, interview. The record grows from the first action.
Bring one open role and the drive you already have. We will run the whole line in front of you.