Bank of America interview experiences from New York and Charlotte

The Bank of America interview process for US technology interns has two rounds after applying. A virtual HireVue records answers to behavioral questions, and a Superday of two back-to-back interviews of about 30 minutes covers tell me about yourself, resume projects, past internships and one or two basic technical questions, with no LeetCode-style coding in 2025 reports. Experienced engineers add a hiring manager screen and a 90-minute panel on Java, SQL, REST and unit testing.

Bank of America does not post a pay range for the summer program, and the 2027 posting prefers a 3.5 GPA. The Bank of America hub has the HireVue question list and program locations.

Bank of America interview process, round by round

Bank of America interview questions and experiences from the US (2025)

Five 2025 US reports from Taro, condensed.

• Software Engineer Intern, New York, offer (October 2025). Applied online, completed a virtual HireVue, then a Superday of two back-to-back interviews of about 30 minutes. Questions included tell me about yourself and your experiences. The whole process took about a month.
• Software Engineer Intern, Charlotte, offer (September 2025). Met two Bank of America software engineers at a conference they sponsored and was interviewed the same day. The 40-minute interview was completely behavioral, built around the resume and questions like how do you like to learn.
• Software Engineer Intern, US, no offer (November 2025). In-depth questions on resume projects and past internships, standard behavioral questions, and one or two basic technical questions such as how you find your way around the files of a new project. There were no LeetCode-style problems.
• Software Engineer, New York, offer (May 2025). An assessment test, a 30-minute Microsoft Teams screen with the hiring manager, then a 90-minute virtual panel with two senior developers covering Java coding, SQL, HTML and CSS, JavaScript, REST and unit testing.
• Software Engineer, New York (September 2025). A phone screen, then a face-to-face video call. The candidate wrote that “behavioral questions are a main part of the interview” and named no coding problems.

What the five reports share. Only the experienced New York hire mentions a coding assessment or live coding. The interns were asked about their own resumes in depth, so interviewers can follow up on any project, tool or internship you list. Two of the five got offers within about a month of first contact, and the Charlotte intern was hired the same day after a conference.

Bank of America interview questions that come up often

US interviews

1. Tell me about yourself and your experiences (Superday opener, New York)
2. “How do you like to learn?” (Charlotte)
3. “How do you navigate through files from a new project?” (US intern)
4. A deep dive on each resume project and past internship
5. For experienced hires: Java coding, SQL, REST, front-end basics and unit testing
6. HireVue: leadership, critical feedback, why Bank of America over competitors, five-year plan

India drives

1. Easy-to-medium coding: string reversal, pattern printing, Fibonacci, second-largest element, longest substring without repeating characters
2. Core Java: JVM, exceptions, multithreading, collections; String vs StringBuilder vs StringBuffer
3. SQL: second-highest salary, employees with no manager
4. Networking basics: IP vs MAC, how five connected computers communicate
5. A scenario on fixing crashes affecting 15,000 of 25,000 employees
6. HR: why banking technology, background verification, which India location you can relocate to

Behavioral interview

In the US, the Superday itself is mostly behavioral: a Charlotte intern was asked how they like to learn, and a New York intern opened with tell me about yourself and your experiences. In India, Bank of America usually closes with a short HR or hiring manager conversation after the technical rounds. The Bank of America behavioral interview questions page has STAR sample answers for these prompts.

Sample answers for high-frequency questions

Q. Implement binary search and state its time complexity.
A. 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?
A. 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?
A. Track two variables, largest and second, both initialized 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.
A. 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 behavior. 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?
A. 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.

Tips from successful candidates

Bank of America India: campus process and interview experiences

In India, the Bank of America campus process includes: 1. Online Assessment (90 minutes) - Coding/aptitude questions. 2. Technical Interview Round 1 (60 minutes) - Technical concepts. 3. Technical Interview Round 2 (60 minutes) - Advanced concepts and projects. 4. HR Interview (30 minutes) - Motivation and company fit. Total duration: 2-3 weeks from application to offer.

For India OA practice, see Bank of America placement papers.

The two campus drives below are from India; the front-end write-up and pooled reports come from GeeksforGeeks and Glassdoor.

Virtual campus drive (2025) - selected

