
Two candidates describe American Express Data Engineer interviews that centered on project experience, SQL, and cloud data pipelines. One was a conversational Teams call; the other had a recruiter screen, a phone round, and an onsite.
$129K
Avg. Base Comp
$145K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates describe quite different American Express Data Engineer interviews, so prepare for both a conversational format and a hands-on SQL format.
One candidate had a screening call followed by a roughly 40-minute Teams interview. It was conversational and project-driven: the interviewer asked about the candidate's tech stack and recent work, then followed up on SQL and ETL optimization. The candidate discussed dbt, Snowflake, Redshift, BigQuery, Informatica PowerCenter, and a 50 TB SQL Server to Snowflake migration using Azure Data Factory, with a 30% cost reduction and 40% faster queries. This candidate reported no live coding.
The other candidate described three rounds: a recruiter screen on basic requirements, a phone round with a hiring manager, and an onsite at the Arizona office. The phone round covered data engineering system design and cloud architecture scenarios, with Kafka mentioned for streaming. SQL was the heaviest topic, and PySpark and Python algorithms came up less. At the onsite, two interviewers had the candidate write SQL on a whiteboard, focused on joins and BigQuery, and explain their reasoning. They also discussed recent projects and ETL pipeline work.
Both candidates ended with no offer. To prepare, be ready to explain a pipeline project with concrete numbers, practice writing joins aloud, and think through how you would design a scalable cloud pipeline. Candidates on visa sponsorship should confirm sponsorship details directly with recruiters, since one candidate reported getting conflicting answers between rounds.
Synthesized from 2 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.
I interviewed with American Express for a Data Engineer role and went through three rounds spread over several weeks. The first round was a recruiter screen focused on confirming I met the basic requirements for the position — nothing too technical, mostly about my background and experience level. They seemed to be filtering for minimum qualifications at that stage.
The second round was the technical deep dive. I had a phone conversation with a hiring manager that covered system design for data engineering solutions, and the interviewer spent considerable time on SQL — it was clearly the most heavily weighted topic. Since I had over three years of experience, they asked scenario-based questions around cloud data engineering architecture and mentioned Kafka for streaming projects. I walked through some recent work and tried to explain my approach to designing scalable data pipelines. The conversation also touched on PySpark and Python algorithms, though not as intensively as the SQL portion.
The final round was an onsite at the Arizona office. Two interviewers sat with me and asked me to write SQL queries on a whiteboard, focusing on joins and BigQuery. They also wanted me to explain my approach and reasoning behind the queries. We discussed my recent projects and ETL pipeline work. The atmosphere was fairly relaxed — they didn't ask particularly critical follow-up questions or dive deep into Python, which honestly surprised me given what I'd prepared for. I left feeling okay about it, but unfortunately didn't move forward. One thing that stung was that I'd clarified with the recruiter after round one whether they could sponsor OPT candidates, and they said yes, but then in round two the technical recruiter said they couldn't. That was a frustrating disconnect.
Prep tip from this candidate
SQL is the centerpiece of this process — especially joins and window functions in BigQuery — so prioritize that heavily over general Python algorithms. Be prepared to discuss system design and cloud architecture for data pipelines, and have concrete examples ready of how you've handled ETL and data reprocessing scenarios.
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 | |
| Fast Food Database | |
| Singly Linked List | |
| Z and t-Tests | |
| Assumptions of Linear Regression | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Xgboost vs Random Forest | |
| Success Measurement | |
| Text Editor With OOP | |
| User Event Data Pipeline | |
| Client Solution Pushback | |
| Holiday Airport Traffic Surge | |
| Fixed-Length Arrays: Deletion | |
| Open Source Reporting Pipeline | |
| Acquisition Threshold | |
| Deer Density | |
| Why Do You Want to Work With Us | |
| Rider Acquisition Target | |
| Your Strengths and Weaknesses | |
| Stakeholder Communication | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Employee Salaries | |
| Comments Histogram | |
| Top Three Salaries | |
| Last Transaction | |
| Subscription Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Both candidates report an initial screening call. One describes it as a check of minimum qualifications, mostly about background and experience level, with little technical content. Expect to summarize your experience and tech stack concisely.
One candidate had a roughly 40-minute Teams call about their tech stack and a major migration project, with follow-ups on SQL and ETL optimization. The other had a phone round with a hiring manager covering data engineering system design, cloud architecture scenarios, Kafka, and heavy SQL. Formats may vary.
One candidate reports a final onsite at the Arizona office with two interviewers. They wrote SQL on a whiteboard, focused on joins and BigQuery, explained their reasoning, and discussed recent projects and ETL pipeline work. The candidate found follow-ups relaxed and Python light.