Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en J.P. Morgan (Bengaluru)
Entrevista
* In one word "Pathetic! "
*J.P Morgan is conducting fake interview drives these days.
Let me explain my experience:
* You attend the Interview, they will take your whole day.
* The HRs are so irresponsible, that they won't tell you anything about the interview results.
* You follow up through Emails and try calling them. Again "NO" response.
*After some days ,they come back and tell you have cleared all the rounds .
*You have to again attend their online coding round and Manager round.
*After you clear these, again the HR becomes invisible for a long time.
*One fine day, they will send you an email saying you won't fit our open roles.
My questions:
* If a candidate has not cleared any one of the rounds, why don't you tell them at that
moment.
* you say that the interview feedback is positive.Later again come back and give some junk
reply saying you might not have cleared all the rounds.
*Be clear in your reasons for rejection.
*Respect others time and effort.
Advice:
* The company doesn't follow any proper way of conducting a recruitment.
*The HRs are irresponsible and arrogant.
* Better think 100 times before attending such interviews.
Preguntas de entrevista [1]
Pregunta 1
Questions were on Java/J2EE
Questions on spring and some scenario based
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
Solicité el puesto a través de un captador. El proceso duró 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
