Skip to content

Bank of America Interview Experiences

How Bank of America fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

Bank of America placement 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.

Eligibility (from student reports): 7.0+ CGPA or 70%.

Fresher package ballpark (from student reports): Analyst: ₹12-20 LPA. Confirm on your offer letter.

Round Duration What they test
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 Projects + domain / puzzles (varies)
HR 20-30 min Motivation, location, background verification

Documented on-campus drive (2024) - not selected

Section titled “Documented on-campus drive (2024) - not selected”

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 in the group of 66 shortlisted out of 134 applicants.

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 address vs MAC address, and cybersecurity basics.
  • Genuinely personal questions mixed in - hobbies, favourite singer, and whether the candidate had interviewed elsewhere.

Round 2 (in person)

  • A deep dive on one project.
  • Why the candidate preferred their programming language.
  • A scenario question: how would you handle a software crash affecting 15,000 employees globally?
  • A hypothetical: what startup would you build?

Outcome: rejected. Only 11 students received offers from the cohort. The candidate reported positive verbal feedback from the round-2 interviewer, roughly four hours of waiting between rounds, 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.

Documented off-campus experience - front-end software engineer

Section titled “Documented off-campus experience - front-end software engineer”

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 visualisation.
  • Round 3 (HR): standard behavioural ground - communication, teamwork, career goals, motivation.

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

  • Glassdoor’s aggregate 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:

  1. Valid parentheses / expression checks. Usually expects stack
  2. Find duplicates in a stream. Usually expects hashing
  3. SQL + coding hybrid (nth highest / joins). Usually expects window functions / careful queries
  4. Discussion on core banking APIs and Java, bottlenecks, failure modes, simple APIs
  5. Detailed project discussion, architecture, hardest bug, what you would change
  1. Why banking technology?
  2. Comfort with background verification timelines
  3. Location preference
  4. Strengths and weaknesses
  • Clear the screening round first. Timed practice beats last-minute topic hopping.
  • For domain questions, explain core banking APIs in plain language, inputs, outputs, what breaks at scale.
  • OOPs and SQL still open a lot of Bank of America panels. Do not skip fundamentals.
  • HR answers should be concrete. One story with a result beats five slogans.
  • If you do not know something, say so and outline how you would find out.

After technical rounds, Bank of America usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

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