GitHub Senior Software Engineer interview questions

Took almost a month to hear anything back from my application. Finally heard back and scheduled a call with an engineering manager and then the hiring manager. The calls seemed to be going well, but with two minutes remaining in my call with the hiring manager, I was caught off guard by being asked if I would be okay interviewing for a position below the senior level, since "other companies level differently than we do". For context, I have a total of 8 years of work experience in web technologies, with 4 years of experience leading technical projects (split between a fortune 500 company and 2 startups), and have been a senior software engineer for 3 years. This was pretty insulting (to say the least) as I meet or exceed all the qualifications for a senior software engineer in GitHub's senior-level job descriptions. I was reconsidering my application after mulling over the question for a couple days when I got an email saying they were no longer considering me for the position. It feels like I dodged a bullet early in the process.

Applied online and after a few weeks received an automated technical test to work on. The test lasted max 5 hours, you receive a repository to work on and have to make a pull request that satisfies requirements. I managed to complete it in about 2 hours and spent some extra time explain trade offs in the PR description. After that I was contacted by a recruiter, asked me to fill in a few answers in a form (motivation, experience with programming languages, etc.), then we had a chat in which some basic technical questions were asked. This was followed by a virtual on-site consisting of: - 2 behavioral interviews - 1 technical coding interview - 1 technical interview where you have to review some code The live coding interview doesn’t follow the leetcode style ones, it’s a more practical exercise during which you share the screen and can consult the internet and collaborate with interviewers. The interviewers were all nice and professional, but scheduling was a nightmare: it all happened via email exchanges (having to keep in mind timezones) and it wasn’t clearly communicated that interviews only happen on Tuesdays, which made it even more difficult to organize. Also, GitHub has a strict no feedback policy. While I understand that feedback is difficult, it can feel pretty hard to gauge where to improve especially due to their non-standard interview process.