I did OK, but only OK on it. His comment when we ran short of time was "Yeah, I think with a little debugging, that solution would probably work" but then he passed.
Perhaps it's just my bruised ego, but I think he made a bad decision. Here he is with 5 members of his own team saying that I'd be a great fit, but he basically selects for people who have encountered a puzzle with very little relation to the actual work involved in the role. He may as well have evaluated me as a developer on my ability to prepare a chocolate souffle in 30 minutes. It would have been roughly as representative of my skill set.
I did end up solving it, but I wasn't happy with the solution and neither was he, with good reason of course, but it was one of those problems I easily could have solved if given the proper time to work on it rather than digitally whiteboarding it for 20 minutes in a high pressure situation. A quick and dirty solution is all you should expect from working on a never before seen problem in 20 minutes on paper without a compiler.
I came away feeling as though their process was more broken than my performance. Doubtless, I could have done better. But it just felt so strange to be washed out after four other engineers thought I was qualified.
P(A and B and C) = P(A) + P(B|A) + P(C|AB)
rather than the product of the probabilities just because I was stressed, then got a nonsensical answer. Fortunately the interviewer just asked me to reconsider that line, but it was not a mistake I would normally make.I'll sometimes even say, "I've asked some of these questions to [person x, person y, ...], but I'd like your perspective."
Also to the person whose interview took 5 months. Is this really a company you would want to work for? Sounds like they don't have their shit together.
but i didn't just say no, i explained that i already had two other interviews and the other interviewers had answered all my questions.
i got hired, so i'm not sure if that's related or not.
I was declined at interview #5, after passing the previous four. Not sure how much that question played a role. It was also the weakest of my technical interviews. I was surprised to get hit with more programming questions after having passed so many other technical interviews with them.
After 5 interviews which dragged out for almost two months that was super disappointing though. It was probably the last interview I needed to pass. It's like being knocked out of the race with a blue shell in the last 20 seconds in Mario Kart.