GitLab's Guide to All-Remote

What it is

GitLab runs as an all-remote company and publishes how it works in its public handbook. The Guide to All-Remote collects that knowledge into a set of pages on remote working, free for anyone to read (source: handbook.gitlab.com, as of 2026-09).

What it covers

Topics include:

• Async and non-linear work: making progress without everyone online at once.
• Handbook-first communication: writing decisions and processes down so people can find answers without asking.
• Meetings: when to hold them, agendas, live documents and recording decisions.
• Getting started and onboarding as a remote hire.
• Mental health: burnout, isolation and boundaries.
• Home office setup, remote management, hybrid models and remote internships.

A theme running through it is not to copy the office experience online, but to design work for distance.

Why read it for a job search

Remote employers screen for these habits. If you understand async work, written decisions and good meeting practice before you apply, you can show them in your take-home tasks, your answers and your first weeks. Many of the questions on the remote jobs roadmap, such as how you work when a teammate is asleep, come straight from these practices.

How long it takes

You do not need to read it all. Two to three hours on the async, communication and meetings pages gives you most of the value. Come back to the burnout and home office sections once you are hired.

How to use it

• Read the async and communication sections and write three habits you will adopt.
• Rewrite one of your own messages or updates in the style it describes.
• Before an interview with a remote-first company, check whether it publishes a handbook too, and read the parts on how it works.

Limits

It describes one company's way of working at scale. Smaller teams may be less formal, and every company differs, but the principles transfer well.

Common questions

Is it only for managers? No, most of it applies to any team member.

Is it free? Yes, it is part of GitLab's public handbook.

Is it up to date? It is maintained in the handbook; check the page history for recent changes.