Academic snapshot
Marks: 7.0+ CGPA / 70% (candidate-reported)
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
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: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list when printed | Coding bar, SQL/project depth |
| Careers portal / referral | Resume screen volume; sometimes no hard published CGPA | Still expect Amex Online Assessment + tech loop |
| Intern → full-time | Conversion interviews may skip a stage | You still defend projects and code |
Off-campus does not mean “easier coding.” It often means more applicants fighting the same timed filter. If your CGPA sits near 7.0, spend energy on mocks, not on hunting a mythical lower cutoff blog post.
Is 7.0 CGPA enough? It matches the commonly reported floor. Selection still hinges on OA correctness and interview narration. A 7.1 with clean timed coding and SQL beats an 8.8 that freezes on edge cases.
Branches: CS/IT/ECE and analytics-related streams dominate shortlists. Adjacent branches show up when DSA and SQL are solid. If your college lists only certain branches for a drive, read the notice.
Gaps and backlogs: Active backlogs are the usual blocker at offer time. A short education gap is easier to explain with a skills story (projects, internship, course) than silence. Lying about CGPA or backlog status is an instant integrity fail in HR.
What helps the resume screen: One project you can defend end-to-end (stack choice, hardest bug, metric), any internship with ownership language, and honest tech keywords you can explain. Certificates are optional extras - DSA and OA mocks matter first. See certifications only after fundamentals are solid.
Academic snapshot
Marks: 7.0+ CGPA / 70% (candidate-reported)
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Branch & skills
Preferred: CS / IT / ECE / analytics-related
Languages: Java, Python, SQL
Focus: DSA, Java, SQL, product thinking
Differentiator: Card/payments domain + Leadership behaviors
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ CGPA / ~70% | Some notices mirror college norms; verify every drive |
| Degree | B.E. / B.Tech / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE, analytics-related | Strong DSA/SQL can help adjacent branches on some drives |
| Year | Final year + recent grads | Internship → conversion paths also appear |
| Backlogs | No active backlogs preferred | Clear them before offer paperwork |
| Coding languages | Java, Python, SQL | Stick to one coding language for OA + interviews |
The minimum CGPA required is 7.0+ CGPA / 70% is the commonly cited campus floor for fresher tech roles. Treat it as a shortlisting filter when printed - Amex still decides on OA correctness and interview narration.
| CGPA Range | Selection chances (rough) | Notes |
|---|---|---|
| Below 7 | Low on many campus lists | May still compete off-campus with exceptional skills |
| 7.0-7.4 | Medium | Eligible on many drives; DSA/SQL must be strong |
| 7.5-8.0 | High | Common shortlisted band with solid projects |
| Above 8 | Very high | Combined with strong technical skills |
Clearing CGPA only gets you into the funnel - coding speed and SQL clarity decide whether you see an interviewer.
Download 2026 American Express placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
American Express does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on Amex Online Assessment: coding correctness + aptitude speed when present |
| Technical | Live coding narration + SQL joins / indexing intuition + project deep dive |
| Product / behavioral | Payments vocabulary + STAR stories for ownership, teamwork, problem-solving |
| HR | Why American Express?, location (Gurugram / Bengaluru / Jaipur), goals, integrity |
| Theme you saw in a set | What to drill next | Why Amex asks it |
|---|---|---|
| Top-K / frequent items | Heap + bucket-sort variants | Ranking, alert priorities, merchant signals |
| Merge intervals | Overlap, insert interval | Settlement windows, promo windows |
| Linked list cycle / two pointers | Floyd, reverse, middle | Classic OA correctness checks |
| Hash map counting | Frequency, prefix sums | Transaction aggregation intuition |
| SQL join + aggregate | Inner/left join, GROUP BY, indexes | Ledger-style follow-ups in tech rounds |
2024 PDFs often drill “merge overlapping delivery slots.” Own the interval template - sort by start, merge when next.start <= cur.end - then drill a related problem with open/closed boundaries. That transfers to interviews; memorising the story text does not.
American Express hires freshers through campus placement cells, the careers portal, referrals, and occasional internship conversion paths. After resume screen, the shape is product-company style: timed OA, then coding + SQL/product interviews, then HR.
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Online applications
Apply on americanexpress.com careers for early-career / fresher tech roles; follow the invite mailer for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
Placement cell or recruiter checks degree, CGPA floor when printed (7.0+ / 70% commonly reported), backlogs, and year of passing. Projects and internships help when volumes are high. This is a gate, not the hard filter - coding is.
Candidate reports describe a timed assessment mixing coding with aptitude / reasoning on many campus drives. Exact section splits vary by drive and year; treat the table as a working map, not a sealed blueprint.
| Section (typical) | What shows up | Time feel | Focus |
|---|---|---|---|
| Aptitude / reasoning | Quant, logic, sometimes verbal | First third of the window | Speed + accuracy |
| Coding | 1-3 problems (easy-medium) | Remaining window | Arrays, strings, hashing, intervals, trees |
| Technical MCQs | When present | Short block | CS basics / light domain |
Languages: Java, Python (SQL for later rounds). Platforms: Confirm yours in the invite - HackerRank-style platforms appear in public write-ups for similar banks/payments drives.
Pass bar in practice: Correct, fully passing solutions beat a brilliant half-answer. Aptitude, when present, punishes slow calculation more than exotic tricks.
Student tip: Spend 3-4 minutes skimming all coding prompts. Bank the solvable one first. Invent two edge cases before submit. Do not burn the clock proving a fancy algorithm if an O(n log n) clear already passes.
| Minute | Move |
|---|---|
| 0-5 | Skim full paper / all coding statements; mark easy wins |
| 5-35 | Aptitude / MCQ block if present - skip sticky puzzles, return later |
| 35-70 | Coding problem(s): restate → brute → optimize → code → sample tests |
| 70-85 | Second coding prompt or harden edge cases on the first |
| 85-90 | Quick revisit of flagged aptitude items; do not open a new hard DSA rabbit hole |
Deeper OA notes and drills: American Express Online Assessment.
Video or onsite shared editor. Expect 1-2 DSA problems, a short project warm-up, and often a SQL or data question. Patterns candidates report: merge intervals, Top-K / heaps, linked-list basics, hashing; SQL joins on transaction-style tables.
You should:
Interviewers care about debugging out loud. Silent staring after a failed mental test case is a common reject signal even when the idea was right.
Example narration shape (Top-K frequent): “Brute force is sort-by-frequency O(n log n). For top-k we can heap in O(n log k) or bucket by frequency.” I’ll use a hash map then a min-heap of size k… Empty input returns empty; ties - I’ll state the rule before coding.” That 40-second plan already signals interview readiness.
Some drives add a second technical or product panel. Treat it as fresher-depth design: actors → APIs → failure modes for a card authorization or fraud-flag flow - not FAANG staff theater.
Why American Express (not “premium brand” only), location preference among Gurugram / Bengaluru / Jaipur, notice period / exams, strengths-weaknesses with proof, conflict and ownership STAR stories. Know the ₹12-22 LPA fresher band so CTC talk is grounded. Ask one real question about the team’s product surface (authorizations, risk, customer servicing tools) - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | Amex Online Assessment | Timed (invite-dependent) | Timed accuracy |
| 2 | Technical (DSA + SQL/projects) | 45-60 min | Code + narration + data comfort |
| 3 | HR / behavioral | 20-40 min | Fit, Leadership behaviors, logistics |
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA completion → shortlist | Few days common | Some batches move faster |
| Interview loop | ~1-2 weeks | Tech → HR (extra tech on some drives) |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~2-6 weeks campus batches often | Off-campus can stretch |
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude / logic | Speed + accuracy | Timed mock quiz |
| Coding Q1-Q2 | Hashing, intervals, heaps, trees | Two timed mediums back-to-back |
| SQL follow-ups | Joins, aggregates, indexes | Explain one ledger query in 3 minutes aloud |
| HR / behaviors | Why Amex, ownership STAR | Two STAR stories + location answer |
American Express still wants correct code, but the flavour is payments + behaviours:
If you are also preparing for Mastercard or Visa, keep DSA shared and customise the product stories per brand.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a American Express invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for American Express sits around ₹12-22 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, SQL. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): American Express eligibility for freshers 2026 is candidate-reported, not one official published cutoff. Common campus/tech baseline: B.E./B.Tech/M.Tech/MCA (often CS, IT, ECE, analytics-related); final-year students and recent graduates; typically 7.0+ CGPA / 70%; no active backlogs preferred. Skills bar: DSA, Java, SQL, product thinking. Always verify the drive notice or careers posting.
What you are training for: American Express fresher loops commonly run: Amex Online Assessment (coding + aptitude mix on many campus drives) → Technical interview(s) covering DSA, Java/SQL, projects → Behavioral/HR on ownership, teamwork, and payments-domain interest. Campus batches often finish in about 2-6 weeks from first filter to offer; off-campus can stretch.
Short version of the prep split: Treat Amex like payments-product hiring. Split time roughly: 45% DSA, 20% Java/SQL + CS fundamentals, 20% timed OA mocks, 15% behavioral/product stories. Clear Amex Online Assessment accuracy first. Languages students usually use: Java, Python, SQL.
Week 1 - pattern, not vibes. 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 - the steep filter. 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 - talk tracks. 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 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a American Express-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the American Express story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed American Express papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many American Express papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in American Express-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed American Express paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why American Express. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For American Express, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three American Express mistakes, you are collecting content, not preparing.
Sit one more mixed American Express set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location (Gurugram, Bengaluru, Jaipur), hiring year, and written components (base / bonus / benefits).
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Fresher / early-career tech | ₹12-22 LPA | Primary band for this hub |
| Some offer write-ups | Toward upper end for certain roles/years | Offer letter wins |
| Mid-level (indicative) | Higher bands | Not the fresher campus default |
Confirm base, joining bonus, and benefits language on the written offer. Do not treat blog midpoints as guarantees.
Policies vary by BU and year. Candidates commonly care about:
Know the ₹12-22 LPA fresher context, ask how the package splits (fixed vs variable), and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor.
Typical fresher path: Amex Online Assessment → Technical (DSA, Java/SQL, projects) → HR / behavioral. Some drives add a second technical or product panel. Campus batches often finish in about 2-6 weeks; off-campus timelines vary. Confirm round names on your invite.
Most fresher tech loops report three major stages (OA + technical + HR). Specialised or larger campus drives may add another technical. Count the mailer, not a random blog.
Yes. Free American Express placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. No registration for the main downloads. Start with the 2026 PDF or the paper archive.
Candidate-reported OA is a timed first filter with coding and often aptitude/reasoning on campus drives. Focus areas: DSA, with Java/SQL comfort expected later. Languages: Java, Python, SQL. Verify platform and duration on your invite.
Commonly reported floor: 7.0+ CGPA / 70%, relevant degree, final-year or recent grads, no active backlogs preferred. American Express does not publish one universal cutoff - your drive notice overrides this page.
Candidate-reported fresher CTC often lands around ₹12-22 LPA (as of August 2026), varying by role and location (Gurugram, Bengaluru, Jaipur). The written offer letter is the only number that matters.
Common India hubs candidates report: Gurugram, Bengaluru, Jaipur. HR usually checks location willingness and joining logistics. Be honest about constraints early.
Split time roughly 45% DSA, 20% Java/SQL + CS, 20% timed OA mocks, 15% behavioral/product. Clear timed OA mocks first. Keep one coding language. Details: preparation guide.
Java, Python, and SQL are the usual set. Confirm on the invite. Do not switch coding languages the week of the drive.
Authorization vs settlement intuition, fraud flags, duplicate charges, transaction APIs, and SQL on ledger-style tables at fresher depth: actors, data, bottlenecks, failure modes in plain language. Practice sketches beat memorised architecture diagrams.
Panels often probe ownership, teamwork, and problem-solving with STAR stories. Tie answers to a real project metric or conflict, not generic “I am a team player” lines. Coding still decides whether you reach that conversation.
All three care about DSA and payments intuition. Amex India loops often emphasise premium-card product context, SQL comfort, and Leadership-behavior storytelling alongside coding. Visa/Mastercard prep still transfers on DSA - customise domain stories per brand.
For campus tech roles, DSA + OA mocks + one strong project + SQL beat certificate stacks. Cloud or domain certs are optional extras after fundamentals. See certifications.
Bank solvable OA problems first, keep a DSA + SQL error log, and rehearse one payments failure-mode explanation out loud before the technical loop. Correctness under time beats a half-finished clever solution.
Start with American Express interview experience on this site, then cross-check recent community write-ups for your target level. Patterns shift by year - use them as maps, not scripts.
Profile patterns that got selected: B.Tech CSE/IT/ECE, roughly 7.2-8.2 CGPA, tier-2 and tier-1 mix, one internship or a strong project, steady DSA practice rather than last-week panic.
Online assessment: Timed coding with aptitude on many campus invites. Clean, fully passing solutions beat partial cleverness. Shortlist mail often arrived in a few days. Students who triaged prompts early kept both coding and aptitude (when present) alive.
Technical rounds: Coding such as merge intervals, Top-K frequent elements, linked-list cycle checks. SQL join + aggregate follow-ups on transaction-style tables. Project deep dive: stack choice, hardest bug, what you would rebuild. Later chat sometimes leaned into auth / fraud at fresher depth - plain explanations worked better than buzzwords.
HR / behavioral: Why Amex? Working with unclear requirements? Location comfort across Gurugram / Bengaluru / Jaipur? Keep answers short: situation → what you did → result.
Takeaway candidates repeated: clear DSA plus coherent SQL and one payments story beats a high CGPA with weak explanation. Talking through the approach before coding mattered as much as the final snippet.
What hurt other candidates in the same cycles: coding before clarifying constraints; treating HR as a formality; payments jargon without a simple failure-mode story; optimising one hard OA item while leaving an easy problem incomplete; freezing when asked “what index would you add?” with zero concrete answer.
Expect a batch PPT, a shared OA window, then stacked interviews within 1-2 weeks. Off-campus can feel quieter between stages - use the waiting week for error-log revision and STAR rehearsal, not for opening five new DSA topics.
Do not open five new DSA topics. Depth on patterns you already know beats breadth panic.
Duplicate charge on a card statement:
That 90-second sketch beats memorising a payments glossary.
More fresher narratives: American Express interview experience.
Mastercard · Visa · Capital One · PayPal · Barclays · JP Morgan