Real, anonymous reports from people who interviewed for Software Engineer at Amex, newest first and distilled into what to expect across the loop.
After I applied, the process kicked off with a video interview that was mostly behavioral, and it felt pretty standard for how they wanted me to walk through my background. I then went into a round of testing right before the final conversation, and finally I had a live coding interview to close things out.
I went through a pretty structured process that felt organized end to end, starting with a recruiter screen and then moving into interviews with more senior engineers and engineering managers. The later rounds were a mix of behavioral questions based on my resume plus coding challenges and even puzzles, so the day wasn’t just about writing code—it was about how I reasoned while answering.
The interview process typically begins with a recruiter screen, followed by a mix of technical and behavioral rounds, often culminating in a live coding session. Candidates noted that the overall timeline can vary, with some experiencing delays between stages, but many found the structure to be clear and organized.
Candidates faced a variety of technical questions, often focused on core programming concepts, data structures, and specific technologies relevant to the role. The difficulty level was generally described as average, with some candidates finding the questions straightforward while others felt they were pushed towards specific solutions.
Behavioral interviews often involved detailed discussions about past projects and scenario-based questions, with a strong emphasis on communication and cultural fit. Some candidates struggled with the expectations during these rounds, indicating that preparation for specific behavioral questions is crucial.
Candidates reported mixed experiences regarding interviewer engagement and communication throughout the process. While some found the interactions to be friendly and collaborative, others noted a lack of feedback and clarity, especially after interviews, which left them feeling uncertain about their performance.
The interviews often emphasized practical knowledge and real-world applications, particularly in technical discussions. Candidates noted that interviewers were interested in how they approached problems and their reasoning rather than just arriving at the correct answer, which added a layer of complexity to the evaluation.
The overall difficulty of the interview process was generally perceived as average, though some candidates found certain rounds to be more challenging than others. Many felt that the experience was structured enough to allow them to showcase their skills effectively, despite the pressure of the final rounds.