Mastercard · Primly Community

My full SWE loop at Mastercard, O'Fallon MO office (April 2026)

backend_bekah · 5 replies

Just finished and wanted to write this up while it was fresh. Applied for a Senior SWE role on the Payments Processing platform team.

Round 1: Recruiter screen, ~25 min. Standard fit questions, a bit of comp probing. She was upfront that the role was hybrid O'Fallon, not remote, which I appreciated.

Round 2: Technical phone screen with a senior engineer. 45 minutes. Two LeetCode-mediums (arrays/hashmaps, nothing exotic), plus maybe 10 minutes of systems design at the end. She asked me to sketch how I'd handle idempotency in a payment API. Classic, if you've done any fintech work you've thought about this.

Round 3 (Final loop, virtual, 4 panels): System design: design a fraud alert notification system. They wanted to talk about scale, latency tolerance, and what happens when the downstream bank's endpoint is flaky. Coding: two mediums, one of which had a follow-up about time complexity. Nothing fancy. Behavioral x2: both panels heavy on "tell me about a time you influenced a decision without authority" and "cross-functional conflict." This is clearly what they care about.

Total time from application to offer call: 5.5 weeks. Recruiter was responsive and kept me in the loop.

The thing that surprised me: they asked almost nothing about payments domain knowledge. The system design was payments-flavored but they were fine if you reasoned through it from first principles. Don't feel like you need to memorize ISO 8583 or whatever.

5 replies

visa_vik

thank you for this. quick question: did they ask about work authorization at any point in the loop? I'm on H1B and I always get nervous about when it comes up.

backend_bekah

recruiter asked in the first call, pretty early, whether I'd need sponsorship now or in the future. I didn't so I can't speak to what happens if you do. but it was upfront and not awkward, she seemed used to fielding it.

ops_omar

the idempotency question is such a standard fintech interview move. good signal that you knew it going in. did the behavioral panels feel like they were reading from a rubric or more conversational?

sec_sasha

curious whether the fraud alert system design went anywhere near threat modeling, auth between services, that kind of thing. or was it more pure distributed systems?

backend_bekah

mostly distributed systems. one of the panelists did ask about how we'd ensure the alert couldn't be spoofed downstream, so I talked through service-to-service auth briefly. but they didn't go deep. I think for a senior IC role it was more about whether you know the questions to ask, not that you have all the answers.