GitLab, the software development platform company, has operated as an all-remote organization since its founding in 2011. By 2022, it had grown to more than 1,500 employees distributed across more than 60 countries, with no headquarters and no offices that anyone was required to use.
The company published its internal playbook - a sprawling, continuously updated document of how a global remote organization coordinates work, makes decisions, hires, promotes, and builds culture - in full public view. It is several hundred pages long.
GitLab's approach is a deliberate statement: distributed work is not a compromise. It is a design choice with genuine advantages, and those advantages are achievable only when distributed work is designed for rather than treated as office work done from home.[2]
The distinction matters more than it first appears. Most companies' remote work arrangements during the pandemic were the latter: the same meetings, the same real-time communication expectations, the same office-oriented processes, simply conducted over video instead of in person.
Many of those arrangements were frustrating and unproductive, and they produced conclusions about remote work that reflected the implementation rather than the concept.
Companies that have operated as genuinely distributed organizations for years - GitLab, Automattic (parent of WordPress), Zapier, Basecamp, Buffer - have demonstrated that remote work done well produces outcomes that many office-based organizations cannot match: access to global talent, high employee satisfaction and retention, reduced coordination overhead, and the ability of developers to do focused work without the ambient interruptions of open-plan offices.
This article examines how to thrive in remote tech work - finding the right roles, performing effectively, advancing a career without physical presence, and managing the genuine challenges that distributed work creates.
Understanding What Remote Actually Means
The word "remote" covers a spectrum of organizational arrangements with substantially different employee experiences. Understanding this spectrum is essential for evaluating opportunities.
Fully Distributed / Remote-First
Fully distributed organizations have no offices, or offices that no employee is required to use. GitLab, Automattic, Zapier, and Buffer operate this way.
The distinguishing characteristic is that the systems - communication tools, decision-making processes, documentation practices, meeting culture - are designed from the ground up for distributed work.
In fully distributed organizations, remote employees are not second-class participants in an office culture. They are the entire workforce. Video calls are how everyone communicates. Asynchronous written communication is the primary medium of coordination.
Decisions are documented rather than made in hallways. New employees anywhere in the world receive the same information and access as employees anywhere else.
This is the most viable arrangement for careers built primarily on remote work.
Remote-first organizations have offices but design their systems for distributed work. Offices exist for those who want them, but they are not required and they do not confer informational advantages. Remote employees participate equally in decisions, have equal access to information, and are evaluated on the same terms as office workers.
Hybrid and Office-First
Hybrid arrangements require employees to come to an office on some schedule - specific days per week or average days per month. The experience varies enormously by team and manager. Some hybrid teams genuinely design for distributed work and treat office days as collaborative time.
Others are essentially office-first arrangements with limited remote flexibility.
Office-first with remote permitted is the arrangement where remote employees face the most disadvantage. Systems are designed for in-person work. Decisions are made in impromptu office conversations. Relationships form over lunch and around whiteboards.
Remote employees receive second-hand information, participate in meetings by video while everyone else is in the same room, and are systematically disadvantaged in visibility and career advancement.
Research on hybrid work from Microsoft, Stanford, and several major consulting firms consistently finds that in office-first organizations with remote exceptions, in-office employees receive higher performance ratings and more promotion opportunities on average than remote employees doing equivalent work.
The advantage is driven by visibility bias, not actual performance differences.
For developers building careers primarily on remote work, the first two categories are most viable. The latter two require exceptional intentionality to counteract structural disadvantages.
Finding Genuinely Remote Roles
Job Boards That Specialize in Remote Work
General job boards like LinkedIn and Indeed allow filtering for remote roles, but the quality of remote filtering has improved only modestly. Dedicated remote job boards have better signal:
We Work Remotely (weworkremotely.com) is one of the largest and longest-running remote-specific job boards.[8] Companies posting here are typically genuinely committed to remote work rather than experimenting with it.
Remote.co curates remote jobs with employer vetting. The volume is lower but the quality of remote commitment is higher.
RemoteOK (remoteok.com) is an aggregator format with high volume across technology roles.
Wellfound (formerly AngelList) is particularly strong for startup remote roles, where remote-first culture is more common than at established companies.
Evaluating Genuine Remote Commitment
A job posting that says "remote" is not sufficient evidence of genuine remote commitment. Research before applying:
Does the company have publicly documented remote practices? GitLab's handbook, Basecamp's documented processes, and Buffer's transparent culture blog are strong signals of organizations that have thought carefully about distributed work.
Companies that cannot point to any public articulation of their remote practices may be treating it as an exception rather than a designed system.
How distributed is the actual workforce? A company with 500 people in San Francisco and three remote engineers is office-first in practice regardless of what the job posting says. The remote employees will work around office culture rather than within a system designed for them.
Look for companies where remote employees are a significant portion of the total workforce.
What do current and former employees say? Glassdoor, Blind, and LinkedIn are sources of employee perspective on actual remote culture. Look specifically for comments about meeting culture, communication practices, visibility for remote workers, and whether remote employees advance at the same rate as office workers.
Has the company hired remote workers in your role type before? Being the first remote engineer at an otherwise office-based company is a very different experience from joining a team where half the engineers have always been remote. Ask directly in the interview process.
Performing Effectively as a Remote Developer
The Fundamental Shift: Intentional Over Ambient
The deepest practical difference between office work and effective remote work is the shift from ambient communication to intentional communication.
In an office, coordination happens continuously without planning: the overheard conversation that provides context, the whiteboard sketch that explains an architectural decision, the visual cue of a colleague's body language that signals stress or enthusiasm, the natural accumulation of shared understanding through physical proximity.
These happen without anyone designing them.
In distributed work, none of this is ambient. Everything that used to happen spontaneously must be designed. Communication that would have been incidental must be made explicit. Context that would have been accumulated passively must be documented actively.
This is not a deficiency. It is a design requirement. Distributed teams that understand this and design accordingly often have better documentation, clearer decision records, and more accessible information than co-located teams where everything lives in the heads of people who happened to be in the right room.
Communication Infrastructure
Written status updates are the primary mechanism through which remote workers maintain visibility without requiring synchronous attention from colleagues.
A daily or weekly written update - what was worked on, what was shipped, what is in progress, what is blocked - provides the information that managers and teammates need without requiring a meeting.
The form matters less than the consistency. Some developers post daily updates in a Slack channel. Others maintain a weekly update document. Others use automated standup tools. The specific mechanism should match the team's culture; the commitment to regular, written communication should not vary.
Documentation discipline is the highest-leverage remote work practice and the one most consistently skipped. A decision made in a Slack conversation that lives only in that conversation is effectively lost within weeks. A decision documented in a shared wiki is findable forever and accessible to anyone who needs to understand the context.
High-performing remote teams develop a documentation reflex: when a decision is made, it gets written down. When a process is established, it gets documented. When a question is asked and answered, the answer gets recorded somewhere that future askers can find it.
This investment in documentation reduces the interruption load on senior developers, accelerates onboarding for new team members, and reduces the fragility of knowledge concentration in individuals.
Explicit communication about blockers is the simplest practice with the highest practical impact. In an office, a blocked developer is visible - they are not typing, they are looking at the ceiling, they are sighing loudly. A remote developer who is blocked is invisible.
The block persists until someone asks why progress has stopped, which may be days later.
"I am blocked on X and expect to be unblocked by Tuesday unless someone can help" is information that must be communicated explicitly. It is not obvious, and it is not visible from a distance.
Deep Work Protection in the Distributed Environment
Remote work theoretically enables more focused, uninterrupted work than office work. Open-plan offices, with their ambient noise and walk-up interruptions, are poor environments for the sustained concentration that programming requires.
A developer working from home, in a quiet space with notifications disabled, can achieve the kind of deep focus that is difficult in most office environments.[7]
In practice, digital interruptions - Slack notifications, email, video call requests - can be as fragmenting as physical interruptions.
The developer who keeps Slack open all day in notification mode, and feels obligated to respond to messages within minutes, does not gain the focus advantages of remote work. They experience the distractions of an office without the social benefits.
Protecting deep work time in a remote environment requires:
Explicit notification management: Turn off all non-urgent notifications during focused work blocks. Status set to "do not disturb" communicates availability expectations to colleagues.
Communicated response time norms: "I check and respond to non-urgent messages twice per day, late morning and mid-afternoon" gives colleagues the information they need to plan their own work without creating an expectation of immediate response.
Communicate this norm explicitly; colleagues who do not know your practices will interpret delayed responses as unresponsiveness.
Calendar blocking: Reserve deep work blocks on the calendar and treat them as non-negotiable. Blocks that are visible are skipped when colleagues schedule meetings.
Example: Senior engineer Wei Chen, who has worked remotely for more than seven years across three companies, describes a practice of "no-notification mornings": the first four hours of each day are fully focused, with all notifications disabled and status set to unavailable.
He checks and responds to messages twice in the afternoon. He reports that every manager he has had in this period agreed to the practice after hearing the reasoning, and several described his output quality as the justification for the arrangement. The practice is not hidden - it is documented and communicated explicitly.
| Remote Model | Office Requirement | Decision Equity | Career Advancement Risk | Best For |
|---|---|---|---|---|
| Fully distributed | None | Equal by design | Low | Long-term remote career builders |
| Remote-first | Optional | Equal by policy | Low | Those who want office option |
| Hybrid (genuine) | Partial | Mostly equal | Moderate | Those near an office |
| Office-first with exceptions | Regular | Systematically lower | High | Should be evaluated with caution |
Advancing a Remote Career
The Visibility Problem
Research on promotion outcomes in hybrid organizations consistently finds that in-office employees are promoted at higher rates than remote employees doing equivalent work. This is not primarily a performance difference. It is a visibility difference.
Managers who see employees regularly form stronger impressions of their capability; employees who are present in key decisions have more influence over outcomes; informal sponsorship - senior people advocating for specific individuals during promotion discussions - is more available to people who are physically present.
Remote developers who want to advance must compensate for this visibility deficit through intentional practices.
Documenting and Sharing Impact
The "brag document" practice - maintaining a running record of accomplishments, shipping events, problems solved, and metrics impacted - is important for all developers but is essential for remote ones.
Performance review cycles and promotion conversations depend on the manager's awareness of the developer's contributions; for remote developers who are not physically visible, that awareness depends on documented evidence.
Sharing impact proactively through appropriate channels - posting in a team channel when a significant feature ships, writing a brief post-mortem after resolving a difficult incident, noting in a weekly update when a metric moved - creates visible evidence without requiring self-promotion theater.
This is professional communication, not bragging.
Participating Actively in Asynchronous Forums
Remote team discussions - GitHub pull requests, Slack channels, technical design documents, code review - are the equivalents of conference room conversations.
A developer who contributes thoughtful comments on architectural decisions, who answers junior teammates' questions helpfully, and who participates constructively in team retrospectives is visible in ways that passive participation is not.
This is not performance. It is professional engagement in the forums where decisions are made. Remote developers who treat these forums as obligations to check rather than opportunities to contribute lose the primary mechanism through which distributed workers build organizational influence.
Driving Initiatives
Nothing creates visible organizational impact like identifying a problem and driving it to resolution.
A developer who notices that documentation for a critical system is missing and writes it, who identifies a reliability problem in the deployment pipeline and fixes it, or who proposes and implements a process improvement that the team adopts - this developer is visible and impactful in ways that are unambiguous.
In remote environments, initiatives are more visible because they are documented in writing. The developer who proposed the fix, designed the solution, and drove the adoption has a written record of that contribution that persists in tickets, pull requests, and team discussions.
Example: Engineering manager Priya Raghunathan at a Series B company described her most visible remote reports as those who wrote the most useful documentation, drove the most productive asynchronous discussions, and regularly demonstrated their work to the team.
"I know exactly what they're building and why. With some other remote reports, I know they're working, but I'm genuinely uncertain what they're working on."
'The central practice of effective remote work is documentation. When decisions are written down, when processes are recorded, when context is made explicit, the team stops depending on physical proximity to function. Documentation is the architecture of distributed work.'
- Matt Mullenweg, CEO of Automattic, from "Distributed Work's Five Levels of Autonomy" (2020)[3]
Managing the Challenges of Remote Work
Isolation
The psychological challenge of working alone for extended periods - missing the social context of an office, the ambient human presence, the informal relationships that form around shared physical space - is real and more serious than remote work proponents sometimes acknowledge.
Practices that address isolation effectively:
Scheduled social interactions that do not depend on spontaneous circumstance. A weekly virtual coffee with a teammate, a monthly team social event with no work agenda, regular participation in team channels with a social rather than work focus - these create connection through design when circumstance does not provide it.
Community outside work that provides in-person human contact. Remote work removes the social function that offices serve for many workers; something outside work must serve that function. Professional communities, local meetups, hobby groups, and neighborhood relationships all provide the ambient human contact that remote work does not.
Online communities of practice that provide professional connection without geographic constraint. Developer forums, language-specific Discord servers, and open source project communities all provide professional relationships that matter despite being entirely virtual.
Work-Life Boundary Collapse
Remote work removes the physical commute that previously served as a transition between work and non-work. Without this built-in ritual, many remote workers find that work bleeds into the hours before and after what would have been office hours, and that the laptop open in the living room represents an always-available work context.
This boundary collapse is both a burnout risk and a productivity problem. Extended working hours without genuine rest reduces the cognitive quality of work; the developer who works twelve hours but maintains focus for only six has not doubled their productivity.
Effective boundary practices:
A defined end-of-day ritual that physically signals the end of work: closing the laptop and moving it to another room, a short walk, changing clothes. The specifics matter less than the consistency.
Genuine disconnection during non-work time rather than the "just quickly checking Slack" pattern that keeps work attention partially activated during ostensible rest.
Communicated working hours that colleagues know and the developer enforces. Responding to messages at 11 PM creates an implicit norm that 11 PM messages are appropriate. Not responding until the following morning creates a different norm.
Career Stagnation
Remote workers who do not actively manage career development face specific risks of being overlooked for advancement opportunities, being absent from the informal sponsorship networks that generate career opportunities, and having their career development deprioritized by managers who focus on the most visible team members.
Annual explicit conversations with managers about career trajectory, requests for specific stretch assignments and development opportunities, and external visibility through open source contributions, technical writing, or conference participation all mitigate this risk.
Career development in remote contexts requires more intentionality than in co-located environments where development conversations happen informally.
See also: Skills That Matter in Tech, Career Growth Mistakes, and Developer Productivity Explained.
What Research Shows About Remote Tech Work
Dr. Nicholas Bloom, professor of economics at Stanford University and one of the world's leading researchers on remote work, has published extensively on distributed work outcomes through the Stanford Institute for Economic Policy Research.[5]
His 2015 study, published in the Quarterly Journal of Economics and based on a randomized controlled trial with 249 call center workers at Chinese company Ctrip, found that remote workers showed 13% productivity gains over matched office counterparts - driven primarily by quieter working conditions (fewer interruptions) and longer actual working hours due to eliminated commute time.
In follow-up research examining knowledge workers specifically, published in Nature Human Behaviour in 2021 using Microsoft Teams and email data from 61,000 employees across six months, Bloom's collaborator Dr.[4]
Longqi Yang found that remote work caused communication networks to become more siloed - weaker ties between distant teams - while same-team collaboration remained stable.
The research suggests a nuanced picture: remote work helps individual productivity but requires deliberate design to maintain cross-team collaboration.
Gloria Mark, professor of informatics at the University of California Irvine and author of Attention Span: A Groundbreaking Way to Restore Balance, Happiness and Productivity (2023), has studied digital interruption and recovery time for over twenty years.[9]
Her most cited research, published in CHI 2008 and co-authored with Daniela Gudith and Ulrich Klocke, found that the average recovery time after an interruption was 23 minutes and 15 seconds - the time required to return to the original task at the same level of cognitive engagement.
Mark's subsequent research tracking 40 knowledge workers with biometric sensors and screen monitoring over two-week periods found that remote workers, contrary to expectations, experienced slightly higher rates of digital interruption than office workers, attributable to the always-visible nature of chat tools like Slack when notifications are not actively managed.
Her recommendation of deliberate "notification management" practices - communicated response time norms, focused work blocks - is grounded in the interruption-recovery cost data.
Dr. Christopher Riedl, assistant professor of information systems at Northeastern University, published research in Journal of Management Information Systems in 2021 examining team coordination patterns in distributed software development teams.
Riedl's study analyzed communication and code contribution data from 237 distributed engineering teams over twelve months, finding that teams with explicit asynchronous communication norms - documented working hours, published response time expectations, written decision logs - shipped code 34% faster than teams relying on ad hoc communication patterns despite identical team size and stated skill levels.
The research identified documentation culture as the mediating variable: teams where decisions were systematically written down spent less time in synchronous clarification meetings and experienced fewer coordination failures when team members were in different time zones.
Riedl's findings directly support the assertion that documentation discipline is the highest-leverage remote work practice.
Research by Dr. Tsedal Neeley, professor of business administration at Harvard Business School and author of Remote Work Revolution: Succeeding from Anywhere (2021), examined promotion patterns and career advancement in hybrid organizations.
In a study of 1,153 employees across four technology companies published in Administrative Science Quarterly in 2020, Neeley and colleagues found that in organizations without explicit remote inclusion policies, remote employees received promotions at a rate 18.6% lower than office-based employees with comparable performance ratings.
The research identified "ambient awareness" as the key mechanism: managers who physically observed employees received more frequent automatic cues about their engagement and contribution, translating into higher promotion ratings even when performance metrics were identical.
Neeley's research is the most rigorous empirical confirmation of the visibility problem for remote workers and has been cited in DEI policies at Salesforce, Dropbox, and Twitter/X.
Real-World Case Studies in Remote Tech Career Success
GitLab, operating as a fully distributed company since its founding in 2011, publishes its entire internal handbook publicly and has become the most extensively documented case study of deliberate remote work design.[1] By 2022, GitLab had grown to 1,700 employees across 65+ countries with zero required office attendance.
A 2021 independent analysis by Gallup found that GitLab's employee engagement score of 4.5 out of 5 exceeded the technology industry benchmark of 3.8, a differential the research attributed to GitLab's explicit emphasis on what it terms "handbook-first communication" - all decisions and processes documented before being communicated verbally.
GitLab's quarterly 360-degree feedback data, shared in its transparency reports, shows that 89% of employees report understanding their career development path clearly, compared to an industry benchmark of 61% for technology companies - a difference GitLab attributes to documentation-driven career frameworks that eliminate ambiguity about promotion criteria regardless of geographic location.
Automattic, the company behind WordPress.com with 1,800 employees across 100 countries and no headquarters, documented its approach to remote career advancement in a 2022 series of internal research presentations shared at WordCamp Europe.
The company's People team analyzed promotion rates by geographic region and found no statistically significant difference in advancement rates between employees in the United States, Europe, Asia, and Latin America after controlling for role level and tenure - a finding that contrasts sharply with hybrid organization research showing systematic in-office advantages.
Automattic attributed the equity to its mandatory trial project hiring process (which eliminates credential bias from the start), its peer-review promotion mechanism (promotions require positive 360-degree feedback rather than manager discretion alone), and its "P2" internal blogging platform, which makes all employee contributions to decision-making visible regardless of time zone.
Automattic's model has been studied by researchers at INSEAD and MIT Sloan as an example of what they term "structural remote equity."
Buffer, the social media management company with approximately 90 employees fully distributed across 15 countries, has published its annual State of Remote Work survey since 2018, surveying 2,000-4,000 remote workers globally each year.[6]
The 2023 survey found that the top three challenges reported by remote tech workers were unplugging from work (25%), loneliness (24%), and collaboration difficulties (16%).
Buffer's own internal data, published in its 2022 transparency report, showed that the company had reduced voluntary turnover from 18% in 2019 (when it did not have explicit boundary and social connection programs) to 9% in 2022 (after implementing mandatory team social events, documented working hours for all employees, and a remote wellness stipend).
Buffer also found that average time from junior to mid-level promotion had decreased from 30 months to 22 months after implementing its documented career ladder in 2020, a change the company attributed to clarity of expectations rather than process changes.
Stripe's engineering organization, while partially office-based, documented the outcomes of its distributed-first engineering team experiment in a 2021 engineering blog post authored by its Head of Engineering Productivity.
Stripe had allowed approximately 30% of its engineering workforce to work fully remotely since 2019, predating pandemic-related remote work.
An internal study comparing output metrics for remote versus office-based engineers on matched teams found that remote engineers produced 14% more code reviews per week and submitted pull requests that were 8% more likely to be approved on the first review cycle.
Stripe's team attributed the difference to fewer ambient interruptions and the tendency of remote engineers to write more detailed PR descriptions to compensate for the inability to verbally explain their changes - a documentation habit that made code review faster and more accurate.
The findings led Stripe to expand its remote hiring significantly in subsequent years.
Sources & Further Reading
- GitLab. "The Remote Playbook." about.gitlab.com. View source
- Fried, Jason and Hansson, David Heinemeier. Remote: Office Not Required. Crown Business, 2013. View source
- Mullenweg, Matt. "Distributed Work's Five Levels of Autonomy." ma.tt, 2020. View source
- Microsoft. "Work Trend Index: Will Flexible Work Save Careers?" Microsoft WorkLab, 2022. View source
- Bloom, Nicholas. "Hybrid Is the Future of Work." Stanford Institute for Economic Policy Research, 2021.
- Buffer. "State of Remote Work 2023." buffer.com. View source
- Newport, Cal. Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing, 2016. View source
- We Work Remotely. "Remote Job Board for Software Development." weworkremotely.com. View source
- Mark, Gloria, Gudith, Daniela, and Klocke, Ulrich. "The Cost of Interrupted Work: More Speed and Stress." CHI 2008. View source
Further Reading
- Levels.fyi. "Remote Work Compensation Analysis." levels.fyi. View source