> ## Documentation Index
> Fetch the complete documentation index at: https://engineering.trewknowledge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding new employees

## First steps

<Steps>
  <Step title="Create email account">
    The pattern is first letter of first name and then the full last name. For example, John Doe would be `jdoe@trewknowledge.com`
  </Step>

  <Step title="Invite new user to our tools and teams">
    * Slack
    * GitHub Organization
    * GitHub CoPilot
    * GitKraken
    * Jira & Confluence
    * Humi
    * Harvest
  </Step>

  <Step title="Invite to teams and groups">
    * Add to Slack's development team
    * Add to GitHub's development team
    * Give the Atlassian's developer role
  </Step>

  <Step title="Policies and documentation">
    The new employee should then spend some time reading the company's policies and documentation including this handbook.
  </Step>

  <Step title="Assign a mentor">
    Assign a mentor to the new employee so they can follow existing projects and learn the company's best practices.
    This step should take at least a few days to a week.
  </Step>

  <Step title="Begin work">
    After following a colleague for a while, the new employee should start working on their first tasks. They can confirm their approach with their manager or project Lead and colleagues to make sure they are following the company's best practices.

    To learn more about our project lifecycle and each role's responsibility, please refer to the [Agile & Scrum](/how-we-work/process/agile-scrum) page.
  </Step>
</Steps>

## Performance review

The Director of Engineering will request weekly reports on the new employee's progress from other managers, mentors, and colleagues. These reports must be added to the new employee's profile in the company's HR system. All of these reports are taken into account during the new employee's probation performance review.