
Reported Bank of America Merrill Lynch Software Engineer interviews include Java-focused technical discussions, practical architecture questions, resume-based behavioral prompts, and HR or managerial conversations in explicitly reported three-round processes.
$125K
Avg. Base Comp
$150K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
Bank of America Merrill Lynch Software Engineer candidates in these reports describe a process that rewards clear practical engineering explanations more than puzzle-only preparation. Technical conversations covered core Java, collections, Java memory allocation, HashMap internals, database queries, and concurrency. Candidates should be ready to move beyond naming an API: explain how a concept works, where it fits in a production service, and the tradeoffs behind the choice.
Architecture discussion can be substantial. Reported prompts included scalable payment processing and a highly available, real-time transaction platform. Relevant experience discussed by candidates included Spring Boot, microservices, REST API design, Kafka-based event-driven systems, SQL, and multithreading. One candidate also received a medium array-or-string problem, while another described a multithreading optimization task. Practice communicating an approach aloud, including assumptions, alternatives, and the reasons for a design decision.
Behavioral questions were closely tied to the candidate's own background. Reports mention resume walkthroughs, current projects, challenging work situations, role-change motivation, production-issue response, and communication. Prepare concise examples that identify your contribution, the technical decision you made, and the result. Several reports explicitly describe three rounds, though the order and emphasis varied: one candidate reported two technical interviews followed by HR, while another reported HR screening, technical, and managerial discussions.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Bank Of America Merrill Lynch process.
The most substantial part of my interview was a one-hour technical discussion with two senior Bank of America developers. I had applied through Insight Global, and a recruiter contacted me within a week. The initial screening lasted about 15 minutes and covered my background, visa status, expectations, availability, and the role and team. It was largely resume-based, with questions about my current project, day-to-day responsibilities, and experience using Java, Spring Boot, microservices, and cloud technologies.
The second round went deeper into the stack without becoming heavily algorithmic. The developers asked about core Java topics such as object-oriented programming, collections, and basic multithreading. We also discussed Spring Boot, microservices architecture, REST API design, appropriate HTTP status codes, API best practices, and foundational SQL and database design. The main system-design question was how I would build a scalable payment-processing system, so I had to explain the architecture and reasoning behind my choices rather than simply name technologies.
There was also a medium-level coding problem involving arrays or strings. It was not an interview dominated by LeetCode-style exercises; most of the hour was spent testing practical knowledge and how clearly I could work through a problem. The interviewers were professional and seemed more interested in my thought process than whether I immediately reached the final answer. I was not selected to move forward after this round, but the overall interaction was positive.
For preparation, I would focus on explaining Java and Spring Boot concepts in the context of real projects, especially microservices and REST API decisions. I would also rehearse a scalable payment-system design and practice talking through a moderate array or string problem aloud.
Prep tip from this candidate
Be ready to design a scalable payment-processing system and justify Java, Spring Boot, microservices, REST status-code, SQL, and database choices. Also practice narrating your reasoning through a medium array or string problem, since the interviewers emphasized thought process over the final answer.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Bank Of America Merrill Lynch
Implementing a priority queue used linked lists.
| Question | |
|---|---|
| Capital One Chatbot Design | |
| Secure Messaging Platform | |
| Triangle as Binary Array | |
| Deciding Between Solutions | |
| Testing Constraints | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Comments Histogram | |
| Prime to N | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Cumulative Distribution |
Synthesized from candidate reports. Individual experiences may vary.
Candidates reported either a recruiter or HR screen, or an online assessment with behavioral prompts. Discussion included a resume overview, current project work, responsibilities, availability, expectations, and role fit. Prepare a concise account of your experience and be able to explain the decisions behind the projects you mention.
Reported technical interviews covered core Java, collections, HashMap internals, memory allocation, concurrency, database queries, Spring Boot, microservices, REST APIs, and SQL. Some candidates also described a system-design prompt on payment processing or real-time transactions, plus either a medium array-or-string exercise or multithreading optimization.
Closing conversations in the reports included HR or managerial discussions. Candidates described behavioral questions, cultural fit, production-issue response, competitiveness, challenging work situations, and reasons for changing roles. Use specific examples from your work that show communication, judgment, and how you handled a difficult situation.