Learn from American Express India Technology Engineer Trainee / GET campus experiences. We synthesized public write-ups into round tables and prep takeaways - Codility OA with three coding problems, long resume-heavy technicals, and a managerial close mixing systems basics with HR.
Round-wise process at a glance
Round
Typical format
What clears you
Online Assessment (Codility)
3 DSA problems, easy → medium/hard
Full ACs matter; partials rarely enough alone
Technical (60-90 min, often 2 interviewers)
Projects + coding + SQL/OOP + puzzle
Depth on your stack; clean duplicate/array code
Managerial + HR
Auth/REST/HTTP + behavioural + why Amex
Ownership stories + culture fit
GD (some non-SDE tracks)
Case/current topic
Clarity and teamwork, not volume
One GET funnel: 10 tech → 4 managerial. One EDA/CFR account: ~11 final → 6 offers.
Why American Express? What motivates you to work here?
Strengths and weaknesses
How do you resolve disputes in a group?
What do you know about Amex as a company/business?
College life; languages known; reflection on prior round
Final result: Offer in select accounts (e.g. 6/11 style funnels on other tracks)
Key takeaways: Why-Amex needs a payments/customer or tech-platform beat, not “prestigious brand” alone.
Sample answers for high-frequency questions
Use these as frames, not scripts.
Technical
Q. Return all duplicates in an array. A. Hash map of frequencies, emit keys with count > 1; or seen + duplicates sets. Discuss O(n) time / O(n) space and sorted two-pointer alternative if mutating allowed.
Q. Why index a column? Why not every column? A. Indexes speed selective lookups/joins but slow writes and use storage. Index high-selectivity filter/join columns; skip low-cardinality flags unless measured.
Q. What is JWT in authentication? A. Signed token (header.payload.signature) issued after login; client sends on later requests; server verifies signature/expiry without server-side session (trade-offs: revocation). Tie to REST API auth flow.
Q. REST and HTTP - essentials? A. Resource URLs + methods (GET safe/idempotent read; POST create; PUT/PATCH update; DELETE). Status codes 2xx/4xx/5xx. Idempotency differences matter when they ask POST vs GET misuse.
Q. Kth largest element - approach? A. Sort O(n log n), then optimize with size-K min-heap O(n log K). Campus panels often require verbalizing both.
Q. Merge overlapping intervals? A. Sort by start, merge in one pass. Tie to billing or promo windows if asked in a payments context.
Q. Two users, one book left - database answer? A. Transaction + UPDATE ... WHERE qty > 0, optimistic version column, or serializable isolation; name lost-update problem.
HR / fit
Q. Why American Express? A. Global payments + India technology centres; one concrete product/trust or engineering fact; map your backend/data skills to card/transaction systems. Avoid generic banking praise.
Q. Resolve a team dispute? A. STAR: align on goal → hear both sides → data/criteria → decide and document. Show facilitation, not winning the argument.
These links are research inputs we used to map round structure and recurring questions - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for American Express.
After technical rounds, American Express usually closes with managerial/HR: motivation, conflict and company awareness. Prepare framed answers on the dedicated page.
Ready to prepare? Treat Codility as the real filter, then go deep on your own backend stack - Amex panels follow JWT, SQL and project decisions until the story breaks or holds.
Pro tip: Shared GET funnels shrink sharply into managerial - resume honesty beats listing every library you once imported.
