Skip to main content

The missing guide to remote onboarding

 

0. Equipment, accounts, access should all be setup BEFORE day 1. If someone starts work without these things you need to make that process better first.



1. First thing should be a video call with your manager. Ideally they will be available for questions for at least the first 1/2 of the day. If you run into problems they should be able to take action right away and not when they're done with meetings



2. The manager should prepare a list of things to read in your first week. Wiki, chat rooms, code, etc.

This list should be explained during the first call and sent as an email to reference over the first few weeks.

One of those links should be documented expectations. Not informal, verbal information. Documented publicly to make sure everyone is on the same page (new hire, manager, co-workers)

Ideally every company >100 people will have an up to date website with org chart information, user aliases, email, phone numbers, etc. This is going to be crucial to new hires to understand how the company works and who they can talk to

Bonus points if the website has a way for the user to bookmark people and add private notes (this helps them remember context on when they met people) and name pronunciation.


Amazon has phonetool with a couple of those features. Disney had rostr. WDAS had ohana



3. Introduction meetings should be already planned and scheduled with co-workers and teams.

Manager should send an introduction email for each meeting to introduce you and say what everyone on the meeting does

e.g.

This is team X

Adam is the manager

Jill is the Sr developer



4. Manager should schedule a follow-up call for Wed or Thurs to check in and have a casual chat.


Some people aren't comfortable asking questions via chat in new teams/companies.



5. There should be an onboarding buddy which has a call day 1 or early day 2. They should daily chat with the new hire for the first ~1-2 weeks to see if there's anything they can help with.



6. Optionally if onboarding a developer it's nice to open onboarding tickets in jira (or whatever you use) so they can be familiar with the workflows/planning and the team can track their onboarding process and help if they're stuck.



7. End of week 1 or 2 there should be a team building/casual call with as many people on the immediate team as possible (timezones allowing) Build trust early and play games, ice breakers, whatever.


That would be an ideal remote onboarding for me. What else have companies done you liked?



You need to invite the new hire into your #YELLING channel too. Maybe not day 1. But it should happen by day 3.

Comments

Popular posts from this blog

On working remote

The last company I worked for, did have an office space, but the code was all on Github, infra on AWS, we tracked issues over Asana and more or less each person had at least one project they could call "their own" (I had a bunch of them ;-)). This worked pretty well. And it gave me a feeling that working remote would not be very different from this. So when we started working on our own startup, we started with working from our homes. It looked great at first. I could now spend more time with Mom and could work at leisure. However, it is not as good as it looks like. At times it just feels you are busy without business, that you had been working, yet didn't achieve much. If you are evaluating working from home and are not sure of how to start, or you already do (then please review and add your views in comments) and feel like you were better off in the office, do read on. Remote work is great. But a physical office is better. So if you can, find yourself a co-working s

Capture and compare stdout in python unit tests

A recent fan of TDD, I set out to write tests for whatever comes my way. And there was one feature where the code would print messages to the console. Now - I had tests written for the API but I could not get my head around ways to capture these messages in my unittests. After some searching and some stroke of genius, here's how I accomplished capturing stdout.

AIT a.k.a Army institute of Technology

Been quite a while that I wrote anything. But I am glad, that I am back. Now that I am done with my submissions for my third year second semester (and that too right on time. Bang!), and 10 days right before the practicals start banging my head off, I am feeling a certain urge of writing about this place. AIT. Army Institute of Technology, Pune. But how could I end up writing a post on AIT . I should instead be doing something else . Anything …sleeping , rope-skipping, play gilli danda , dancing or doing anything more worthwhile. But NO! My idiotic , uncontrollable , insensible , psychotic and involuntary mind could think of doing nothing else when I was getting the urge to write this senseless post. But as I am a man of my words [huh ? What words ? Half the time I don’t even know what I speak] . MAN AM GOING CRAZY THESE DAYS . I blame this summer heat for turning me crazy with the utter joy of timely submissions, So I am going to write something on AIT. Mighty mighty AIT they s