This was a job opening for a developer/analyst role for a reference data delivery solutions project. The interview process was very disappointing, though. The interviewer was not interested in knowing anything about my current project. As a matter of fact, he didn't even ask me what my role was in the current project. It was I who mentioned it deliberately.
As the introduction was over, he asked me about my comfort level with writing database queries. He gave me a single query and left the room. After 5 minutes, another person came in and asked me: "Do you need more time for the query?" I gave the query to him, and he asked me to maintain it. 2 minutes later, they asked me to leave for the day.
I mean, this is unfair. Totally ridiculous. You cannot judge a person based on one single query. You need to ask more questions. At least a few Java-related questions, for that matter, because, guess what, it was for a Java developer role. And this thing happened with many candidates that day. People leaving in just 5 minutes. Just one tricky question and no other chance. Is this real evaluation?
Rather than asking questions about the project, he was interested in the reasons for leaving my current company; he wanted to know some juicy answers, I guess.
Two tables: emp and sal.
Get the employees whose cumulative salary is greater than 300. But don't display the cumulative salaries. Display the actual salary of each month for those employees.
The following metrics were computed from 15 interview experiences for the JPMorgan Chase Applications Developer role in Mumbai, Maharashtra.
JPMorgan Chase's interview process for their Applications Developer roles in Mumbai, Maharashtra is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for JPMorgan Chase's Applications Developer interview process in Mumbai, Maharashtra.