← Back to Directory

Stripe interview notes, page 15 of 35

Large Enterprises

Most of these Stripe write-ups come from Software Engineers (295), then Product Managers (22) and Data Scientists (20). The most reported rounds are the technical phone screen (206), the system design round (39), the behavioral / leadership round (22) and the product sense round (20).

342 interview notes · updated Oct 2026

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding round focused on a data parsing and rendering problem, the kind where you spend the first ten minutes just trying to understand what the JSON schema even wants from you.
  • Given JSON files describing bike trips and stations, parse the data, extract relevant fields like station coordinates and ride paths, and render a map with markers for stations and paths for rides.

“The actual parsing wasn't the hard part.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe SWE interview where they hand you a broken JSON parser and tell you to fix it. No scaffolding, no hints, just read the code and figure out what's wrong. Felt like a real debugging shift more than a coding interview.
  • You're given a working-ish JSON parser implementation that handles the full spec (objects, arrays, strings, numbers, booleans, null, escape sequences). It has multiple bugs. Identify and fix all of them.

“This one took me a while to even get my footing.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

May 2026
Stripe system design round for a software engineering role. Two-part question that combined financial infrastructure design with third-party integration, which felt like a lot to cover in one session.
  • How would you design a ledger system that maintains strong consistency while also scaling to handle high transaction volumes?
  • Walk through how you'd integrate an external mapping library into a production application, including how you'd design the API boundary, manage data flow, handle errors, and think about deployment.

“This is the kind of question where you can go deep fast and still feel like you barely scratched the surface.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding screen for a software engineer role, one question but it had three layers that kept getting harder. The progression from flat pricing to tiered to a hybrid base-plus-tiers felt reasonable on paper but the off-by-one stuff at tier boundaries genuinely tripped me up mid-session.
  • Implement a shipping cost calculator in JavaScript with three progressively complex pricing models (flat per-unit, tiered per-unit, and a flat base fee for the first N items plus tiered pricing beyond that), driven by a config object keyed by destination. Define the function signature and describe edge case tests including quantity 0, exact tier boundaries, unknown destinations, negative inputs, and floating-point handling.

“I got the first two parts pretty fast.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding interview for a software engineer role, this one was a multi-part problem built around a fraud detection pipeline. The final part asked you to replace a generic label with specific error codes and then render everything as a formatted plain-text report. Pretty involved for a single session.
  • You have a multi-stage fraud detection pipeline that labels each transaction as VALID, INVALID, or SUSPICIOUS. Refactor it so that SUSPICIOUS is replaced by specific prioritized error codes (missing field, amount out of range, blocked payment method, behavior mismatch). Each transaction should output at most two error codes ordered by a configurable priority, or OK if clean. How do you design and implement this?
  • For the final output, produce a column-aligned plain-text report with transaction ID, status, and up to two error codes. How do you compute column widths and handle padding?

“This was the meat of the whole interview.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding interview with a scheduling problem that looks deceptively clean on the surface. One question, but it had enough edge cases to keep me busy for the whole session.
  • You have a list of user accounts, each with a subscription plan and a signup timestamp. You also have a schedule that maps email types (like welcome, upcoming expiry, expired) to time offsets relative to plan lifecycle events. Write a function that produces all the emails that should be sent, sorted chronologically, with the recipient and email type for each.

“Spent the first few minutes just making sure I understood the data model before touching any code.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe phone screen for a software engineer role, centered entirely on one multi-part coding problem about invoice reconciliation. The problem kept expanding with each sub-task and it felt like the whole interview was designed to see how far you could push a single solution before it broke.
  • Build an invoice reconciliation system: given a list of invoices and a list of payments (each with an id, amount, currency, timestamp, etc.), match payments to invoices and identify any discrepancies such as overpayments, underpayments, duplicates, or unmatched records. Then extend the solution to handle multi-currency conversion, partial payments, and refunds across three incremental parts.

“The first part felt manageable, just matching ids and flagging mismatches.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe SWE screen focused on transaction processing, the kind of question that looks straightforward but has enough moving parts to trip you up if you're not careful about the details.
  • Given a stream of transaction records (each with an id, timestamp, and payload like sender, receiver, amount), sort them by timestamp oldest-first and build hashmap-based summaries grouping transactions by user with aggregates like count, total amount, and last seen. Discuss time complexity and how you'd handle timestamp ties.

“The sort part was fine, O(n log n), said it out loud and moved on.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding screen for a software engineer role, the problem was a file processing task involving a left outer join across two CSVs. Pretty implementation-heavy, less algorithmic than I expected.
  • Given two files (a customer file and a processor file), iterate over the customer file and produce an output row for every customer record. If no matching record exists in the processor file, still emit the customer row but leave the processor columns blank while preserving all comma delimiters. Essentially implement a left outer join over flat files.

“The join logic itself wasn't the hard part.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

May 2026
Stripe system design round for a software engineer role. The whole interview was built around a single multi-part problem that kept layering on complexity, which I wasn't fully prepared for going in.
  • Design a load balancer that distributes WebSocket connections across multiple Jupyter servers. Start with basic assignment logic, then extend it to handle disconnections, object-level stickiness, per-server capacity limits, and graceful server shutdown with connection re-routing.

“This was five questions disguised as one.”

View Post