Developer Tools

How to get a job at GitHub

20 real interview questions, insider tips on the hiring process, and what GitHub actually looks for. Most people read about it. Very few practise for it.

London, UK 2,000+ 4.4/5/5 Glassdoor
Practise GitHub interview free

Sign up free · No card needed · Free trial on all plans

Video Interview Practice

Choose your interview type

Your question

Tell me about yourself and what makes you a strong candidate for this role.

30s preparation 2 min recording Camera + mic

About GitHub

Company overview

GitHub operates offices in London supporting product development, customer success, and operations. GitHub is the world's leading platform for software development and collaboration, with over 100 million developers on the platform.

The London office contributes to product development with focus on developer experience, AI-assisted development, and enterprise features.

Inside the company

Culture & values at GitHub

GitHub's culture emphasises developer focus, openness, and collaboration. The company values transparency and putting developers first. Culture is inclusive and innovation-driven.

Work-life balance is genuine, with flexible arrangements and remote-first policies. GitHub invests in employee development and celebrates learning and growth.

Why people want to work here

Work on the platform where developers collaborate globally. GitHub offers competitive compensation, remote-first flexibility, meaningful work impacting millions of developers, and exposure to AI and developer experience innovation.

What to expect

Working at GitHub

The working environment at GitHub reflects the developer tools sector — structured but dynamic, with a mix of planned project work and responsive tasks. Most roles involve regular collaboration with colleagues across different teams and functions, with clear expectations for deliverables and timelines. Flexible and hybrid working arrangements are increasingly common, and the organisation recognises that different roles require different working patterns.

As a 2,000+-person organisation, GitHub sits at a size where you can genuinely know people across different departments. Teams tend to be close-knit, and there's a real sense of shared purpose. You'll likely have more visibility with senior leadership than you would at a larger employer, which means your contributions are noticed and your ideas can reach decision-makers more quickly.

The culture at GitHub shapes how the day feels beyond just the work itself. Colleagues describe the environment as one that values Developer Empathy and Technical Strength. Lunch breaks, team socials, and informal catch-ups are part of the rhythm — GitHub recognises that building relationships across the organisation is as important as the deliverables themselves. Most employees report that the people are one of the best things about working here, and that the team dynamic makes challenging work feel manageable.

The hiring journey

GitHub interview process

GitHub's interview process focuses on technical skills, problem-solving, and cultural fit. Interviews assess coding, system design, and collaboration. The company values communication and developer empathy.

1

Recruiter Screen

20–30 minutes

Initial conversation about background and interest in GitHub.

2

Technical Phone Interview

45–60 minutes

Coding or system design. GitHub expects thoughtful, well-communicated solutions.

3

On-site / Virtual Interviews (2–3 rounds)

45–60 minutes each

Technical interviews and team fit discussion. Assess collaboration and cultural alignment.

4

Manager Round

30–45 minutes

Conversation with hiring manager about role and team.

2–3 weeks from first contact to offer

Insider tips

Show genuine interest in developer tools and GitHub's mission. Be familiar with GitHub if possible. Emphasise collaboration and communication. Ask about remote work and team dynamics. Demonstrate developer empathy.

Stand out from the crowd

What GitHub looks for

Developer Empathy

Deep understanding of developer needs and workflows. GitHub is for developers; you need to think like one.

Technical Strength

Strong fundamentals and problem-solving ability. GitHub hires capable engineers.

Collaboration & Communication

Clear communicator who works well in teams. Remote-first requires excellent communication.

Ownership

Take responsibility for projects and outcomes. GitHub trusts engineers with autonomy.

Continuous Learning

Growth mindset and willingness to develop new skills. AI and emerging tech are evolving rapidly.

Real questions asked

GitHub interview questions

20 questions sourced from real GitHub candidates. Practise answering them out loud before your interview.

  • 1Tell me about your experience as a developer using GitHub.
  • 2Describe a project involving collaboration or version control.
  • 3How do you approach building developer tools?
  • 4Tell me about a time you collaborated effectively in a remote environment.
  • 5Describe your experience with APIs or integrations.
  • 6How do you think about user experience for developers?
  • 7Tell me about a time you shipped something you're proud of.
  • 8Describe your approach to code quality and testing.

Your career here

Growth & development at GitHub

Career progression at GitHub follows a relatively clear path for most roles. Promotions typically depend on demonstrating increased responsibility, deeper expertise, and leadership capability — whether that's leading teams, managing clients, or driving technical innovation. The organisation values both specialist depth and the ability to take on broader management responsibilities, so there are usually multiple progression routes available. Don't assume you need to move into management to advance — many developer tools organisations increasingly recognise and reward technical and specialist career paths.

