Very poorly taken interview. The interviewer seemed to be in a hurry to wrap up the interview, finishing within 25 minutes. He asked silly Java questions, which should be asked to someone with 2 years of experience (I have 5+ years of experience). Despite giving most answers correctly, he somehow decided not to recommend me for the next round. Hardly any good questions were asked, except one on Class Loaders.
In some interviews, you don’t make it, but you leave with a positive experience due to good questions asked. However, in some, you leave with a negative experience because you were asked silly questions, you answered most of them, but still were not recommended for God knows what reason. This was that later kind of interview.
I felt that JPMC should frame interview panels more carefully. They also shouldn’t put pressure on interviewers to finish up fast. Bad experience, not trying anymore for JPMC (at least for quite some time).
Is the JRE system platform dependent?
Explain about Class Loaders. How many types of Class Loaders are there?
Method overriding criteria/rules.
ArrayList vs. LinkedList. (I was like, REALLY?)
How to sort a list of Employee objects based on emp ID?
Removing of duplicate Employee objects from a list based on their employee ID.
One question on array of ints, printing them with their values followed by a minus or plus symbol, depending upon whether the previous and following ints are the same or different.
The following metrics were computed from 1 interview experience for the JPMorgan Chase Java/Full Stack Developer role in India.
JPMorgan Chase's interview process for their Java/Full Stack Developer roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for JPMorgan Chase's Java/Full Stack Developer interview process in India.