@@ -25,8 +25,6 @@ Not only are buddies helpful to someone that has just started with GitLab, but a
- For new GitLab team-members who have not worked in a [remote organization](/handbook/company/culture/all-remote/) before, they may need assistance in thinking through an ideal [workspace](/handbook/company/culture/all-remote/workspace/) and embracing [informal communication](/handbook/company/culture/all-remote/informal-communication/). Consider asking seasoned remote colleagues in the `#remote` Slack channel to reach out and answer questions.
- If they're new to Git, consider asking experts in the `#git-help` Slack channel to reach out and offer a tutorial.
- If they're new to [Markdown](https://about.gitlab.com/blog/2018/08/17/gitlab-markdown-tutorial/), consider asking experts in the `#content` Slack channel to reach out and offer support.
1.**Help with the team page.** For less technical new hires, adding themselves to the [team page](/handbook/company/team/) might feel like the most daunting task on the onboarding issue. Offer to help with the process. This doesn't necessarily have to happen on day one, but you should let them know that you're available to help if and when they need it. Consider scheduling a second meeting later in the week to walk them through [the process](/handbook/about/editing-handbook/#add-yourself-to-the-team-page)
- In particular, help them to create their SSH key as this tends to be a sticking point for many new hires. You can also show them [Lyle's walkthrough](https://youtu.be/_FIOhk03VtM).
1.**Check in regularly.** You may very well be the first friend the new GitLab team-member makes on the team. Checking in with them regularly will help them feel welcome and supported. Reach out via Slack, and schedule at least two follow-up calls for the week after their start date, and at least one follow-up call for the rest of the first month. But since it differs from one person to another, you may also ask them if they prefer more or less frequent calls per week.
1.**Provide backup if needed**. If you plan to be out (e.g. [vacation](/handbook/people-group/time-off-and-absence/time-off-types/), [company business](/handbook/finance/travel/), [events](https://about.gitlab.com/events/), etc.) during a new GitLab team-member's first few weeks, please ensure that a backup onboarding buddy is available to offer support.
1.**Consider a long-term mentorship program**. It can take a long time before new team members are comfortable in their new role, and having a mentor during that process goes a long way to help the transition into their role's responsibilities go as smooth as possible. Consider setting up a weekly, or bi-weekly one-hour mentorship session, which your buddy can use to bring up any matter they are struggling with along the way.
