Skip to main content

Interviewing or starting at GitHub? Read these first

6 min read

Summary: 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.

Table of contents

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.

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 is the source of truth.

The short version: Open and Async

If you’d rather read one thing than seventeen, I wrote Open and Async 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.

Out now

OpenandAsync

The collaborative software development playbook for remote and distributed teams. Drawing on over a decade at GitHub. On Kindle, Apple Books, Kobo & more.

Buy it for $9.99 (opens in a new tab)

How GitHub’s culture works

GitHub’s operating system runs on a few core principles: communicate in writing, work asynchronously, and show your work. 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

How GitHub ships

How GitHubbers work and lead

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.

Keep going

For more, these are the books that most influenced my time at GitHub, the ones I most often recommend to colleagues looking to level up their thinking about culture, leadership, and collaboration.

These opinions are my own, 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.

Keep reading

Ben Balter

I'm Ben Balter, and I write here about developer platforms, product and engineering leadership, open source, and showing your work. I spent over a decade building developer platforms at GitHub. For five years I was a product manager for trust and safety, shipping 500+ features and the API endpoints behind them to 50M+ developers. I also led a bottom-up rewrite of GitHub Pages and wrote the open source library behind GitHub's license detection, and my open source projects have hundreds of millions of downloads. I wrote Open and Async, the playbook for remote and distributed teams, and shipped a Model Context Protocol (MCP) server alongside it so agents can query it directly. More about the author

Follow along: Bluesky LinkedIn

Originally published February 1, 2021 View revision history

This page is open source Help improve this article on GitHub

Keyboard shortcuts

Search

  • / or ⌘ K Open search
  • ↓ or j ↑ or k Move through results
  • Enter Open the selected result
  • Esc Close search

Go to

  • g then h Home
  • g then p All posts

This page

  • y Copy link to this page
  • ? Show this list

Turn off if you use voice control or keep triggering them by accident. ⌘ K still opens search, and this list stays under "Keyboard shortcuts" in the footer.