GitHub · Primly Community

Went through the full GitHub eng loop last fall, here's what actually mattered

staff_steph · 5 replies

Did the GitHub Staff SWE loop in October. Sharing what I actually remember.

Recruiter screen was 30 minutes, pretty standard. She was good, asked about my background honestly and gave me real signal about what the team needed. Not the usual recital.

Phone technical screen: they gave me a problem involving parsing a git-like log structure. Nothing insane algorithmically, but the framing was clearly GitHub-flavored. That was refreshing. I got to talk about edge cases rather than just grinding through optimal complexity.

Virtual on-site (4 panels): Coding: two problems, both practical. One involved API design for a webhook system. The interviewer told me to think out loud and asked follow-up questions mid-solution. Felt collaborative. System design: design a simplified version of GitHub Actions. I was not expecting that level of domain specificity. Lean into it, it's a good sign. Behavioral: 3 questions, values-heavy. They really do care about influence without authority and how you've pushed back on decisions you disagreed with. Cross-functional leadership panel: this was for a staff-level hiring bar calibration. Very conversational. Less about what I built, more about how I shaped what got built and by whom.

Process took 5 weeks total. Offer was competitive but not top of band. The RSU vesting schedule was Microsoft-style (quarterly after 1-year cliff), worth asking about.

Biggest surprise: the interviewers were all clearly current GitHub employees who used GitHub daily. Questions felt like they came from real problems, not a question bank.

5 replies

frontend_fran

The system design being GitHub Actions-flavored is such a good detail. Did you prepare specifically for that or did it catch you off guard?

staff_steph

Caught me a little off guard but in a good way. I had prepared generic distributed systems stuff. Being comfortable with the problem space (I use Actions constantly) made up for not having a scripted answer. If you're interviewing for platform or dev tools teams, actually knowing the product helps more than an extra LeetCode session.

careerveteran

The behavioral weight for staff-level at GitHub tracks with what I've seen. Once you're past senior, the bar is almost entirely about influence and judgment. The coding round is almost a formality at that level, it's really a calibration check.

quietquit_quincy

5 weeks is long if you're employed and trying to keep it quiet. Did they accommodate scheduling flexibility at all or were you doing the 'urgent dentist appointment' thing on a Tuesday afternoon.

staff_steph

They were pretty good about it actually. Recruiter offered morning slots for most panels. I think I used one fake meeting and one real PTO day. Could have been worse.