How Mastercard Interviews in 2026: Process, Questions & What They Score

• Given two strings, determine whether they are anagrams of each other.Tests character frequency counting or sort and compare on two strings, and whether you state the hash map versus sorting tradeoff.
• Compare quicksort and merge sort, and give the time complexity of the common searching and sorting algorithms.Tests Big O recall for common sorts and searches plus stability, extra memory and worst case tradeoffs between the two sorts.
• Write a program to compute the GCD and LCM of a set of numbers.Tests the Euclidean algorithm, the GCD times LCM identity, and folding both across a list without overflow.
• Solve a basic dynamic programming problem in a timed online assessment.Tests spotting overlapping subproblems and writing a memoised or tabulated recurrence under a clock.
• Solve a string manipulation and implementation problem under time pressure in the online round.Tests index handling and edge cases in string parsing, the most repeated online assessment theme across campus reports.
• Explain memory allocation on the stack versus the heap.Tests the memory model: lifetime, allocation cost, size limits and which values live on the stack versus the heap.
• Explain polymorphism with an example.Tests OOP fundamentals, compile time versus runtime polymorphism, with a concrete overriding example from your own code.
• Here is a straightforward technical problem. Now that you have solved it, here is an added constraint. How does your approach change?Tests adapting a working solution as constraints are added, the question format both official engineering kits describe.
• There are two bulbs inside a room and two switches outside it. You may enter the room only once. Identify which switch controls which bulb.Tests deductive reasoning with a hidden state trick, using bulb heat as a second observable channel beyond on or off.
• Arrange numbers on the circumference of a circle and at its centre so that the sum along every diameter is the same.Tests arithmetic pattern reasoning, pairing numbers across the centre so opposite pairs sum to the same total.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

• Design a data model for the Washington, D.C. metro system.Tests entity relationship modelling: stations, lines, journeys, cards and swipes, with assumptions stated before drawing.
• Here is a dataset. What potential problems can you identify with it?Tests data quality inspection: nulls, duplicates, type mismatches, key integrity and inconsistent granularity in a dataset.
• Looking at this sales dataset: what is the date range, which month has the highest and lowest average sales, and how do sales vary across time?Tests translating questions into aggregation plans in plain English, min and max dates and group by month averages.
• What summary statistics would you pull from this data, and what metrics would stakeholders be interested in?Tests choosing summary statistics and stakeholder metrics that describe a dataset without writing any SQL yourself.
• Explain the ACID properties.Tests transaction fundamentals, atomicity, consistency, isolation and durability, with an example of each guarantee.
• Explain database normalization, and draw an ER diagram for the scenario I describe.Tests relational design: normal forms to remove redundancy and drawing entities, attributes and relationships for a scenario.
• What is a cardinality ratio, and how would you design the database for this situation?Tests relationship cardinality (one to one, one to many, many to many) and turning a described situation into a schema.
• Imagine the team is building weather.com. How would you test the website?Tests test planning on an open scope: narrowing scope, clarifying questions, stating assumptions and splitting by component.
• We have a function that takes the hour and minute as two separate inputs and outputs the angle between the hour and minute hand. How would you test it?Tests test case design from a spec: normal, edge and invalid inputs, plus clarifying 12 versus 24 hour and smallest angle.
• Design a real-time transaction history viewer, and discuss how you would handle batch processing for millions of transactions.Tests system design for a read heavy transaction feed and batch processing at scale, a single source coaching claim.
• How would you approach migrating a monolith to microservices?Tests service decomposition strategy: bounded contexts, strangler pattern, data ownership and incremental migration.
• How would you secure a payments flow? Talk me through OAuth 2.0, tokenization and encryption in that context.Tests payments security concepts: OAuth 2.0 flows, tokenization of card data and encryption at rest and in transit.
• Walk me through how your project integrated REST APIs, and the operations you exposed.Tests explaining your own API design: resources, HTTP verbs, operations exposed and how the client integrated them.
• How does a lift work? Design it, simplified to a single user.Tests object oriented and state machine design for a lift, simplified to a single user before adding scheduling.
• In React, explain state versus props, the virtual DOM versus the real DOM, and class versus functional components.Tests React fundamentals tied to the candidate's own project stack: state versus props, virtual DOM and component types.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

• What is an example of when you have had to face a difficult challenge or solve a tough problem? How did you solve this and what did you learn along the way?
• Think about a time when you have had an important idea you wanted to share and communicate. How did you get your message across to your audience?
• Think about some of the relationships you have with fellow students, mentors, professors or colleagues. What do you do to make those relationships work? What makes them challenging?
• What is an example that illustrates the roles you have played within a team?
• Think about a time when you took ownership or maintained a positive attitude during a difficult time.
• Tell me about a time when you communicated a technical problem to a more general audience.
• What were some of the best projects you have worked on, and what could you have done better?
• How often do you seek feedback?
• What challenges have you faced, and what did you learn from them?
• What do you look for in a manager?
• How would you handle a disagreement with a product, sales or engineering partner?
• How do you prioritize when three stakeholders want different outcomes?
• Walk me through a project where you improved a process or a metric.
• Tell me about a time you had to influence a difficult stakeholder.
• How do you manage dependencies across different teams?
• What would you do if a launch caused a drop in conversion or authorization?

• Why Mastercard?
• Walk me through your resume. Tell me about this specific line item and what you took away from it.
• Why are you interested in this role? What aspects of Mastercard Data and Services appeal to you compared to other companies you have researched, whether culture, mission or project format?
• What excites you about software, and what excites you about this role in particular?
• What questions do you have for us?

• How much does a Washington, DC Uber driver make in a day?
• How many transactions does Walmart record in a single day?
• You are the CEO of MakeItHappen consulting. Starbucks is replacing in-store queuing with iPads for mobile ordering and will outsource the implementation. You intend to bid. How much would you bid?
• Walk me through the steps to design a product that does X.
• What would you change about your favorite website for Y?
• How would you design a bookcase for children?

Mastercard's process has 8 stages, in order: Application through careers.mastercard.com, Introductory conversation with a recruiter, Online assessment or coding test (role dependent), Interview with the hiring manager, Interviews with team members, Final selection decision, Offer, Background check and start date.

Mastercard evaluates candidates against Key skills and attributes Mastercard looks for in every successful candidate: You are naturally curious and always learning, You build strong relationships and collaborate with intention, You adapt quickly when priorities shift, You always do the right thing, even when no one is watching, You think critically and bring structure to complexity, You have a growth mindset.

Mastercard's question bank spans 5 categories: Coding and algorithms; Systems, data and design; Behavioral and values; Motivation and fit; Case and estimation.

This playbook is medium confidence, compiled from 23 public sources, and last verified September 5, 2026. It describes one well-documented shape of Mastercard's interviews, not a guarantee of what any individual loop will look like.