Candidates describe the American Express Software Engineer interview as an online assessment or recruiter screen, then technical rounds on DSA, Java fundamentals, and resume projects, followed by a behavioral or HR conversation.
$108K
Avg. Base Comp
$125K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the American Express Software Engineer interview as fundamentals-first. Most reports include an online assessment or a short recruiter screen, then one or more technical conversations, and finally a behavioral or HR discussion. Reported round counts vary from two to four, depending on the role and level.
The coding questions are usually described as easy to medium. Examples include a Two Sum-style hash map problem, sorting an array of 0s, 1s and 2s, an LRU cache, string permutations, and a tree problem. One candidate said the interview began with an easy problem and added requirements in stages. Two candidates were asked to explain a brute-force answer, and one of them was told not to use a standard data structure. Another was asked for both the brute-force and optimized solutions and went deep on how a HashMap works internally. Practice narrating your reasoning from the simple approach to the better one.
Project deep-dives come up in many reports. Interviewers ask what you built, why you made certain choices, and what you would change. Several Java-focused candidates also mention Spring Boot, OOP, and threading questions. One reported REST API design and a React question. Interns report a HireVue video round and "Why American Express?".
On outcomes, most reports here are rejections. Two candidates said the role was filled internally after long silences, so follow up on timing.
Synthesized from 40 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the American Express process.
The interview started with a short introduction and discussion about my resume and projects. Most questions focused on React, JavaScript, backend APIs, databases, and basic system design. I was asked to explain one project in detail and justify some of my technical choices. There were also a couple of DSA questions involving arrays and strings, followed by complexity analysis. The interviewer asked some OOP and SQL fundamentals as well. Overall, it was a mix of project-based and technical questions, with follow-up questions based on my answers. The interview was conversational and lasted around 45–60 minutes.
Questions asked:
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at American Express
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Precision and Recall | |
| Hurdles In Data Projects | |
| Success Measurement | |
| 85% vs 82% | |
| User Event Data Pipeline | |
| Offer Matching API Design | |
| Holiday Airport Traffic Surge | |
| Loan Model | |
| Optimize Model Performance | |
| Fixed-Length Arrays: Deletion | |
| Text Editor With OOP | |
| Decision Tree Evaluation | |
| Open Source Reporting Pipeline | |
| Client Solution Pushback | |
| Stakeholder Communication | |
| Why Do You Want to Work With Us | |
| Acquisition Threshold | |
| Your Strengths and Weaknesses | |
| Fast Food Database | |
| Singly Linked List | |
| Deer Density | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Rolling Bank Transactions |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report a short recruiter call or questionnaire before any technical work. One said it covered background, role expectations, and compensation range. Another said it was mostly basic personal questions. Timing and responsiveness vary, and some candidates describe slow scheduling between stages.
Candidates report a timed online assessment, often Codility or a browser IDE. Reported formats include easy array and string questions, two coding problems plus CS fundamentals, and a mix of multiple-choice and coding with countdown timers. One candidate reported no copy-paste and no outside help. It typically works as a filter, so practice under a timer.
Intern and entry-level candidates report a recorded HireVue interview with short prep time and limited answer time per question. Questions were mostly behavioral: motivation, why American Express, and future interests. One candidate also saw a basic technical trivia question. Experienced-hire reports do not consistently mention this step.
Candidates report one or more technical rounds. Coding questions are usually easy to medium, such as hash map, sorting, LRU cache, string, and tree problems. Some candidates were asked for brute-force before optimized solutions. Java-focused reports add HashMap internals, Spring Boot, OOP, threading, and REST API design. Interviewers commonly dig into resume projects.
Candidates describe behavioral questions about conflict, disagreement, ownership, and influencing without authority, along with interest in American Express. Some talked with a hiring manager or HR. Outcomes vary: a few interns report offers, while several experienced candidates report rejections. Two report the role was filled internally after slow follow-up.
