There was a programming assignment provided as a first step, which one had to complete in 3 hours and submit back. The question was mainly on reading two files and a reference data store. Based on that, some simple calculations had to be done. The output would be producing a file. The problem statement was long enough to keep one occupied for the 3 hours. I could complete 80% of the assignment's use case. There was a subsequent F2F interview where the programming problem was to be discussed. I am not sure either of the interviewers had seen the assignment I submitted earlier. The questions were very generic to general software development models and nothing specific. To my surprise, the feedback was negative. It is a bit of a disappointment to have gone through the interview. Had some deficiencies in my solution been discussed or some questions asked which I could have not answered, it would have been much easier to understand the process.
The following metrics were computed from 1 interview experience for the JPMorgan Chase Java Developer for Trade Survillance Team role in Singapore.
JPMorgan Chase's interview process for their Java Developer for Trade Survillance Team roles in Singapore is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for JPMorgan Chase's Java Developer for Trade Survillance Team interview process in Singapore.