Onboarding

One person will be attributed to the onboarding, usually this will be Mael.

Before the day

Create an account in Google workspace, and add it the the relevant organisational unit and groups. Don't click on send credentials, add them to the welcome email.
(If this is a permanent employee) Send over their computer
Invite the account to the various tools the person will use
Organise a welcome meeting on the first day. This meeting WILL be half a day long so make sure you have the time freed up.
Finally send them the welcome email (template is available in Gmail)

On the first day

So this is the half-day long meeting. Whenever possible this should be done in person. The goal of this meeting is to ensure the new comer is aware of this handbook, ready to work and aware of our compliance terms.

If this is a permanent employee, go through the Linux installation steps
While Linux is being set up, go through the handbook, make sure the person is aware of it
Make a brief on the security and why it's important
Explain how we work, how we communicate and how the week is planned
Once linux is set up, ensure the Google workspace account is functional, ensure the person also has access to the tools we use for work
This is finally the time to go through every tool the person is going to use, explain how we use them, and why.
(most importantly) Take notes about what went well and what can be improved in the onboarding process, and come back edit this document accordingly

For engineers

There are some additional steps needed to onboard engineers:

Explain the project structure, and how to start development.
Do pair coding to ship at least one feature (or plan for one as soon as possible):
- If the person is an experienced Dev, the pair coding will be lead by them
- If the person is a junior, the first pair coding will be lead by the senior dev, and a second one should be organised where they will lead the session