# Interviewing or starting at GitHub? Read these first

**TL;DR:** GitHubbers have been unusually intentional about writing their norms down: communicate in writing, work asynchronously, and show your work. If you're joining GitHub, preparing for an interview, or just curious how a remote-first company operates, start with the four posts I'd pick if you only have an evening, and read for the why, not the how-to.

Published 2021-02-01 · [View on Ben Balter's site](https://ben.balter.com/2021/02/01/what-to-read-before-starting-or-interviewing-at-github/)

---

Your first few weeks at any new company are an exercise in pattern matching: figuring out the unwritten rules, the communication norms, the things everyone "just knows" but nobody thought to write down. Your first few weeks at GitHub are no exception, except that GitHubbers have been unusually intentional about writing those norms down (it's kind of their thing).

Over my years there, I tried to capture what makes GitHub's culture tick: how GitHubbers communicate asynchronously, how they ship, and how they think about leadership. If you're joining GitHub, preparing for an interview, or just curious about how a remote-first, async-by-default company actually operates day to day, consider this your unofficial reading list.

> **Some of these posts are a decade old. Is any of it still true?** The specifics, maybe not: tools change, teams reorg, and GitHub is a much bigger company than the one I joined in 2013. The principles hold up better. Writing things down, defaulting to async, and showing your work were true when GitHub was a few hundred people, and they're still how distributed teams scale. Read for the why, not the how-to.

## If you're interviewing at GitHub

I can't tell you what's in the interview, and the process has surely changed since I was there. What I can share is how the work actually gets done, and that's what I'd want a candidate to understand, whether or not anyone asks about it directly. For open roles and the current process, [GitHub's careers site](https://www.github.careers/careers-home) is the source of truth.

> **Only have an evening?** Read these four:
>
> - [15 rules for communicating at GitHub](https://ben.balter.com/2014/11/06/rules-of-communicating-at-github/): writing is the job, and this is the house style
> - [Why you should work asynchronously](https://ben.balter.com/2022/03/17/why-async/): how decisions get made when nobody's in the same room, or the same time zone
> - [The seven habits of highly effective GitHubbers](https://ben.balter.com/2016/09/13/seven-habits-of-highly-effective-githubbers/): what good looks like once you're in the door
> - [Leaders show their work](https://ben.balter.com/2022/02/16/leaders-show-their-work/): if you're interviewing for a leadership role, how leaders are expected to explain their decisions
>

## The short version: Open and Async

If you'd rather read one thing than seventeen, I wrote [*Open and Async*](https://open-and-async.com/?utm_source=benbalter-reading-list) for exactly that. It's my playbook for working in writing, asynchronously, and in the open. Most of the posts in the first list below were adapted into the book or inspired one of its chapters.

## How GitHub's culture works

> **I'm not interviewing at GitHub. Is this for me?** Probably. Nothing here needs a GitHub badge. If your team is remote, spread across time zones, or tired of meetings that should have been a doc, these are the same patterns, just written down by people who've used them for years.

GitHub's operating system runs on a few core principles: [communicate in writing(/2014/11/06/rules-of-communicating-at-github/), [work asynchronously](https://ben.balter.com/2022/03/17/why-async/), and [show your work](https://ben.balter.com/2022/02/16/leaders-show-their-work/).]{#github-core-principles} If you're coming from a more traditional, meeting-heavy, synchronous organization, the shift can feel disorienting at first, like switching from a monolith to microservices. The architecture is different, but once you internalize the patterns, everything clicks.

These posts cover those foundational patterns: the habits, tools, and mental models that help GitHubbers thrive.

### How GitHub communicates

- [15 rules for communicating at GitHub](https://ben.balter.com/2014/11/06/rules-of-communicating-at-github/): How GitHub uses asynchronous communication to eliminate the "you had to be there" aspect of most corporate workflows.
- [Why everything should have a URL](https://ben.balter.com/2015/11/12/why-urls/): When knowledge lives in people's heads and inboxes, it doesn't scale. URLs make context discoverable, asynchronous, and opt-in.
- [Why you should work asynchronously](https://ben.balter.com/2022/03/17/why-async/): Async is what makes remote work actually work. It produces better outcomes, improves work-life balance, and protects the long stretches of focus that deep work needs.
- [Meetings are a point of escalation, not a starting point](https://ben.balter.com/2023/04/20/meetings-are-a-point-of-escalation/): Most meetings are just information downloads that could've been a doc. Treat them as escalation, not the default.
- [Tools of the trade: How I communicate at GitHub (and why)](https://ben.balter.com/2020/08/14/tools-of-the-trade/): How I think about the tools we use to communicate, from issues and discussions to Slack, Zoom, and email.
- [How I manage GitHub notifications](https://ben.balter.com/2020/08/25/how-i-manage-github-notifications/): My system for staying on top of 200+ daily GitHub notifications without losing focus.

### How GitHub ships

- [Seven ways to consistently ship great features](https://ben.balter.com/2017/05/23/seven-ways-to-consistently-ship-great-features/): The best developers over-communicate, write features before code, ship the smallest delta possible, and optimize for users.
- [The six types of pull requests you see on GitHub](https://ben.balter.com/2015/12/08/types-of-pull-requests/): Not all pull requests are created equal. Six distinct strategies for using pull requests to collaborate.
- [Four characteristics of modern collaboration tools](https://ben.balter.com/2015/11/18/tools-to-empower-open-collaboration/): Modern collaboration tools are open, linkable, asynchronous, and naturally capture process.

### How GitHubbers work and lead

- [GitHub for non-developers: a beginner's guide](https://ben.balter.com/2023/03/02/github-for-non-technical-roles/): GitHub isn't just for developers. Everything you need to follow along, collaborate, track work, and get started with confidence.
- [The seven habits of highly effective GitHubbers](https://ben.balter.com/2016/09/13/seven-habits-of-highly-effective-githubbers/): Traits I've observed in successful GitHubbers, from shipping early and often to contributing to the appreciation economy.
- [Eight things I wish I knew my first week at GitHub](https://ben.balter.com/2016/10/31/eight-things-i-wish-i-knew-my-first-week-at-github/): Tips I offer new employees, from shipping something in your first two weeks to knowing when the overwhelm hits.
- [Leaders show their work](https://ben.balter.com/2022/02/16/leaders-show-their-work/): Great leaders don't just communicate what decision was made. They explain how and why.

## Role-specific guides

The posts above apply broadly, but if you're a Product Manager, Technical Program Manager, Chief of Staff, or Engineering Manager, you might wonder what those roles look like in practice at a company where the defaults around hierarchy, process, and decision-making are a bit different from what you're used to. These go deeper.

- [Twelve things a product manager does](https://ben.balter.com/2016/06/06/twelve-things-a-product-manager-does/): What does a product manager actually do all day? Twelve responsibilities from user advocacy to strategic thinking.
- [Nine things a (technical) program manager does](https://ben.balter.com/2021/03/26/nine-things-a-technical-program-manager-does/): What a Technical Program Manager actually does day-to-day, from a PM who transitioned into the role.
- [The seven things a corporate Chief of Staff does](https://ben.balter.com/2022/03/09/seven-things-a-corporate-chief-of-staff-does/): The Chief of Staff role is poorly understood. Seven core responsibilities that make it indispensable.
- [Manage like an engineer](https://ben.balter.com/2023/01/10/manage-like-an-engineer/): If issues, pull requests, and project boards are the best way to develop software, should they not also be the best way to manage it?

## Keep going

For more, [these are the books that most influenced my time at GitHub](https://ben.balter.com/other-recommended-reading/), the ones I most often recommend to colleagues looking to level up their thinking about culture, leadership, and collaboration.

These opinions are [my own](https://ben.balter.com/fine-print/), and as organizations grow, cultures and communication patterns naturally evolve. The underlying principles tend to be more durable than the specifics. If you have questions or want to compare notes, [my inbox is open](https://ben.balter.com/contact/).
