Real, anonymous reports from people who interviewed for Software Engineer at Bank of America, newest first and distilled into what to expect across the loop.
My process felt fairly standard and linear. After an initial recruiter call, I moved into a technical screen and then a final hiring-manager conversation. The recruiter stage was mostly about my background and fit, and then I got pulled into a technical format where the questions were anchored in my language and project experience rather than random trivia.
The first conversation I had was unusually casual. It was more of a fit-and-interest check than a technical assessment. Most of what we covered was behavioral, including my interest in working with mainframe and what I already knew about how it’s used at the company.
The interview process typically follows a structured sequence starting with a recruiter call, followed by technical interviews, and concluding with a managerial discussion. Candidates noted that the overall timeline can span about a month, with multiple rounds focusing on both technical and behavioral aspects.
Technical interviews often emphasize practical coding skills, system design, and problem-solving rather than pure theoretical knowledge. Candidates faced questions on Java, Python, SQL, and system architecture, with a strong focus on clarity and structured reasoning during coding exercises.
Behavioral interviews are a significant part of the process, with a focus on communication skills, cultural fit, and personal experiences. Candidates reported that interviewers often sought to understand their thought processes and how they handle real-world challenges in a team environment.
Candidates experienced various assessment formats, including online coding tests, live coding sessions, and panel interviews. Some reported a mix of behavioral and technical questions, while others faced more intense technical grilling, which varied by the interviewer's style and expectations.
The difficulty level of interviews varied, with some candidates feeling intense pressure during timed assessments or live coding sessions. Many reflected that the process rewarded clear communication and structured responses, especially under time constraints.
Candidates emphasized the importance of preparing to discuss their past projects and experiences in detail, as well as being ready for both technical and behavioral questions. A common reflection was the need to articulate thoughts clearly and maintain structure in responses.