
HSBC software-engineer reports describe values-focused screening, role-and-experience discussions, and a technical session that may combine architecture analysis with coding and complexity reasoning.
$143K
Avg. Base Comp
$204K
Avg. Total Comp
2 rounds
Typical Rounds
2 weeks
Process Length
HSBC Software Engineer candidates report a process that can combine values-focused screening with practical technical discussion. One candidate completed a scenario-based assessment tied to company values before a technical interview; another described HR conversations about values, prior experience, and expectations, followed by a discussion with the technical team about role-specific experience. Prepare concise examples that connect your work to values and explain the decisions you made in past roles.
For the technical portion, one candidate reported reviewing a Kubernetes-based payment application for design issues rather than designing a system from scratch. That same session then moved to easy-to-medium data-structures-and-algorithms coding, with time and space complexity discussion. Practice reading an unfamiliar design, naming concrete risks or trade-offs, and clearly walking through a solution and its complexity.
Communication and scheduling varied across reports: one candidate encountered duplicate HR calls, while another cleared an initial interview but saw hiring paused without a restart timeline. Thin evidence means the exact format may differ by team, so ask the recruiter what stage comes next and keep your search active while waiting for updates.
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.
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 | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| P-value to a Layman | |
| Size of Joins | |
| Top 3 Users | |
| Over-Budget Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report either a scenario-based assessment tied to HSBC values or HR conversations covering values, prior experience, and role expectations. Prepare specific examples from your work and explain the choices you made.
One candidate described a discussion with the technical team about the role and relevant experience. Expect to explain how your past work relates to the position; the precise interview format may vary by team.
One reported technical interview began with analysis of a Kubernetes-based payment application, then included easy-to-medium data-structures-and-algorithms coding. Candidates may need to explain correctness and time and space complexity.