Interview experience
American Express interview experiences covering Online Assessment, Technical Interview 1, Technical Interview 2 / Manager Round, HR Round. Round-wise notes, common questions, and what candidates report clears each stage.
American Express Interview Questions and Answers (2026)
American Express is a global payments and premium financial services company known for its card products and merchant network. In India, American Express hires engineers in Gurugram and Bengaluru to build payments infrastructure, risk systems, and digital customer platforms.
Explore: Interview experience · HR interview questions · Overview · Placement papers · Preparation guide
Overview
American Express’s fresher hiring is a straightforward 3-4 stage loop anchored by a Codility-based online assessment, with technical rounds leaning on OOP and low-level design more than pure algorithmic depth.
HR interview questions
American Express HR interview questions with sample answer frameworks - motivation, relocation, STAR stories, and culture-fit prompts.
American Express interview process at a glance
| Round | Duration | What they test |
|---|---|---|
| Online Assessment | ~90 min | 3 coding questions (medium-hard) on Codility |
| Technical Interview 1 | 45-60 min | DSA, OOP concepts, low-level design |
| Technical Interview 2 / Manager Round | 45-60 min | Deeper technical + behavioral mix |
| HR Round | 20-30 min | Motivation, team fit, logistics |
American Express online assessment: quick answers
These answers are compiled from public candidate reports, not from an official American Express notice, and technology and analytics drives use different tests. The instruction screen of your own test is the final word.
| Question | Answer |
|---|---|
| Which platform is it on? | Codility for technology roles, in an August 2025 Engineer Trainee campus drive and in 2020-2021 campus drives. A November 2025 report also describes a 2-question Codility test. Analytics internship accounts do not name a platform. |
| How many questions and how long? | Technology: 3 coding questions (one very easy and two medium in the 2025 account; this page’s other reports say medium to hard) in about 90 minutes, the same 3 questions in 1 hour 30 minutes reported for 2020-2021 campus drives. Analytics (CFR) internship: about 90 minutes - 60 MCQs in 45 minutes, then 2 coding questions in 30 minutes. |
| Does it have negative marking? | It depends on the test. The analytics internship MCQ section had 0.25 negative marking per wrong answer in one GeeksforGeeks account. Codility coding tests for technology roles are scored on test cases, and no penalty is reported. |
| Is there a sectional cutoff? | Not published. On the analytics test you cannot switch between the MCQ and coding sections, so time each one separately. |
| How much is the cutoff? | No score cutoff is published. Engineering eligibility is typically 7.0 CGPA or above with no active backlogs, depending on the drive, per GeeksforGeeks’ recruitment-process page; a 2020 campus account also reports a CGPA cutoff of 7. |
| Is there coding, and what kind? | Yes - array, string and data-structure problems, with only one or two visible test cases on many 2025 tests. Analytics coding examples: find the missing bowl in a sorted sequence, and count students ahead in a queue with higher capability. |
| Is the manager round technical? | Often partly. The 2025 Engineer Trainee manager round asked for second-highest salary and employees ranked 10th to 15th in SQL alongside background questions. |
American Express interview questions by role
| Role | Reported questions and topics |
|---|---|
| Technology Engineer Trainee / Software Engineer | Codility test (2020 report): minimum deletions so every letter has a unique frequency, and count subarrays with sum 0; merge sort with a trace and the midpoint overflow fix; Climbing Stairs, maximum subarray; OOP pillars and access specifiers; process vs thread, critical sections, context switching; SQL vs NoSQL, ACID and CAP, concurrent purchases of one item, indexing; how a MERN frontend talks to the backend |
| Technology manager round | Background and college life; serverless computing and prompt engineering from the resume; SQL for second-highest salary and salary ranks 10-15 |
| Analytics intern (Credit and Fraud Risk) | Next number in a prime series; 3-digit numbers divisible by 3 and 4; wire-burning, hourglass and contaminated-pill puzzles; structure vs class, references vs pointers; UNION vs UNION ALL, ACID, predicting SQL output; attributes for choosing pizza-delivery pin codes |
Asked across every role: a detailed walkthrough of your main projects, how American Express makes money, and why American Express.
Online Assessment
A roughly 90-minute Codility test with 3 coding questions at medium-to-hard difficulty. Codility’s grading weighs code quality and edge-case handling alongside raw correctness, unlike a simple pass/fail judge. Many 2025 campus accounts report only one or two visible test cases per problem - hidden cases decide shortlists, so brute-force that passes samples but fails edge inputs is risky.
Common questions
- Array and string manipulation problems
- Basic data-structure implementation (stacks, queues) under time pressure
- Edge-case-heavy variants where partial test cases matter for your score
- Graph BFS/DFS or binary-search variants on sorted structures (reported in 2026 India GET write-ups)
- Kth largest / top-K patterns where interviewers expect brute force first, then heap optimization in later rounds
Technical Interview 1
Mixes core DSA with OOP fundamentals and a lightweight low-level-design prompt - expect to both write code and reason about class/schema structure in the same round.
Common questions
- Implement or reason about a linked-list or queue-based data structure
- Core OOP concepts - inheritance, polymorphism, interfaces vs abstract classes
- Design a small system or database schema (e.g. a simple rewards or transaction-logging system)
- Merge intervals or duplicate-detection on transaction timestamps - narrate O(n log n) sort vs sweep
- SQL joins and indexing on card- or merchant-style tables; normalization follow-ups
- Merge Sort trace + integer overflow on
(low + high) / 2midpoint (common Spring/Java campus panel)
Technical Interview 2 / Manager Round
A deeper technical round that often blends into a hiring-manager conversation - some candidates report this stage merging with HR, reducing the total to 3 rounds instead of 4.
Common questions
- Follow-up depth on your Technical Interview 1 answers
- Project walkthrough - architecture decisions and trade-offs
- Behavioural questions mixed with technical ones (team fit, ownership)
Round-by-round narratives are on the American Express interview experience page.
HR Round
A closing 20-30 minute conversation on motivation, team preference, and logistics.
Common questions
- Tell me about yourself, and why American Express?
- Which team or role would you prefer, and why?
- Describe a time you had to be extremely careful about accuracy under pressure
- Strengths and weaknesses
Sample answer frameworks for each of these are on the American Express HR interview questions page.
American Express technology vs analytics roles
American Express hires freshers into technology and into analytics and risk teams, and the tests are not the same.
| Technology (Engineer Trainee, Software Engineer) | Analytics and risk (for example Credit and Fraud Risk interns) | |
|---|---|---|
| Test | Codility, 3 coding questions, about 90 minutes | About 90 minutes: 60 MCQs with 0.25 negative marking, then 2 coding questions |
| Interviews | DSA, OOP, OS and DBMS rounds, then a manager round | Puzzles, aptitude, SQL and a guesstimate-style business question, then a techno-HR round |
| Business knowledge | Why American Express and payments interest | How American Express makes money is asked directly |
This page mainly covers technology hiring. If your drive is for an analytics or risk role, prepare puzzles, SQL and the MCQ paper.
Common technical interview questions and answers
Q: How do you implement a queue using two stacks?
Keep an input stack and an output stack. Enqueue always pushes onto the input stack, which is O(1). Dequeue checks the output stack: if it is empty, pop every element from the input stack and push it onto the output stack, which reverses the order so the oldest element ends up on top, then pop from the output stack. If the output stack is not empty, just pop it. Each element is moved at most twice across its lifetime, once in and once across, so dequeue is amortised O(1) even though a single dequeue can cost O(n). The mistake to avoid is transferring back and forth on every operation, which makes it O(n) per call. Total space is O(n), and peek follows the same lazy-transfer rule as dequeue.
Q: How do you design a stack that returns its minimum in O(1)?
Keep a second stack of minima alongside the main stack. On push, push the value onto the main stack and push the smaller of the new value and the current top of the min stack onto the min stack, so the min stack’s top is always the minimum of everything currently in the structure. On pop, pop both stacks together. getMin then just reads the top of the min stack. All operations are O(1) time and the structure uses O(n) extra space. If the interviewer pushes for O(1) extra space, the trick is to store an encoded value when a new minimum arrives, pushing 2 * newValue - oldMin, and to decode the previous minimum on pop; that works but risks overflow, which is worth calling out before you write it.
Q: How do you merge two sorted linked lists?
Create a dummy head node and a tail pointer starting at it, then walk both lists together: compare the two current nodes, splice the smaller one onto the tail, advance that list, and advance the tail. When one list runs out, attach the remainder of the other in a single step rather than continuing node by node. Return dummy.next. It is O(m + n) time and O(1) extra space, because you are relinking existing nodes rather than allocating new ones. The dummy node is what removes the awkward special case for choosing the first head. If instead you are merging k sorted lists, push the head of each onto a min-heap and repeatedly pop the smallest and push its successor, which is O(N log k) time for N total nodes.
Q: What is the difference between an interface and an abstract class?
An abstract class can hold state through instance fields, constructors, and any mix of concrete and abstract methods, and a class can extend exactly one of them. An interface historically declared only method signatures and public static final constants; since Java 8 it can also carry default and static method bodies, and since Java 9 private helpers, but it still cannot hold instance state, and a class can implement many interfaces. The design rule is that an abstract class expresses an is-a relationship with shared implementation, such as an abstract Transaction base carrying an amount, timestamp, and a shared audit method, whereas an interface expresses a capability that unrelated types can offer, such as Refundable or Auditable. Prefer interfaces when you want to keep the type hierarchy flexible, since single inheritance of classes is a hard constraint, and reach for an abstract class only when subclasses genuinely need to share fields or constructor logic.
Q: How would you design a database schema for a card transactions and rewards system?
Start with the core entities: customers, cards, merchants, transactions, and reward ledger entries. A cards table holds a card ID, its customer ID as a foreign key, a product or tier code, status, and a token rather than the actual card number, since raw card numbers should never sit in an application database. Transactions hold a transaction ID, card ID, merchant ID, an amount stored as a decimal type rather than a float, a currency code, a timestamp, a status such as authorised, settled, or reversed, and an idempotency key so a retried request cannot post twice. Rewards belong in an append-only ledger of point entries, each referencing the transaction that earned or redeemed them, so the balance is a sum rather than a mutable column that can drift; a running balance can be a periodically materialised snapshot for speed. Index on card ID plus timestamp for statement queries, and partition transactions by month, since that is the table which grows without bound. Rates and category multipliers belong in their own effective-dated table so a promotion changing tomorrow does not rewrite the meaning of yesterday’s transactions.
Q: How do you check whether a string of brackets is balanced?
Walk the string with a stack. On an opening bracket push it; on a closing bracket, if the stack is empty the string is unbalanced, otherwise pop and check that the popped opener matches the closer’s type using a small map from closer to opener. After the loop the string is balanced only if the stack is empty, which catches unclosed openers like a trailing open parenthesis. That is O(n) time and O(n) space in the worst case of all openers. Two edge cases interviewers deliberately test are an empty string, which should return true, and a string beginning with a closer, which must fail without underflowing the stack. If the input mixes brackets with other characters, decide explicitly whether they are ignored or invalid rather than assuming.
Q: How would you model a rewards engine so new offer types can be added without rewriting it?
Put each earning rule behind a common interface, for example a RewardRule with a method that takes a transaction and returns points earned, plus a predicate saying whether the rule applies. Concrete implementations then cover a flat rate per rupee, a category multiplier for dining or travel, a merchant-specific bonus, and a capped promotional offer, and adding a new offer means adding a class rather than editing a growing conditional. A RewardEngine holds an ordered list of applicable rules loaded from configuration and composes their results, which is the Strategy pattern combined with a Chain of Responsibility if some rules should stop evaluation. Keep rules effective-dated and stateless so they can be unit tested in isolation and so replaying an old transaction reproduces the original points exactly. The design principles to name are Open-Closed, since the engine is open to new rules and closed to modification, and dependency inversion, since the engine depends on the interface rather than on any concrete offer.
Q: How do you keep a transaction ledger accurate when requests can be retried or arrive out of order?
Make writes idempotent by requiring the client to send an idempotency key with every state-changing request and storing it under a unique constraint alongside the resulting outcome; a retry with the same key returns the stored result instead of posting a second entry. Make the ledger append-only and double-entry, so a correction is a compensating reversal entry rather than an update or delete, which keeps a complete audit trail and lets you rebuild any balance by replaying entries. Handle out-of-order arrival by keying on the event’s own business timestamp and sequence number rather than the arrival time, and by making the apply step commutative where possible so ordering does not change the final balance. Use a database transaction with an atomic conditional update, or a SELECT ... FOR UPDATE row lock, whenever a balance is both read and written, so two concurrent postings cannot both see the same starting balance. Finally, run a periodic reconciliation job that recomputes balances from the ledger and alerts on any drift, because in a payments system detecting an inconsistency late is the expensive failure.
Q: How do you find the Kth largest element in an array?
State brute force first: sort descending and pick index K minus one, which is O(n log n). The optimization Amex interviewers often push toward is a min-heap of size K: scan the array, push each value, and pop the smallest whenever size exceeds K, so the heap always holds the K largest seen - O(n log K) time and O(K) space. If K is close to n, quickselect gives average O(n). Always mention duplicates (does Kth mean distinct values?) and whether the input fits in memory. Campus panels frequently ask you to verbalize complexity on the easy warm-up before the harder variant.
Q: How do you merge overlapping intervals?
Sort intervals by start time, then walk with a merged list: if the current interval overlaps the last merged one (current start less than or equal to last end), extend the last end to the maximum of both ends; otherwise append a new interval. That is O(n log n) from sorting and O(n) extra space for output. Tie to Amex-flavoured examples such as billing cycles, promotional rate windows, or fraud-review time ranges on a card account. Mention edge cases: empty input, single interval, intervals that touch at a point (clarify inclusive vs exclusive ends).
Q: Two users try to buy the last item at the same time - how do you handle it?
Name the issue: a lost update or race without proper isolation. Practical pattern: wrap decrement-inventory and create-order in a database transaction at serializable or repeatable-read isolation, or use UPDATE inventory SET qty = qty - 1 WHERE sku = ? AND qty > 0 and check affected rows - zero rows means someone else won. Optimistic locking with a version column is another answer: read version, attempt update with WHERE version = ?, retry on conflict. For high contention, a short-lived lock or queue per SKU reduces thrashing. Amex DBMS panels often follow with ACID definitions and when you would pick SQL vs NoSQL.
Frequently asked questions about American Express interviews
Does the American Express online test have negative marking?
It depends on the role. One analytics (Credit and Fraud Risk) internship account reports 0.25 negative marking on a 60-question MCQ section. Technology roles take a Codility coding test scored on test cases, and no penalty is reported.
Which platform does American Express use for its online test?
Codility, for technology roles - an August 2025 Engineer Trainee campus drive had 3 coding questions on Codility, one very easy and two medium. Many 2025 candidates report only one or two visible test cases per problem, so hidden cases decide the shortlist.
What is the American Express interview process for freshers?
American Express campus hiring typically runs an online coding assessment (around 90 minutes, 3 questions of medium-to-hard difficulty on Codility), followed by one or two technical interviews (45-60 minutes each, DSA plus OOP and low-level design), and a final HR round. Total timeline is usually 2-3 weeks from test to offer.
What questions are asked in American Express interviews?
American Express technical rounds cover DSA problems (stacks, queues, linked lists), OOP concepts, and low-level design questions such as designing a small system or a database schema. The HR round asks why American Express, strengths and weaknesses, and which team or role you’d prefer.
How many rounds are there in the American Express interview?
Most American Express campus drives use 3-4 rounds: Online Assessment, one or two Technical Interviews, and an HR round. The later technical round is sometimes combined with the hiring manager discussion, so some candidates report only 3 stages.
What is the American Express online assessment like?
The OA runs about 90 minutes on Codility, with 3 coding questions at medium-to-hard difficulty - typically covering arrays, strings, and basic data-structure manipulation rather than heavy algorithmic puzzles. Codility auto-grades on both correctness and code quality/performance, so partial-credit test cases matter.
How should I prepare for American Express interviews?
Practice timed coding on Codility-style platforms specifically, since its scoring and test-case format differs slightly from LeetCode/HackerRank. Revise OOP and low-level design basics - Amex interviewers like asking you to design a small system or a simple schema. Prepare a clear story for why you want to join a payments and financial-services company, since that’s asked directly in HR.
Does American Express ask payments/fintech-domain questions for freshers?
Sometimes, though less than at a pure fintech startup. Interviewers occasionally frame low-level-design prompts around a card-transaction or rewards-style system, and the HR round explicitly checks your interest in payments/financial services. The core technical bar, though, is standard DSA/OOP/LLD rather than deep domain knowledge.
Does American Express use a video interview?
Many early-career candidates report a one-way recorded behavioural stage (often attributed to HireVue). Treat vendor name as unconfirmed; practise timed STAR answers either way.
How long is the Amex process?
Public guides often cite roughly 3-6 weeks across recruiter, assessment, video, and live rounds.
What fresher CTC is candidate-reported?
India fresher bands in campus chatter often sit around ₹12-22 LPA. Confirm the offer.
What interviewers are scoring at American Express
Amex scores Blue Box Values alignment, payments-aware technical judgment, and often a recorded video / HireVue-style behavioural screen before live loops.
| Signal | What a strong answer looks like |
|---|---|
| Values stories | Customer commitment, integrity, and quality with metrics |
| Tech track | Medium DSA, SQL, and APIs; fraud/payments framing when asked |
| Accuracy under pressure | One story where a mistake was caught before customer impact |
| Video discipline | Timed, concise answers without reading a script |
Gurugram / Bengaluru / Jaipur hub preferences should be consistent.
Behavioural themes to prepare
Why Amex, teamwork conflict, ethical judgment, adaptability, and ownership. Prep:
- Integrity - refused a shortcut that risked customer data or accuracy
- Customer recovery - fixed a payments/ops issue with clear communication
- HireVue timing - 90-second STAR cuts rehearsed aloud
Frameworks: American Express HR interview questions.
How to prepare for American Express interviews
- Loop map: Online Assessment; Technical Interview 1; Technical Interview 2 / Manager Round; HR Round. Confirm timings from the drive mail.
- Technical depth: Drill the Q&A section until answers are spoken, not read. Know every resume project cold.
- Experiences: Study round-wise notes on the interview experience page - real prompts beat generic lists.
- HR: Three STAR stories + a specific “Why American Express?” on the HR page.
A practical American Express prep plan
Use this as a default four-week loop before a American Express drive. Adjust to your invite timeline.
- Week 1: Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the American Express previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
- Week 2: Most American Express drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
- Week 3: Technical interviews at American Express usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why American Express?” with one concrete product, lab, or business line - not a slogan.
- Week 4: Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
10-day crash version: Days 1-4 timed DSA, days 5-7 resume projects + CS fundamentals, days 8-9 mock interviews out loud, day 10 HR STAR stories on the HR page.
Compensation notes
Candidate-reported fresher/early-career packages for American Express often cite ₹12-22 LPA fresher band. Treat forum numbers as ranges, not guarantees - confirm the written offer letter for your team and location.
Sources
Interview process details and sample questions on this site are editorially organized from public candidate reports and hiring write-ups, with round structure, prep notes, and company-specific framing added by our team. For round-by-round stories, see the American Express interview experience page. For OA papers and coding drills, use American Express on placementpapers.app. OA quick answers and role-wise questions draw on GeeksforGeeks American Express posts (the August 2025 on-campus Engineer Trainee account, a 2020 on-campus FTE account, an on-campus CFR/EDA internship account and the American Express recruitment-process page) and a November 2025 Glassdoor candidate snippet seen via search.