GitHub logo

GitHub

Size:
1000+ employees
time icon
Founded:
2008
About:
GitHub is a web-based platform for developers to host and collaborate on software projects through Git. Its tools include repository management, pull requests, issue tracking, automation, security, and AI-driven development for individuals and organizations. Founded in 2008 and based in San Francisco, it is a Microsoft-owned subsidiary since 2018.

GitHub Interview Questions: 2 Questions to Prepare for in 2026

November 20, 2026
Questions
2
tracked from real interviews
Difficulty
0 Easy2 Med0 Hard
Rounds
3–4
Recruiter + technical loop + culture
Interview Process
1
Recruiter conversation
Background, motivation, and role fit
screen
2
Technical interview 1
Practical implementation and clear tradeoffs
coding
3
Technical interview 2
APIs, debugging, or another role-specific exercise
technical
4
Culture interview
Collaboration, feedback, and decision-making stories
behavioral
Topics Covered
Practical coding HTTP and APIs Debugging Collaboration Feedback Project judgment
Recent software-engineering accounts describe practical technical exercises alongside a culture interview. The exact technical format varies by team and seniority.

GitHub software-engineering interviews combine hands-on technical work with conversations about teamwork, decision-making, and difficult situations. One Software Engineer II process included a recruiter conversation, two technical interviews, and a culture interview. The loop varies by team, so use your recruiter's packet as the final source for the format.

What to Expect: GitHub Interview Process

The recruiter interview usually covers your background and fit for the role. The process has no single standard format and may include hands-on application work. Recent applicants have reported small application tasks and HTTP/API work, followed by conversations about culture, teamwork, and decision-making.

Be prepared to explain requirements and review your own code. A correct answer may still be incomplete if you omit testing, error handling, or the reasoning behind the interface. For the culture round, prepare stories detailed enough to distinguish your decisions from your team's work. Make the outcome specific and verifiable.

How to Prepare and Pass GitHub Interviews

If your implementation skills are current, give yourself at least four to six weeks. During the first half, build small, realistic projects: parse input, call or design an API, test edge cases, and explain what you would change with more time. During the second half, rehearse concise stories about conflict, feedback, and ambiguous projects.

Complete at least two sessions in a shared editor. Start by confirming inputs and failure behavior. Then, while acting as the interviewer, give your partner time to run tests and read the results. For an HTTP exercise, discuss timeouts, retries, response validation, and how you would keep the client easy to change. This sequence makes your engineering judgment clear.

Focus each story on the context, your decision, and the result. Use Lodely for company-specific practice with detailed editorials and daily questions.

GitHub
GitHub Interview Questions
Recently asked in real interviews
These questions were asked recently in real GitHub interviews. Practice these and 4,000+ other questions from 1,000+ companies on Lodely.
Explore All Questions
Free to get started

GitHub Interview Breakdown

Tell me about a time when you solved a complex problem and how you went about it.

GitHub Interview Question
Medium
Tell me about a time when you solved a complex problem and how you went about it.
behavioral
Choose one genuinely complex problem and explain how you reduced the ambiguity, weighed options, handled blockers, and measured the result.
Also Asked At
AmazonAtlassianGoogleIntuitMicrosoftOpenAIOracle
Open Question on LodelyFree to get started

Type: Behavioral problem-solving. The Trick: Choose a problem with some ambiguity and explain which alternative solutions you rejected. What It Tests: Ownership, judgment, and clear explanation.

Tell me about a time when you had to deliver negative feedback.

GitHub Interview Question
Medium
Tell me about a time when you had to deliver negative feedback.
behavioral
Describe a specific feedback conversation, the evidence you used, how you protected the working relationship, and what changed afterward.
Also Asked At
AnthropicFacebookGoogle
Open Question on LodelyFree to get started

Type: Behavioral collaboration. The Trick: Show that you communicated directly without making the story about someone else's shortcomings. What It Tests: Directness, empathy, and whether your feedback led to a change.

What Comes After The Interview

The panel reviews the technical and culture signals before the recruiter communicates the decision. If you receive an offer, compare the entire package. As of August 2026, the reported median U.S. total compensation for an E4 is $283K. Base pay remains the largest component, and equity vests over four years.

Candidate Experiences

One recent Software Engineer II candidate described moving from a recruiter conversation directly to an interview day. That day included two technical sessions—one involving a small game and another involving HTTP calls—plus a separate culture interview. The candidate accepted the offer and described the process as straightforward. Prepare for practical building tasks and a focused discussion about collaboration.

Conclusion

GitHub values real-world results, tradeoffs, and authentic stories of collaboration. Use Lodely to practice GitHub questions and understand the reasoning behind each answer before your interview.

Compensation by Level
Level
Title
Median
Annual breakdown
E1
Software Engineer
$139K
$115K base · $13.7K stock · $9.9K bonus
E2
Software Engineer II
$162K
$134K base · $18.7K stock · $9.8K bonus
E3
Software Engineer III
$203K
$162K base · $27.9K stock · $13.2K bonus
E4
Senior Software Engineer
$283K
$210K base · $51.2K stock · $21.6K bonus
Table of Contents

Land Your Dream Software Engineering Job

Start Now
Sent! Land top tier tech offers.
start your free trial →
Oops! Something went wrong while submitting the form.

Land Your Dream Software Engineering Job

Start Now
Sent! Land top tier tech offers.
start your free trial →
Oops! Something went wrong while submitting the form.

Other Company Interviews

Browse all