Interview experience
Bank of America Interview Questions and Answers (2026)
Overview
Section titled “Overview”Bank of America’s India technology hiring runs through BA Continuum India (GTO), opening with a one-way HireVue video round before moving into a standard OA-plus-two-technical-rounds-plus-HR loop.
Bank of America interview process at a glance
Section titled “Bank of America interview process at a glance”| Round | Duration | What it tests |
|---|---|---|
| HireVue video round | Self-paced, ~30 min | 2 HR/behavioral + 2 coding + 1 technical question, recorded |
| Online Assessment | 90-120 min | Aptitude + coding / technical MCQs |
| Technical Round 1 | 45-60 min | DSA, OOPs, SQL, Java/C++ |
| Technical Round 2 | 45-60 min | OOD/system-design flavor, projects, domain topics |
| HR | 20-30 min | Motivation, location, background verification |
HireVue video round
Section titled “HireVue video round”A one-way, self-paced video interview where you record answers to preset prompts with no live interviewer watching. It’s an early filter before any human touchpoint, so clear, structured answers on the first take matter more than polish.
Common questions
- Tell me about yourself / why Bank of America
- A coding question explained verbally, e.g. reverse a string or find the second-largest number in an array
- A short technical concept question (OOPs basics, a data structure trade-off)
- Describe a time you worked in a team under a deadline
Online Assessment
Section titled “Online Assessment”Aptitude plus coding/technical MCQs covering DBMS, OS, and core programming, with a couple of coding problems on strings and data structures.
Common questions
- Coding on strings and basic data structures (easy-medium)
- DBMS queries and normalization MCQs
- OS fundamentals - scheduling, memory management
- Logical reasoning and quantitative aptitude
Technical Round 1
Section titled “Technical Round 1”A DSA-and-fundamentals round: live coding plus questions on OOPs and SQL, with the interviewer probing complexity and edge cases as much as the final answer.
Common questions
- Binary search implementation and variants
- Merge two sorted linked lists
- Explain the four pillars of OOPs and SOLID principles
- Write and optimize a SQL query (joins, aggregates)
Technical Round 2
Section titled “Technical Round 2”Leans into OOD/system-design-style thinking plus a detailed project walkthrough and domain conversation - core banking APIs and Java come up often for Global Technology roles.
Common questions
- Walk through your most complex project - architecture, hardest bug, what you’d rebuild
- Design a small object-oriented system (apply SOLID principles) rather than a full distributed design
- Explain how a core banking API might handle a failure or retry
- Front-end or back-end deep-dive questions depending on the specific role
Full round-by-round narratives are on the Bank of America interview experience page.
HR round
Section titled “HR round”A closing 20-30 minute conversation on motivation, location, and logistics - background verification timelines come up specifically given the regulated environment.
Common questions
- Why Bank of America, and why banking technology specifically?
- Comfort with background verification timelines
- Which GTO location (Mumbai, Chennai, Hyderabad, Gurugram, GIFT City) can you relocate to?
- Strengths, weaknesses, and a teamwork or conflict story
Sample answer frameworks for each of these are on the Bank of America HR interview questions page.
BA Continuum India and the GTO footprint
Section titled “BA Continuum India and the GTO footprint”Bank of America’s India hiring sits inside BA Continuum India Private Limited (BACI), the non-banking subsidiary that runs Global Technology and Operations (GTO) work - application development, infrastructure, and business process support for Consumer Banking, Global Banking and Markets, and Global Wealth and Investment Management. Unlike a single-campus tech center, BACI operates across five India locations - Mumbai, Chennai, Hyderabad, Gurugram, and GIFT City (Gandhinagar) - so the HR round’s relocation question is genuinely consequential, not boilerplate.
Common technical interview questions and answers
Section titled “Common technical interview questions and answers”Q: Implement binary search and state its time complexity.
Keep two pointers lo = 0 and hi = n - 1 on a sorted array. Each iteration compute mid = lo + (hi - lo) / 2 - written that way rather than (lo + hi) / 2 to avoid integer overflow - and compare arr[mid] with the target: return mid on a match, move lo = mid + 1 if arr[mid] is smaller than the target, else hi = mid - 1. The search space halves every step, giving O(log n) time and O(1) space for the iterative version (O(log n) stack space if written recursively). Interviewers usually follow up with the lower-bound variant: instead of returning on a match, keep shrinking to the left half to find the first index whose value is greater than or equal to the target.
Q: How do you merge two sorted linked lists?
Use a dummy head node and a tail pointer, then walk both lists at once: at each step append whichever node has the smaller value and advance that list’s pointer. When one list runs out, attach the remaining list wholesale to the tail. This is O(m + n) time and O(1) extra space because you relink existing nodes rather than allocating new ones. The dummy node is the trick worth mentioning explicitly - it removes the special case of choosing the first head.
Q: How would you find the second-largest element in an array in one pass?
Track two variables, largest and second, both initialised to negative infinity. For each element: if it is greater than largest, set second = largest and largest = element; else if it is greater than second and not equal to largest, set second = element. That is a single O(n) pass with O(1) space, versus O(n log n) if you sort. The edge cases interviewers probe are arrays with fewer than two distinct values and arrays with duplicates of the maximum - decide up front whether [5, 5, 3] should answer 5 or 3 and say so.
Q: Explain the four pillars of OOP with a banking example.
Encapsulation hides internal state behind methods - an Account class keeps balance private and exposes deposit() and withdraw() so no caller can set a negative balance directly. Abstraction exposes only what matters: a PaymentProcessor interface declares process(), and callers never see whether it is NEFT or UPI underneath. Inheritance lets SavingsAccount and CurrentAccount reuse Account’s common behaviour. Polymorphism lets one Account reference call the correct calculateInterest() at runtime depending on the actual subclass - the mechanism behind dynamic dispatch via the virtual method table.
Q: What are the SOLID principles, and which one do people violate most often?
Single Responsibility (one reason to change), Open/Closed (open to extension, closed to modification), Liskov Substitution (a subtype must be usable wherever its base type is), Interface Segregation (many small interfaces beat one fat one), and Dependency Inversion (depend on abstractions, not concrete classes). The most commonly violated in real code is Single Responsibility - a service class that validates input, writes to the database, and formats an email has three reasons to change. Dependency Inversion is the one that most directly enables unit testing, since injecting a repository interface lets you swap in a mock.
Q: Write a SQL query to find the second-highest salary in an Employees table.
The portable version uses a subquery: SELECT MAX(salary) FROM Employees WHERE salary NOT IN (SELECT MAX(salary) FROM Employees); This returns NULL rather than erroring when there is no second distinct salary, which is usually the desired behaviour. A cleaner modern answer uses a window function: SELECT DISTINCT salary FROM (SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS rnk FROM Employees) t WHERE rnk = 2; Use DENSE_RANK rather than ROW_NUMBER so that tied top salaries do not push the real second-highest out of position.
Q: What is database normalization, and when would you denormalize?
Normalization removes redundancy in stages: 1NF requires atomic column values, 2NF removes partial dependencies on part of a composite key, and 3NF removes transitive dependencies where a non-key column depends on another non-key column. In a banking schema that means customer details live in a Customers table and transactions reference customer_id rather than repeating the name and address on every row, so an address change is a single update. You denormalize deliberately for read-heavy reporting - a pre-joined daily balance summary avoids a five-table join on every dashboard load - accepting duplicated data and the write-time cost of keeping it consistent.
Q: How should a core banking API handle a failed or timed-out payment request?
The safe pattern is idempotency: the client sends a unique idempotency key with the request, the server records that key with the result, and a retry with the same key returns the stored result instead of debiting twice. Retries should use exponential backoff with jitter so a recovering service is not immediately overwhelmed by every client retrying in lockstep. A timeout is the dangerous case because the request may have succeeded - so never blindly retry a non-idempotent write; instead reconcile by querying transaction status with the same key. A circuit breaker that trips after a threshold of failures stops you from hammering a downstream system that is already down.
Frequently asked questions about Bank of America interviews
Section titled “Frequently asked questions about Bank of America interviews”What is the Bank of America interview process for freshers?
Bank of America’s Global Technology (BA Continuum India / GTO) process typically runs 4-5 stages: 1. A HireVue on-demand video round - 5 recorded questions (2 HR/behavioral, 2 coding, 1 technical) answered on camera with no live interviewer. 2. An Online Assessment (90-120 min) with aptitude plus coding/technical MCQs. 3. Technical Interview 1 (45-60 min) - DSA, OOPs, SQL, Java/C++. 4. Technical Interview 2 (45-60 min) - system-design-flavored OOD, projects, and domain topics like core banking APIs. 5. An HR round (20-30 min) on motivation, location, and background verification. Total timeline is roughly 2-3 weeks.
What is the Bank of America HireVue round like?
It’s a one-way recorded video interview - no live interviewer - with 5 questions typically split as 2 HR/behavioral prompts, 2 coding questions (explained verbally or typed, not always compiled live), and 1 broader technical question. It’s an early filter before the online assessment and live technical rounds, so structure and clarity matter as much as content.
What questions are asked in Bank of America interviews?
Coding questions lean easy-to-medium: binary search, reverse a string, two-sum variants, finding the second-largest number in an array, merging two sorted linked lists. Technical rounds also cover OOPs and SOLID principles, SQL queries, DBMS/OS fundamentals, and a deep walkthrough of your resume projects. Domain conversations touch core banking APIs and Java. HR checks ownership, teamwork, and comfort with background verification.
How many rounds are there in the Bank of America interview?
Typically 4-5 touchpoints: a HireVue video round, an online assessment, one or two live technical interviews, and a closing HR round. Some drives fold the HireVue stage into the online assessment step or skip a technical round - check your specific college placement email for the exact sequence.
How should I prepare for Bank of America interviews?
Practice timed DSA and aptitude mocks (binary search, linked lists, array problems come up often), revise OOPs/SOLID principles and SQL, prepare one crisp project narrative you can defend in depth, and rehearse the HireVue format by recording yourself answering common behavioral and coding-explanation prompts on camera.
Where does Bank of America hire technology talent in India?
Through BA Continuum India Private Limited (BACI), the non-banking subsidiary that runs Bank of America’s Global Technology and Operations (GTO) in India, with campuses across Mumbai, Chennai, Hyderabad, Gurugram, and GIFT City (Gandhinagar). Which city you’re hired into affects relocation logistics discussed in the HR round, but the interview process itself is standardised across locations.