So, at the beginning everything started out pretty par for the course. The first phone call I got was to get a brief feel for the position, as well as for me to give my background. Given I'd been working in the Bay Area Software field for a few years now, and given I've had extensive experience with API development, it was a pretty solid fit.
First interview goes down, and I'm a bit rusty, but get the job done. Simple question, find the distance between two entries in a list, and find the closest distance if there's more than two. At this point, I was feeling pretty good about the process. It was definitely one of the easier and more lax interview processes I've dealt with. Unfortunately, things went south from here.
So, the second interview comes around. This guy is a bit condescending, and writes off four years of Military Cyber work as "Not actual software experience." I've had this thrown at me before, so unfortunately I wasn't too put off by the remark. However, next he proceeded to ask me "So, did you ever kill anyone?"
Twitch, applicants, random readers? If you can take even one thing from this overview of the recruiting process, let it be this: Do not ask a veteran if they've killed someone. It's rude, discriminatory, and implies that's the sole defining feature of a servicemember.
So, at that point, and for the rest of the interview, I was completely stunned. This engineer (A different person from the two conducting the previous interviews) apparently had zero respect for me as a person. However, I've dealt with unpleasant co-workers and superiors before. So I naively opted to continue on with the interview.
At this point, he poses the question: Make an Iterator for a Binary Search Tree. Easy, just use a Stack Container populated with nodes going left of the root node. I began explaining my plan, and was immediately told not to use Stacks.
I was blown away by the request. I myself have issued this question to potential hirees before, and they'd almost always go with Stacks to avoid recursion issues and save memory.
So, I wound up spending a majority of the phone interview writing out an Iterator without using a Stack Collector, which wound up being far longer and more convoluted than I would have liked. At this point we were running over on time, so we concluded the interview.
From the looks of how the Engineer interviewing me was acting, I'm very much inclined to believe he was trying to push me out of the candidacy pool for the positions I was interviewing with. His actions were insulting, and I am incredibly disappointed that Twitch would involve someone such as this with the interview process, let alone give them any authority over other personnel.