Anyways, I'm now in the "remote till I die" camp and I have been struggling to translate this into a remote first company. It can be challenging to make a new remote team member feel comfortable, productive, and "safe" without that physical presence.
Facebook’s was one of the most insulting corporate experiences I’ve had. Multiple speakers for the (very long, exhausting days of lectures) straight up didn’t show up. No comms/reschedule, just the entire onboarding class sitting and waiting for an hour.
Basically:
1. Here's how to get the dev environment setup locally.
2. Here's your first task.
3. Here's the people that will be most helpful in solving that task.
Once you can submit a PR and have code review (and ideally have it merged), you're effectively onboarded. After this it's time start worrying about the culture/philosophy/meeting people/etc.
Needless to say (hopefully), the new hire should not feel pressure to get a PR up quickly, the process and guidance should be set up for success.
But then when will we have time for all the DEI training if we waste the first week getting the employee productive?
It also worked well for me at large, stable organizations. I.e., more initial bureaucracy, but it was a pretty refined process.
Fast-growing companies above a certain size are where I've had the most hiccups.
Having a well-chosen onboarding buddy also makes a huge difference IME.