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.
After applying through Insight Global, I heard back from a recruiter within about a week. That recruiter call felt fairly standard: we went over my background, my visa situation, and what I expected, then I got a quick overview of the role and the team. About a day later I moved into a longer technical interview with two senior developers, and that round was very Java- and backend-focused.
My process started with a HireVue video interview. It was one-way and felt pretty manageable: I answered a handful of preset questions, with a short prep window before speaking. The emphasis was mostly behavioral and on my interest in the financial sector rather than deep technical coding.
The interview process typically begins with a recruiter call or a HireVue video interview, focusing on behavioral questions and the candidate's background rather than deep technical skills. This stage serves as a preliminary filter to assess fit and interest in the role.
Candidates can expect one or more technical interviews that cover core programming concepts, particularly in Java, as well as system design and database fundamentals. The emphasis is on understanding and explaining concepts rather than just producing correct code.
Behavioral questions are a significant part of the interview process, often focusing on past experiences and how they relate to the role. Candidates should prepare to discuss their projects and problem-solving approaches in a conversational manner.
The interview format often includes multiple rounds, sometimes with panel interviews, where each interviewer focuses on different areas of expertise. Candidates should be prepared for a mix of technical and behavioral questions in a structured manner.
Candidates have reported varying experiences with communication post-interview, with some experiencing delays and a lack of feedback. It's important to manage expectations regarding follow-up timing and the potential for ghosting.
The overall difficulty of the interviews is generally considered average, with a focus on assessing foundational knowledge and communication skills rather than high-pressure coding challenges. Candidates should approach the interviews with confidence in their understanding of core concepts.