Stripe Software Engineer interview questions

295 Software Engineers have shared notes from their Stripe interviews, with the questions they were asked in each round. That is 86% of the 342 Stripe interview notes on Screna AI.

295 Software Engineer interview notes

Stripe·Software Engineer·Onsite - Multi Round

Sep 2026
Did a virtual onsite for a Stripe SWE intern role, two parts: coding and an integration section. Finished most of it but left the last coding problem a little rough around the edges, and now I'm sitting here refreshing my email wondering if messy code kills an otherwise decent performance.
  • Coding problem where you needed to implement a solution, refactor it for cleanliness, and handle edge cases with your own test cases.
  • Integration section questions covering API behavior and how components interact.

“Got through 3 of 4 coding problems.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Aug 2026
A friend with 4 years of experience went through Stripe's API integration round and finished 2 out of 3 parts, explaining the approach for the last one but not actually coding it up before time ran out. Posting here to get a read on whether that's a normal outcome or a red flag.
  • In Stripe's API integration round, candidates are given a multi-part coding problem. Can partial completion (finishing 2 of 3 parts and verbally explaining the third) be enough to pass, or is full completion expected?

“Asking for a friend who ran out of time on part 3.”

View Post

Stripe·Software Engineer·Online Assessment (OA)

Jul 2026
Got an OA invite from Stripe for a Software Engineer role focused on Money Movement in London. Still in early stages, mostly trying to figure out logistics before diving into prep.
  • Is Python acceptable to use throughout the Stripe hiring process, or do they prefer statically typed languages?
  • How fast do interview rounds get scheduled after clearing the OA? Is it purely based on candidate availability?
  • What resources or prep materials are most useful for preparing for Stripe's interview process?

“Genuinely unsure about this.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe frontend coding round, one big component question that looked manageable but had enough wrinkles to keep you honest for the full session.
  • Build a UI component that accepts an array of name/amount pairs, renders the list with a text search filter and a minimum-amount filter, and highlights the item(s) with the highest amount in the currently filtered results in real time. Also explain your state management approach, how you compute the max efficiently, the time/space complexity, and describe edge-case test scenarios including empty lists, ties, non-ASCII names, and rapid typing.

“The base rendering was fine.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe coding round, one question about bitmap fonts and rendering characters as grids. Niche problem but the core logic isn't too bad once you break it down.
  • You're given an array or string of 0s and 1s representing a bitmap font. Write code to render each character as a grid where 0 becomes '.' and 1 becomes '#', and support concatenating multiple characters to print whole words.

“The rendering part clicked pretty fast for me, map bits to characters, chunk by row width, done.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe coding screen for a software engineer role. One problem, the whole time, and it was deceptively tricky to get right. The sliding window part was straightforward enough but the event deduplication logic is where things get messy if you're not careful.
  • Given transaction logs sorted by timestamp, each with a merchant ID, status code, error code, and count field: monitor each (merchant_id, status_code) pair using a rolling window. For each log entry at time t, the rolling count is the sum of all counts for that pair within [t - window_size + 1, t]. Emit a TRIGGER event when the rolling count crosses from below threshold to at or above it, and a RESOLVE event when it drops back below. No duplicate consecutive events per pair. Return all events in chronological order.

“The sliding window itself wasn't the hard part.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe SWE interview with a payments-flavored coding problem. Pretty domain-specific which was a nice change from generic leetcode, but the complexity discussion at the end caught me slightly off guard.
  • You're building a payment processor. Given a fee table that maps (payment_type, payment_status) pairs to rates in basis points, and a list of transactions each with an id, type, status, and amount in cents, compute the processing fee for each transaction using floor(amount * rate / 10000), return 0 for unmatched rules, and return both the per-transaction fees in input order and the total. Discuss time and space complexity.

“The core logic clicked pretty fast, just build a dict from the fee table and do a lookup per transaction.”

View Post

Stripe·Software Engineer·Hiring Manager Screen

Jul 2026
Hiring manager behavioral round at Stripe for a software engineer role. Pretty standard stuff but a few questions had follow-ups I wasn't fully ready for. No technical coding involved, just a lot of talking about yourself and your work.
  • Tell me about the most interesting project you've worked on and what made it interesting to you.
  • Describe a time you ran into a problem you couldn't solve on your own. What did you do?
  • Can you walk me through a situation where you had to make a quick decision under time pressure? What was your reasoning?
  • What are your career plans going forward, and what do you look for most in a job?
  • How would you define success for yourself in your first six months on the team?
  • What are the top three qualities or traits you'd bring to this team?

“They dug into this one more than I expected.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe coding round for a software engineer role. The whole thing was one big multi-part design-and-implement question about a connection router, built up incrementally across five parts. Took longer than I expected to get all the edge cases right.
  • Design and implement a stateful connection router for a multi-tenant server system. Start with basic round-robin routing: given N target servers, implement a connect(connId) method that assigns each new connection to the next available target in cyclic order and returns the chosen target index.
  • Extend connect(connId) to handle duplicate connection requests: if the same connId is already connected, return its existing target without modifying any state.
  • Implement a disconnect(connId) method that removes an active connection, decrements the target's connection count, and returns true. If the connId isn't found, return false without changing any state.
  • Enforce per-target capacity limits in the connect logic. During round-robin scanning, skip targets that are full. If every available target is at capacity, return -1 and leave all state unchanged.
  • Implement a shutdown(targetIndex) method that marks a target as permanently unavailable, evicts all its current connections, and returns the evicted connIds in the order those connections were originally created.

“The round-robin part itself is not bad, just a pointer you increment mod N.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Stripe system design round for a software engineer role. The whole thing was basically one big distributed systems question about counting events at scale, and it went pretty deep into territory I wasn't fully prepared for.
  • Design a system that tracks application activity counts per user, device, and region with high write throughput and near-real-time read access. Define APIs like increment(key, timestamp), getCount(key), getCount(key, timeWindow), and getUniqueActors(key, window).
  • How would you handle idempotency and deduplication in this counting system, and what are the tradeoffs between exactly-once and at-least-once delivery?
  • Walk through how you'd implement time-windowed aggregations, both sliding and tumbling windows, for this event counting system.
  • How would you deal with hot-key sharding when a single user or region generates a disproportionate volume of writes?
  • How would you handle offline client buffering and syncing events back to the server when connectivity is restored?
  • What are your considerations around data retention, TTL policies, and backfill or reprocessing for this system?
  • What privacy considerations apply to this kind of activity tracking system, and how would you address them in the design?
  • Provide a capacity estimate for this system and describe potential failure modes and how you'd mitigate them.

“I started with the API surface which felt like the right move, but I underestimated how much the interviewer wanted me to think through the storage layer early.”

View Post