Chase Software Engineer interview questions

The first interview stage was way too easy, almost feeling wrong. They ask you to prepare for 90 minutes for a take home exercise, but it barely took me 5 minutes. The second stage had a pair programming exercise which was a bit more challenging, asking to use trees or recursion. The third stage was again some questions and some pair programming exercise. The first question was how a ConcurrentHashMap works internally, very specific and not everyone knows that, but ok. Moved to questions as time complexity inside different Maps. And finally something about GC's. The exercise part was one of those terrible online tools experience. No debug, no running the code, no auto complete. An algorithmic question, full of edge cases, with some 20 minutes to solve it. Lastly, a question about how to turn a list immutable. Overall, two first stages too easy, third stage not such a good interview experience.

There were 5 interview rounds: 1) HR phone call - 15 mins 2) Hackerrank Test - 90 mins 3) Hiring Manager - 30 mins 4) Pair Programming - 60 mins 5) System Design - 60 mins The first 3 rounds went well. But the Pair programming round was not good at all. The interviewer did not have any patience to listen to my answers. They only cared about whether they asked enough questions. In their mind, they had an answer; if you don't give that answer, it's wrong. In any programming language, there are multiple solutions to any problem and an interviewer, they should allow the candidate to provide their rationale.