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:
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.
Chris Wanstrath, CEO & Co-Founder
(as of May 23, 2016)
This report is comprised of information that GitHub employees (“Hubbers”) identified for themselves. We are strongly committed to self-identification while remaining cognizant that the standard reporting categories mandated by the U.S. federal government are not as inclusive as they need to be.
Where data is available, we have chosen to share progress made from 12/31/2014 to the present.
576 Hubbers
44% Based in San Francisco HQ
35% US-based, not in SF
20% International
(as of May 23, 2016)
36% Women
64% Men
A deeper look at gender at GitHub shows us that over 1% of Hubbers identify as transgender, genderqueer, or nonbinary. We are proud that this is a growing segment of our company.
(2014)
21% Women
79% Men
(as of May 23, 2016)
35% Women
65% Men
"Leaders" are defined as anyone who manages others at GitHub.
(as of May 23, 2016)
22% Women
78% Men
Technical roles include everyone in the Engineering organization and Engineers embedded in other areas (e.g. Sales). This also includes all technical roles in the Product organization. The Support function is not included in this data.
(US only)
(as of May 23, 2016)
2% Black or African-American
6% Hispanic or Latino
5% Two or more races/ethnicities
12% Asian
11% Unreported
64% White
(2014)
<1% Black or African-American
3% Hispanic or Latino
6% Two or more races/ethnicities
6% Asian
17% Unreported
67% White
(as of May 23, 2016)
0% Black or African-American
3% Hispanic or Latino
7% Two or more races/ethnicities
17% Asian
10% Unreported
63% White
“Leaders” are defined as anyone who manages others at GitHub.
(as of May 23, 2016)
1% Black or African-American
4% Hispanic or Latino
3% Two or more races/ethnicities
13% Asian
14% Unreported
65% White
Technical roles include everyone in the Engineering organization and Engineers embedded in other areas (e.g. Sales). This also includes all technical roles in the Product organization. The Support function is not included in this data.
(as of May 23, 2016)
4% Black or African-American
7% Hispanic or Latino
7% Two or more races/ethnicities
15% Asian
10% Unreported
57% White
Intersectional data is critical to understanding the growth of our diversity. We will increase the number of axes along which we will report Hubber data in the future. On this first iteration, we have chosen to report data on the intersectionality of race/ethnicity and gender.
% of Total Hubbers
Age range
Due to the current conversation around the lack of age diversity in tech, we have chosen to report and measure this demographic as our baseline and will continue to do so.
Average age: 34
Median age: 33
40%
We are pleased to report that 40% of Hubbers who self-reported are parents or step-parents. From newborns to children in their 20s. Our “Octokittens” are an important part of life at GitHub. We have a flexible paid time-off policy and our maternity/paternity leave policies exceed the tech industry’s norm. In addition, our policies do not differentiate between maternity or paternity leave.