What to read before starting (or interviewing) at GitHub

Posted February 1, 2021 | View revision history

Over the years I’ve written a number of posts about GitHub’s culture and communication patterns. If you’re joining (or preparing for an interview at) GitHub, here are some of my favorite posts that might help you understand how GitHub works and what it’s like to be a GitHubber:

And if you’re a Product Manager or Technical Program Manager:

Of course, these opinions are my own, and please take the publication date in mind when reading. GitHub (and I) have changed a lot since 2013, and as organizations grow and mature, cultures and communication patterns naturally evolve. If you have any questions, feel free to reach out on Slack, Twitter, or the comments below.

If you enjoyed this post, you might also enjoy:
benbalter

Ben Balter is a Staff Technical Program Manager at GitHub, the world’s largest software development network. Previously, as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →

This page is open source. Please help improve it.

Edit