How many interview rounds does Amex have for Software Engineer candidates, and what are they?

For Amex Software Engineer interviews, the loop commonly runs through Application Review, an Online Assessment, a Recruiter Screen, a Live Coding Session, and a Final Assessment Center. The Live Coding Session and Final Assessment Center are the main technical evaluations, with deep dives and behavioral evaluation in the final stage.

How hard is it to get an offer at Amex for a Software Engineer role?

Across reported interviews, the most common difficulty level is average. The offer rate reported for these interviews is 31%, which gives a sense of how competitive the process can be.

What topics get tested most for Amex Software Engineer interviews?

Expect Data Structures and Algorithms focus, including algorithmic problem solving like Two Sum, Anagrams, and Reverse String. You should also be ready for system and architecture topics such as System Design and Kafka Architecture, and for concurrency or correctness concepts like Race Conditions and Hash Tables or HashMap fundamentals.

What Java and Go topics should I prioritize for Amex Software Engineer interviews?

Java-focused rounds often emphasize HashMap internals, collision resolution and resizing, plus concurrency concerns like race conditions and deadlocks. For Go, you should be comfortable explaining goroutines, channels, and mutexes at a fundamental level, since concurrency mechanics show up in the technical areas.

What does Amex Software Engineer compensation look like, based on candidate and job-posting reports?

Reported compensation ranges from $103,750 base up to $215,250 total, with pay varying by level and location. Candidates also report the broader totals rather than a single figure, so plan your expectations around the range.

What should I study first for Amex Software Engineer live coding and final assessment center rounds?

Prioritize DSA and clean algorithmic problem solving first, because it is a top-tested area. Then move to your primary stack topics that match the role expectations, especially Java HashMap fundamentals and/or Go concurrency concepts, and be ready for Kafka architecture and system design discussions in the later technical rounds.

AmexSoftware Engineer

Updated Mar 18, 2026

Amex Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Amex, newest first and distilled into what to expect across the loop.

Get your personalized Amex Software Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

6 months ago

Difficult Positive London, England

I went through a clearly technical, higher-difficulty loop that felt centered on real engineering depth rather than just interview basics. After the recruiter stage, I ended up in technical rounds that were strongly focused on Kafka, Go, and microservices, with architecture and design questions layered on top. The conversations felt like they were trying to gauge whether I could think through system design and operational realities, not just write code.

In parallel to that, I also had an onsite-style experience that relied on my work experience and then shifted into whiteboard-style coding. The coding themes leaned on Java 8 features—things like streams and pattern matching—along with system design questions. I received positive feedback during those rounds, which made it more frustrating that the selection still didn’t go my way.

6 months ago

Average Negative Scottsdale, AZ

I started with an online application, then an initial assessment followed by a HireVue video interview. The HireVue portion leaned heavily into competency questions—leadership, teamwork, problem-solving, and why I was motivated to join. What stuck with me was how clearly everything was communicated: I always knew what the next step was, and the whole thing felt more structured and transparent than intimidating.

After that, the process moved into a more direct technical conversation. In my case it was a single technical interview that still felt fairly fair and grounded in the role, with coding questions included. The interviewer was friendly, but the communication wasn’t always smooth—there was a noticeable accent that made it hard to build rapport while I worked through the questions. Overall though, the experience still felt organized, and the online stages didn’t drag on.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences

Difficulty, sentiment and outcomes
New reports added every week

See all experiences

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Timeline

The interview process typically begins with a recruiter screen, followed by a series of technical and behavioral rounds that may include coding challenges, system design discussions, and assessments of past experiences. Candidates noted that the timeline was generally efficient, but some experienced delays in feedback and uncertainty about next steps.

Recruiter screenTechnical roundsBehavioral assessment

Technical Depth & Focus

Interviews often emphasized a strong technical foundation, with a focus on data structures, algorithms, and specific programming languages like Java and Python. Candidates faced a mix of coding problems, system design questions, and discussions about their previous projects, reflecting a high bar for technical competency.

Data structuresAlgorithmsJava

Behavioral & Cultural Fit

Behavioral interviews were integrated throughout the process, focusing on teamwork, leadership, and problem-solving skills. Candidates were encouraged to use structured frameworks like STAR to articulate their experiences and motivations for joining the company.

Behavioral questionsSTARCultural fit

Coding Challenges & Problem-Solving

Candidates encountered a range of coding challenges, from easy to medium difficulty, often requiring them to explain their thought process while solving problems. The interviews aimed to assess not just correctness but also clarity in reasoning and adaptability to changing requirements.

Coding challengesLeetCodeProblem-solving

Panel Dynamics & Interviewer Interaction

Some candidates experienced panel interviews where multiple interviewers assessed them simultaneously, leading to a fast-paced and demanding environment. The interaction style varied, with some candidates noting difficulties in communication or rapport building due to interviewer accents or pacing.

Panel interviewsInterviewer dynamicsCommunication

Overall Difficulty & Candidate Reflections

The overall difficulty of the interviews was perceived as medium to high, with candidates reflecting on the need for strong preparation across technical and behavioral aspects. Many noted that despite feeling well-prepared, the final decision often felt unpredictable and outside their control.

Difficulty levelPreparationCandidate reflections