Very long interview process. I applied in the beginning of January and didn't get the offer until the end of March.
Back-to-back interviews on the same day:
The on-site was in NY. It included a 1-hour tour and 1 hour with the director, but mine was only 20 minutes. In the end, they ran out of positions in the NY office and only offered me the Phoenix position. Such a turnaround.
I needed to follow up a lot with the recruiters, which made me feel like I was a back-burner choice.
Campus interview 1: Traveling Salesman Problem
Campus interview 2: Knapsack, SQL, basic algorithms
Skype interview: A lot of Java concepts, like the difference between String and StringBuffer. I had to read up on common Java concepts, which helped so much. Some coding questions, but they were simple algorithm things. Also SQL, HTML, web programming, and JavaScript. Be prepared, as it might not be simple.
On-site interview: No coding at all. I thought I did well as a person; coding is not everything. However, they chose someone else, and I was relocated for the Phoenix position.
The following metrics were computed from 34 interview experiences for the American Express Software Engineer role in New York, New York.
American Express's interview process for their Software Engineer roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for American Express's Software Engineer interview process in New York, New York.