Involved firstly a phone interview, and then a face-to-face at Canary Wharf. The phone interview involved probably about 30 questions based around JavaScript. Minus about 2 questions, I answered them all solidly. I did feel like, although I performed well, the questions were too excessive. The interviewer was very happy with my understanding of JavaScript, so invited me for a face-to-face.
When I arrived at 25 Bank Street, I waited for about ten minutes in the posh reception area after the agreed time before being escorted to one of the top floors. I gotta give it to them; the place is top-notch. I was taken around the floor and offered a drink of water. It was all decorated in old mahogany with a Pod-like desk arrangement, not to my liking, to be honest. Everyone was dressed smart, as you would expect in a corporate bank.
I was then taken to a room where I would be sat around a boardroom-styled table, with lush views of London across the water. We dialled into Glasgow, where another individual would listen in to our conversation. There were microphone problems for about five minutes.
What followed was a constant influx of technical questions. No care for me as a person, what I like doing. It was purely business. 'Do you know X?' I've had little exposure. 'Do you know B framework?' Yes. 'How much have you used React? What do you know about Redux?' What is a stateless component? 'Do you know TypeScript?' 'What is X in TypeScript?' React Lifecycle? Benefits? Drawbacks? What would you do in this situation? 'What's going on lately with React? What's the latest trends?' 'What is happening with Y occurs? Why does that happen?'
It was the worst interview I've ever experienced, and has actually put me off working for a corporate bank. Even he outlined the frustrations, such as no communication in the team (a vertical approach where no-one is aware of what the other is doing).
I asked them what they do for fun. I think the word was lost on him.
After the meeting, he took me for a brief walk around to meet the team. Everyone I saw was very friendly and welcoming. I also got a preview of the product I 'would' be working on. The interviewer took me back down and respectfully shook my hand and said, "We'll be in touch".
I'll be sticking to jobs with a dress-down, Google-like culture, where people are actually happy, can collaborate, and be innovative. I can see why others in my generation opt for the same thing. Banks should change their culture and not remain in the 80s. The only thing luring people to these places is the money. This is a well-known thing, and to me, there is more to life than money. These were the thoughts I had as I left the office after an hour and a half interrogation.
I got an email from the recruiter saying my knowledge of frameworks was not strong enough, and I didn't proceed to the next stage, and I was not bothered by it at all. It makes me like my current job more. So, the fact I know JavaScript very well, but don't know the 'frameworks' is not enough. All developers have gaps in their knowledge. To me, what makes a good developer is someone who communicates effectively, is willing to learn, understands requirements, and can implement them in the most effective & efficient way, not be able to answer 99/100 randomly selected questions about things that don't always matter. Overall, I would say I answered about 80% of the questions strongly, but this is not enough.
What new features of TypeScript do you like?
The following metrics were computed from 2 interview experiences for the JPMorgan Chase Frontend Developer role in London, England.
JPMorgan Chase's interview process for their Frontend Developer roles in London, England is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for JPMorgan Chase's Frontend Developer interview process in London, England.