CadreHiring
Ask better, read faster, decide on the record. Your own apply form, your own pipeline, and an assist on the reading that shows its work.
Three parts of Hiring. Each with a page of its own.
- PipelinesNamed pipelines with your own stages, and every applicant’s position through them, including the stages you deliberately skipped.
- Apply formsQuestion sets reused across postings, sections that become steps, and questions that only appear when they apply.
- The reading assistA rubric you write yourself, a score against each criterion with its reasoning, and a snapshot that keeps old runs comparable.
Ask what you actually need to know. A form built from your questions, not a template’s.
It’s copied onto the posting the moment you attach it, so refining the set later never disturbs one already taking applications.
- Question sets built once, attached to any posting
- Sections become steps, so the form can be finished
- A section or a question appears only when it applies
- Twelve kinds of answer, from yes/no to file upload
- A signed-in applicant reuses a document already sent
A pipeline you drew. Your stages, in your order, for the roles that need them.
Every posting picks a pipeline, defaulting to the one you set, and each applicant carries their own position through it, not a single shared status.
- As many named pipelines as you have kinds of hiring
- Your stages, in your order, marked review, interview or decision
- Each applicant’s own position: active, completed, skipped
- Notes and a 1–5 rating that outlive the meeting
- Source, campaign and referring page kept on every application
An assist on the reading. Not a verdict: a second pass that explains itself.
A rubric you wrote
Your criteria, your weightings, your scale, and your guidance on what a good answer looks like. Not a generic model of a good candidate.
It shows its work
A score against each criterion with the reasoning for it, a summary, and suggested next steps, not a number on its own.
Comparable later
Each run keeps a copy of the rubric and the posting it judged against, so refining your criteria doesn’t quietly rewrite old assessments.
On submit, or on demand
Have it run as applications arrive, or only when somebody asks for it. Either way the decision, and who made it, stays with your team.
Give hiring a system. The beta is open now.
No. They can apply outright. If they do sign in to your Hub (with a one-time email code, no password), they can follow where their application has got to and reuse documents they have already sent you.
Yes. Build as many named pipelines as you need, with your own stages in your own order, and pick one per posting. New postings start from your default.
No. It reads an application against the rubric you wrote and shows a score, its reasoning per criterion, and suggested next steps. Moving somebody forward is always somebody’s decision, and it is recorded as theirs.
Every submission carries two quiet checks: a hidden field that only an automated script would fill in, and how long the form actually took. Obviously automated submissions are flagged rather than quietly mixed in with the rest.