Marqeta is the modern card issuing platform — powers cards for Square, Doordash, Instacart, and many fintechs. The interview is payments-engineering-heavy with focus on card networks, real-time authorization, and the regulatory framework around card issuing.
Process
Recruiter screen → 60-minute coding phone (DSA medium) → onsite virtual: 2 coding, 1 system design, 1 craft deep-dive, 1 behavioral. Cycle: 4–6 weeks.
What they actually ask
- Design a real-time card authorization system with sub-100ms latency — walk the auth message from the network through the issuer processor to an approve/decline decision. Interviewers probe how you keep the hot path fast: in-memory balance and limit checks, no synchronous writes to slow stores, tight timeouts, and a stand-in decision when a downstream call runs late.
- Design just-in-time funding — fund the card seconds before authorization. Explain how the issuer calls the program’s funding source in real time on each auth, approves or declines inside the network’s response window, and falls back to a decline when the funding call times out. Be ready to talk reconciliation when the funded and settled amounts differ.
- Design fraud detection at the moment of swipe — real-time scoring that has to fit inside the same latency budget as the auth itself. Expect questions on velocity checks (too many swipes in a short window), combining simple rules with a model, and the tradeoff between blocking fraud and declining good customers.
- Coding: medium DSA, often with concurrency or financial framing — think arrays, strings, and hash maps at medium difficulty, sometimes wrapped in a money-movement story. A common twist is thread-safety: updating a ledger or account balance from concurrent requests without double-spending. Drill the standard patterns so you can code them cleanly under time pressure.
- Behavioral: customer focus, working with payments domain, regulatory awareness — have STAR stories about a reliability or money-movement incident you owned, and a time you made a compliance-aware call under pressure. They want to see you treat correctness and uptime as non-negotiable given the financial stakes.
Levels and comp (2026)
- SE II: $150K–$190K total
- Senior SE: $215K–$290K
- Staff: $310K–$420K
- Principal: $430K–$570K
Prep priorities
- Be fluent in Java (the bulk of the codebase) — expect to write idiomatic Java in the interview, not pseudocode. Know the collections, exceptions, and the concurrency primitives (threads, locks, atomics) you would reach for in a money-movement service.
- Understand card networks: Visa, Mastercard, EMV, ISO 8583 — know the ISO 8583 message structure (the MTI and data elements) and the auth → clearing → settlement flow. Be able to explain what EMV chip data adds over a mag-stripe swipe and where the issuer sits in the transaction.
- Brush up on card issuing regulations: BSA, OFAC, FFIEC — you don’t need to be a lawyer, but know what each one governs: BSA/AML reporting, OFAC sanctions screening on transactions, and the FFIEC guidance issuers are examined against. Being able to point to where these touch the code sets you apart.
Frequently Asked Questions
Is Marqeta remote-friendly?
Hybrid in Oakland (HQ), London, Sydney. Some engineering roles fully remote within US.
How does Marqeta compare to Stripe Issuing or Galileo?
Marqeta is the largest pure-play. Stripe Issuing is part of broader Stripe stack. Galileo (SoFi-owned) is the legacy player. Marqeta engineering culture leans deeper on payments expertise.
What is the engineering culture?
Mature, payments-focused, methodical. Strong testing and reliability culture given the financial stakes.
Similar company guides
Prepping for Marqeta? Put it to work:
