As a Software Engineer at Industrial and Commercial Bank of China (ICBC), you will play a pivotal role in developing and maintaining the technological backbone of one of the world’s largest banking institutions. Your work will directly impact the efficiency and effectiveness of banking operations, enhancing both customer experience and internal workflows. This role is essential not only for the day-to-day functioning of banking services but also for driving innovation within the organization, ensuring that ICBC remains at the forefront of financial technology. The complexity and scale of the systems you will work on are immense. You will engage with various teams to deliver robust solutions that handle millions of transactions daily. From developing software that powers core banking systems to creating applications that improve customer interactions, the work is both challenging and rewarding. You will contribute to strategic projects that leverage technology to solve real-world banking challenges, making a meaningful difference in the financial services landscape. Expect to collaborate with cross-functional teams, including product managers, data scientists, and operations staff, to design and implement software solutions that support ICBC's mission. This role is not just about coding; it’s about understanding the business and user needs, and translating them into technical solutions that drive value for the bank and its customers.
HR Screening
reportedInitial screening to assess candidate's background and fit for the role.
What to demonstrate
- Initial screening to assess candidate's background and fit for the role
- Depth in Multithreading
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Interviews
reportedInterviews with team leads or senior engineers focusing on technical skills.
What to demonstrate
- Interviews with team leads or senior engineers focusing on technical skills
- Depth in Multithreading
How to prepare
- Answer aloud and timed: Describe a challenging technical problem you faced and how you resolved it.
- Answer aloud and timed: How do you approach debugging a complex software issue?
Behavioral Assessment
reportedEvaluation of candidate's collaboration, problem-solving, and cultural fit.
What to demonstrate
- Evaluation of candidate's collaboration, problem-solving, and cultural fit
- Depth in Multithreading
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral assessment above and write down what you would ask to confirm before it.
PracHub editorial advice for the preparation topics above.
Understand ICBC’s Values
Research and align your responses with the company’s core values. This alignment can significantly enhance your candidacy.
Practice Behavioral Questions
Prepare for behavioral questions by using the STAR (Situation, Task, Action, Result) method to structure your responses effectively.
Engage with Interviewers
Treat interviews as a two-way conversation. Asking insightful questions about the team and projects can demonstrate your genuine interest.
Stay Updated on Technology Trends
Familiarize yourself with emerging technologies relevant to the banking industry, as this knowledge can impress your interviewers.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function to sort an array of integers.
Write a function to sort an array of integers.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you implement a search algorithm for a large dataset?
How would you implement a search algorithm for a large dataset?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Describe the time complexity of your proposed solution.
Describe the time complexity of your proposed solution.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
Can you explain the concept of LINQ and how you have used it in your projects?
Can you explain the concept of LINQ and how you have used it in your projects?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe a challenging technical problem you faced and how you resolved it.
Describe a challenging technical problem you faced and how you resolved it.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What design patterns are you familiar with, and how have you applied them?
What design patterns are you familiar with, and how have you applied them?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you design a system to handle real-time transactions?
How would you design a system to handle real-time transactions?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Imagine you are tasked with improving the performance of a legacy application. What steps would you take?
Imagine you are tasked with improving the performance of a legacy application. What steps would you take?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you approach designing a feature that enhances customer security in online banking?
How would you approach designing a feature that enhances customer security in online banking?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you approach debugging a complex software issue?
How do you approach debugging a complex software issue?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Industrial and Commercial Bank of China candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Industrial and Commercial Bank of China loop
- Write out the reported sequence: HR Screening, Technical Interviews, Behavioral Assessment.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 3 reported rounds, with the weakest marked.
02Work Multithreading
- Spend the session on Multithreading, which Industrial and Commercial Bank of China candidates report being tested on.
- Write one worked example in Multithreading and time yourself on it.
Deliverable: One timed worked example in Multithreading.
03Work C#
- Spend the session on C#, which Industrial and Commercial Bank of China candidates report being tested on.
- Write one worked example in C# and time yourself on it.
Deliverable: One timed worked example in C#.
04Work SQL Server
- Spend the session on SQL Server, which Industrial and Commercial Bank of China candidates report being tested on.
- Write one worked example in SQL Server and time yourself on it.
Deliverable: One timed worked example in SQL Server.
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: What is your experience with C# and SQL Server?
- Answer aloud, timed: Can you explain the concept of LINQ and how you have used it in your projects?
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: Behavioral / Leadership
- Answer aloud, timed: Describe a time when you had to work under pressure. How did you handle it?
- Answer aloud, timed: What motivates you to work in the banking sector?
Deliverable: Spoken answers to 2 reported Behavioral / Leadership question(s), under time.
07Answer out loud: Problem-Solving / Case Studies
- Answer aloud, timed: How would you design a system to handle real-time transactions?
- Answer aloud, timed: Imagine you are tasked with improving the performance of a legacy application. What steps would you take?
Deliverable: Spoken answers to 2 reported Problem-Solving / Case Studies question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
What is your experience with C# and SQL Server?
What is your experience with C# and SQL Server?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a time when you had to work under pressure. How did you handle it?
Describe a time when you had to work under pressure. How did you handle it?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What motivates you to work in the banking sector?
What motivates you to work in the banking sector?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you prioritize tasks when faced with multiple deadlines?
How do you prioritize tasks when faced with multiple deadlines?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Share an experience where you had to persuade a team member or stakeholder to adopt your viewpoint.
Share an experience where you had to persuade a team member or stakeholder to adopt your viewpoint.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
What is your experience with C# and SQL Server?
- 02
Describe a time when you had to work under pressure. How did you handle it?
- 03
What motivates you to work in the banking sector?
- 04
How do you prioritize tasks when faced with multiple deadlines?
What is the typical interview difficulty for a Software Engineer at ICBC?
The interview difficulty can vary but is generally considered to be moderate. Candidates should expect a mix of technical and behavioral questions that assess both their coding skills and cultural fit.
Industrial and Commercial Bank of China Software Engineer candidate reports ↗How much preparation time is typical?
Candidates usually benefit from at least a few weeks of focused preparation, depending on their familiarity with the technologies and concepts relevant to the role.
Industrial and Commercial Bank of China Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates often demonstrate a strong understanding of both technical skills and the banking sector. They articulate their experiences clearly and show a genuine interest in ICBC’s mission and values.
Industrial and Commercial Bank of China Software Engineer candidate reports ↗What is the culture like at ICBC?
ICBC promotes a collaborative and supportive culture that values innovation and continuous improvement. Employees are encouraged to share ideas and contribute to team success.
Industrial and Commercial Bank of China Software Engineer candidate reports ↗What is the typical timeline from initial screening to offer?
The timeline can vary, but candidates may expect to hear back within a few weeks after their initial interview, with potential follow-ups for additional rounds.
Industrial and Commercial Bank of China Software Engineer candidate reports ↗What topics does Industrial and Commercial Bank of China test in interviews?
Industrial and Commercial Bank of China interviews most often cover SQL, Python, Decision-Making Under Uncertainty, Data Analysis, and Liquidity Risk. The exact emphasis depends on the specific role you apply for.
Industrial and Commercial Bank of China Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Industrial and Commercial Bank of China Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Aerospike Software Engineer Interview Questions & Guide 2026
Aerospike database-engine preparation through an original single-owner Python key-value store with bounded logical index accounting, disk-offset reads, conditional writes, tombstones, process-restart recovery and 3,240 checks. Existing 14 p
Slack Software Engineer Interview Guide
What Slack asks Software Engineer candidates, from reported rounds and questions.
Securitas Software Engineer Interview Guide
What Securitas asks Software Engineer candidates, from reported rounds and questions.