HR questions
Frameworks
Mastercard Interview Experiences
Overview
Section titled “Overview”These Mastercard interview notes are rewritten from public student posts and prep-site summaries. Your panel can still look different.
Usual flow: Online assessment / Codility-style coding → Technical rounds → HR/behavioral
Payments domain employer; OA is mostly coding vs bank aptitude papers.
What technical rounds look like
Section titled “What technical rounds look like”DSA, Java/backend, payments basic domain knowledge helpful but not always required for fresher SDE.
What HR rounds look like
Section titled “What HR rounds look like”Behavioral + location.
What students reported
Section titled “What students reported”- The coding round is easier than the reputation suggests, but it is scored on edge cases. A 2022 on-campus write-up describes two genuinely easy problems (check whether a string is a pangram; sum the even numbers between two values). Other reports mention GCD/LCM-style maths, string manipulation, and basic DP. The recurring theme across accounts is that the logic is rarely the hard part - partial scores come from empty inputs, duplicates, and boundary values, so spend the last few minutes on edge cases rather than a second optimisation pass.
- Technical rounds move across topics quickly rather than digging into one. One candidate’s first technical round covered OOP principles, ACID properties, NoSQL partitioning, the tech choices in their project, and pseudocode for finding an array’s min and max - all in a single sitting. The second round shifted to REST APIs, how they’d integrate a third-party API (Google Maps was the example), version-control basics, a team-conflict scenario, and a “why did you pick that database” justification. Breadth beats depth here.
- The HR round is not a formality, and it can be the round you lose on. The same candidate was asked to speak for three minutes on any topic of their choosing - political, technical, anything - and described their brain freezing. They cleared the technical rounds and still were not among the ~15 selected from campus. Rehearse a couple of impromptu-speaking topics; it’s a real evaluated slot.
- Prep advice that repeats across write-ups: know DBMS properly (SQL queries and normalization, not just definitions), be solid on core Java including OOPs and exception handling, and expect at least one puzzle. Reported puzzles are classic-style rather than payments-specific - one account describes arranging numbers around a circle so the sums along each diameter match.
Sources
Section titled “Sources”- Mastercard Interview Experience for Software Development (On-Campus) 2022 (gfg)
- Mastercard Interview Experience for Software Development, NIT Surat (gfg)
- Mastercard Interview Experience | Software Engineer | Full Time (On-campus) (gfg)
- Mastercard Interview Experience for SDE Intern (On-Campus) (gfg)
- Mastercard Software Engineer interview questions (glassdoor)
- Mastercard careers (other)
These notes come from public reports and can differ by campus, year, and role. If your college placement email or the official careers/notification PDF says something different, follow that.
Related
Section titled “Related”HR interview
Section titled “HR interview”After technical rounds, Mastercard usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.
Similar companies
Section titled “Similar companies”Visa · PayPal · American Express · PhonePe · Stripe