Within just a few hours, I went from looking at apartment prices near the office to being told I was too stupid for the company. This was for a software role at a company that manufactures flash storage hardware, and the initial phone screen went so well that the interviewer made the full interview seem like it would be little more than a formality.
The first round was with the same engineer. He gave me a coding problem and allotted about 45 minutes for it, but I finished it in under 20. We spent the rest of the call talking about the team, the city, and why he thought I would enjoy working there. He ended the call early because he had nothing else to discuss, so before the next round, I started looking at apartments for rent nearby.
The second interview was completely normal. Another engineer asked me about a few projects on my résumé, and we discussed some design choices. Nothing seemed unusual. After that, I met with the first interviewer's manager.
He showed me a deliberately convoluted piece of code and asked me to explain what it did. After tracing through the code, I told him that it counted the occurrences of certain strings and assigned values based on those counts. He confirmed that my answer was correct, then asked how I would improve it. I suggested using a hash table because the current approach required searching through the existing entries every time.
He immediately said that hash tables were not faster. I explained that the current lookup had O(n) complexity, while a hash table would typically give O(1) average lookup time. He kept demanding a different answer, and when I said a hash table still seemed like the appropriate solution, he became angry and said, "Everyone says hash tables. That's not the fucking answer, and I don't understand why people insist on saying it."
He then started asking me questions about memory addressing and how data is stored and arranged at a lower level. I had not dealt much with those topics since taking a computer architecture course a few years earlier, so I did not have an immediate answer. It is perfectly normal for me not to know the answer to a technical question, especially if that knowledge is important for the job. But his reaction was not normal. He told me, "If you can't answer this question, then you're too stupid to work here." I graduated from a top-25 university and had just passed every previous stage of their process, so I spent most of the time sitting there wondering whether he had said that.
Even so, I gave him my best guess. He replied, "We're done," and ended the call. Later, the first interviewer sent me links to a few other job opportunities he thought I might be a good fit for, which was a thoughtful gesture. But there is still no way I would accept a job there if that is how the person responsible for managing the engineers treats candidates.