Mastercard HackerRank Online Assessment: 2-3 Problems, 45-90 Min

Mastercard HackerRank online assessment: the reported 2-3 coding problems in 45-90 minutes, proctoring settings, Mastercard's AI rules and a 3-day prep plan.

By OphyAI Team • • Updated October 22, 2026 • 1217 words

Last updated: October 2026

Quick Answer

The Mastercard HackerRank online assessment is the coding screen many software engineering candidates take before the technical and behavioral rounds: candidates most often report two or three LeetCode easy-to-medium problems in about 45-90 minutes, sometimes with a short block of multiple-choice questions. Some regions use Codility instead. Practice timed problems in OphyAI Coding Interview and mock rounds in OphyAI Interview Practice; Mastercard asks candidates not to use AI during the real assessment unless invited.

PartWhat candidates report
PlatformHackerRank in most reports; Codility in some regions
Problems2-3, easy to medium, sometimes a bonus third
Time45 minutes in a 2025 O’Fallon intern report; 60-90 minutes elsewhere
ExtrasMultiple-choice questions in a 2024 Singapore report
AI useOnly if Mastercard invites it, with its own guidelines
Next stepLive technical rounds plus a behavioral round

What Mastercard Is Testing in This Round

Whether you can turn a plain problem statement into correct, efficient code under a clock; hidden test cases do the grading. Mastercard’s interview tips page says technical questions “may differ from standard classroom algorithms”, so expect classic problems in business wording. The Mastercard interview guide covers the Java and Decency Quotient rounds that follow.

Red flags that fail candidates:

  • Code that passes the sample but fails empty, duplicate or very large hidden inputs.
  • A brute-force O(n^2) answer that times out on large hidden cases.
  • Leaving an easy problem unsubmitted while stuck on the hardest.
  • Pasted code or tab switches flagged by HackerRank’s integrity settings.

What to Expect

Mastercard does not publish the format; its process “varies depending on the role you’re applying for”. Test details below are candidate-reported.

  • Shape. A September 2025 O’Fallon, Missouri intern report describes “2 Questions 45 minutes with a bonus 3rd question” in a HackerRank environment, then a 30-minute behavioral round; interviewers encouraged questions, so some US teams run it live. A 2024 Singapore report describes two coding problems plus MCQs; Pune reports describe two problems in about an hour.
  • Codility. A Pune report and third-party guides say the first screen is HackerRank or Codility depending on region, so check your invitation link.
  • Languages. HackerRank supports about 60 languages, with per-test-case limits of 4 seconds for Java and 10 for Python 3. Backend roles name Java and Spring Boot, so Java is a safe default.
  • Proctoring. Employers choose per test. Secure Mode enforces full screen, blocks pasting, alerts on tab switches and allows one monitor; Proctor Mode adds webcam checks, phone detection, screenshots and a session replay.
  • AI rules. Mastercard’s AI use guidelines say “candidates may be invited to use AI as part of the technical assessment process” for some roles, and warn that misrepresenting your “skills, experience, or readiness” during a technical assessment may lead to disqualification. Unless invited, sit it unassisted. See our tracker of companies that allow AI in interviews.

Example Questions and How to Answer Them

These are reported themes, not leaked questions.

1. An anagram or character-frequency check

One report mentions an anagram check. Approach: Count characters in a hash map or 26-slot array, compare, and test empty strings.

2. Duplicate transactions in a list

Illustrative, not reported. Approach: Pin down what makes two records duplicates (same card, amount and merchant within a time window), sort by time, and keep a hash map of the last timestamp per key.

3. A graph traversal such as counting connected regions

Named in a Pune report. Approach: BFS or iterative DFS with a visited set; test disconnected and single-node inputs.

4. A medium dynamic programming problem

Named in a Pune report. Approach: State the subproblem, write the recurrence, then base cases. Memoized recursion that passes most cases beats an unfinished table.

5. An OOP or SQL multiple-choice question

Third-party topic lists name OOP and databases. Approach: Know overriding versus overloading, join types and ACID; skip anything that takes over 60 seconds.

How to Prepare in 3 Days

  • Day 1: patterns. Hash maps, two pointers, sliding window, sorting, BFS and DFS. Solve eight problems untimed from our coding interview examples and solutions, writing your own edge-case tests.
  • Day 2: timed sittings. Two sittings of two problems in 45 minutes, no autocomplete. After each timer stops, review missed approaches in OphyAI Coding Interview (Premium), then re-solve the problem unassisted. Mastercard’s guidelines name “AI-driven mock interview platforms” as acceptable preparation.
  • Day 3: logistics and talk-through. Confirm platform, time limit and proctoring from the invitation and test your webcam. Then run one technical mock in Interview Practice so you can explain your solution aloud for the live rounds.

Start practicing →

Common Mistakes

  • Assuming it is unattended. Some US candidates report an interviewer present.
  • Ignoring the hidden cases. Test empty, one-element and large inputs before you submit.
  • Choosing an unfamiliar language. Use your fastest one.
  • Using AI during the test. Mastercard rules it out unless you are invited.

Frequently Asked Questions

How many questions are on the Mastercard HackerRank test?

Most candidate reports describe two coding problems, sometimes with an optional bonus third. A September 2025 O’Fallon intern report describes two problems in 45 minutes plus a bonus, and a 2024 Singapore report describes 10-15 questions in total, two coding and the rest multiple choice. Mastercard publishes no fixed count.

How long is the Mastercard online assessment?

Reports range from 45 minutes for a US intern screen to 60-90 minutes in third-party guides and Pune reports. HackerRank shows the time limit on the instructions screen before the timer starts, and that figure is the one to plan around. Leave five minutes to test edge cases.

Is the Mastercard HackerRank assessment proctored?

It depends on the settings Mastercard chooses for your test. HackerRank Secure Mode enforces full screen, blocks pasting and allows one monitor, while Proctor Mode adds webcam monitoring, phone detection and periodic screenshots that reviewers can replay. The onboarding screens ask for consent to whichever applies, so you will know before you start.

Can I use ChatGPT or other AI on the Mastercard assessment?

Not unless Mastercard invites you to. Its AI use guidelines say some roles may invite AI use in a technical assessment with clear guidance, and that misrepresenting your skills or readiness in a technical assessment may lead to disqualification. The same page names AI mock interview platforms as acceptable preparation, so use AI before the test, not during it.

Does Mastercard use Codility instead of HackerRank?

Sometimes. Candidate reports and third-party guides describe the first coding screen as HackerRank or Codility depending on region and team, and a 2025 Pune report describes another vendor entirely. Both platforms grade with hidden test cases, so the preparation is the same: timed problems, edge-case testing and a language you know well.

Sources and verification notes

Checked October 2026. Mastercard and HackerRank pages were opened directly; Glassdoor and LeetCode blocked fetches, so candidate reports came from search summaries.

Tags:

Mastercard interview Mastercard HackerRank online assessment coding assessment fintech interview US

Turn the advice into a realistic practice session

Run a role-specific mock interview, review feedback across four scoring areas, and repeat the answers that need work.