01
Role template
Start with a complete example.
Choose a public template for the role. Kit copies its stages into your account so you can adapt the names, instructions, reviewers, and timing.
Browse templates by role
Custom hiring process
Set every next step before the first application.
Start with a role template or an empty pipeline. Then decide what candidates see, what your team does, and what evidence closes each stage.
The process lives with the job, so everyone works from the same sequence while candidates get clear instructions for the step they are in.
Templates are starting copies. Each job keeps its own process.
One configured stage
Growth strategy work sample
01
Public promise
2–3 hours · Submit a short campaign brief
02
Private task
Review the launch plan, assumptions, and trade-offs.
03
Review rule
Score 4 criteria · 2 reviewers
Candidates get the context they need. Your review instructions stay with the team.
Choose your starting point
Start from a role, your own template, or an empty pipeline.
Use a proven role sequence, save your own reusable process, or assemble only the stages this hire needs.
02
Your template
Reuse the process your team trusts.
Save an account template for a hiring pattern you repeat, then apply a fresh copy whenever a new job opens.
03
Empty pipeline
Add only what earns a decision.
Build the sequence stage by stage. Use a short process for a narrow role or combine application, practical work, interviews, references, and offer.
12 stage types
Give each step one clear job.
Mix collection, assessment, conversation, and decision stages. The label explains the moment; the configuration decides what happens there.
Start the conversation
Collect the application and run an initial human screen.
Gather job-relevant evidence
Ask for written, existing, live, or newly produced work.
Set the context
Give candidates role or team context before asking them to continue.
Review and close
Bring the team together, check references, and send the decision.
Public promise. Private task.
Say enough to earn the candidate’s time.
A stage can have two different descriptions because candidates and reviewers need different context.
Candidates see
The promise before they commit.
Put the stage purpose, expected effort, and next step in the public description. It appears with the job and in candidate-facing progress updates.
Public description
You’ll prepare a short launch brief. Plan for two to three hours; we’ll review the thinking, not production polish.
Reached candidates see
The actual assignment when it is time.
Keep task materials, submission instructions, candidate-specific links, and deadlines in the private brief. Only candidates who reach and start the task can read it.
Private brief
Use the attached launch context. Submit a one-page plan, channel rationale, assumptions, and the first experiment you would run.
One stage holds the promise and the work. Candidates do not need access to reviewer notes or internal scoring rules.
Candidate point of view
The board is your view. This is theirs.
Candidates open one private link to see their application, the current step, the work they need to complete, and an interview slot when it is time to book.
What the candidate sees
A clear application timeline shows the current stage and what has already happened.
The candidate starts when ready, then reads the private brief and sees the deadline tied to that start.
Role-specific questions appear in the same portal, with answers saved against the application.
Available interview times appear only when the candidate reaches the scheduling step.
Consistent evidence
Configure the decision before you meet the candidate.
Add the reviewers and criteria while the role is still calm. The same questions and scale then follow every candidate through that stage.
Name the evidence
Define what a strong answer or submission should demonstrate. Give criteria weights when some signals matter more than others.
Assign the people
Put the right reviewers on the stage and decide whether every reviewer or a vote threshold is required.
Record the call
Keep scores, written evidence, and the advance or reject decision connected to the candidate and stage that produced them.
A template can carry the structure. Your team still owns the role-specific bar and every hiring decision.
A deliberate boundary
Templates start jobs. They do not silently rewrite them.
Applying a template makes a copy of its stages for that job. Edit the live job when this search needs to change; edit the template when future jobs should start differently.
Template
The reusable starting point
becomes a copy for
Open job
The stage sequence used by this job
That separation prevents a template cleanup from changing instructions or deadlines in an active search.
Configuration that can travel
Use the screen. Keep YAML and MCP for repeatable work.
Most teams can choose a starter and edit the job’s stages in Kit. Technical teams can also keep a process in YAML or create a template through Kit’s MCP tools.
YAML
Review the whole process as text.
Export a job configuration, keep it with your hiring notes, and use it as a reviewable record of stage order and settings.
MCP
Ask your coding agent to create the draft.
Kit’s hiring tools can create an account process template from a structured definition. A hiring admin can review and edit it before it is used.
YAML and MCP are optional. Candidate communication, reviewer judgment, and the final decision stay with your team.
Before you configure
Process template questions
Does a process template lock every job to the same pipeline?
No. Applying a template creates stages for that job. You can change the live job without changing the template, and template edits affect only jobs created from it later.
What does a candidate see?
Candidates see the public description, their application progress, and the instructions for the stage they have reached. Private task details appear only after they reach and start that task.
Can different roles use different hiring processes?
Yes. Start with a role template, save an account template for a process you repeat, or build a job from an empty pipeline.
Do I need to write YAML?
No. Choose a starter and edit the job’s stages in Kit. YAML and MCP are optional ways to keep or create a reusable process definition.
Build the process before candidates enter it.
Choose a role template, make the candidate promise explicit, and give every reviewer the same decision frame.
$8€6,9929,99 zł£5.99 per member/month · every hiring stage included
Start hiring free