I recently joined GitLab to lead its all-remote initiatives. I've lived and worked remotely in a variety of settings (all-remote, remote-first, part-remote, etc.) and I'm building out pages within GitLab's publicly accessible All-Remote section to hopefully answer questions like these. The hub is here (as mentioned by langitbiru — thank you!): https://about.gitlab.com/company/culture/all-remote/

We're sharing what we've learned scaling the company to over 800 people across nearly 60 countries, 100% remote with no offices. The goal is to share this knowledge and see other organizations replicate, iterate, and evolve.

Some of the more recent ones are below.

People: https://about.gitlab.com/company/culture/all-remote/people/

Jobs: https://about.gitlab.com/company/culture/all-remote/jobs/

Hiring: https://about.gitlab.com/company/culture/all-remote/hiring/

Compensation: https://about.gitlab.com/company/culture/all-remote/compensa...

Learning and Development: https://about.gitlab.com/company/culture/all-remote/learning...

Informal Communication: https://about.gitlab.com/company/culture/all-remote/informal...

Meetings: https://about.gitlab.com/company/culture/all-remote/meetings...

Part-remote: https://about.gitlab.com/company/culture/all-remote/part-rem...

Remote work conferences, summits, and events: https://about.gitlab.com/company/culture/all-remote/events/

Advantages and benefits: https://about.gitlab.com/company/culture/all-remote/benefits...

Disadvantages: https://about.gitlab.com/company/culture/all-remote/drawback...

More to come! If you have questions on making all-remote work, hiring all-remote workers, or managing/communicating in an all-remote environment, leave a comment! We're always looking for challenges happening across the space, so we can ideally find and document solutions.