What's the Company Culture Like at GitHub in San Francisco?

Key Insight for Candidates

• Collaborative & Supportive Culture: Colleagues in San Francisco are often described as helpful, respectful, and constructive, with code review and RFC norms that encourage thoughtful feedback. Feedback suggests teams value kind collaboration and lightweight meetings that protect maker time.
• Learning & Knowledge Sharing: Work in the San Francisco office relies on writing-first practices—design docs, proposals, decision logs, and blameless postmortems—that make context transparent and learning durable. Managers are said to coach communication and cross-team influence, and teams regularly dogfood GitHub’s own tools to share knowledge.
• Healthy Workload & Retention: Feedback suggests the San Francisco team benefits from a remote-first setup with flexibility, trust without micromanagement, and rituals that support focus time. Emphasis on personal and family needs, along with strong benefits, contributes to a sustainable pace.

• Bureaucracy & Red Tape: Large-platform rigor—security reviews, compliance gates, and cross-org coordination within Microsoft—can slow decisions and feel process-heavy for those who prefer speed. Issue/PR-driven decision making and multiple stakeholders sometimes lengthen cycles across time zones.
• Poor Communication: Some accounts describe leadership as tone-deaf or inconsistent, with disorganization and a lack of transparent communication during frequent changes. These gaps leave teams seeking clearer direction and alignment.
• Change Fatigue & Ineffective Decision-Making: Post-acquisition shifts, layoffs, reorgs, and closer alignment with Microsoft priorities have introduced uncertainty and political friction for some teams. This churn is cited as undermining clarity around strategy and belonging during transition periods.