Openingloading the content…

Loadingone moment…

Finance, Payments & Fintech

American Express

Financial services / payments · Data Engineering interview

Strong SQL + PySpark with a production-first mindset; real-time card-transaction pipeline design with duplicate handling.

Cloud / platform

Hybrid; Hadoop/Hive/Spark heavy, GCP/AWS in places

Reported difficulty

Not reported

SQLPythonPySparkSparkDistributed systems

Hiring process

Recruiter

3–4 rounds (SQL/Spark → architecture)

Project deep-dive + behavioral

Offer

Round-by-round breakdown

SQL

High confidence

Find the second highest salary in each department
Window functions (RANK/DENSE_RANK/LEAD/LAG)
Self-joins; multi-table aggregation

PySpark

High confidence

Optimize a Spark job running slow due to data skew
repartition() vs coalesce()
Partitions, shuffling, caching, broadcast variables

System & pipeline design prompts

Design a pipeline to ingest real-time credit-card transaction data; handle duplicates (exactly-once vs at-least-once + idempotent dedup on transaction id)

Prep — high priority

SQL window functions + logic-puzzle queries
PySpark tuning (skew, repartition vs coalesce, broadcast)
Real-time transaction pipeline design with dedup/idempotency

Prep — medium priority

Data modeling for transactions
Data quality/validation stories

Rejection patterns

Lacking a production-first mindset (no data-correctness, validation, failure-handling)
Weak window functions
Cannot explain Spark skew fix or repartition vs coalesce

Reported experiences

Data Engineer (mid)

IllustrativeComposite

Composite: recruiter → SQL (2nd-highest-salary-per-dept; window) → PySpark (skew optimization; repartition vs coalesce) → system design (real-time card-transaction pipeline with dedup) → behavioral (production incident ownership).

Rehearse for American Express

Answered questions on what American Express actually asks — each with the short answer, the answer that gets you rejected, and the follow-up.

Then build one and have it reviewed: design a daily orders pipeline or model a marketplace. No account.

All interview experiences

Openingloading the content…

Finance, Payments & Fintech

American Express

Financial services / payments · Data Engineering interview

Strong SQL + PySpark with a production-first mindset; real-time card-transaction pipeline design with duplicate handling.

Cloud / platform

Hybrid; Hadoop/Hive/Spark heavy, GCP/AWS in places

Reported difficulty

Not reported

SQLPythonPySparkSparkDistributed systems

Hiring process

Recruiter

3–4 rounds (SQL/Spark → architecture)

Project deep-dive + behavioral

Offer

Round-by-round breakdown

SQL

High confidence

Find the second highest salary in each department
Window functions (RANK/DENSE_RANK/LEAD/LAG)
Self-joins; multi-table aggregation

PySpark

High confidence

Optimize a Spark job running slow due to data skew
repartition() vs coalesce()
Partitions, shuffling, caching, broadcast variables

System & pipeline design prompts

Design a pipeline to ingest real-time credit-card transaction data; handle duplicates (exactly-once vs at-least-once + idempotent dedup on transaction id)

Prep — high priority

SQL window functions + logic-puzzle queries
PySpark tuning (skew, repartition vs coalesce, broadcast)
Real-time transaction pipeline design with dedup/idempotency

Prep — medium priority

Data modeling for transactions
Data quality/validation stories

Rejection patterns

Lacking a production-first mindset (no data-correctness, validation, failure-handling)
Weak window functions
Cannot explain Spark skew fix or repartition vs coalesce

Reported experiences

Data Engineer (mid)

IllustrativeComposite

Rehearse for American Express

Answered questions on what American Express actually asks — each with the short answer, the answer that gets you rejected, and the follow-up.

Then build one and have it reviewed: design a daily orders pipeline or model a marketplace. No account.

All interview experiences