Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en J.P. Morgan (Hong Kong) en mar 2018
Entrevista
Pretty bad experience. Interviewer was not prepared at all and for me his attitude was not professional, eg I was asked to write simple method to swap 2 ints, but when I was about to finish this, he changed his mind and asked to do it in place. This guy as VP!
He was not able to keep our conversation and looked he asked questions and was trying to remember my answers.
For me Hong Kong JP branch is very weak in terms of technology.
If you are hands on dev and smart don't go for interview there, it's wasted time.
I didn't go for next interview after what I experienced during first round.
Preguntas de entrevista [1]
Pregunta 1
1. Could you describe your recent project. (Architecture, role), What was most difficult during development.
2. If we have static method in class, is it thread safe?
3. How can you assess your java knowledge? from 1 to 10
4. Java memory management
5. write method that will reverse string
6. We have a in-bound and out-bound queue and between is a multithreaded logic that threads take a messages from in-bound queue and write to outbound queue. Propose solution that messages from outbound queue will be available in he same order as data in in-bound queue
7. Then he told me about 2 roles avilable in the bank, and asked me which one I prefer and why.
I has a phone call discussion explaining process then the team has scheduled with 2 technical rounds on Java, DSA followed by HR.
Process was long. In Between all the rounds there was 7-10 days.
Very good behavioural analysis and java 8, spring, springboot, angular ,reactjs,collections ,very good experience,please prepare yourself and your team project,excellent communication with technical skills.salary hike is very good and work culture also very nice
Me postulé a través de un reclutador. El proceso tomó 1 día. Acudí a una entrevista en J.P. Morgan (Nueva Delhi) en may 2022
Entrevista
First round ,he directly jumped asking scenario based question on MQ and transactions in DB.
And few questions on indexes, no Java questions .
I have answered correctly to indexes related questions and for scenario based questions I have couple of answers seems he has fixed answer in his mind , he didn't satisfy
if 100 transactions there in DB you have to pick 20 transactions ut of 20 process 10 and skip 10 whenever scheduler job runs next time and for next run you should not pick processed 20 transactions