Finished GitHub's PM loop in February. Got to the offer stage but ended up declining for a different role. Sharing this because there's not much GitHub PM-specific content out there.
The process was: recruiter screen, PM phone screen with a current PM, then a virtual onsite with 4 rounds.
Phone screen focused on a product case. They gave me roughly a week of notice and sent a brief. The brief was about improving a specific GitHub feature (the one I got was around notification management, which tells you something about their internal focus areas). 30-minute presentation, 30-minute Q&A. The prep time was more than I expected.
Onsite rounds:
Product sense. Traditional case format. They asked me how I'd think about improving GitHub for a specific user segment. I got open source maintainers, which again felt very specifically tailored to their business context rather than generic. They pushed me on prioritization and metrics.
Strategy. Higher-level. Where do you see the developer tools space in 5 years, what does that mean for GitHub, what bets would you make. This requires genuine knowledge of the space. Copilot, the IDE integrations market, Codespaces, Actions as a CI/CD platform. You need to have a real view.
Execution. "Tell me about a time you shipped a feature that failed and what you learned." Standard, but they went deep on specifics. Wanted actual numbers, actual timeline, actual changes you made.
Behavioral. Same async-focus themes that come up in the SWE interviews. They seem to apply this to everyone.
Salary range for PM at GitHub: for senior PM in remote US roles I saw ranges in the 200-270k total comp ballpark in public discussions, though my specific situation was more complex. Worth researching current levels.fyi data.
Overall GitHub PM interviews felt more substantive than a lot of PM loops I've done. Less brain-teaser energy, more "do you actually know how to think about product."