> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/tech-lead-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/tech-lead-handbook/hiring/hiring-process.md).

# Hiring Process

## The What

The **end-to-end** process of hiring a developer - from "looking to hire" to "hired".

## The How

### [Prepare a Hiring](/tech-lead-handbook/hiring/prepare-a-hiring.md)

### Publish a Job Ad

1. Raise it in the Application Tracking System (ATS)
2. Go through the approval process in ATS (nudge people to accelerate the process)
3. Go Live
4. Share in your network: LinkedIn, Meetups, etc

### Interview

1. Decide an interview process, for example
   * First Round: background, experience, projects, hard skills
   * Take-home assignment
   * Second Round: present back, comment, challenge, and cultural questions
2. [Shortlisting](/tech-lead-handbook/hiring/shortlisting.md)
3. Prepare questions and tailor questions for each candidate
4. Track your feedback
5. Debrief with your hiring team
6. Make a decision - progress or reject 👍 👎

### Checks :mag:

* Reference check
* Policy check
* Psych test

### Offer

1. Offer negotiation - TA
2. Offer signed 🎉

### Preboarding

1. Meet and Greet
2. Issue hardware
3. Book a casual team huddle (optional)
4. Set up accounts - IT

### Onboarding

1. Grant permissions for internal software
2. Set up email lists, slack channels, workspace, groups, etc
3. Technical Induction
4. Warm-up code and documentation

## :white\_check\_mark: Exceptions

{% hint style="success" %}
Internal candidates\
Referrals
{% endhint %}

## :red\_circle: Red Flags

{% hint style="danger" %}
Slow response\
Long process
{% endhint %}

## :scroll: Tips

* Keep the process short
* Quick response
* Make CV screening part of your daily routine
* No perfect candidate

## :hole: Pitfalls

* Perfectionism


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jamiewen00.gitbook.io/tech-lead-handbook/hiring/hiring-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.