In 2023, while most tech companies were busy herding employees back into offices, GitLab CEO Sid Sijbrandij said something in an interview that cut through the noise: "We're not remote-first. We're all-remote. And we're never going to have an office." This wasn't a marketing slogan. GitLab has team members in over 65 countries, and the company's entire operating system is built on a publicly available handbook that exceeds two thousand pages. No headquarters, no physical offices, no weekly all-hands meetings. What they do have is a work culture built on written communication, asynchronous collaboration, and the relentless measurement of output.

This isn't a Silicon Valley anomaly. Automattic, the company behind WordPress, has been fully distributed since its founding in 2005, spanning more than 90 countries. Basecamp (now 37signals) has practiced remote work since the late 1990s—its founders Jason Fried and David Heinemeier Hansson wrote an entire book, Remote, arguing that offices are the enemy of productivity. Zapier, Buffer, Doist (the company behind Todoist)—these companies share a common trait that goes beyond "allowing employees to work from home." Their organizational DNA was designed from the ground up for asynchronous collaboration.

Understanding this distinction is critical. "Allowing remote" and "built for remote" are two fundamentally different organizational models. The former patches remote capability onto a traditional company framework—you can work from home, but the meetings are the same meetings, just migrated from conference rooms to Zoom. The latter rebuilds from the foundation—synchronous meetings are not the default, all decision-making processes are documented in writing, and the default mode of communication is text, not voice.

Why Async Collaboration Is a Superior Way to Work

Synchronous communication—real-time conversations and meetings that require everyone to be online simultaneously—has a fatal flaw: it assumes everyone's time has equal value in that moment. A one-hour meeting with eight people doesn't cost one hour. It costs eight. And of those eight hours, the actual information exchange that required everyone's simultaneous presence might account for fifteen minutes. The rest is people listening to discussions irrelevant to them, waiting for their turn to speak, or mentally drifting.

GitLab's handbook captures this precisely: "If a decision can be communicated through a document, it should not be communicated through a meeting. Meetings are the most expensive form of synchronous communication." Their approach: all proposals are first written as Issues or Merge Requests. Relevant stakeholders read and provide feedback at their convenience. The responsible person makes the decision and records it in the document. The entire process requires no one to be online at the same time.

Basecamp's Shape Up methodology goes further. Work is divided into six-week cycles. At the start of each cycle, teams receive a "pitch"—a thoroughly argued proposal document, not a presentation meeting. Team members read it on their own, plan their own approach to delivering within six weeks, and in between there are no daily standups, no progress check-in meetings. At the end of six weeks, you either shipped or you didn't. Results talk.

Automattic's internal communication runs primarily through a tool called P2—essentially an internal blog platform. Every team and every project has its own P2, and all discussions happen in long-form text. CEO Matt Mullenweg once said: "If you can't write down your idea, you probably haven't fully thought it through." This isn't a motivational poster quote. It's the core logic by which Automattic filters talent: if you can't clearly articulate your thinking process in writing, you won't survive at this company.

The Brutal Side of Async: An Output-Only Game

Here's something that isn't entirely politically correct: async remote work is paradise for some people and hell for others. It's paradise for those who can self-manage, excel at written communication, and sustain output without external pressure. It's hell for those who depend on office structure and atmosphere for motivation, who communicate better face-to-face, or whose work habits require real-time feedback.

In a traditional office, you can create the illusion of value by "looking busy." Arriving early, leaving late, speaking up actively in meetings, frequently walking within the boss's line of sight—these behaviors all signal "effort" in a physical office. In an all-remote company, every one of these signals becomes invisible. Nobody sees what time you start working. Nobody knows whether you're paying attention in a call. The only thing visible is your output: the documents you wrote, the code you committed, the designs you delivered, the projects you moved forward.

GitLab's performance evaluation system directly reflects this logic. Their handbook states explicitly: "We measure results, not input. We don't care when you work or how long you work. We care about what you deliver." This sounds liberating, and it is—but the flip side is unforgiving: if you don't deliver, no excuse is valid. You can't say "I was in six meetings today, I was busy," because in an async culture, meetings aren't work. The output of meetings is work.

This "output-only" culture demands enormously from workers. You need strong time management, because no one will schedule your day for you. You need excellent written communication skills, because more than 80% of collaboration happens through text. You need discipline, because your manager won't—and shouldn't—micromanage you. You need initiative, because in an async environment, people who wait to be told what to do get culled quickly.

What This Means for Job Seekers

If you're considering joining an all-remote company, the first thing you need to do isn't updating your technical résumé. It's asking yourself honestly: are you built for this?

All-remote companies often interview differently from traditional ones. GitLab's process involves substantial asynchronous written communication—you may be asked to complete a written assignment rather than (or in addition to) a live video interview. This isn't to save the interviewer's time. It's because written communication ability is itself the core skill being evaluated. If you can't express your ideas clearly in writing during the interview, you won't perform any better in daily work.

Automattic's interview process is famously distinctive—they have a "trial project" phase, typically lasting three to eight weeks, during which you actually participate in company projects. You get paid, but it's a mutual evaluation. They want to see not just your skills, but whether you can consistently produce high-quality work when nobody's watching you.

Some concrete advice for job seekers. First, before applying, spend a few days working in a completely async mode—turn off instant messaging, conduct all communication via email or documents, batch-process messages at fixed times instead of responding instantly. See if you can tolerate this rhythm. Second, start building a "written portfolio"—technical documentation, project proposals, decision memos. These artifacts are more useful in all-remote interviews than any verbal presentation. Third, if possible, gain actual async collaboration experience through freelancing or part-time remote work first. Fourth, carefully read the target company's public handbook—GitLab's handbook is public, Basecamp's Shape Up documentation is public. Reading and understanding these documents is more valuable than any job-search guide.

The Truth About Remote Work: It's Not a Benefit, It's an Organizational Philosophy

Many people treat remote work as an employee benefit—a fancier version of free lunch or flexible hours. But in the context of GitLab, Automattic, and Basecamp, remote work isn't a perk. It's a fundamental organizational design choice. It changes communication patterns, decision-making processes, performance evaluation criteria, and even how company culture is defined.

These companies chose all-remote not because it's better for employees (though for some employees it certainly is), but because they believe this way of working produces better outcomes. When you force all communication through writing, you force people to think more deeply. When you eliminate most meetings, you return time to the deep work that actually creates value. When you stop measuring performance by attendance, you select for people who can autonomously deliver.

That's why the title calls remote work a "selection mechanism." It doesn't just select for employees who are suited to remote work. It selects for a way of thinking, communicating, and maintaining work discipline that is suited to remote work. Not everyone fits this system, just as not everyone fits a clock-in-clock-out office. But if you're the kind of person who can sustain output without external structure, who thinks more clearly in writing than in speech, who thrives on autonomy over your own work rhythm—then an all-remote company isn't just a job option. It might be the best environment you'll ever work in.

The strongest companies are embracing async not because it's trendy, but because in a globalized talent market, whoever removes the constraint of "everyone must be in the same place at the same time" first gets to hire the best people from everywhere on Earth. The office isn't the source of productivity. Talent is. And asynchronous collaboration is the key that unlocks the global talent pool.