AfterpayAfterpay's buy-now-pay-later product processes a high volume of small transactions where fraud and credit-risk decisions have to happen in milliseconds, so its engineering interviews put real weight on correctness under edge cases and on reasoning about money moving through a system, not just feature-building. As part of Block's broader payments ecosystem, engineers are also expected to think about compliance touchpoints (like PCI-DSS) as a normal part of design, not a separate afterthought handled by another team.
Expect a recruiter screen, a technical screen focused on practical coding (arrays, lists, maps, and refactoring under time pressure), a system design round centered on payments or fraud-detection scenarios, and a values/behavioral round assessing ownership and customer impact.
Given a list of transactions, write a function to detect duplicate charges within a short time window.
A direct, codeable version of a real fraud-prevention problem — tests array/map manipulation plus awareness of edge cases like near-simultaneous legitimate retries.
How would you design a system to approve or decline a buy-now-pay-later payment in under 200 milliseconds?
Core to Afterpay's product: checks understanding of low-latency decisioning, caching risk scores, and graceful degradation under load.
Refactor this function that calculates a customer's remaining installment balance to handle partial refunds correctly.
Directly tests handling of money-related edge cases (partial refunds, rounding) where a bug has real financial consequences for customers.
How would you design a fraud-detection system that flags suspicious repayment patterns without generating excessive false positives?
Balances technical system design with product judgment — over-flagging real customers is treated as seriously as missing actual fraud.
Tell me about a time you had to make a trade-off between shipping quickly and being fully certain your code was correct.
In a payments context, this checks judgment about when speed is acceptable and when it isn't — a distinction good candidates can articulate clearly.
How would you ensure a new feature that touches customer payment data meets PCI-DSS compliance requirements?
Screens for baseline awareness that compliance is an engineering design constraint at a payments company, not solely a legal/security team concern.
Design a system to process a high volume of merchant payouts reliably, even if some downstream services are temporarily unavailable.
Tests resilience patterns — retries, idempotency, dead-letter queues — applied to a scenario where losing or duplicating a payout is a real financial error.
Describe a bug you found in production that involved money. How did you handle it?
A behavioral question specific to fintech — assesses transparency and urgency when the stakes of a bug are directly financial rather than cosmetic.