HSBC Software Engineer candidates describe a values-based assessment or HR screen, easy-to-medium coding and technical interviews, and in some cases a Karat session or manager round. Here is what they report and how to prepare.
$175K
Avg. Base Comp
$205K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates who interviewed for HSBC software engineering roles describe a process that leans on fundamentals, role-specific experience and HSBC's values more than on hard algorithm puzzles. One candidate completed a scenario-based values assessment before any technical interview. Another had two HR conversations built around values-based questions, experience and role expectations. It is worth reading HSBC's published values and preparing concrete examples of how your past work reflects them.
Coding questions are described as easy to medium and focused on basic data structures and algorithms. One candidate had a Karat session split into two parts. The first was about 20 minutes reviewing the architecture of a Kubernetes-based payment application and explaining its issues. The second was about 40 minutes of coding in a language of their choice, including time and space complexity analysis. Practice explaining the complexity of your solutions out loud, and be ready to critique an existing design rather than only build one. An intern candidate saw a LeetCode-style coding assessment, a database design question for a food delivery app and a closing puzzle.
Senior candidates should expect more depth. One senior Java candidate described 30 minutes of live coding followed by Java, Spring and API design questions, including API performance optimization. Next came a system design round on Spring Boot microservices across multiple databases. The final round lasted about two hours with the potential manager and peers and mixed technical and fit questions.
Candidates also report slow or uneven communication. One was promised feedback within a week but heard nothing after a month. Another was told hiring was on hold while headcount was revised. Keep other applications moving while you wait.
Synthesized from 29 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Hsbc process.
The HSBC process started with an HR phone screening where I did a self-introduction and answered one behavioral and one situational question. They kept it pretty conversational—nothing too formal, maybe 25 minutes total. If you pass that stage, they send your CV to a manager, and if they're interested, you move to a final interview with them.
Before that initial call, I also went through an online assessment that included a video interview component and some selection questions asking about what skills make you a good candidate for the role. Then there was a coding test on the Codility platform. I was honestly relieved when I saw the questions—they weren't algorithm heavy or trying to trick you. They were more practical, scenario-based problems that tested how you'd actually approach a real engineering task rather than grinding LeetCode.
The virtual interview rounds were timed and happened on their website. They'd give you a brief scenario, give you a couple minutes to prepare, and then you'd answer on camera. It felt more like they were testing how you think through a problem and communicate your reasoning rather than memorizing solutions. Overall the whole process felt less intimidating than typical tech interviews, but also less technical depth than I expected for a software engineer role.
Prep tip from this candidate
Focus on practical coding scenarios and problem-solving approach over algorithm complexity—Codility questions test real-world logic more than data structure optimization. For behavioral rounds, prepare specific examples from your projects or resume that demonstrate your reasoning and communication skills, since they dig into what you've actually built.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Hsbc
How would you evaluate whether a decision tree is the right model and assess its performance before and after deployment
| Question | |
|---|---|
| Stakeholder Communication | |
| Why Do You Want to Work With Us | |
| Employee Brand Ambassadors | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Size of Joins | |
| Total Spent on Products | |
| Top 3 Users | |
| Get Top N Frequent Words | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Google Maps Improvement | |
| Scrambled Tickets | |
| Prime to N | |
| Comments Histogram | |
| Slacking Employees Salaries | |
| Last Transaction | |
| Like Tracker |
Synthesized from candidate reports. Individual experiences may vary.
One candidate completed an online scenario-based assessment built around HSBC's company values before the technical stage. Another had HR conversations focused on values-based questions, experience and role expectations. Prepare concrete examples tied to the published values.
Reported coding is easy to medium and centered on basic data structures and algorithms. One candidate had a Karat interview with about 20 minutes reviewing a Kubernetes-based payment application's architecture and 40 minutes of coding with time and space complexity analysis. An intern candidate took a LeetCode-style coding assessment.
Candidates describe discussions with the technical team about role-specific experience. Reported topics include database design for a food delivery app and a puzzle. For a senior Java role, topics included Spring, API design, performance optimization and microservices system design.
One senior candidate described a final round of about two hours with the potential manager and peers. It mixed technical questions with cultural fit and team dynamics. This round was not reported in every account.
Follow-up was inconsistent. One candidate was promised feedback within a week but heard nothing after a month. Another was told hiring was on hold while headcount was revised. Ask the recruiter about timelines and keep other applications active.
