Getting hired by GitHub

August 28, 2014


I started working at GitHub in January of 2014, during the hiring process I read posts by Coby and Mu-an.


My job search started back in early August 2013. Experiences from working at more than my fair share of companies in the past 14 years had been a mix of highs and humbling moments. Distilling what I was looking for had become simple, what I needed was to:

I love GitHub, and there were and are plenty of colleagues and friends who shared the sentiment.

For those developers that have implemented GitHub as part of their work flow, it has made fundamental changes to how products and services are being developed and deployed to the web. The changes have been deep and profound. GitHub is not merely a wrapper around Git or just a place to store source code. Pull requests, merges and Forks have enabled some workflows and processes to be easily integrated into existing workflows. For many development teams, pull requests + webhooks have made automated testing and continuous integration something that can be set up with a few clicks of the button.

For better and for worse, contribution to public projects has changed as well. There is a new generation of developers an Open Source project is not defined by the type of license it has but by whether or not it is up on GitHub.

For me, GitHub had become a central part of my work flow. As development teams moved over to GitHub hosted code, I was learning how to use git. When I finally learned how to code, GitHub was central part of the Ruby on Rails tutorial.

First Contact

In August 2013, my job search started when I went to the jobs page at GitHub and found that they were looking for Technical Supportocats in non-US Timezones. As GitHub has grown it has gained customers from timezones all over the globe. Optimizing for happiness now meant finding support people in timezones all over the world.

Luckily, there were some Hubbers visiting Japan on the week that I started looking into working at GitHub. I was able to meet with them and learn about position, working at GitHub, and the interview process.

The process started with my application on GitHub Jobs. The first part of the interview process is answering sample questions and filling out a questionnaire. This part was fun, but each subsequent part of the process was even more fun, while also increasingly nerve wracking.


A couple weeks after the questionnaire, the actual interview part of the interview process started. Over the next two months, I Skyped with four different Supportocats. It was pretty clear that they were building their picture of who I was. Each interview was different as they filled in the blanks.

Stories like this about GitHub gave me some insight into how support at GitHub worked. The interview process would only strengthen the positive feelings that I had about GitHub and support at GitHub.

Each interview was more a conversation than an interrogation, and as I had anticipated each time I talked to another Hubber, the feeling that I wanted to work with them got stronger.

Onsite Interview

The final step was an onsite interview at GitHub HQ 3.0 in San Francisco. My onsite was the week of Thanksgiving (the other option was to wait until late January). I was flown out a couple of days in advance of the onsite interview. I was hoping to get over my jet lag. Unfortunately, jet lag was not (or was?) my friend that week and I was not able to sleep for over 24 hours leading up to the morning of the interview.

The onsite started with a nice breakfast. @sundaykofax and @jgreet let me know who I would be meeting that day, and I let them nkow that I was super jetlagged.

The rest of the day was a bit of a blur (I think I drooled a lot), but it was still very clear that each interview was probing a different area that was crucial for the position and for being a Hubber. I met with Supportocats, developers and designers.

Each session was 45 minutes to an hour. Each conversation was a lot of fun, at this point I was almost desperate as I really wanted to work with these people.

The last session of the day was pairing up with @jgreet to answer some actual tickets. I was super nervous but, I was so jetlagged that it probably all balanced out.

The Waiting

The next few weeks were waiting to hear back. There was an incident or two that made this part take longer than anyone had hoped, but @sundaykofax was very open about what was going on (to the extent that she could be).

At this point I was sure that I loved the product/service. And people that I met and talked to from GitHub were just plain amazing.

The day after my wife was hospitalized to prepare for the birth of our second child (our daughter!), I received an amazing (electronic) letter from GitHub.

Eight Months Later

It’s been over eight months since I joined the company and I can honestly say that this has been the most incredible job and company that I have had.

And, we’re hiring.

Discussion, links, and tweets

Good Morning!