One round of telephonic technical discussion. The interviewer seemed to be fixated on certain Java concepts with no willingness to hear. He seemed to be reiterating my points while not acknowledging that I was saying the same.
I was interviewing for a Java Microservices role; however, I don't believe he had much idea about the tech stack he was supposed to interview me on. He threw me a few algorithm questions too, a couple of which I could straightforwardly point out solutions to. I was stuck on a tough one, and it was a telephonic round, but he wanted things to be fast.
It was a pathetic experience. I expected better from the Wells Fargo brand.
This is not a usual rant. I just wanted to point out that an interviewer should either be familiar with the profile they want to hire for or at least have the capability to keep an open mind.
Immutable class (seemed the most important question)
Lowest common ancestor of a binary tree
Something with heaps
Split array into 2 parts with equal sums
Hashmap internals
Stream vs. collections
The following metrics were computed from 2 interview experiences for the Wells Fargo Senior Software Development Engineer role in Bengaluru, Karnataka.
Wells Fargo's interview process for their Senior Software Development Engineer roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Wells Fargo's Senior Software Development Engineer interview process in Bengaluru, Karnataka.