Mastercard runs two visibly different loops. Engineering hiring, concentrated in Pune and on Indian campuses, starts with a timed two-question coding test (or a Karat/HR screening call for laterals) and then a 'Superday' of three or four largely non-eliminatory panels covering DSA, Java/OOP, DBMS, low- and high-level design, a Bar Raiser resume deep-dive and a Hiring Manager conversation, closed out by an HR round that leans heavily on 'why Mastercard' and family/background questions. Consulting and commercial hiring, mostly US, Canada and the UK, is a HireVue or pre-recorded video screen followed by a short superday of back-to-back consulting case interviews, with more arithmetic than a typical MBB case and an unusually weighted behavioral component. Candidates across both tracks consistently report a very slow, opaque decision phase after the final round.
These 31 writeups cover software engineering, data & science, consulting and other roles, India tech + US/Canada consulting. 30 of them were posted under a pseudonym (Reddit, GeeksforGeeks or forum handles), so we could not verify the authors’ identities.
Typical rounds
2.61-6 range
Outcomes shared
16/11offer / not
Most common round
Technical
Sources span
2015 - 2026
Most frequently reported · Behavioral(30), Data structures & algorithms(12), Past projects(12), Arrays & strings(9), DBMS(9)
Mastercard’s official process
Mastercard describes interviews as conversations that combine behavioral questions with problem-solving, with the format varying by role. It names three distinct tracks: a technical interview that uses real-world engineering scenarios rather than textbook algorithms and looks at thought process; a product management interview built around designing or critiquing a product and prioritising user needs against business goals; and a consulting interview using case exercises drawn from real client engagements. It advises candidates to know every line of their resume, prepare an answer for 'Why Mastercard?', and ask questions, and it publishes role-specific guides, practice cases and a candidate attribute rubric. A companion page (careers.mastercard.com/us/en/mastercards-hiring-process) states the published process is only a global guideline and that the real experience differs by location and role. Mastercard also asks candidates to review its AI-usage guidelines before using AI in an application or interview.
Covered · Data structures & algorithms, Arrays & strings
2
Technical interview 1Technical
Introduction, then an anagram-style string problem, followed by textbook questions on polymorphism and transaction ACID properties, and a walkthrough of why the candidate picked their project's tech stack.
Covered · Arrays & strings, OOP, DBMS, Past projects
3
Technical interview 2Technical
Opened with an open-ended design question about how a lift should work, progressively simplified by the interviewer, then a switches-and-bulbs logic puzzle spun into several variants, then project, database and API questions and some background questions off the resume.
Covered · System design, Puzzles, API design, Resume deep-dive
4
HRBehavioral
A short round on motivation for a payments/finance firm specifically, plus role and compensation discussion and questions about family background and positions of responsibility.
Received an offerSalary 24 lakhs, 2.5 lakhs signing/relocation, 1.5 lakhs annual bonus (total ~28)4 rounds
1
Screening (elimination)Phone screen
Two medium-difficulty algorithm problems; this was the only round the recruiter described as eliminatory.
Covered · Data structures & algorithms
2
TechnicalTechnical
A 45-minute round with two more coding problems, both easy-to-medium and string-centric.
Covered · Arrays & strings, Data structures & algorithms
3
Technical + designSystem design
One coding problem followed by resume questions and a mix of low-level and high-level design discussion.
Covered · Low-level design, System design, Resume deep-dive
4
Bar raiserBar raiser
A deep dive into past work, including caching choices such as Redis and the reasoning behind past technical decisions, mixed with behavioral questions.
Covered · Resume deep-dive, Behavioral, Past projects
A casual recruiter call covering current role, tech stack, salary expectations and the Pune job location, plus an explanation of the loop.
Covered · Behavioral
2
Technical screeningTechnical
Asked to explain object orientation in the simplest possible terms, then to model a car system using design principles and patterns, then a short number-theory coding problem.
Covered · OOP, Low-level design, Data structures & algorithms
3
Superday, technical SMETechnical
The four pillars of OOP with examples, a stack-based parenthesis-matching problem with edge cases, a linked list implementation and discussion of current work.
Covered · OOP, Data structures & algorithms, Past projects
4
Superday, bar raiserBar raiser
Two buggy Java snippets to fix, one on file handling and one on a singleton, then a harder string-decoding problem the candidate could not finish in time.
Covered · Debugging, OOP, Data structures & algorithms
5
Superday, hiring managerHiring manager
Which design patterns the candidate knew and an explanation of the builder pattern by analogy, a simplified longest-increasing-subsequence problem, and a discussion of projects, achievements and motivation.
Recruiter call to establish fit and walk through the remaining stages.
Covered · Behavioral
2
Karat technical screenTechnical
An outsourced screening interview combining a design discussion of a file-handling application with two algorithm problems, one array/hashing and one depth-first traversal. Result came back the next day.
Covered · System design, Data structures & algorithms, Graphs
3
Bar raiserBar raiser
One of three panels the recruiter described as non-eliminatory, with the decision made collectively afterwards.
Covered · Behavioral, Resume deep-dive
4
Hiring managerHiring manager
Manager conversation as part of the same non-eliminatory panel set.
Covered · Past projects, Behavioral
5
Technical SMETechnical
Subject-matter-expert technical panel closing out the loop.
Covered · System design, Domain knowledge
6
Additional director roundFinal
After roughly a month of silence and repeated follow-ups, an unplanned extra interview with an engineering director was added before the offer was released.
Two problems, one on matrix row operations and one on substitution-cipher style string encoding. Only 38 candidates advanced, and shortlisting weighted CGPA and submission time as well as score.
Covered · Arrays & strings, Data structures & algorithms
2
Technical interview 1Technical
A long round spanning authentication tokens and hashing/encryption, TLS on a hosted project, paging and scheduling, linked lists and hash collisions, ACID and normal forms, Java-versus-C++ trivia, an optimised sparse-matrix transpose, router/switch basics, and finally how the candidate would scale their project to a thousand concurrent users.
Covered · Past projects, Networking, Operating systems, DBMS, OOP, Scalability
3
Technical interview 2Technical
A shorter round focused on projects, tooling, why the candidate had no internship on the resume, where machine learning could fit into an e-commerce product, and OOP concepts with real-world examples.
Covered · Past projects, OOP, Resume deep-dive
4
HRBehavioral
A short round on something not on the resume, family and hometown, the standard 'why Mastercard', how the candidate handled earlier internship rejections, and their questions about work culture.
A standard online coding screen ahead of the interview day.
Covered · Data structures & algorithms
2
Technical interview 1Technical
The hardest round for this candidate: unit testing and browser automation tooling, CI/CD scripting, Java synchronisation and mutexes, then a two-table schema exercise on relationship type, keys and how to speed up reads in both relational and NoSQL stores, then REST verbs and TLS, a missing-number array problem, and a scenario about distributing questions across people.
Covered · Testing, Concurrency, DBMS, SQL, API design, Data structures & algorithms
3
Technical interview 2Technical
Centred on projects and extracurriculars, with the interviewer taking particular interest in the candidate's unusual project naming, plus one simple second-largest-element problem and a discussion of hackathons.
Covered · Past projects, Data structures & algorithms
4
HRBehavioral
Family background, non-technical achievements and internship history.
Two easy problems, one requiring reading a whole sentence from standard input and checking a character-coverage property, one a simple arithmetic range sum.
Covered · Arrays & strings
2
Technical interview 1Technical
The four OOP pillars with real-life examples, ACID properties, partition tolerance in the CAP trade-off for NoSQL stores, questions on the candidate's web stack, and pseudocode for finding array minimum and maximum.
Covered · OOP, DBMS, Past projects, Data structures & algorithms
3
Technical interview 2Technical
Project- and situation-based: REST fundamentals, use of a mapping API, git basics, when to choose relational over NoSQL, and how the candidate would handle an underperforming teammate.
Covered · API design, DBMS, Conflict handling, Past projects
4
HRBehavioral
Standard motivation questions plus an unusual improvised task: speak for three minutes on any topic of your choice. The candidate was rejected at this stage.
One hour, two string problems (a rotation check and a manual string-to-integer conversion). 40 of 190 candidates advanced.
Covered · Arrays & strings
2
Technical interview 1Technical
Started from the candidate's GitHub and stated interests (including a question distinguishing privacy from security), then Java string internals and the string pool, OOP concepts, and easy-to-medium SQL.
Covered · OOP, DBMS, SQL, Past projects
3
Technical interview 2Technical
Circular and singly linked lists, stack versus heap memory, memory types, and C-versus-C++ language history and differences.
Covered · Data structures & algorithms, Operating systems
4
HRBehavioral
Situational prioritisation questions, who Mastercard's CEO is, and favourite subjects.
Two easy-to-medium problems, one array manipulation and one trickier string problem. 24 candidates advanced.
Covered · Arrays & strings, Data structures & algorithms
2
Technical interview 1Technical
A two-interviewer panel working through each project on the resume and the reasoning behind each tech choice, heavy on front-end framework internals (state, virtual DOM, hooks, component types), then drawing an entity-relationship diagram for a given scenario and basic array/string problems and memory allocation.
Covered · Past projects, DBMS, Data structures & algorithms
3
Technical interview 2 + HRPanel
A combined panel with one engineer and one HR representative: REST integration, every OOP concept with a practical example, normalisation, challenges faced on projects, then motivation questions and extracurriculars.
One hour with an easy string problem heavy on edge cases and one medium greedy problem. 40 of 140 eligible students advanced.
Covered · Arrays & strings, Data structures & algorithms
2
Technical + HR combinedPanel
A single hour-long round that opened with rapport-building, then Java string internals, project discussion, OOP and exception handling, keys and SQL queries, deadlock, a hashing-based array problem, palindrome counting and matrix path dynamic programming, a clock-hands puzzle, multithreading, and closing questions on competitive-programming history and long-term goals.
A 60-minute webcam-proctored test on a third-party platform with one linear dynamic-programming coding question plus multiple-choice questions spanning aptitude, data science and core computer science. The role was restricted to maths-and-computing students, so everyone who sat the test got an interview.
Detailed questioning on the resume's projects, with a clear preference for deep-learning work the candidate could defend in depth. Rounds were run as Zoom breakout rooms with feedback between each.
Covered · Past projects, Domain knowledge
3
Project deep-dive 2Technical
A second pass over the same projects with different interviewers, again probing implementation detail.
Covered · Past projects, Domain knowledge
4
Mathematics and toolingTechnical
The hardest round: physical intuition behind determinants and eigenvectors, the analytic forms of standard probability distributions, Python data-structure distinctions, and familiarity with web frameworks.
Covered · Domain knowledge, Aptitude
5
Head of AI GarageHiring manager
Mostly the interviewer explaining what the AI organisation does, which teams sit under it and what they expect from freshers, closing with which team the candidate wanted and how the role fit their goals.
Covered · Behavioral, Domain knowledge
6
HRBehavioral
General motivation and personal-resilience questions.
Opened from the candidate's stated interests, then a palindrome check with a push to optimise, prior internship work in depth, REST methods, front-end design considerations, basic database theory, questions about college leadership roles, and a closing logic puzzle about mislabelled boxes.
Covered · Arrays & strings, API design, DBMS, Puzzles, Past projects
2
Technical interview 2Technical
Started with a question about Mastercard's main competitor, then C/C++/Python differences, a second-highest-salary SQL query written on paper, normalisation, a tricky string problem, light OOP, and repeat questions about why no return offer from the prior internship.
Family background, motivation behind a specific project, how the candidate became a club chairperson, volunteering work, and whether they intended to leave for a master's degree. 9 of 22 candidates who reached this round got offers.
Two weighted problems, an easy string manipulation and a harder knapsack variant. Roughly 80 students advanced.
Covered · Arrays & strings, Dynamic programming
2
Technical interviewTechnical
Rated easy-to-medium: inheritance and polymorphism, nested SQL queries with grouping and filtering, join types and their relative cost, simple array questions, project and internship detail, and C-versus-C++. Around 30-35 advanced.
Covered · OOP, SQL, DBMS, Data structures & algorithms, Past projects
3
HRBehavioral
Introduction, the toughest decision the candidate had made, why Mastercard, and how they spend free time improving their skills. 10-12 final offers.
Four separate hour-long interviews spread over several weeks, after which the candidate was told they were not selected.
Covered · Behavioral
2
Additional tie-break interviewFinal
A week after the rejection the candidate was recalled for an extra hour because panel feedback had been mixed; feedback on this round was positive, but two weeks later an automated email said the role had been filled.
A single interview day about a week after applying through the university portal, with one interview by a senior director and one by a senior associate. Both cases covered market entry and growth in retail and travel, with noticeably more arithmetic than a standard consulting case, and both included a weighted behavioral segment. Callback came about a week and a half later.
Two cases, one on the profitability of a bicycle manufacturer and one on a food delivery service, alongside a behavioral conversation. The process ran two to three months end to end and included a background check.
A recorded video assessment that was almost entirely behavioral.
Covered · Behavioral
2
SuperdayPanel
Two interviews on the same day, the first on motivation for Mastercard and for business development plus resume questions, the second a more conversational discussion of what skills the role demands.
A single largely behavioral conversation with a recruiter visiting the campus; the interviewer had studied the same non-quantitative subject as the candidate.
A resume-driven conversation about prior experience and the candidate's university, alongside a personality test and background check. The process dragged on for four to five months.
A single virtual round of two interviews. Each opened with fit questions and moved into a profitability case; the second case was structurally the same problem with a different client context.
The firm assigned the candidate an internal buddy to run a practice case with before the real interviews. The scheduling ran efficiently up to the interviews and then stalled afterwards.
Mastercard runs two visibly different loops. Engineering hiring, concentrated in Pune and on Indian campuses, starts with a timed two-question coding test (or a Karat/HR screening call for laterals) and then a 'Superday' of three or four largely non-eliminatory panels covering DSA, Java/OOP, DBMS, low- and high-level design, a Bar Raiser resume deep-dive and a Hiring Manager conversation, closed out by an HR round that leans heavily on 'why Mastercard' and family/background questions. Consulting and commercial hiring, mostly US, Canada and the UK, is a HireVue or pre-recorded video screen followed by a short superday of back-to-back consulting case interviews, with more arithmetic than a typical MBB case and an unusually weighted behavioral component. Candidates across both tracks consistently report a very slow, opaque decision phase after the final round.
What topics does Mastercard test in interviews?
Commonly reported topics include Data structures & algorithms, Arrays & strings, OOP, DBMS, SQL, System design.
These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often; treat this as directional prep, not a script.