← Back to Directory

Stripe interview notes, page 6 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·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Stripe PM interview, one question, classic metrics-and-diagnosis scenario. Not sure what round this was exactly but it felt like a product sense screen.
  • You're the PM at a ride-sharing company and cancellations by users have suddenly spiked. Walk through how you'd diagnose the problem and what you'd do about it.

“I went straight to segmentation, which I think was the right instinct.”

View Post

Stripe·Software Engineer·Hiring Manager Screen

Apr 2026
Interviewed for an EM role at Stripe. One question about goal-setting for engineering teams. Short but made me think harder than I expected about how I actually run my team.
  • How do you set goals for your engineering team?

“I rambled a bit.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding interview, one meaty function implementation question with a bunch of follow-ups baked in. The core problem wasn't too bad but the discussion around edge cases and failure modes is where I felt like I was scrambling.
  • Implement a function that sends invoice reminder emails for unpaid invoices, applying rules around due dates and cooldown periods between reminders. The function should update state on each invoice it processes and return the list of reminded invoice IDs.
  • How would you make this reminder function idempotent, and why does it matter here?
  • If the notifier.send call fails, how do you handle that? Do you retry with backoff, surface the error immediately, or something else?
  • How would you adapt this function to handle very large invoice lists efficiently?

“The filtering logic was pretty straightforward once I slowed down and read the rules carefully.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Stripe system design round, one meaty graph problem that took up the whole session. The problem was more interesting than I expected but I definitely underestimated how much complexity was hiding in the follow-up discussion.
  • You're given a list of user records where each field has a weight. Two users are connected if the sum of weights for their matching fields exceeds a threshold. Build this similarity graph and return all users in the same connected component as a given target user, including those reachable through multiple hops. Then discuss your approach to union-find vs BFS/DFS, and how you'd avoid the O(n²) pairwise comparison cost.

“I started with the naive approach, compute every pair's match score, build the graph, run BFS from the target.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe backend interview, felt like a scheduling and event-driven systems problem dressed up as a product extension. The question was a follow-on to an earlier task so you had to carry context from before, which tripped me up a bit.
  • You have a subscription system where changes can now include an extension of days added to the current plan. On the day of the extension, a 'Renewed' email should go out. The upcoming-expiry and expired notification emails must also be rescheduled to fire relative to the new expiry date. How do you design this?

“The tricky part isn't sending the renewal email, that's just a triggered event.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding interview focused entirely on a multi-part credit card validation problem. Four progressively harder tasks built on each other, starting from basic Luhn checks and ending with error-correction enumeration. The last two parts were rough.
  • Given a digit-only card number string, implement a function that checks whether it passes the Luhn checksum and, if valid, returns which brand it belongs to (VISA, MASTERCARD, or AMEX), or INVALID_CHECKSUM otherwise.
  • Extend the previous function so that a number passing the Luhn check but not matching any known brand pattern returns UNKNOWN instead of being lumped in with invalid results.
  • Allow the card number input to contain wildcard characters where each wildcard represents any single digit. Return the count of valid card numbers per brand that the pattern could represent, formatted as brand-count pairs.
  • Given a card number string where a trailing '?' indicates exactly one error occurred to the preceding digits (the error being one of: a changed digit, a removed digit, an added digit, or a transposition of two adjacent digits), enumerate all originally valid card numbers and their brands that could have produced the observed string.

“This part was fine.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding interview for a software engineer role, one problem that looked like a clean matching exercise but had enough edge cases to keep you honest for a while.
  • Given a list of invoices and a list of payments, each with a customer ID, write an algorithm to match payments to invoices. A match requires the same customer, equal amounts, and if multiple invoices qualify, pick the one with the earliest due date. Each invoice can only be matched once. Return the payment-to-invoice mapping plus whatever's left unmatched on both sides.

“I started by grouping invoices by customer and amount, which felt right, but then I fumbled the FIFO part for a few minutes.”

View Post

Stripe·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Stripe PM interview with a product design question about adapting LinkedIn for a student audience. Pretty open-ended, which I wasn't fully prepared for.
  • How would you design LinkedIn specifically for students?

“I went straight to features, which was probably the wrong move.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe SWE interview with a graph-style matching problem that looked simple on the surface but had some tricky edge cases worth thinking through.
  • Given a list of merchant records where each record has an id, name, email, and phone, and given a target merchant id, return all merchants that share at least one field value with the target merchant.

“My first instinct was to just loop through everything and compare field by field, which works but I spent too long second-guessing whether they wanted something more clever.”

View Post

Stripe·Software Engineer·Hiring Manager Screen

Apr 2026
Interviewed for an EM role at Stripe, basically one question about what skills matter most for engineering managers. Not much to report in terms of rounds or structure, it felt more like a conversation starter than a real technical screen.
  • What do you consider the most important skills for an engineering manager to have?

View Post