HSBC software engineer candidates report values-based screening, practical discussion of prior experience, and technical work spanning architecture analysis, complexity, and coding.
$81K
Avg. Base Comp
$204K
Avg. Total Comp
5 rounds
Typical Rounds
2 weeks
Process Length
HSBC software engineer interviews described by candidates combine behavioral and technical evaluation rather than following a coding-only script. Prepare to explain both how you work and how you reason about software. One candidate completed a scenario-based assessment tied to company values before a Karat technical session. Another had HR conversations focused on values, experience, and role expectations, followed by a discussion with the technical team about relevant background.
The most detailed technical account was split between architecture analysis and coding. The candidate spent about 20 minutes reviewing a Kubernetes-based payment application, identifying flaws in an existing design, then about 40 minutes coding in a language of their choice. The coding questions were described as easy to medium, but the discussion also covered time and space complexity. That makes code reading and verbal reasoning as important as writing a working solution.
For preparation, practice narrating how you inspect a system: clarify assumptions, identify risks, and explain tradeoffs. Review core data structures and algorithms, including complexity analysis, and be ready to connect past projects to the role. Candidates also report values-oriented questions, so prepare concise examples about judgment, collaboration, and expectations. Evidence is limited and formats may vary by team; one candidate’s process paused after an initial round because hiring was put on hold.
Synthesized from 3 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 most frustrating part was that I was told I was the only candidate who cleared the first-round interview, yet the role never moved forward. I received an initial call more than three weeks after applying and completed the first-round interview, but I was not given a result afterward. When I followed up, I was told that hiring had been put on hold globally while headcount was being revised.
I continued checking in over the next two months and received the same explanation each time. There was no indication of another interview round or a concrete timeline for restarting the process. The experience left me disappointed because I had cleared the interview and was excited about the opportunity, but the company did not provide a clear resolution or communicate proactively. I would go in expecting that the role's headcount may be unsettled even after an initial interview, and I would keep pursuing other opportunities rather than pausing your search while waiting for an update.
Prep tip from this candidate
After the first round, ask the recruiter whether the role has approved headcount and request a concrete expected timeline; this process remained on hold for months despite the candidate clearing the interview.
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 | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Comments Histogram | |
| Prime to N | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Top 3 Users | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
A candidate reported beginning with a values-based assessment using workplace scenarios and company values. Prepare to explain how you would handle practical situations, but the exact assessment format may vary by role and team.
Candidates report HR conversations about values, prior experience, and expectations for the role. Have concise examples ready that connect your past work, collaboration style, and career interests to a software engineering position.
In one Karat technical interview, a candidate spent roughly 20 minutes reviewing a Kubernetes-based payment application and identifying flaws. Practice reading an existing design, stating assumptions, and explaining risks rather than only proposing a new system.
The same technical session included about 40 minutes of coding in the candidate’s chosen language. Candidates report easy-to-medium data-structures-and-algorithms questions plus discussion of time and space complexity, including evaluating a proposed solution.
Another candidate described a follow-up discussion with the technical team focused on role-specific questions and relevant experience. Be ready to walk through past engineering work, your decisions, and how your experience applies to the team’s needs.