GitHub Site Reliability Engineer interview questions

Honestly, I had a really great experience from beginning to end. Here is a recap of what I experienced firsthand.... I applied online after hearing about some of the new projects that GitHub is working on. After my application, I received an email from the recruiter and I scheduled a video meeting later the same week. She spent about 30 mins getting to know my background and asking some traditional questions. I scheduled a take-home assignment. Overall, it was a fun assignment. A couple of days after submitting my pull-request I received an email from someone to schedule meetings with technical staff and the hiring manager. Overall, the people I met were great and appeared to be highly capable. The hiring manager was eccentric but I warmed up to him by my second meeting with him. After a week, I spoke with the recruiter. It turns out that they didn't see my experience inline with what they were looking for. She did mention something about a "no- feedback" policy -- but in my experience, all of the technology companies have the same policy (Google, Facebook, Slack, etc.). OVerall, it was a good experience -- even if I didn't get the job.

As other reviews have mentioned, I was introduced to a super nice lady who seemed very proactive and eager about the process. She asked simple screening questions about my work and career, etc., and explained roughly what the process going forward will look like. Be careful, and don't be fooled: they're nice and ecstatic in the short call, but you will be hardpressed to get even a single response for long periods of time. In my case I had to repeatedly send emails just to get her to start the take-home coding test. After finishing the (easy) test, I received absolutely no email or contact from anyone for a week, until I finally sent multiple emails over some days and got a 1-line response that was effectively, "we'll get back to you when ready". Helpful. 3 more weekdays passed until a generic rejection letter came in. tl;dr, complete waste of time, I wouldn't tell any competent developer colleagues to apply here.