GitHub invests in structured learning and development programmes, including access to training courses, conferences, and professional certifications. Many employees report that the L&D budget is generous and genuinely encouraged — not just a line in the benefits package that nobody actually uses. Whether it's technical upskilling, leadership development, or industry certifications, there's real support for continuous learning. While formal mentoring programmes may vary across departments, the culture generally encourages learning from more experienced colleagues. Building relationships with senior team members is one of the most effective ways to accelerate your development — seek out people whose career trajectory you admire and ask them for advice regularly.

For technology professionals, GitHub offers exposure to projects and challenges that build a strong CV whether you stay long-term or move on after a few years. The skills and experience you gain — particularly around Developer Empathy and Technical Strength — are transferable across the developer tools sector and beyond. Internal mobility is possible for strong performers, with opportunities to move between teams, departments, or even locations as your career develops. Many senior leaders at GitHub started in entry-level or early-career positions, which speaks to the genuine career development opportunities available.

Compensation

Salary & benefits at GitHub

GitHub UK salaries are competitive. Engineers typically earn £100,000–£150,000 base salary, with annual bonuses (15–25%) and equity. Total packages are strong and comparable to Big Tech.

Notable benefits

Competitive salary and performance bonuses
Equity grants vesting over 4 years
Comprehensive health, dental, and vision insurance
Unlimited paid time off (PTO)
Remote-first and flexible working
Learning and development budget
Home office equipment and allowance
Mental health and wellness support
Parental leave (up to 16 weeks paid)
Relocation and visa assistance

How they hire

What it's like interviewing at GitHub

With 2,000+ employees, GitHub doesn't hire in massive volumes, which means each vacancy gets focused attention. You're less likely to be processed through an impersonal system — expect more direct interaction with hiring managers earlier in the process. The flip side is that roles may appear less frequently, so when a position opens, move quickly with a strong application.

The interview culture at GitHub balances professionalism with personality. They're assessing whether you can do the job and whether you'll fit the team — both matter. Come prepared to demonstrate Developer Empathy and Technical Strength through specific examples, but also be ready for more open-ended conversation about your ambitions and what motivates you.

Life at the company

Work-life balance at GitHub

GitHub offers flexible and hybrid working arrangements for most roles. The specifics vary by team and function — some roles are predominantly remote, others require regular office presence — but the overall direction is towards flexibility. This isn't just policy on paper: employees generally report that managers support flexible working in practice, not just in the handbook. Notable extras include dedicated wellbeing and mental health support.

The overall pace at GitHub is shaped by technology cycles and business priorities. Most employees report a manageable workload with occasional busy periods tied to project deadlines or seasonal demand. The company increasingly recognises that sustainable performance requires sustainable working patterns, and there's a genuine effort to support employee wellbeing alongside commercial objectives.

Frequently asked questions

How remote-first is GitHub?

Genuinely remote-first. GitHub acquired by Microsoft in 2018 but maintains independence and remote-first culture. Teams are distributed globally, and full remote work is the norm. Office space exists but is optional.

What's the impact of Microsoft ownership?

GitHub maintains independence and developer-first focus. Microsoft integration exists (account linking, etc.), but GitHub's core mission and culture haven't changed. Microsoft provides resources and scale; GitHub retains autonomy.

How much of the work involves AI and automation?

Increasing. GitHub is investing heavily in AI (Copilot, code analysis). If AI interests you, GitHub has significant opportunities. Traditional development work continues alongside AI initiatives.

What's the community and open-source involvement like?

Central. GitHub celebrates open-source and developer community. Employees often contribute to open-source and engage with the community. If community matters to you, it's well-aligned.

How are promotions and growth handled?

Merit-based and regular for strong performers. GitHub promotes from within and encourages growth. Promotions are transparent, and you'll know where you stand.

Can I contribute to open-source as an employee?

Yes. GitHub encourages open-source contribution and allocates time for community engagement. Many employees maintain projects and contribute to public repositories.

What is the work-life balance like at GitHub?

Work-life balance at GitHub varies by role and team. Most employees report a reasonable workload with flexible working options available for many roles. Like any organisation, there are busier periods, but the overall culture supports sustainable working patterns.

Does GitHub sponsor work visas for UK roles?

Visa sponsorship at GitHub may be available for specialist roles. Check their careers page or contact their recruitment team directly to confirm whether the specific position you're interested in offers sponsorship. Immigration policy changes can affect eligibility, so verify current requirements with GitHub's HR team during the application process.

Your GitHub interview is coming.

Be ready for it.

Practise with real GitHub questions, get scored across 6 competencies, and walk in confident you can perform under pressure.

Start free

Sign up free · No card needed