Stereotypical interview process - phone screen with a recruiter, tech screen over a phone call, 4 on-sites. Phone screen and tech screen went off without a hitch - everything went well. Recruiter asked what language I would prefer to interview in for the on-site, I stated python - this is important later. Get to the on-site and go for my first interview. I'm asked what language I want to program in. Caught off guard, I answer I requested Python. The interviewer stated he didn't know python but would be willing to learn from me in the interview. Finish their question and they ask how making the process multi-threaded would work. I explain the nuance of Python threading, explain it isn't like other languages and why then implement the change. Second on-site. Same deal. Asked what language and I started seeing a problem at this point. The interviewer didn't know Python again. No big deal - we get through the problem, I explain the solution along the way, how I planned to solve it, and get valid code that compiles and does as it should. Then the interviewer takes a look and can't figure out how it works. I walk them through it, they still don't get it. A few more walkthroughs after and I realize they aren't getting that there's a variable being declared, modified, then sent back as the control for the loop. I explain that part more carefully, they say they think they got it but time ran out to confirm. On to the next one. Go to lunch, meet with the guy I tech screened with, no big deal. He has to go to a meeting so he drops me off at the lobby to wait for the next interview. The interview is supposed to start at 2pm. 2pm comes along and nothing. Ok, no big deal, probably just caught up in a meeting. 2:05pm, still nothing. 2:10pm I go to the front desk and ask for them to be pinged. 2:15pm, still no one. 2:20pm they finally show up. We go to the room and they start the basic questions. "What's your experience?", "Why are you leaving your other company?", etc. After this, they give me a question and I start talking it through, writing up things to keep track of on the white-board. I turn around and they are answering emails on their computer, not paying attention at all. Get to the end of the problem and I walk through some test cases. Interviewer: "How does this work without a global variable?" Me: "There's a return statement, right here..." I: "That doesn't matter. How does it get the data from the other parts without a global?" Me: "It's a recursive function - the retur-" I: "No. This won't work without a global." Me: "It doesn't need a global, the return statement passes the data ba-" I: "Sorry, times up. Let's get you to the next interview." The fourth interview I cannot complain about - the person knew Python well enough to read my code and we got along great. They were attentive and respectful the entire time. More questions about general concepts for network develoupment and the likes. Don't even leave the hotel and I get the news that they are not hiring. At this point, I was bummed out but didn't think to make a post about it here. Then today, over a week after the interviews, my recruiter reached out and asked how it went. Over a week after I was told I wasn't getting the position. ----------------- Closing notes: Disorganised interview process, lack of communication between the recruiters/hiring committee/interviewers, and lack of interest from the interviewers.