Documented on-campus drive (2024) - not selected

Source: GeeksforGeeks, Bank of America on-campus 2024

The most detailed public account is worth reading precisely because it did not end in an offer. The candidate came through an on-campus drive and was among the 66 shortlisted out of 134 who took the assessment.

Pre-interview online assessment - five tasks, completed roughly two weeks before the interviews:

• A recorded video response on how the candidate’s skills aligned with the role.
• One easy coding question.
• One medium-difficulty coding question.
• A recorded video explaining the approach to the medium problem.
• A second skill-alignment video response.

Round 1 (in person)

• Introduction and a walkthrough of projects.
• Core technical questions: C vs C++, computer networks, IP vs MAC addresses and their bit lengths, how five connected computers communicate, and cybersecurity basics.
• Genuinely personal questions mixed in - hobbies, favorite singer, and whether the candidate had interviewed elsewhere.

Round 2 (in person)

• A deep dive on one project.
• Which language the candidate would pick for future projects (Python or JavaScript) and why.
• A scenario question: how would you handle a software crash affecting 15,000 of 25,000 employees globally?
• A hypothetical: what startup would you build in 15 years?

Outcome: rejected. Only 11 students received offers from the cohort. The candidate reported unprompted positive feedback from the round-2 interviewer, waiting from the end of their interview at 12:30 p.m. until 4 p.m. before being sent home (results came at 7 p.m.), and frustration at how opaque the selection criteria were. That is a useful expectation to set: at BoA the funnel is narrow at the end, and good feedback in the room does not translate reliably to an offer.

Takeaways

• What decided it: In this report, nothing in-room feedback guaranteed - only 11 of 66 shortlisted converted, despite positive verbal notes
• Common fail: Assuming a strong round-2 chat equals an offer, or under-preparing the recorded video + coding pre-assessment
• How to practice: Complete a full five-task mock (two videos, two codes, one approach video); treat waiting time and opaque criteria as part of the process

Documented experience - front-end software engineer

Source: GeeksforGeeks, Bank of America Software Engineer interview experience

A second write-up describes a three-round remote process for a front-end role, useful because it shows how much the question mix shifts by track:

• Round 1 (timed remote coding assessment): implement binary search on a sorted array; find the second-largest number in an array; reverse a string using a stack; then front-end tasks - building responsive page layouts in CSS, dynamic forms in JavaScript, and a feature in React or Angular.
• Round 2 (live technical): designing scalable, responsive layouts for data-heavy applications; explaining front-end architecture and how it integrates with the back end; and designing a system for real-time data visualization.
• Round 3 (HR): standard behavioral ground - communication, teamwork, career goals, motivation.

The candidate cleared the process but declined in favor of another offer.

What pooled reports add

• Glassdoor’s pooled reporting for the Technology Analyst role rates difficulty at about 2.6/5 with roughly 78% of candidates calling the experience positive - on the easier end for a global bank.
• The recurring advice across write-ups is blunt and consistent: have a genuine hold on DSA fundamentals, revise core CS subjects (OS, DBMS, networks), and only put things on your resume you can fully defend - BoA panels are reported to interrogate resume claims directly.

Takeaway: the differentiator at BoA is not exotic algorithms. It is core-CS fluency, a project you can defend line by line, and composure in scenario questions that have no single right answer. Prepare for a video-recorded assessment stage too - it is a format many candidates meet for the first time here.

Sources:

• Bank of America – Virtual Campus Drive 2025 - GeeksforGeeks (selected candidate write-up)
• Bank of America Interview Experience 2024 (On Campus) - GeeksforGeeks (student write-up, not selected)
• Bank of America Interview Experience for Software Engineer - GeeksforGeeks (candidate write-up)
• Bank of America Interview Experience - GeeksforGeeks (candidate write-up)
• Bank of America Technology Analyst interview questions - Glassdoor (pooled candidate reports)

Sources

The US reports come from Taro: a New York intern report, a Charlotte intern report, a US intern report, a New York Software Engineer report and a September 2025 New York report. The GPA preference is from Bank of America’s 2027 Global Technology Summer Analyst posting.

Similar companies

Goldman Sachs · JP Morgan · Wells Fargo · Capital One · Deutsche Bank · Morgan Stanley