Software Engineer Interview Experience - Oakland, California
Process
After a video chat with the hiring manager, I scheduled a time to do an online test for GitHub.
In a separate email, I was informed that the test would involve writing a simple NodeJS AddOn, and that the particular task didn't require specialized domain knowledge beyond knowing C++.
The email informed me that the code for the test was developed against a specific version of NodeJS, which was older than the available current version, and that I would be sent a link to the GitHub repo, which would be accessible for a limited time.
Finally, the email said there would be a README file that contained specific instructions for setting up the development environment.
On the day of the test, I received an automated email that contained a link to the GitHub repository, as promised.
I cloned the repository onto my laptop. There was a README file that contained a description of the problem I was supposed to solve. The file contained information about how to run the unit tests to exercise the project I was supposed to modify, but there were no instructions on setting up the environment to run the project.
I spent a significant amount of time and effort just setting up the development environment, as I had to scour the GitHub forums to resolve my issues.
I only have a passing familiarity with NodeJS and had never written a NodeJS AddOn, which I admitted readily to the hiring manager. However, it was really unfair to have to struggle with development environment set-up issues in addition to having to work with a new technology on a time-limited test.
That stress over the development environment was completely unnecessary.
On top of that, one of the unit test scripts contained an output formatting error. This bug in the test script resulted in the failure of the unit tests because the output lines it produced did not contain carriage returns, even though the output lines produced by the test from the solution logically matched the output lines of the file containing expected output.
Given that the expectation was that the unit tests were supposed to be a black box, it was unclear whether the bug in the test script was an intentional bug I was expected to fix.
Dealing with these set-up problems and debugging the unit test script issues ate up a good chunk of the time I was given to access the test repository. Although I solved the problem itself, I was not able to make a clean submission for my test.
In conclusion, this test had one of the shoddiest set-ups I have ever experienced.
Coding tests should be fun, and while I learned a new technology (NodeJS AddOns are cool!), the stress from the set-up problems with which I had to deal – problems that could have been solved with better instructions – did not make this test fun.
Questions
Write a NodeJS Addon, and make sure it passes all the provided unit tests.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the GitHub Software Engineer role in Oakland, California.
Success Rate
GitHub's interview process for their Software Engineer roles in Oakland, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for GitHub's Software Engineer interview process in Oakland, California.
GitHub Work Experiences
- 5.0Culture of a startup with the backing of an MNCSoftware Engineer • Current EmployeeHyderābād, Telangana, IndiaMay 14, 2021Pros: Awesome people, lots of new projects. Perks like upfront home office, L&D, and mobile reimbursement.Cons: In GitHub India, a shadow of MS culture can still be seen.
- 5.0Great company, great colleagues, great ❤️Software Engineer • Current EmployeeRemote, Oregon, United StatesJune 8, 2015Pros: The best part about working at GitHub is the great colleagues! They are uniformly friendly, super talented, and have a positive, supportive attitude. All the engineers I have worked with have been really motivated and produce high-quality work. A majority of GitHub employees work remotely; some in small satellite offices, but most at home, cafes, or shared office space, whatever. Because of this, the company goes to a lot of effort to make remote work effective. Communications are largely asynchronous (e.g., via GitHub issues and pull requests), most meetings are streamed and recorded, and there are lots of chances to meet other GitHubbers when necessary: the annual company summit, mini-summits for departments or teams kicking off a project, plus we are welcome to travel to visit HQ or other GitHubbers when we feel the urge to connect. Most "synchronous" discussion takes place in online chat, though even here transcripts are kept for anybody to read. Time zones can be a real hassle, but otherwise it all works quite well. It's so awesome being able to work for a San Francisco-based company while being able to live almost anywhere! The company is very transparent. Many company-wide issues are discussed in the open, and anybody's input is welcome. Until the beginning of 2014, GitHub didn't have any formal management structure to speak of. The result was predictable: people worked on what they found exciting, but it was hard to gather critical mass to implement large-scale projects. Since then, people-managers have been introduced, which has improved the company focus. So far, management has used a relatively light touch. In particular, work is still mostly organized by the engineers working on it rather than top-down by management. In my opinion, the introduction of management has improved the company, though it has definitely caused a shift in the culture. GitHub, the company, also seems to have a good heart. As far as I can tell, everybody at the company, from top to bottom, is really trying hard to do the right thing: * There is a constant internal dialog about how to improve diversity, both within GitHub (e.g., by doing everything we can to eliminate bias in our recruiting processes) and also within the whole industry (for example, by supporting organizations and events that are targeted at underrepresented groups). This isn't just an HR goal; we are all thinking about it. * We do everything we can to support open-source software. Most obviously, we provide free Git hosting to open-source projects, and we give our free users every bit the same level of support as we give to our paying customers. We contribute internally-developed code to upstream open-source projects as much as possible. We have "open-source Fridays" twice a month when GitHubbers are encouraged to work on open-source projects. We sponsor many open-source conferences and other events. * GitHub promotes a healthy work-life balance. I guess (being alpha-geeks) a lot of us work too many hours, but that pressure doesn't come from the company. I've never seen anything but encouragement for people announcing vacation (which is unlimited) or taking parental leave (4 months PTO for new parents). Finally, it's great to build a product that millions of people use and love. It's a pleasure to run into GitHub users in real life because they are so positive about the company. We're helping to propagate the open-source ethos: * We provide a great place for open-source projects to host their code. * Companies use GitHub to promote code-sharing and communal development internally, and often to open-source internal projects. * There are even governments that put draft legislation in GitHub and allow citizens to propose pull requests to change it. Reading back over what I've written, it sounds like I'm a marketing shill. But in fact, I'm just a very happy software engineer. After nearly two years at the company, I am still almost giddy that I get to work at GitHub.Cons: Remote work impedes serendipitous communication. It's an effort to keep up with what is happening in the rest of the company when you don't bump into your colleagues in the kitchen or in the elevator. As a hangover from the management-free days, it can sometimes still be hard to figure out who is in charge of what.
- 5.0Awesome Team, Remote FriendlySoftware Engineer • Former EmployeeAlexandria, Alexandria Governorate, EgyptDecember 9, 2020Pros: Great, remote-friendly, flexible, awesome team.Cons: The only con is that it doesn't hire from all places in the world. I had to work through a third-party company.
GitHub Interview Questions
