The interview started with a very brief introduction of the interviewer and then dived right into a rapid-fire round of Java theoretical questions. This is something you would get if you searched "Java interview questions" on Google.
After mentioning these were not experience-oriented, the interview switched to more practical and experience-based questions in the second half.
Towards the end, the interviewer asked to open an IDE and share my screen for some coding. I mentioned I did not get a heads-up to have this set up.
Overall, in the one-hour interview, it was 55 minutes of questions from their side and only 5 minutes for me to ask them questions.
Honestly, I did not like the one-sided interview style, and the project also seemed not as advanced as I had hoped.
Google "top Java interview questions".
RESTful web services Basic Oracle SQL
The following metrics were computed from 6 interview experiences for the Bank of America Java Developer role in United States.
Bank of America's interview process for their Java Developer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Bank of America's Java Developer interview process in United States.