HSBC Technology India TSE and SDE loops emphasize CoCubes OA, a real Values Assessment cut, fundamentals-heavy technicals, and values-aware HR. This page synthesizes those patterns into round tables, outcome notes, and prep traps.
Round-wise process at a glance
Round
Typical format
What clears you
Online Assessment (CoCubes / AON)
Phase 1: ~70 MCQs in 75 min (aptitude ~20, English ~20, CS ~30). Phase 2: 2 coding problems in 30 min
Pace on MCQs; at least one coding problem with all test cases passing
HSBC Values Assessment
Situational / psychometric - best/worst or most-like-you choices; often take-home
Consistent answers aligned to Open, Connected, Dependable - real elimination
Technical interview
20-40 min, often on-campus virtual (Zoom) with panels
Depth on fundamentals + honest project ownership
HR interview
15-30 min
Motivation, values awareness, location, communication
Reported fresher TSE packages in recent public campus posts cluster around ~9 LPA; treat that as a reported figure, not an offer guarantee.
India campus vs SHL, HireVue and assessment centre
Public India Technology write-ups (2023–2025 batches) consistently describe CoCubes / AON, a separate Values Assessment email, then Zoom or on-campus technical and HR rounds. UK and global graduate guides instead describe SHL tests, HireVue, and an assessment centre / experience day with group exercises and case studies - still scored against Open, Connected, Dependable. If your portal shows HireVue or an experience-day schedule, prep competency STAR stories and commercial awareness; if it shows CoCubes and a values link after coding, prioritise timed MCQs, one full coding AC, and fundamentals depth.
About 70 questions in 75 minutes; one shared funnel had 254 sit this round
Rough split: ~20 aptitude (percentages, ratios, time & work, DI), ~20 English (error spotting, sentence rearrangement, RC), ~30 technical MCQs
Technical MCQs: DBMS (normalisation, keys, transactions), OOP, OS/Linux basics; some drives also touch Java/output and light cloud
Difficulty easy-moderate - pace is the constraint (~1 minute each)
Tip: Do not stall. Mark and move; the paper rewards coverage over perfection
Round 1, Phase 2 - Coding (30 min)
2 problems: one easy, one easy-to-moderate (arrays / strings / hashing are the usual territory)
Need at least one solution passing all test cases to progress; finishing both helps
Window often opens only after Phase 1 is cleared - stay in the CoCubes flow
Tip: Finish one problem completely before touching the second
Round 2 - HSBC Values Assessment
Next funnel size in one account: 76 candidates
Scenario-based behavioural / psychometric questions (best describes you; sometimes best and worst response)
Anchored to HSBC values - commonly framed as Open, Connected, Dependable
An actual elimination round (other campuses report large cuts here)
Tip: Read the values page and JD first, then answer consistently - favour transparency and early escalation over quietly absorbing risk
Round 3 - Technical Interview (20-30 min)
47 candidates at this stage in the same shared funnel
Self-introduction → preferred language and why → DSA inventory (heaps, stacks, queues, linked lists, arrays)
Implement a stack using an array, then using a linked list; discuss trade-offs (fixed size / contiguous memory vs dynamic nodes / pointer overhead)
SQL versus NoSQL; ACID properties with a concrete banking-style example
Deep dive on resume projects and academic standing; interviewer feedback often given before HR handoff
Result: Cleared
Tip: Fundamentals with depth beat a long list of half-known topics. Ask a thoughtful question at the end
Round 4 - HR Interview (~30 min)
15 candidates at this stage; in that account all 15 were selected (not a universal rule)
Introduction and family background; location preference; living away from family
Open prompts: automate one thing in college; confidence vs overconfidence
Values / website awareness; cyber-security threats and scams; how you stay current; who inspires you
Final result: Offer received
Tip: Open-ended questions score reasoning and communication - think out loud
Key takeaways: The OA is where most candidates exit. After that, HSBC checks fundamentals and fit - and the values assessment genuinely cuts people, so prepare for it like a real round.
Takeaways
What decided it: CoCubes pace plus at least one full coding AC, consistent Values Assessment answers, then fundamentals depth (stack implementations, ACID banking example)
Common fail: Dying on OA timing, or treating Values Assessment as a soft survey
How to practise: Timed 70-MCQ + 30-min coding mocks; read HSBC values then answer scenarios consistently; implement stack via array and LL
Technical interview experience 2 - SDE / TSE role
Technical interview experience 2
Candidate profile: Information Technology student, 7.6 CGPA, comfortable with Python and SQL
Round 1 - Online Assessment
Aptitude and English were straightforward; technical MCQs decided the cut
DBMS (normalisation, keys), OOP (inheritance, polymorphism), Linux commands
Coding: solved the easy problem fully; partial tests on the second
Tip: Revise Linux basics - they show up in MCQs and are easy to overlook
Round 2 - Values Assessment
Scenario choices; format can feel repetitive but stay consistent across items
Nothing technical to revise - values framing is the prep
Tip: Answer as the person who reports a problem early, not the one who hides it
Round 3 - Technical Interview
Python: mutable vs immutable, list comprehensions, how dictionaries work under the hood
SQL written live: joins, GROUP BY; DBMS: ACID, indexes and why not index every column
Project walkthrough - data, what you built, what you would change now
Live coding in some panels: Two Sum-style problems, pattern printing, string/array manipulation
Result: Cleared
Tip: They ask “why” after almost every answer - know the reasoning, not just the fact
Round 4 - HR Interview
Why HSBC, what you know about the organisation, which value resonates (with a real example)
Location among Indian technology centres; higher-studies plans
Final result: Offer received
Tip: Keep one concrete STAR story mapped to Open / Connected / Dependable
Key takeaways: Depth in one language plus solid DBMS/SQL beats exotic graph algorithms. Banking context shows up as transactions, indexes and consistency questions.
Takeaways
What decided it: Language depth and DBMS/SQL with transaction framing over exotic graph algorithms
Common fail: Broad shallow topic lists, or no banking-flavoured ACID story
How to practise: One language end-to-end; normalisation + transactions; one ATM/payment ACID walkthrough
OOP design for Swiggy-style classes; ER modelling for BookMyShow-style entities
Sorting approaches compared; Quick Sort coded after discussing complexities
4-square and water-jug puzzles - logic under time pressure, not LeetCode hards
Result: Cleared → HR in another room immediately
HR Interview
Introduction, family, why HSBC, hobbies
Final result: Selected (offer after ~2 days)
Key takeaways: Some HSBC panels weight puzzles and OOP design as heavily as DSA. Practice explaining trade-offs out loud.
HR interview experience
HR interview experience
Candidate profile: Electronics and Communication student, selected candidate
HR Interview (~20-30 min)
Conversational; more discussion than interrogation
Typical questions:
Tell me about yourself and your family background
Why HSBC? What do you know about us - did you visit our website / what was on the first page?
Which of our values means the most to you, and can you give an example?
If you had to automate something in your college, what would it be?
What is the difference between confidence and overconfidence?
Are you aware of common cyber-security scams?
Location preference and relocation comfort
Who is your role model?
Final result: Offer received
Key takeaways: The “did you visit our website” question is asked literally. Open thinking questions have no single right answer - the reasoning is what is scored.
Technical interview experience 5 - Intern, on-campus, late 2025 (Reddit)
Many short questions mixing HR-style situations and mental ability, built to test speed and accuracy
About 200 students took it; 5 moved on to coding
Round 2 - Coding (3 questions)
The candidate passed every test case on all three in 15-20 minutes; most others needed about an hour
4 candidates went through to interviews
Round 3 - Technical interview (virtual)
Relaxed, mostly about projects, checking that you really understand what your resume says
One very easy DSA question plus general conversation. Others in the thread were asked to find the most frequent character in a string, or to compute a Fibonacci-style recurrence in O(1) space
Round 4 - HR (about 5 min)
Why HSBC, and whether you can relocate to Pune or Hyderabad
Final result: The only selected intern from the batch
Key takeaways: Speed on the coding round separated this candidate from the rest. Interviews were easy, but another candidate in the same thread who felt their 30-minute interview went well was later told by the TPO they were not selected, so don’t read an easy interview as an offer.
Technical interview experience 6 - On-campus, September 2026 (Reddit)
Two-round interview day
Round 1 - Technical (40-45 min)
One DSA problem
A long project deep dive: why you built each feature, its impact, the resource constraints, the hurdles you hit while building it, and what would break under which conditions
DBMS and OOP questions
Round 2 - HR (about 20 min)
Why financial services and banking, why HSBC, HSBC’s values
Hackathons and past work experience
Key takeaways: The project discussion is where the technical round is won or lost. Prepare trade-offs and failure modes for every feature you list, not just what it does.
Online assessment experience - 2027 batch, 16 September 2026 (Reddit)
Behavioural test plus AI-assisted coding
Candidate profile: Software Engineer role, intern and full-time tracks in the same drive
Round 1 - Behavioural and data interpretation
Behavioural (about 40 questions): rank options for workplace situations, vocabulary, short audio clips with true/false statements, and emails, texts or meeting minutes to read and judge
Data interpretation (37 questions): argument analysis, pattern completion, drawing conclusions, bar graphs and tables
Shown as untimed, but at one college many who submitted late did not get the next link
Shortlists varied widely: 6 of 70 intern and 3 full-time candidates at the poster’s college; 30+ of 60 at another; 30 of 34 at a college that had already filtered to 8+ CGPA
Round 2 - AI-assisted coding (Codility)
Some candidates got only DSA, others DSA plus a development task. An AI assistant was available inside the IDE for the dev task, with Python, Node or Spring allowed
The DSA was easy: store products in a map and return how many there are, plus a short debugging task
Platform problems delayed some candidates’ links by a day or two
Result and pay
Interview shortlist expected 5-7 days after the coding round; rejected candidates got a feedback email
Reported pay: ₹50,000 a month for interns; ₹16.3 LPA CTC for full-time, of which ₹1.4 LPA is variable
Key takeaways: The first round, not coding, is the big filter. In the AI-assisted round, others in the thread warned that your prompt history is likely reviewed: set up the context first, use the assistant to go faster, and fix its mistakes yourself.
We read recent public posts from HSBC Trainee Software Engineer candidates (2026 and 2027 batches) on Reddit, Glassdoor and LeetCode Discuss and pulled out what came up repeatedly. This is a summary of patterns, not individual stories; your drive can differ.
Topic
What recent candidates describe
OA format
The 2027-batch drives (Sept 2026) ran two online rounds. Round 1 is a behavioural test plus data interpretation: situational ranking, vocabulary, audio clips, emails and meeting notes to judge true or false, then charts, argument analysis and pattern questions (about 75-80 questions in all). Round 2 is coding on Codility. Earlier drives used a 60-minute behavioural / mental-ability test, and some colleges still see the older CoCubes MCQ block
Coding questions
New in 2026: an AI-assisted coding round. Some candidates got only DSA, others DSA plus a small development task with an AI assistant built into the IDE (Python, Node or Spring). The DSA was easy (for example, counting distinct products with a map, plus a simple debugging task). Late-2025 drives used 3 plain coding questions
Gap to interview
About a week. One college had the OA on 16 September and interviews from 22 September; a senior told candidates the interview shortlist takes 5-7 days after the coding round
Number of interviews
Usually 2, often virtual: a 30-45 minute technical round, then a 5-20 minute HR round
Technical depth
One easy DSA problem (most frequent character in a string; a Fibonacci-style recurrence in O(1) space) plus a long project deep dive, DBMS and OOP
HR
Short but still eliminates people: why banking and financial services, why HSBC, HSBC’s values, hackathons or work experience, and relocation to Pune or Hyderabad
Pay (one 2027-batch report)
Software Engineer intern stipend ₹50,000 a month; full-time CTC ₹16.3 LPA including ₹1.4 LPA variable. Older Trainee Software Engineer reports are much lower (around 9 LPA), so check which role and year a figure refers to
After selection
Background verification is run by an external agency and is the most common source of delay. Missing documents hold it up; offer letters and joining dates can slip by weeks to months
A typical 2026 TSE drive, pieced together from candidate reports
This is not one person’s story. It strings together the steps that recent candidates describe most often, so you can picture the process.
Pre-placement notice. The campus mail lists the Trainee Software Engineer role, an eligibility line (commonly 60%+, no active backlogs) and an OA date.
Simulation / values assessment. An online test where you rank responses to workplace situations, answer audio and email-based true/false items, and (in 2026) work through a data-interpretation block. It is shown as untimed, but candidates suspect finishing time counts, and it cuts hard: at one college 6 of 70 intern applicants moved on. Answer consistently and in line with HSBC’s values (Open, Connected, Dependable).
Coding assessment. On Codility. Until 2025 it was 2-3 plain problems (strings, arrays, counting). In 2026 it became AI-assisted: easy DSA and sometimes a small development task with an AI assistant inside the IDE. Full test-case passes still matter, and candidates believe your prompts and edits are reviewed too.
Shortlist and interview day (about a week later). The technical interview runs 40-45 minutes. It starts with your introduction and a project deep dive, often with a request to sketch the design. It then moves to OOP, SQL joins and keys, a bit of OS, and one or two easy-medium coding tasks such as implementing a queue.
HR (10-15 min). Why HSBC, relocation and location preference, how the technical round went, and something about you that is not on your resume.
Result and background check. Results often arrive the same or next day. The external background check and offer paperwork then take anywhere from a few weeks to a few months.
What candidates say helped
Solving all coding questions quickly. One candidate who passed every test case in under 20 minutes said most of the room took about an hour.
Treating the values / simulation test as a real round, not a formality.
In the AI-assisted coding round, setting up the context and specification before asking the assistant for code, and correcting what it gets wrong rather than pasting its output.
Knowing every line of your resume; interviewers ask you to sketch your project’s design.
Common complaints
Long silence after the final round, and slow background checks before the joining date is confirmed.
Use these as frames, not scripts - interviewers probe follow-ups.
Technical
Q. Implement a stack using an array vs a linked list. Trade-offs? A. Array stack: contiguous memory, O(1) push/pop when capacity remains, risk of overflow / resizing cost. Linked-list stack: push/pop at head in O(1) without fixed capacity, extra pointer memory and poorer cache locality. Prefer array when max size is known; list when size is unpredictable.
Q. Explain ACID with an example. A. Atomicity (all-or-nothing transfer), Consistency (balances stay valid), Isolation (concurrent transfers do not interleave dirty reads), Durability (committed transfer survives crash). Example: debit ₹100 from A and credit ₹100 to B as one transaction.
Q. SQL vs NoSQL? When would you pick each? A. SQL: structured schema, joins, strong transactions - good for payments/ledger-style data. NoSQL: flexible documents/key-value, horizontal scale - good for logs, profiles, high-write unstructured data. HSBC panels often expect you to tie this to consistency needs.
Q. Why not index every column? A. Indexes speed reads/lookups but slow writes (each insert/update maintains the index) and consume storage. Index selective columns used in WHERE/JOIN; skip low-cardinality or write-heavy columns unless measured.
HR / values
Q. Why HSBC? A. Tie three beats: (1) global banking + India technology centres, (2) a concrete fact from the careers/values page or PPT, (3) how your skills (e.g. backend/data) map to that work. Avoid generic “prestigious bank” only.
Q. Which value resonates - with an example? A. Pick one of Open / Connected / Dependable. STAR: Situation → Task → Action that shows the value → Result. Example for Dependable: you owned a production bug, escalated early, fixed with tests, and documented so the team was not blocked.
Q. Automate one thing in your college? A. Pick a real friction (attendance, lab booking, certificate requests). State the user, the painful step, and a simple automation (form + DB + notification). Show product sense, not buzzwords.
Common questions checklist
Online assessment
Quant: percentages, ratios, time & work, averages, DI
Global graduate / assessment centre (when invite says so)
SHL numerical, verbal, inductive reasoning
HireVue competency video (values-mapped STAR)
Group exercise, case study, presentation
Strengths-based final interview
Tips from successful candidates
Assessment tips
Roughly a minute per MCQ - pace beats perfectionism
Revise DBMS, OOP and Linux for technical MCQs
Coding: one full AC before starting problem two
Do not neglect English - it is scored
Values assessment tips
Read Open, Connected, Dependable (and the JD) first
Answer consistently across scenarios
Favour transparency and early escalation
Treat it as a real elimination round
Interview tips
Depth on fundamentals beats half-known breadth
Be ready for “why” after every answer
One STAR story per stated value
Think out loud on open HR prompts; ask a question back
Sources
These links are research inputs used to map HSBC CoCubes, Values Assessment, and TSE technicals - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.
Verify CoCubes vs HireVue path against the current drive notification.
After the technical round, HSBC closes with a roughly 15-30 minute HR conversation: background, motivation, values, awareness and location preference. Prepare framed answers on the dedicated page rather than cramming them into this hub.
