Mission: Our mission is simple; code is about the people writing it. We focus on lowering the barriers of collaboration by building powerful features into our products that make it easier to contribute. The tools we create help individuals and companies, public and private, to write ...
Coming in at #28 for companies leading in cloud computing! http://glassdoor.com/slink.htm?key=vQelQ
Check out what one of our newest team members had to say about their time interviewing @ GitHub: http://glassdoor.com/slink.htm?key=vQElW
Come help us make collaboration even better!
Founded in 2008 and based in San Francisco, California GitHub is the world's largest code host community.
At GitHub we build the tools that make collaborating and writing software easier for everyone. We’ve built a company we truly love working for, and we think you will too.
At the core, GitHub is how people build software. With a community of more than 14 million people, developers and non-developers can discover, use, and contribute to over 30 million projects using a powerful collaborative development workflow.
A Remote and Flexible Workplace
At GitHub, we think that a diverse company is a strong company, and we work hard to foster a supportive and welcoming workplace.
We encourage Hubbers to build amazing things with a high level of autonomy and self-direction. Work/life integration is important to us, which is why we offer flexible work schedules and unlimited PTO. We believe that if a job allows for it, people should work wherever and whenever they’re happiest.
A diverse and inclusive workplace
At GitHub, we think that a diverse company is a strong company, and we work hard to foster a supportive and welcoming workplace.Our office
Our office in SOMA is designed for everyone to work better and happier, and includes unique spaces like a cafe, a game room and library to cater to any work style. Some of our local GitHub staples include an annual charitable dodgeball tournament, and various athletic groups.You + Your Family
All full time employees enjoy 100% coverage of health insurance premiums across our Medical, Dental and Vision plan offerings, including coverage for dependents. We also offer four months of paid family leave to all new parents with the flexibility of using it all at once, or throughout the baby’s first year.Stay fit
We cover gym memberships and offer fitness classes in our onsite gym, the OctoDojo. In the Zen room, Hubbers can recharge through meditation or complimentary massage.The Future
Every Hubber has a stake in the future success of GitHub with stock option grants. For full time employees we offer competitive 401k planning with a dollar-for-dollar company match of up to 4% of your year-to-date salary.Keep growing
Everyone at GitHub receives an Amazon gift card to buy the books they need. We’ll also send you to one work-related conference per year of your choice, anywhere in the world. If you’re invited to speak at a conference, we’ll cover you to get there.
Please note that benefits vary by country, the ones shown above are for our US based employees. Benefit information for non-US based positions will be provided to individuals who interview for those roles.
There are over 600 of us (Hubbers) and you can find us all over the world! Over %50 of the company works remote and so we use and build tools that enable us to do that best work of our lives at any time of the day and any place.
GitHub is made up of people with many different backgrounds and lifestyles, and we like it that way. We invite applications from people of all stripes. We don't discriminate against employees or applicants based on gender identity or expression, sexual orientation, race, religion, age, national origin, citizenship, pregnancy status, veteran status, or any other differences that people imagine to discriminate against one another.
Internships at GitHub
No coffee runs here! We love watching talented people learn and explore their skills. Our interns gain real work experience by pairing up with GitHubbers on real projects.
Check out what our 2016 class worked on here!
A Letter from our CEO
At GitHub our goal is to help everyone build better software. To do that, we know we must create a company where anyone, regardless of what they look like or where they come from, can grow and thrive. When we deliberately seek different perspectives, life experiences, and identities, we can build better products for developers all around the world.
Over the past 18 months, diversity and inclusion have become a major focus for us. We’ve learned how diversity of life experiences makes a big difference in how we identify and solve problems, design software, and communicate. Today, we’re releasing our diversity data for the first time to show where we’ve made progress, where we haven’t, and to be transparent about how much further we have to go. We will also provide updates annually and share lessons we learn along the way.
This journey started for us in 2014, after we made some major mistakes and people got hurt. We were forced to re-evaluate our culture and our goals. We had to ask ourselves hard questions about where we fell short.
We started by looking at our own demographics—and they weren’t good. Our diversity was nowhere near industry standard, which is already too low. We also asked what we needed to do to make GitHub a place where everyone can do their best work, then started making changes.
So far, we’re seeing early signs of progress. For example, GitHub has grown from under 1% women of color at the end of 2014 to over 10% today. We’ve increased the number of women in leadership roles to 35% while the number of women overall has grown from 21% in 2014 to 36% today. Of our US employees, 6% are Latino and more than 1% of Hubbers identify as transgender, genderqueer, or nonbinary. We are proud that these are all growing segments of our company.
Still, we are falling short in obvious ways. There are no Black/African-American GitHubbers in management positions, which is unacceptable. Diversity in technical roles lags behind our overall organization. Our gender imbalance remains. And we still have a lot of work to do to ensure we are building an inclusive culture.
Specifically some of the areas we’re focusing on are:
Improving our recruitment processes to find candidates from all backgrounds, ensure that they meet a diverse slate of interviewers, and improve our hiring and onboarding practices so they are inclusive.
Institutionalizing our long-held belief that formal education is only one of many paths to success at GitHub and in tech overall. We want to hire great people based on their skills, which can be obtained in a multitude of ways.
Providing training for all Hubbers on building emotional intelligence, mitigating bias, and interpersonal communication as critical pieces of building inclusive culture.
Expanding our benefits to include transgender health care, fertility treatments, and ensuring that our maternity/paternity leave policies exceed the tech industry’s norms.
Modifying our San Francisco office to be more accessible. We’ve always intended our headquarters to be welcoming to our community by hosting events and are currently making changes to make it more inclusive. Hopefully we’ll see you here someday in the future.
Building partnerships with organizations that are successfully removing barriers to entry in tech like EveryoneOn, CODE2040, and Maven. This is a deliberate investment in the future workforce of our industry and in those who will increasingly use GitHub to build amazing things.
In looking at our data and the areas we're focusing on, there's a lot to be hopeful about—but we still have so much further to go. We are just at the beginning of making substantial changes and seeing their results.
I’ve personally learned a great deal over the past few years. One huge lesson for me has been learning that everyone has the potential to be a great developer, but not everyone has the opportunity. That's something we want to fix in our company and our community, and I invite you to join us in doing so.
I’ve also learned that increasing diversity isn’t a short term project but a lifelong journey. We want our company to reflect our world and I look forward to sharing updates on our progress with you in the future.
View our Diversity report here
I have been working at GitHub full-time (More than a year)
- Great benefits
- Empathetic co-workers
- Most people are easy to work with
- Great distributed workforce culture
- Not easy to communicate across departments
- Too much chaos and change
- Not enough goal alignment throughout the company
- Many people fight the implementation of processes
- While some people are brilliant, some are VERY inexperienced. Need more senior people who can mentor others.
- Culture is changing and things are becoming more so like a large company
Advice to Management
Implement more processes (This will help with company growth), keep up the social impact work and culture (Don't become a company that is only about lip service), improve the current benefits (instead of cutting them), remain true to the company values.
I applied online. The process took 3 weeks. I interviewed at GitHub (Seattle, WA) in October 2017.
The interview process was quite efficient. First, there was a short video conference screen with a member of the talent acquisition team. Then, the first of two technical and interpersonal interviews. The final round consisted of a series of 45 min interviews with members of the team and a diversity and inclusion discussion with a member of the human resources team. The interview process concluded with a short conversation the development manager and followup with the same talent acquisition team member.
This was the most relaxed and friendly interview process I have ever experienced! The team member interaction during the process was awesome.
I felt that I did well but stuttered on one of the technical questions. GitHub is very much committed to diversity and inclusion and the interview process was mostly centered around interpersonal interaction and communication skill. They seem to walk the walk, so to speak. I would say this position, specifically, seems to require someone both technically adept (well versed in Ruby) and effective at communicating complex technical problems into simple language.