Taro Logo

Senior Software Engineer Interview Experience - New York, New York

June 1, 2021
Negative ExperienceNo Offer

Process

Worst experience ever. It took a week to get the link to an assessment involving the building of an API. In a traditional interview, someone gives you a problem to solve or an API that needs to be designed, and you come up with the solution. The other person is right there, so you can immediately ask questions to clarify what they are looking for.

Not here, lmao. You are given a very vague set of requirements, and if you simply create what was asked, you are disqualified. I added tests, wrote a good PR message, and added documentation. But guess what? I missed a requirement. In the midst of 3 hours of coding the solution and tweaking, I missed one feature. That was enough to instantly disqualify me. I never spoke to anyone – not HR, not a technical person. I was never asked any questions like why I missed the feature or how I would implement it if I had the time. There is no one there to clarify anything, just an anonymous automated message to tell you that you did not pass.

Quite an asinine way to waste 3 hours of my life.

Tips for anyone doing the first assessment:

  • Make sure your storage handles de-duping data (in my case, I forgot this, but it would have been a one-line change, so don't mess it up).
  • Also, it says it should take 2 hours; that is a lie. Go ham with the 5 hours they give you.
  • Finally, if at any time you feel the process is BS, go do something else. GitHub isn't the only company out there.

Questions

Implement Data Storage API

  • Fix basic spelling and grammar mistakes.
  • Add newlines and spacing as appropriate.
  • Format lists with bullet points when they are present in plain text.
  • Add newlines in appropriate places to avoid "wall-of-text" presentation.
  • For numbered or bulleted lists, keep list items close together without extra newlines between each point.
  • Do not format into a bulleted list if there are fewer than 2 items to display.

While doing this, make sure to respect the original text as much as possible. Don't add entire phrases or sentences. At most, add a verb here or there if it's missing. The final word count of the cleaned text should be within 10% of the original text.

Interview Statistics

The following metrics were computed from 4 interview experiences for the GitHub Senior Software Engineer role in New York, New York.

Success Rate

50%
Pass Rate

GitHub's interview process for their Senior Software Engineer roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive75%
Neutral0%
Negative25%

Candidates reported having very good feelings for GitHub's Senior Software Engineer interview process in New York, New York.