American Express Software Engineer candidates most often report coding and data-structure questions alongside resume-based technical discussion, with behavioral conversations appearing in several processes.
$137K
Avg. Base Comp
$175K
Avg. Total Comp
2 rounds
Typical Rounds
2-4 weeks
Process Length
American Express Software Engineer interviews reported here commonly combine programming evaluation with a close discussion of the candidate’s own work. Be ready to explain both a brute-force and an optimized approach: one candidate was specifically asked to compare them, while others encountered coding problems involving arrays, hash maps, sorting, and general data structures and algorithms. Explaining reasoning, edge cases, and trade-offs matters as much as reaching code.
Project discussion is a recurring part of the technical conversation. Candidates report questions about what they built, design decisions, technologies used, and what they would change; several accounts also mention Java or backend fundamentals. Prepare a concise walkthrough of each resume project that connects your contribution to the technical choices you made. Some candidates also described light architecture or API-design discussion, so be ready to reason aloud about a practical design prompt when it arises.
Behavioral discussion appears in recruiter, manager, and later interview conversations. Have specific examples for collaboration, challenges, ownership, and influencing without formal authority. Candidate accounts vary by team and role focus, so the exact sequence and technical emphasis are not consistently reported.
Synthesized from 9 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 technical interview was more demanding than I expected because they wanted both the brute-force and optimized solutions to the DSA problems, and the difficulty ranged from medium to hard. The process began with an online assessment, with results coming about a week later. After that, I had a technical round followed by a managerial round. The overall process felt structured and aligned with the role, though communication between stages could be slow during busy periods.
In the technical discussion, the interviewers focused on algorithmic problem solving and expected me to explain my reasoning rather than jump straight to code. I was also asked detailed questions based on my resume and experience, so I would not treat the coding preparation as separate from project preparation. One topic that stood out was the internal implementation of a hash map, where they went into detail rather than keeping it at a surface-level definition. There was also a behavioral component, and the questions generally felt relevant to the job description.
I did not receive an offer. My main takeaway is to be ready to walk through a DSA solution from the brute-force approach to the optimal one, including the tradeoffs, and to know the technical details behind every item on your resume. I would also review how a hash map works internally, not just how to use one.
Prep tip from this candidate
Practice explaining DSA solutions from brute force to the optimal approach, and review hash map internals in detail. Be prepared for technical questions directly tied to every project and skill listed on your resume.
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 | |
| 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 | |
| Text Editor With OOP | |
| Fixed-Length Arrays: Deletion | |
| Decision Tree Evaluation | |
| Open Source Reporting Pipeline | |
| Client Solution Pushback | |
| Stakeholder Communication | |
| Acquisition Threshold | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Fast Food Database | |
| Singly Linked List | |
| Deer Density | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Empty Neighborhoods | |
| Top Three Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter screen focused on background or basic questions. Several candidates then completed an online assessment with programming or core-computer-science questions before moving to interviews; this step may not appear in every process.
Candidates report coding discussions covering data structures and algorithms, including array, string, hash-map, sorting, and palindrome-style problems. Some interviewers asked candidates to articulate a brute-force solution and then an optimized approach, while backend-focused accounts also included language or API fundamentals.
Candidates report detailed questions about projects, prior work, tools, and design choices. Depending on the team, the discussion may extend to practical architecture, system-design, or API-design reasoning; explain your role, trade-offs, and lessons clearly.
Several candidates report a manager, HR, or behavioral conversation after or alongside technical evaluation. Topics included collaboration, challenges, work style, future goals, and an example of influencing others without direct authority.
