Stripe Interview Questions — Page 26

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Stripe SWE interview with a multi-part OOP/design question that kept building on itself. Each part felt manageable until the LRU piece showed up and I had to think pretty carefully about data structures under time pressure.

Design an AccountScheduler class that tracks which accounts are locked until a given timestamp. Implement an is_available(account_id, t) method that returns whether the account can be used at time t.
Extend the class with an acquire(account_id, t, duration) method that locks an account for a duration starting at t, using the formula: locked_until[account_id] = max(locked_until[account_id], t) + duration.
Further extend the class with an auto_acquire(t, duration) method that automatically picks the least recently used available account, locks it, and returns its ID. Accounts never previously acquired should be treated as oldest.

“Straightforward to start.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Stripe system design screen for a software engineer role, focused on designing a server health-tracking system from scratch. The problem built up incrementally, starting with the SET HEALTHY operation, and felt more like a distributed systems contract negotiation than a typical coding round.

You're building a server health-tracking system. Servers are pre-registered with an id and metadata. Design and define the SET HEALTHY operation: what arguments does it take, what happens if the server was never registered, how do repeated calls behave, and how does it handle overwriting prior status?

“I jumped straight into the happy path and forgot to define the error contract for unregistered servers until the interviewer nudged me.”

View Post

Stripe·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026

Behavioral round at Stripe for an EM role. Just the one question from what I can tell, focused on change management and leading teams through uncertainty.

Tell me about a time you led your team through a major change, like a reorg or a significant shift in process. What did you actually do?

“I had a decent story ready for this but I kept second-guessing whether my example was 'big enough.' Ended up picking a process overhaul we did mid-cycle and structured it as situation, actions, result.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Jun 2026

Stripe system design round, one big question about building a superhero dispatch platform. Think Uber but for saving the world. The scope was wide enough that I kept second-guessing which parts to go deep on.

Design a superhero dispatch system that matches available superheroes to incoming world events in real time, similar to how a ride-sharing platform assigns drivers to riders. Walk through event ingestion, hero availability tracking, geospatial indexing to find the nearest hero, the matching service, real-time updates, and how you'd scale the whole thing.

“I spent way too long on event ingestion and didn't get to geospatial indexing until they nudged me.”

View Post

Stripe·Data Scientist·Onsite - Behavioral / Leadership

Jun 2026

Stripe data scientist interview with a pretty intense behavioral/project question that required way more prep than I gave it credit for. The structure they wanted was exhaustive and I definitely undersold the quantitative side of my story.

Walk me through a project you led that measurably moved a core business metric. Cover the context, your specific goal and constraints, the three most consequential decisions you made including trade-offs and stakeholders across regions, one intentional risk you took, and before/after numbers with dollar impact and how you validated attribution. Then tell me what you'd do differently to double the impact in the same timeframe, and what you'd cut if you had to ship in three hours.

“This question is basically four questions stapled together and I did not pace myself well.”

View Post

Stripe·Software Engineer·Online Assessment (OA)

Jun 2026

Took the Stripe online assessment, one question split into three parts, 60 minute window. Finished with about 8 minutes to spare and passed all test cases, but now just sitting here waiting to hear back and not totally sure what to expect.

A multi-part coding problem broken into three sub-questions, completed within a 60-minute online assessment.

“Got through all three parts and every test case passed, which felt like a win.”

View Post

Stripe·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026

Behavioral round at Stripe for a software engineer role. Just one question but they really sat with it, pushing on the reasoning behind the decision not just the outcome.

Tell me about a time you had to make a decision very quickly. Walk through the situation, the constraints you were working with, the options you weighed, what you chose and why, and how it turned out. How did you think about trading off speed against making a good call?

“I had a decent story ready but fumbled the constraints part.”

View Post

Stripe·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

Stripe PM interview with a product sense question that felt deceptively open-ended. You pick your own products, which sounds like a gift until you realize the follow-up is where they actually judge you.

Name three products you know well and care about. Pick one and explain what draws you to it, then walk through how you'd adapt it for a new market segment.

“The first part felt easy and I probably spent too long on it.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Stripe data engineer interview with a meaty CSV parsing and fee aggregation problem. The question looks like a glorified ETL task but there's enough edge cases baked in that you can easily spiral if you're not careful about how you structure it.

Given a CSV string of payment transactions and several lookup dictionaries (base rates by provider, completed rates by provider and country, and FX conversion factors), write a function that computes the total processing fee per merchant and returns the result as a CSV string. Walk through your fee calculation logic, fallback handling for missing keys, and how you'd test edge cases like empty input, malformed rows, or unknown currencies.

“This took me longer to parse (no pun intended) than I expected.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Jun 2026

Stripe frontend systems design question, basically a deep dive into debugging wrong DOM attributes in an unfamiliar framework. Solid technical round, felt more like a whiteboard war-game than a typical interview.

You're working in an unfamiliar frontend framework and the rendered DOM has wrong attributes, like className instead of class, miscased data-* attributes, or boolean props serialized incorrectly. Walk through how you'd debug this end to end, fix it, and make sure it doesn't happen again.

“This one sprawled in a way I didn't expect.”

View Post