As a Software Engineer at East West Bank, you play a pivotal role in shaping the technological landscape that supports our diverse financial products and services. This position is essential not only for optimizing internal processes but also for enhancing customer experiences through innovative software solutions. You will engage in developing and maintaining applications that cater to the bank's needs, ensuring they are secure, efficient, and user-friendly. Your work will impact various teams, including product development, operations, and IT support. By collaborating closely with stakeholders, you will contribute to strategic initiatives that drive the bank’s growth and customer satisfaction. The complexity and scale of projects will challenge you to leverage your technical skills and creativity, making this role both rewarding and critical to our mission of delivering exceptional banking services.
Phone Screen
reportedInitial screening call to evaluate candidate's background and role fit.
What to demonstrate
- Initial screening call to evaluate candidate's background and role fit
- Depth in System Failure Troubleshooting
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 Assessments
reportedIncludes coding challenges or system design discussions to assess technical skills.
What to demonstrate
- Includes coding challenges or system design discussions to assess technical skills
- Depth in System Failure Troubleshooting
How to prepare
- Answer aloud and timed: Describe how you would handle error management in a software application.
- Answer aloud and timed: What are the key principles of RESTful API design?
Behavioral Interviews
reportedInterviews focused on cultural fit and communication skills.
What to demonstrate
- Interviews focused on cultural fit and communication skills
- Depth in System Failure Troubleshooting
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 interviews above and write down what you would ask to confirm before it.
PracHub editorial advice for the preparation topics above.
Practice coding challenges
Make use of online platforms to refine your coding skills and get comfortable with problem-solving under time constraints.
Understand the bank’s mission
Familiarize yourself with East West Bank’s values and strategic objectives to align your responses with their goals.
Prepare for behavioral questions
Use the STAR (Situation, Task, Action, Result) method to structure your answers for behavioral questions effectively.
Stay updated on technology trends
Being knowledgeable about the latest trends in software development will demonstrate your commitment to continuous learning.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Can you explain the difference between synchronous and asynchronous programming?
Can you explain the difference between synchronous and asynchronous programming?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Write a function to reverse a linked list.
Write a function to reverse a linked list.
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?
Explain how you would approach optimizing a sorting algorithm.
Explain how you would approach optimizing a sorting algorithm.
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?
Can you solve the problem of finding the longest substring without repeating characters?
Can you solve the problem of finding the longest substring without repeating characters?
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?
Write a program to check if a string is a palindrome.
Write a program to check if a string is a palindrome.
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?
Discuss the time and space complexity of your solution to a specific problem.
Discuss the time and space complexity of your solution to a specific problem.
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?
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?
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?
How would you optimize the performance of a web application?
How would you optimize the performance of a web application?
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 how you would handle error management in a software application.
Describe how you would handle error management in a software application.
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 are the key principles of RESTful API design?
What are the key principles of RESTful API design?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Discuss a recent project where you implemented a new technology stack.
Discuss a recent project where you implemented a new technology stack.
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?
Read latency spikes on a sixty-second sawtooth
The cached listing read path serves about 14k reads/second at an 85% hit rate. p99 sits at 35 ms for 57 seconds, jumps to 900 ms for 3, and repeats. During each spike the primary shows several hundred identical listing queries starting within the same millisecond, all carrying one large tenant's id. Cache entries use a 60-second TTL. Give the mechanism, the ordered checks, the fix, and the correctness hazard your fix must not introduce.
Approach
- Match the period to a configured number before theorising about load. A spike every 60 seconds against a 60-second TTL is an entry expiring, and you confirm it by correlating spike timestamps with the entry's write time rather than with the traffic curve. If the period had matched a cron or a GC interval instead, this is a different investigation.
- Establish the concurrency of the miss. Several hundred identical queries in one millisecond means the miss path has no coalescing: every request that arrives between expiry and repopulation recomputes. The herd size is that key's arrival rate times its recompute time, so at 1.2k reads/second for the hot key and a 250 ms recompute you expect about 300 concurrent misses, which matches what is observed.
- Add single-flight on the miss path so one caller per key recomputes under a short-lived lock while the rest wait for its result. Prefer stale-while-revalidate where the read tolerates it: return the expired value immediately and refresh asynchronously, which removes the latency spike rather than serialising it into a queue of waiters.
- De-synchronise the keys. Write TTLs with jitter, for example 60 seconds plus or minus 10%, so a deploy or a mass invalidation does not align every key on the same second and turn a per-key herd into a fleet-wide one.
Follow-up
- The same sawtooth appears on a key that is invalidated on write rather than expired. Is that the same bug?
- How does your answer change if the recompute takes 4 seconds instead of 250 ms?
Built from the rounds and topics East West Bank candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the East West Bank loop
- Write out the reported sequence: Phone Screen, Technical Assessments, Behavioral Interviews.
- 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 System Failure Troubleshooting
- Spend the session on System Failure Troubleshooting, which East West Bank candidates report being tested on.
- Write one worked example in System Failure Troubleshooting and time yourself on it.
Deliverable: One timed worked example in System Failure Troubleshooting.
03Work Incident/Issue Resolution
- Spend the session on Incident/Issue Resolution, which East West Bank candidates report being tested on.
- Write one worked example in Incident/Issue Resolution and time yourself on it.
Deliverable: One timed worked example in Incident/Issue Resolution.
04Work Full-Stack.NET
- Spend the session on Full-Stack.NET, which East West Bank candidates report being tested on.
- Write one worked example in Full-Stack.NET and time yourself on it.
Deliverable: One timed worked example in Full-Stack.NET.
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: How would you optimize the performance of a web application?
- Answer aloud, timed: Can you explain the difference between synchronous and asynchronous programming?
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: Behavioral / Leadership Questions
- Answer aloud, timed: Describe a time when you faced a significant challenge in a project. How did you overcome it?
- Answer aloud, timed: How do you prioritize tasks when working on multiple projects?
Deliverable: Spoken answers to 2 reported Behavioral / Leadership Questions question(s), under time.
07Answer out loud: Coding / Algorithms
- Answer aloud, timed: Write a function to reverse a linked list.
- Answer aloud, timed: Explain how you would approach optimizing a sorting algorithm.
Deliverable: Spoken answers to 2 reported Coding / Algorithms 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.
Describe a time when you faced a significant challenge in a project. How did you overcome it?
Describe a time when you faced a significant challenge in a project. How did you overcome 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?
How do you prioritize tasks when working on multiple projects?
How do you prioritize tasks when working on multiple projects?
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?
Give an example of how you effectively communicated technical information to a non-technical audience.
Give an example of how you effectively communicated technical information to a non-technical audience.
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 situation where you had to work as part of a team. What was your role?
Describe a situation where you had to work as part of a team. What was your role?
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 handle feedback and criticism from peers or supervisors?
How do you handle feedback and criticism from peers or supervisors?
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
Describe a time when you faced a significant challenge in a project. How did you overcome it?
- 02
How do you prioritize tasks when working on multiple projects?
- 03
Give an example of how you effectively communicated technical information to a non-technical audience.
- 04
Describe a situation where you had to work as part of a team. What was your role?
How difficult is the interview process, and how much preparation time should I expect?
The interview process can be challenging, with a focus on both technical and behavioral assessments. It's advisable to allocate several weeks for thorough preparation, reviewing core concepts and practicing coding problems.
East West Bank Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates often demonstrate a strong technical foundation, effective communication skills, and a clear understanding of East West Bank's values and how they align with the role.
East West Bank Software Engineer candidate reports ↗What is the culture and working style at East West Bank?
The culture at East West Bank emphasizes collaboration, innovation, and a commitment to customer service. Engineers are encouraged to share ideas and work together to solve complex problems.
East West Bank Software Engineer candidate reports ↗What is the typical timeline from initial screen to offer?
The timeline can vary, but candidates can expect the process to take several weeks, depending on the number of interview rounds and scheduling.
East West Bank Software Engineer candidate reports ↗Are there remote work or hybrid expectations?
The bank's policy on remote work may vary by team, so it's best to clarify during the interview process regarding expectations for in-office versus remote work.
East West Bank Software Engineer candidate reports ↗What topics does East West Bank test in interviews?
East West Bank interviews most often cover Stakeholder Management, SQL, Machine Learning, Stakeholder Communication, and Requirements Gathering. The exact emphasis depends on the specific role you apply for.
East West Bank 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.
- 01East West Bank 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.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai 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.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.