> For the complete documentation index, see [llms.txt](https://docs.leapwise.co/backend-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leapwise.co/backend-handbook/life-at-leapwise/onboarding-process.md).

# Onboarding process

The onboarding process is a crucial step in the "life cycle" of every individual joining a new position. Aware of this fact, at Leapwise, we conduct the onboarding process through educational one-on-one conversations between all current team members and the new person.

The purpose of such onboarding conversations is for each team member to briefly introduce what they do and what projects they are working on to the new person.

This way, from day one, the new individual develops a more personalized relationship with their new colleagues, gains a deeper understanding of the logic behind business processes, and obtains a clearer picture of where their skills are needed in the overall process.

The onboarding process lasts for approximately seven days. Besides the onboarding from colleagues, each person gets a dedicated mentor.

We also have an **internal onboarding handbook** so everyone can go back to crucial information in case they forget what they heard during the onboarding. 🙂

<figure><img src="/files/daX9sNofIe3k9gJxJ7ul" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://docs.leapwise.co/backend-handbook/life-at-leapwise/onboarding-process.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.