GitHub: Born Remote, Scaled Remote
GitHub was founded in 2008 on the principle that great developers work everywhere. The company famously had no formal management hierarchy in its early years, used its own tool for distributed code review and collaboration, and built a culture around async, documentation-first work from the very start.
After Microsoft acquired GitHub for $7.5 billion in 2018, there was widespread concern that the remote-first culture would be absorbed into Microsoft corporate norms. In 2026, those fears have proven partially unfounded: GitHub maintains significant remote-first practices while also operating within Microsoft governance structures.
Tool-Driven Remote Culture
GitHub employees use GitHub to manage GitHub - this is not a cliche, it is a real organizational practice. Product decisions, roadmap discussions, feature design, and many operational processes happen in GitHub Issues, Pull Requests, and Discussions. The tooling has an alignment benefit: teams understand their product deeply because they use it for their own work.
Internal wikis, decision records, and team documentation all live in GitHub repositories. This creates a searchable, versioned institutional memory that new employees can access immediately - addressing one of the hardest challenges of remote onboarding.
InnerSource: Open Source Practices for Internal Teams
GitHub pioneered the concept of "InnerSource" - applying open source collaboration practices to internal company work. Anyone in the company can see any codebase, file issues, and submit pull requests to teams they do not directly work with. Cross-team contributions are welcomed and credited.
For remote work, InnerSource solves a real problem: how do you enable the kind of spontaneous collaboration that happens when engineers from different teams are in the same office and overhear each other solving problems? The answer GitHub found: make all work visible and low-friction to contribute to.
Post-Microsoft: What Changed
The Microsoft acquisition brought some changes to GitHub culture. More formal management structure, more structured performance reviews, alignment with Microsoft corporate calendar and policies. Some GitHub employees who valued the startup-era lack of structure found this difficult; others appreciated the stability and resources.
Remote work practices have largely been preserved. GitHub employees remain distributed globally, with strong async culture. Microsoft acquisition has not resulted in the office-return mandates that some feared.
How GitHub Hires for Remote
GitHub hiring processes include explicit evaluation of async communication skills. Candidates submit written proposals or work samples that demonstrate how they think and communicate in writing. The interview process involves significant written exchange - not just video calls - because written communication is central to how GitHub teams operate.
GitHub looks for self-direction, comfort with ambiguity, and the ability to build context from documentation rather than requiring constant guidance. These traits are specifically assessed in the hiring process.