First, I had a phone call where the interviewer asked basic Java questions and why I was looking for a switch.
The next phase was the in-person coding challenge. The interview process in this case was a mess. The interviewers told me they didn't even know they were interviewing five minutes earlier. Then they came in without the sheet which I needed to do the coding challenge. They just gave me a basic idea and asked me to solve the problem. I started coding, and when I was almost done, they brought in the requirement sheet. I noticed that they actually had a couple more methods to implement, which they hadn't told me about, and I would have never known. Then I actually ran my code and showed them that my methods actually worked according to their specifications. After that, they asked me a few questions, which I got most of, but may have missed a few. But the feedback I received was that I couldn't even get my code to compile, which is absurd!
Overall, my experience is negative, and if anyone is approached by this company, don't even bother. They give wrong feedback to recruiters, which could negatively impact your career. At least be truthful about the feedback, for God's sake.
What are optionals, streams, hash maps, etc.?
The following metrics were computed from 1 interview experience for the HSBC Java Developer role in Toronto, Ontario.
HSBC's interview process for their Java Developer roles in Toronto, Ontario is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for HSBC's Java Developer interview process in Toronto, Ontario.