The first interview was via telephone, and it was with a VP and lead engineer.
The VP started it, and my initial impression was very good. His questions were general personality questions, nothing really technical.
Then he handed it over to the lead engineer for the technical part, and that's where I think it started to fall apart. I could barely hear him, which was complicated by the fact that he had a thick accent. So, what I did actually hear, I had a hard time understanding. I had to ask him to repeat himself several times.
The majority of the technical part of the interview was focused on Windows Workflow, a large part of the job requirement. I don't remember many of the questions now, but I do remember him asking the same question about three different ways. I wasn't sure if he was looking for a specific answer, and this was his way of "coaching" me or what.
The entire experience left me nonplussed.
When would you use a Code Activity versus a GUI activity (e.g., a Flowchart)?
Why wouldn't you use only GUI activities?
What other types of GUI activities have you used other than Flowchart?
What's the extent of your experience with SQL Server?
Do you have experience with Telerik controls or KendoUI?
The following metrics were computed from 10 interview experiences for the Bank of America Software Engineer role in Charlotte, North Carolina.
Bank of America's interview process for their Software Engineer roles in Charlotte, North Carolina is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Bank of America's Software Engineer interview process in Charlotte, North Carolina.