Academic snapshot
Floor: Often 7.0 / 70%
Degrees: B.E./B.Tech/M.Tech/MCA
Backlogs: None active
Year: Final year / Launch batch
Mastercard Placement Papers 2026
Mastercard operates a global payments network connecting issuers, acquirers, merchants, and cardholders for secure transactions worldwide. Its technology teams build payment processing, cybersecurity, and data analytics products, with India centers hiring for software engineering and platform roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Mastercard fresher eligibility for campus drives
Mastercard does not publish one universal CGPA cutoff for every India SDE / Launch drive. Campus JDs and careers posts differ. Treat numbers below as candidate-reported (as of August 2026).
Who this hub is for
- For: Students targeting Software Development Engineer I / SDE intern / Launch roles on Mastercard payments and platform teams - mostly Pune, also Vadodara and Bengaluru.
- Not the same track: Assuming “Mastercard = bank PO aptitude paper.” This hub is engineering. Store or ops roles are a different path.
- Experienced hires: Deeper Java/Spring, payments domain, cyber. Use fresher sections as a base.
Campus SDE vs launch vs intern
Campus SDE is a batch event: one OA window, then stacked interviews. Launch off-campus posts (early-career / ~18-month journeys in some write-ups) can add SHL-style assessments and different city lists (Pune, Vadodara, Gurgaon). SDE intern campus drives target pre-final years and may merge the last technical with HR - one GFG intern select got a same-evening message and 7 intern offers from the pool.
If you are 2025-2026 batch applying off-campus, still treat timed coding as the exam unless the invite says SHL. A Pune hybrid JD does not mean you can stay in another city forever. Lead/HR interviewers ask about joining logistics because payments on-call is real.
NCG vs 0-2 YOE: some listings welcome freshers and early career. The loop still starts with coding. Do not assume a year of internship skips DSA. It may only change the resume conversation in Technical 2.
Pune as the default India story: a large share of SDE-1 chatter is Pune (sometimes cited near ₹18.5 LPA). Vadodara shows up on Launch/ops-adjacent tech lists; Bengaluru on some platform teams. If you will only join Bengaluru and the letter says Pune, say that in HR - better than accepting and freezing. Hybrid language on a JD still usually means you have a desk in that city. Payments on-call is not a fully remote fresher default.
Launch vs campus in one paragraph: campus is a hall, a Codility-style OA, a same-week loop. Launch is an early-career program story in off-campus posts - sometimes SHL, sometimes an 18-month framing, sometimes Gurgaon in the city list. Same company values (ownership, payments curiosity). Different mailer. Do not copy a GFG campus SDE transcript onto a Launch SHL invite and call it prep.
Degree, projects, and “is 7.0 enough?”
Yes - 7.0 / 70% meets the commonly reported floor. It is not a selection guarantee. A 7.1 with two fully passing OA solutions beats an 8.8 who freezes on SQL joins.
Projects that help: any API with auth, a small payments/wallet demo, Spring Boot services, a SQL-backed order system. Unique project naming and story helped one GFG on-campus select even when they felt weak in Java - uniqueness does not replace OA coding. A certificate pile with zero “what I built” talk dies in Technical 2.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus SDE / intern | Batch OA (Codility-style), reserved seats | DSA bar |
| Launch / careers | Resume volume; possible SHL | Still expect coding or assessments |
| Referral | Visibility | Interviews stay hard |
Off-campus does not mean easier DSA. It often means more applicants on the same filter.
Documents and portal hygiene
- Keep CGPA consistent with the form.
- Screenshot invite: Codility vs HackerRank vs SHL and duration.
- If you listed Java/Spring/REST/SQL, you will be asked - one 2024 campus Tech 1 went to JUnit, Selenium, TLS, and Book/Author schema.
- Pune / Vadodara relocation is common; be ready.
- Clear active backlogs before offer paperwork.
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ / ~70% | Campus cells may pre-filter |
| Degree | B.E./B.Tech/M.Tech/MCA | Related computing |
| Branch | CS, IT, ECE (and related) | Strong DSA can help adjacent |
| Year | Final year + recent grads | Intern = pre-final |
| Backlogs | No active backlogs | Hard filter on many JDs |
| Languages | Java, Python, C++ | Java/Spring common in Pune |
| Location | Pune / Vadodara / Bengaluru | Hybrid on some posts |
Skills & focus
Primary: Medium DSA
Secondary: Java + SQL + payments vocab
First filter: Timed coding OA
Differentiator: Reliability / four-party talk
Selection feel by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| Below 7.0 | Often filtered on-campus | Off-campus only if JD allows |
| 7.0-7.4 | Meets many listed floors | Need strong OA + resume depth |
| 7.5-8.5 | Common shortlisted chatter | OA still decides |
| 8.5+ | Strong academically | Tech 1 still tests Java/SQL |
Mastercard previous year paper PDFs
Download 2026 Mastercard placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What these papers train for the written and SQL rounds
Mastercard does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers - not leaked live Codility tests.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed DSA accuracy (2 problems / 45-60 min style) |
| Technical 1 | Projects + Java/SQL + light DSA |
| Technical 2 | Deeper resume, second DSA, hackathons |
| HR | Why Mastercard, family/intern, location |
Themes that keep repeating (2024-2026)
- 2024 campus SDE (GFG, selected): OA then 2 technicals + HR. Tech 1 was hard for that candidate: Java (they admitted weakness), JUnit, Selenium, CI/CD, mutexes, Book/Author many-to-many + indexing vs sharding, REST GET/POST, TLS, a missing-element DSA, a scenario assigning questions to people. Tech 2: projects (Hindi/Sanskrit names helped curiosity), second-largest element, hackathons. HR: family, non-tech, internships. Verdict: selected despite feeling underprepared in Java - they credit project uniqueness; do not treat that as permission to skip Java.
- SDE intern campus (GFG): Coding round → Tech 1 → Tech 2 → HR (last combined technical+HR). Same-evening select; 7 interns. Challenges on projects + Why Mastercard.
- 2025-2026 prep expectation: Keep two-problem OA stamina. Add Java/SQL and payments reliability (double charge, four-party model at fresher depth). Launch posts may add SHL - do not assume every 2026 invite is Codility. Treat PDFs as pattern catalogs.
How to use one paper set in a single sitting
- Timed: 45-60 minutes, 2 prompts (or SHL if that matches your invite).
- Untimed review: rewrite the cleaner solution; list three payment-flavoured edges (empty, duplicate id, timeout).
- Map each miss to a theme and pull cousins from coding questions.
- 15 minutes: explain idempotent pay or a SQL join out loud.
- Log one STAR story (load, production bug, unclear requirements).
Related problems to practice
| Theme you saw | What to drill next | Why Mastercard asks it |
|---|---|---|
| First unique character | Hash + second pass | OA strings |
| Stack with min | Aux stack | OA design |
| Kadane | Running max | OA arrays |
| Missing number | XOR or sum | Reported Tech 1 |
| Second largest | One pass | Reported Tech 2 |
| SQL Book/Author | Many-to-many + index | Reported Tech 1 |
2025 sets often drill “first unique character.” Own the count-then-scan template, then drill a related problem. That transfers; memorising Q1 text does not.
Free practice packs. Full archive: previous year question papers.
Mastercard hiring rounds in 2026
Mastercard hires NCGs through campus cells, careers.mastercard.com, and referrals. After resume screen, the shape is payments-tech: timed OA, two technicals, HR.
Application methods
Campus recruitment
Eligibility list → Codility/OA → 2 technical + HR. GFG SDE and intern selects used this ladder.
Online applications
careers.mastercard.com for SDE-1 / Launch. Follow the invite for Codility vs SHL.
Referrals
Better resume visibility. You still need passing OA code.
1. Resume / eligibility screen
7.0+ / 70%, no active backlogs, CS-related degree. Java/SQL projects help. This is a gate - OA is the filter. A referral does not skip Codility when the campus uses it.
PPT is still worth attending. Teams mention network reliability, Pune hubs, cyber/analytics. Skipping it is how people walk into HR with “famous card brand” and zero four-party sentence.
2. Online Assessment
Community reports describe:
| Item | Reported detail |
|---|---|
| Platform | Codility or similar (candidate-reported) |
| Shape | Often 2 coding problems |
| Duration | Commonly 45-60 min (confirm invite) |
| Languages | Java, Python, C++ typically |
| Launch variant | SHL-style assessments in some posts |
Pass bar: Two solid full passes beat one perfect and one blank. Codility-style graders are test-case hungry - edges matter.
Student tip: Skim both in 3 minutes. Bank the easier. Leave 15 minutes for tests on the harder. Do not die on an unstated third idea.
Codility-style graders: hidden tests love empty strings, single-element arrays, already-unique characters, and overflow-adjacent sums. A solution that “works on the sample” and fails 40% of cases is a reject. Write two extra tests before you leave the editor. If the platform shows a performance report, O(n²) on n=10⁵ is why you thought you solved it. Hash maps and one-pass scans are the usual Mastercard OA flavour - not a 45-minute DP research problem.
If the invite is SHL (Launch): expect timed cognitive/behavioural plus or instead of two DSA. Mock that shape. Bringing only Codility habits into an SHL window is the same class of mistake as bringing LTFS papers to LTTS.
Deeper notes: Mastercard Online Assessment.
Related problems to practice
- First unique character → count + second pass.
- Min stack → parallel min stack.
- Kadane → running sum reset.
- In-place reverse → two pointers.
3. Technical 1 (~50-60 min)
Projects, DBMS/SQL, DSA, Java (even if you are “not a Java person” - one select still got JUnit, sync, TLS). This round is often the hardest. Warm syntax and one join query before the call.
Worked mini-outline - payment retry / double charge:
- Client times out after pay succeeds → retry with the same idempotency key.
- Server stores key → outcome; second call returns the first result.
- Without this, you debit twice. Say that before drawing boxes.
Java honesty vs Java homework: the 2024 GFG select admitted they were not strong in Java and still got JUnit, Selenium, mutexes, and TLS. They were selected and credited projects. That is a lucky path, not a plan. If your resume says Java, spend a weekend on collections, synchronized, and one JUnit test you can describe. If your resume does not say Java, expect the panel to still probe OOPs in your language - and maybe still ask Java trivia. Saying “I have not used JUnit” is better than inventing annotations.
SQL that actually appears: many-to-many (Book ↔ Author) needs a join table; primary vs foreign keys; “how do I make this faster?” → index on the lookup column, not “use NoSQL” as a reflex. Sharding/partitioning is a bonus sentence if you have a reason (write volume, not because a blog said so). Write one JOIN and one GROUP BY from memory the night before.
4. Technical 2 (~30-45 min)
Projects, extracurriculars, a lighter DSA (second largest), hackathons. Friendlier in some write-ups - still scored. Know every project name and why it exists.
5. HR (~20-30 min)
Family, internships, Why Mastercard, location (Pune/Vadodara), communication. Intern loops may merge this with technical. Same-evening results happen on campus.
| # | Round | Duration (typical) | What they check |
|---|---|---|---|
| 1 | OA | 45-60 min / 2 DSA | Timed correctness |
| 2 | Technical 1 | 50-60 min | Java, SQL, DSA, projects |
| 3 | Technical 2 | 30-45 min | Resume depth |
| 4 | HR | 20-30 min | Fit, city |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT with or after OA |
| OA → interviews | Days to a week | ~38 cleared OA in one PrepInsta campus note |
| Interview loop | 1 day campus | 2 tech + HR |
| Offer | Same evening to days | Intern GFG: 9 PM message |
| End to end | ~1-3 weeks campus | Launch off-campus longer |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| 2-Q stamina | Full AC + tests | One 50-min mock |
| Strings / arrays | Easy bank | Two timed easies |
| Hashing / stacks | Medium | One each |
| Java / SQL | Tech 1 | One join + OOPs card |
| Why Mastercard | Network reliability | 90-second story |
Mastercard aptitude, coding & interview practice
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.
A practical Mastercard prep plan
If a Mastercard 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 Mastercard sits around ₹14-25 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Mastercard eligibility for SDE / Launch freshers is candidate-reported: often 7.0+ CGPA or 70%, B.E./B.Tech/M.Tech/MCA in CS, IT or related, final-year students and recent graduates (2025-2026 batches on many posts), no active backlogs. Always verify the campus JD or careers.mastercard.com posting. DSA plus Java/backend and payments curiosity matter after the academic gate.
What you are training for: Campus SDE loops commonly run: Online Assessment / Codility-style coding (often 2 DSA in ~45-60 min) → Technical 1 (~50-60 min: projects, SQL, DSA, Java) → Technical 2 (projects, lighter DSA) → HR. Some intern drives merge last technical with HR. Timeline is often 1-3 weeks for campus. Off-campus Launch can add SHL-style assessments - trust the invite.
Short version of the prep split: Split time roughly: 45% DSA (arrays, strings, hashing, stacks - Codility accuracy), 20% Java + SQL/DBMS, 15% timed OA mocks, 10% payments vocabulary (four-party model at fresher depth), 10% HR/STAR. Languages: Java, Python, C++ - Java/Spring shows up in Pune interviews.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Mastercard 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 Mastercard 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 Mastercard 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 Mastercard?” 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.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Mastercard-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.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Mastercard story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Mastercard PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Mastercard papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Mastercard papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Mastercard-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Mastercard 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 Mastercard. 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.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Mastercard, 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.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Mastercard mistakes, you are collecting content, not preparing.
Mastercard compensation & benefits
Figures are candidate-reported (as of August 2026). Level, Pune vs Vadodara vs Bengaluru, and written split move the number.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| SDE-1 / fresher | ₹14-25 LPA | Primary band for this hub |
| Pune SDE-1 chatter | ~₹18.5 LPA cited | Offer letter wins |
| Some L9 / market notes | ~₹15-23 LPA | Role dependent |
Confirm base, joining bonus, and any equity on the written offer.
Benefits students actually care about
- Health insurance
- Hybrid norms for Pune
- Relocation support - ask
- Learning / Launch-style programs
- On-call expectations for payments teams
How to talk CTC in HR
Know ₹14-25 LPA, ask fixed vs variable, and clarify joining vs exams. Do not negotiate from a blog screenshot.
Recent Mastercard placement trends
- Codility-style 2 DSA remains the campus rumour default - not a guarantee; Launch may use SHL.
- Java + SQL resume depth can fill a full hour.
- Pune / Vadodara joining stays a real HR filter.
- Treat ₹14-25 LPA (and ~₹18.5 Pune chatter) as reported bands, not promises.
- Intern campus loops can return same-evening results.
- Payments vocabulary (idempotency, four-party) shows up more than generic e-commerce talk.
FAQs students ask about Mastercard placements
Process & papers
What is the Mastercard placement process for freshers?
Typical SDE path: OA → 2 technical interviews → HR. Campus often 1-3 weeks. Intern drives may merge the last round. Launch off-campus can add SHL.
How many interview rounds does Mastercard usually have?
Most freshers report 4 stages counting OA. Some merge HR. Count the mailer.
Can I download Mastercard placement papers PDF for free?
Yes. 2024-2026 style practice is on this site. Start with the 2026 PDF or the archive.
What does the Mastercard OA look like?
Community reports: Codility-style, often 2 DSA in 45-60 minutes. Languages usually Java, Python, C++. Launch may differ. Trust your invite.
Eligibility & offer
What eligibility / CGPA do SDE drives usually expect?
Commonly 7.0+ CGPA / 70%, CS-related degree, no active backlogs. Mastercard does not publish one universal cutoff.
What is Mastercard fresher salary in India?
Candidate-reported SDE-1 CTC often ₹14-25 LPA (as of August 2026); Pune chatter ~₹18.5 LPA. Written offer wins.
Do I have to relocate to Pune?
Often yes for India SWE. Vadodara and Bengaluru also appear. HR will ask. Be honest.
Prep & Mastercard-specific
How should I prepare?
45% DSA, 20% Java/SQL, 15% OA mocks, 10% payments, 10% HR. Details: preparation guide.
Which programming languages are allowed?
Java, Python, C++ typically. Java/Spring is common in Pune interviews. Do not switch the week of the drive.
What is Mastercard Launch?
An early-career / new-grad style path in some off-campus posts. Not identical to every campus SDE drive. Read the JD for assessments and city.
Mastercard vs Visa vs PhonePe?
Visa/Mastercard: global network reliability. PhonePe: India UPI product speed. All want DSA. Compare written offers and the team’s surface area.
Any pro tip that actually changes outcomes?
Two fully passing OA problems first. Know every resume keyword. One double-charge story. Do not fake Java.
Where can I read real interview experiences?
Mastercard interview experience and GFG on-campus SDE/intern write-ups. Maps, not scripts.
Is Mastercard OA always Codility with 2 questions?
No. That is the community-reported campus flavour. Launch/off-campus may use SHL or another vendor. Screenshot your invite.
Mastercard - recent candidate experiences
On-campus SDE (gfg, nov 2024, selected)
Process: Online test → 2 technical → HR. Tech 1: felt like one of their hardest interviews - intro; Java despite admitting weakness (JUnit, Selenium, CI/CD, mutexes); Book/Author many-to-many, PK/FK, SQL indexing vs NoSQL sharding; REST GET/POST; TLS; missing element in [1,2,3,5]; scenario assigning 10 questions to 3 people. Tech 2: projects (Hindi/Sanskrit names drew interest), second-largest element, hackathons. HR: family, non-tech, internships. Verdict: selected. Their reflection: underprepared in Java; uniqueness of projects likely helped. Junior takeaway: still learn Java/SQL; do not rely on a cute project name.
On-campus SDE intern
Process: Coding → Tech 1 → Tech 2 → combined technical+HR. Project challenges, Why Mastercard, behavioural. Verdict: selected same evening ~9 PM; 7 interns from the pool. Takeaway: campus intern loops can be fast; keep HR answers ready the same day as OA.
Launch / Pune SDE-1 colour
Prep-community notes list SDE-1, Pune, ~₹18.5 LPA, Java/DSA/DBMS/Spring/REST, process OA → Tech 1 → Tech 2 → HR. Off-campus Launch write-ups add 70% academics, 2024-2026 batches, and SHL mentions. Treat those as colour, not your mailer.
What hurt other candidates: starting the harder OA first; resume Java they could not explain; Why Mastercard with zero network sentence; no Pune plan; fake internships.
More notes: Mastercard interview experience.
Sample technical follow-ups you should rehearse
- Auth vs authorization in a payment-app example.
- Idempotency key on
POST /pay. - SQL: Book/Author many-to-many; index vs full scan.
- Java: synchronized vs concurrent collections in one sentence.
- TLS - what it protects at fresher depth.
- Missing number; second largest - both in one pass.
- Four-party model in 30 seconds.
Answer out loud. The 60-minute technical was mostly resume + these families.
Offer-stage discipline
If you clear HR:
- Read Pune/Vadodara hybrid and joining vs exams
- Confirm base / bonus on the written letter
- Do not resign until that letter lands
- Background verification expects consistent CGPA
Payments companies still run batch HR. Keep the thread.
One more mock template (50 minutes / 2 problems)
| Minute | Action |
|---|---|
| 0-3 | Read both; order easy → hard |
| 3-22 | Problem 1 full AC |
| 22-42 | Problem 2 |
| 42-50 | Edges + leftover tests |
Run this on a weekend, then write one SQL join from a blank page the same evening.
Why “famous card brand” fails
A better 40-second Why Mastercard: you want to work on network reliability - a charge that must not happen twice, an issuer/acquirer route that must not drop, a Java service with tests - and you have practised those failure modes. If you only know the logo on a card, you are not ready for Technical 1.
Week-of-drive checklist
- Screenshot OA vendor (Codility vs SHL) and language list.
- Two timed DSA problems with extra tests; one SQL join from blank.
- Recite four-party model and idempotent
POST /pay. - 60-second answers for every Java/REST keyword on the resume.
- Pune / Vadodara / Bengaluru yes or no - pick before HR.
- Sleep. Same-evening intern results happen; keep HR answers ready the day of OA.
Related companies to compare
Visa · PayPal · American Express · PhonePe · Stripe