HSBC Interview Experience (On Campus)

Round 1:

It was an online test, on CoCubes. The test consisted of 3 sections, Logic, Verbal, and Technical. All of these were very difficult. Technical sections section had questions asked from almost all of the subjects in curriculum and also some questions from cloud computing machine learning, data mining. Technical section was the toughest section. There weren’t any basic questions or questions related to data structures, or OOPS. Test was focused on database, operating systems, and newer technologies. Predict-the-output type of questions were also asked. Confusing predict the output of Javascript, Java, C++ programs were asked. There was a static cut-off score. If you cross  it, you are redirected to coding round immediately. Out 550 around 200 something went for next round.

Round 2:

This round started immediately after the first round. It consisted of 2 codes to be written in 30 minutes. Both of them were very easy. Related to arrays and sorting. If you code frequently, this will be a piece of cake for you, but if you don’t time might seem a little less. It took me 12-13 minutes to complete both codes. We weren’t allowed to use library functions (only iostream was included for c++). Out of around 200, 83 went for the next round. Getting one code to run might get you selected for next round, but I’ll suggest you run complete both, and not worry about optimizing them.

Round 3:

This was a face to face technical interview. The questions asked in this round depend more on who interviews you and what you’ve written in your resume and also on how the flow of interview goes. The interviewer went through my resume.

Generic questions that were asked:

  1. Introduce yourself.
  2. Questions on Java, why multiple inheritance isn’t allowed, abstract class vs interface, collections, spring.
  3. Questions on multi-threading.
  4. Questions on complicated exception handling in Java, data-structures, puzzle.

Questions on resume and projects:

  1. Questions on NodeJS, front-end related questions, and navigating users through webpages depending on some logic.
  2. Questions related to HTTP, GET vs POST, difference between PUT and POST, security and SSL.
  3. HTTP status codes, javascript exception handling, promises, error-first callbacks, etc.
  4. API design case study, questions on Django, authentication in REST APIs.

She seemed to be quite impressed by the resume and projects. 57 out of 83 went for the next round.

Round 4:

This was HR round. The sheet that previous interviewer had filled was passed to the HR interviewer. The interviewer had to take a lunch break, but I had an exam so she waited for my interview to get over because I had to leave for my exam. It was quite short. The questions asked were:

  1. How was your day so far, how was you technical interview?
  2. Which question did you like the most from the technical interview, and why?
  3. How do you keep up with current affairs?
  4. What do you know about HSBC?
  5. What keeps you motivated?
  6. Which work location would you prefer, Pune vs Hyderabad?

The HR can see in the sheet how good your technical was. If it was very good, they don’t give a lot of stress on non-technical part. Messing up a little bit is okay, but don’t give them a serious reason to reject you. 33 were selected out of 57.

Results were declared after all interviews were over. In the end, 33 candidates got the job out of 550.

Write your Interview Experience or mail it to contribute@geeksforgeeks.org



My Personal Notes arrow_drop_up

If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.

Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.




Article Tags :
Practice Tags :


2


Please write to us at contribute@geeksforgeeks.org to report any issue with the above content.