Create engineering onboarding guideline

[kaiomagalhaes]

One of the biggest issues we have right now is onboarding. Most of our daily practices and processes are explained over and over to every new engineer joining the company, and here lies one of our biggest knowledge gaps.

[kaiomagalhaes]

Main topics:

• Git/Branching flow
• Where to start ( possibly by adding the name on the website )
• Link to security docs
• GitHub access

[iancampelo]

A good way could be someone that already has experience in our company, describe his day, like a story-telling (with script).
I.E.:
1th, I log in Slack, check my emails and my calendar
2nd, I check my task board, notify my team about my work
etc, etc.
That way the new-comers will have a routine to mimic

[kaiomagalhaes]

@iancampelo that would be a daily work explanation I imagine, correct?

[duranhumes]

Both of those together would be great, a designated person to guide the newcomer and assist if they have questions and a readme of sorts with the main topics @kaiomagalhaes outlined above and more along with code standards etc, maybe even team/project specific docs in one place, maybe I'm missing something but atm it seems a bit 'all over the place' when it comes to team docs and that can be improved maybe by having all links to the docs in one place or having the docs themselves in one repo along with the hr guidelines as well.

[kaiomagalhaes]

• Access to Codelitt's Calendar
• Access to our Slack Etiquette Manual ( we need to write still

[iancampelo]

@iancampelo that would be a daily work explanation I imagine, correct?

Yep.

[kaiomagalhaes]

• 15five (what is it, how it works)

[kaiomagalhaes]

• 1password

[kaiomagalhaes]

#65