Mastercard India SDE: 2022 Four-Round HR Rejection

The 4-round on-campus process: what actually happened

This account comes from a GeeksforGeeks interview experience titled "Mastercard Interview Experience for software development (On-Campus) 2022", posted by a candidate who sat through the full process at their college. The source identifies an on-campus software-development drive but does not establish the hiring team, office location, current role title, or process outside that cohort.

The candidate described a structured 4-round process. Round 1 was an online coding test with two DSA problems at easy difficulty. Round 2 was the first technical interview, focused on OOP concepts, DBMS fundamentals, a project walkthrough, and a live pseudocode task. Round 3 was a second technical interview covering REST API design, the Google Maps API, version control, and team-management scenarios. Round 4 was the HR round.

The candidate cleared the coding round and both technical interviews but was rejected after HR. They reported that fifteen students from the college received offers in the same drive. That sequence proves HR affected this candidate's outcome, but it does not reveal the reason for rejection. No CGPA cutoff, package figure, or offer timeline was disclosed.

This is one candidate's reported experience from one campus drive. It does not establish another batch, campus, or year's rounds, difficulty, or outcomes. Check the current role notice and Mastercard's official careers page.

Round-by-round breakdown and what each round tested

Here is the round structure as reported, with the topics and tasks the candidate faced.

Round 1: Coding test, easy-level DSA

The coding round had two problems. The first was a pangram check, which asks whether a string contains every letter of the English alphabet. The second was summing even numbers between two bounds. The candidate described both as easy. The source does not say how Mastercard scored the test, whether partial credit applied, or how the result was used in ranking.

For a pangram solution, first clarify whether matching is case-insensitive and whether non-letter characters should be ignored. Normalise only as the prompt permits, track each required alphabet character, and return success after every required character has appeared. State the time cost in terms of the input length and test empty input, repeated letters, mixed case, punctuation, and a string missing one character. For the even-number task, clarify whether both bounds are inclusive, handle reversed or negative bounds according to the contract, and avoid iterating over every value if the prompt expects a direct arithmetic derivation. These are solution checks derived from the reported tasks, not extra Mastercard questions.

Round 2: Technical Interview 1, fundamentals and project depth

The first technical interview opened with OOP concepts, but the account does not enumerate the individual OOP questions. It then names DBMS, ACID properties, and partition tolerance. The candidate also walked through a project stack that included React, JavaScript, Node, Firebase, and GCP. The live pseudocode task was to find the minimum and maximum of an array. The source does not publish the panel's scoring rubric for any of these topics.

Round 3: Technical Interview 2, applied design and reasoning

The second technical interview shifted from fundamentals to applied design. The account names REST API design, a discussion of Google Maps API usage in the candidate's project, version-control basics, team-management scenarios, and the rationale for a database choice. Prepare the relevant decisions and trade-offs, but do not infer an unpublished evaluation rule from that topic list.

Round 4: HR, the round that rejected this candidate

The HR round covered personal background, motivation for joining Mastercard, and college extracurriculars. The distinctive element was a spontaneous three-minute speaking exercise on an interviewer-chosen topic. The source records the rejection after this round but does not identify the failed answer or evaluation criterion, so the cause must remain unknown.

How to prepare for Mastercard India's software development interview in 2026

DSA and coding round

Start with strings, arrays, basic number reasoning, and hash-map problems. The reported coding round used a pangram check and an even-number sum, but a current assessment may differ. Practise writing complete solutions, defining edge cases, and testing bounds rather than chasing an arbitrary solved-problem count.

Technical fundamentals

Review the concepts this account actually names. For OOP, prepare accurate examples from code you have written. For DBMS, explain the ACID properties and distinguish database-level guarantees from distributed-system trade-offs. The source also names partition tolerance, but it does not report normalisation questions or a fixed follow-up sequence.

Project walkthrough

For every project on your resume, prepare a concise summary, a tech-stack rationale, the hardest bug you fixed, and what you would improve. If you list React, Node, Firebase, or GCP, be ready to explain why you chose each over alternatives. This account supports project-stack questioning for its candidate, not a guaranteed script for every panel.

HR and communication

The source does not reveal why the candidate was rejected, so do not diagnose the failure. Prepare a clear, honest answer for "Why Mastercard?" using current information from the role description and Mastercard's own pages. For the reported speaking exercise, practise giving a timed response with a clear opening, supported points, and a close.

Common mistakes and red flags

• Treating HR as a formality. This candidate cleared three technical rounds and was rejected at HR. Prepare for it like any other round.
• Listing technologies you cannot defend. If your resume names Firebase, GCP, or another service, prepare the decision and trade-offs you can support from your own project.
• Skipping a reported concept. Partition tolerance appeared in Round 2. Review what the term means and where it applies without adding unreported questions to this account.
• Unstructured speaking. The source reports a three-minute spontaneous speaking exercise but does not say how it was scored. Practise delivering a point with a beginning, middle, and end.
• Unsupported motivation claims. Build a truthful answer from the current role description and Mastercard's own pages instead of repeating generic culture claims.
• Assuming the 2022 pattern is the 2026 pattern. Rounds, difficulty, and topics change. Use this as a baseline, not a guarantee.

Real-world data points

• 4 rounds total, as reported in the GeeksforGeeks account (on-campus, 2022 drive).
• 2 DSA problems in the coding round, both easy difficulty (pangram check, sum of even numbers between bounds).
• 15 students from the candidate's college received offers in the same drive, per the candidate's report.
• 1 candidate (the author of the account) was rejected at the HR stage after clearing all three technical/coding rounds.
• 3-minute spontaneous speaking exercise in the HR round, topic chosen by the interviewer.
• 0 package figures or CGPA cutoffs disclosed in the source post.
• Project stack mentioned in Round 2: React, JavaScript, Node, Firebase, GCP.
• Source account is from 2022; verify the 2026 cycle on Mastercard's official India careers page.

Sources & credits

• https://www.geeksforgeeks.org/interview-experiences/mastercard-interview-experience-for-software-development-on-campus-2022/