I recently interviewed with Twitch, an Amazon subsidiary. With about 10 years of experience and an L6 loop, I was excited. I crushed the interview technically, but received a no-offer.

Fast forward a day, the recruiter reached out and said the manager and director would like to have drinks/dinner. We met and had a great time. It turns out their concern was behavioral, and I assuaged those concerns over dinner. A very strong L6 offer came my way. We agreed to terms. I made a separate thread here about this fiasco.

Fast forward a day, the recruiter reached out, saying how embarrassing this was, but they'd like me to do a technical phone screen. Their explanation was that no L6 SDE interviewed me, so the official committee couldn't let the hire through, despite the manager and director fighting for it. I accepted this oddity and obliged to do the phone screen.

I took the tech screen, which was said to be algorithm-focused and explicitly not design-focused, according to the recruiter (pre-interview) and the interviewer (I asked during). I killed it and awaited my official offer.

Tick tock... I heard nothing. I finally asked what was up. They stated because I did not show indicators of L6-level design skills in the phone screen that they could not make an offer. This was the exact thing they explicitly stated was not being evaluated, both before and during the screen!

In the end, I met them three separate times, had a no-offer, followed by a very strong L6 offer, followed by a no-offer, but could have an L5 offer extended, which I hard declined.

What a calamity. If you were on this loop and read this, I hope you sincerely look at your process and improve it. You missed a great, excited candidate because you kept "moving the goalposts" and misrepresenting what you really wanted. To anyone hoping to interview with Twitch, beware the ride of insanity coming your way.

Leverage the Twitch API to show mutual followers and following.

Must implement in JavaScript and show the code running.

Note: Only given access to the Twitch API documentation.

Paired programming: Reduce the cyclomatic complexity of existing Go code used in production.

Print a binary tree row-by-row, printing left-to-right for even-numbered rows and right-to-left for odd-numbered rows.