1st call was 30 mins and the typical introduction to the role and a chat about my work history. Interviewer made pains to describe how the company is super inclusive when considering candidates, and makes sure to see if they can fit anywhere in the business. That and the fact that they don't outright dismiss candidates because they don't adhere to some arbitrary list of 'tickboxes'. This statement turned out to be misleading, if not completely false. 2nd stage was a HackerRank 'leetcode' type exercise whose description could have been reduced from the scrolling-marathon it occupied in the sidebar to a concise paragraph. Effectively, the challenge was to take an array of strings, each one a space-delimited set of values representing an ID, an IP address and a timestamp (so "4 170.111.136.12 50100"), then return an array of integers for the IDs to reject if more than 2 of the same request was made from the same IP address within a second of each other. I took the time to tokenise the input data, show an example of data modelling to make the code readable, and work methodically, but 5 minutes before finishing my last conditionals the 50 minute time expired and the page was immediately locked out. No opportunity to provide supporting information. Because of this, I received an e-mail two hours later saying that I'd 'failed' the tests and they wouldn't be putting me forward. Their house, their rules and all that, but I've been in this industry as a programmer for over 20 years now and I didn't find this test to be a particularly good example of what day-to-day work is like. Nobody sits on your shoulder for an hour pressuring you to write a function. You have the tools and the time and the support of your intuition, research and colleagues, and failing a coding exercise because you took maybe 5 minutes longer than they mandated seems a little churlish at best, and elitist at worst. Still, it is what it is. Looking at other interviewed candidates responses on Glassdoor shows that I may, in actuality, have dodged a bullet based on some of the 3rd/4th stage horror stories of unintelligible / uninterested interviewers, and unrealistic expectations of no debugging or reference material research I've read. Make of it what you will. My advice would just be to use the knowledge of this interview process to give you a leg up to get through to the next stage and form your own judgements.