GitHub Sr. Software Engineer interview questions

I recently applied for a senior role and a recruiter reached out and asked me to complete a coding exercise that needed to be finished within 5 hours of starting it. It was a simple exercise that asked to create basic HTTP services to upload/download files and there were a few unit tests that needed to pass. I completed the exercise by taking into account proper solution structuring, registering DIs, creating repositories/services/models, etc. I think it was a pretty good solution for the problem described. I even wrote a detailed paragraph explaining how the code could be improved in a real world use case. The recruiter came back with a rejection email in a week and did not provide any feedback. At this point, I think GitHub's interview process is crap and would not recommend people to go through the same thing I did.

Steps in the process: 1) Interview/meeting with the recruiter 2) Meet with the hiring manager and advance to the final round 3) Consisted of 4 final round interviews - Coding (Pair-programming) 90 minutes - Coding #2 (Pair-programming) - 90 minutes - Diversity and inclusion interview - 30 minutes - Skip-level interview - 30 minutes Most of the people I interviewed were previous Microsoft employees so my fear was that they would low-ball me or try to level me down since that's a Microsoft trick. After a few days, I got a response back from the recruiter that they want to extend an offer but they don't really hire "senior" engineers externally. I really love GitHub but the offered salary was too low so had to take another offer that got the leveling right (actually got hired as Staff at another big tech company, two levels up). I will say that their benefits package is amazing, no one is beating that. Word of advice, apply for a higher level because they will level you down and try to low ball you.