Most confusing and potentially worst interview experience I have ever had.
First weird thing was that I had to share my screen and pull up my own IDE to do the technical questions, which I have never done before. I was not told about this beforehand, so was not prepared and had to spend a few valuable minutes getting it set up.
As I was coding solutions to the questions and explaining my thought process, the interviewer said almost nothing. For around 40 minutes, there was pretty much zero communication from the interviewer's side aside from the occasional comment, and then telling me the next thing to implement.
Then, while I was in the middle of coding a solution and explaining what I was doing, the interviewer stopped me mid-sentence, told me there were 2 minutes left, and asked if I had any questions.
No feedback, no comments, nothing at all. All of this left me feeling really confused. It was a huge put-off. Haven't heard anything back yet, but will not be accepting regardless.
Implement Fibonacci.
Implement it iteratively.
Write a function that will prevent int overflows for large fib numbers.
The following metrics were computed from 132 interview experiences for the JPMorgan Chase Software Engineer role in United States.
JPMorgan Chase's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for JPMorgan Chase's Software Engineer interview process in United States.