I had applied for the Sr. Software Engineer position via their careers page. Although I had received rejections many times, this time I received an email inviting me to take a coding assessment.

Coding Assignment Round

They asked for my programming language of choice upfront. After four days, I received an email with a link to the Github Assignment bot. The assignment required me to add my logic to methods within pre-written tests to pass them – that's the basic criteria. Once you start the assignment, you should finish it within five hours. Although they mention it's preferable to complete within three hours, I'd suggest taking the full five hours but make sure to raise a PR within three hours. You can add changes on top of that. They intentionally don't specify any other criteria. Yet, you should make sure your code is:

• Production-grade (i.e., verbose logs, code comments, modular).
• Includes unit/integration tests for any applicable modules.

I received the results almost a week after submission and was selected for the next rounds.

There were two rounds after this: one coding round and one system design round. They would ask if you want to fast-track the application process by scheduling both rounds on the same day with a half-hour difference. DO NOT opt for that. I made this mistake because your performance in the second round can be affected by how the first round goes, as there will be barely ten to fifteen minutes between the two rounds.

Coding Round: The interviewer was friendly, although in a hurry to finish everything within an hour. This was an easy-medium question, which I could complete. Then, she moved to an LLD (Low-Level Design) question, which was also easy, but I fumbled. However, the overall feedback was good.

Then, we moved to the System Design Round: The interviewer was a Sr. Engineering Manager. He was very friendly too. He asked a medium-difficulty system design question. It could have been easily solved, but I was still replaying the mistakes from the first round. I provided a solution, but it wasn't enough, and time ran out. I was rejected.

Anyway, in case I had been selected, there would have been two non-technical rounds: one diversity round and one behavioral round containing situational-based questions. If I had gone through those, the final round would have been with the Hiring Manager for offer discussion.

On a side note, don't fall for the "no-whiteboard interviews" at Github. When I read other interview experiences on Glassdoor, they weren't using whiteboards. Unfortunately, that wasn't the case, at least in India. Also, the experience with HR was not that great, as mentioned in other reviews. Communication was mostly email-centric; even the rejection was a templated email.

Anyway, overall, I would say the interviews aren't difficult compared to FAANG, Uber, or similar companies. You should be able to crack them with moderate effort. All the best!

Questions were at an easy-moderate level. I cannot mention the exact questions as I have signed an NDA.