← Back to Directory

Stripe interview notes, page 16 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 screen for a software engineer role. Pretty focused on string manipulation and hash map usage, nothing too wild but the canonicalization details tripped me up a bit.
  • Given a list of email addresses, return the count of unique recipients after applying email canonicalization rules: strip everything after the first '+' in the local part, remove all '.' from the local part, and leave the domain unchanged.

“I knew the general idea but fumbled on the order of operations at first.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

May 2026
Stripe coding round for a Software Engineer role, focused on a 'review-assignment' problem using JGit. The task was interesting but the official JGit docs were down, which made setup a real pain. Small config mistake killed my Part 1 output even though the logic itself was fine.
  • Using JGit, write code to compare two branches of a git repository, then use a CSV file mapping files to owners to find which owner had the most files changed. The goal is to simulate automatic reviewer assignment after a pull request is opened.

“The logic was actually solid.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

May 2026
Stripe system design round for a software engineer role. One big meaty graph problem that took the whole session. Left feeling like I covered maybe 70% of what they wanted to hear.
  • Design a bicycle route planning system over a weighted city graph where edges have distance, bike-lane availability, elevation gain, and traffic risk. Compute a composite-cost optimal route, support top-K alternatives, handle dynamic road closures, and produce turn-by-turn directions. Walk through data structures, algorithm choices, heuristics, complexity, correctness validation, and edge cases like disconnected components.

“This was basically a full 45-minute question.”

View Post

Stripe·Data Scientist·Take-home Assignment

May 2026
Stripe data scientist take-home. The prompt looked manageable at first glance but the scope was clearly designed to swallow a weekend if you let it.
  • You receive a take-home with a suggested 6-hour limit but enough scope to fill 20+ hours. Walk through how you would build a concrete work plan that actually fits inside that window.
  • How do you decide what to cut from a take-home when you can't do everything? What stays, what goes?
  • Before submitting a take-home, how would you proactively communicate the trade-offs and limitations you made to the hiring team?
  • How do you structure a take-home report and appendix so that it shows good judgment even when the work is incomplete?
  • If you get rejected after a take-home, how do you reflect on what went wrong and apply it to the next one?

“My first instinct was to just start coding and see how far I got, which is obviously the wrong call.”

View Post

Stripe·Software Engineer·Take-home Assignment

May 2026
Take-home round for a Software Engineer role at Stripe. The task was a full data pipeline in Java: parse bikemap data from JSON files, build out model classes for the schema, and wire it together using okHTTP and jsoniter. More involved than I expected for a take-home.
  • Build an end-to-end data fetch and parsing pipeline in Java that reads bikemap data from JSON files, defines typed model classes matching the schema, and exposes structured access to the parsed entities using okHTTP and jsoniter.

“The scope crept up on me.”

View Post

Stripe·Software Engineer·Hiring Manager Screen

May 2026
Stripe software engineer interview, one question that felt more like a values check than anything technical. Pretty low-key but it made me think harder than I expected.
  • How would you define success for yourself in your first six months on this team? What outcomes, relationships, or learnings would you want to have built, and how would you track your own progress?

“I fumbled this a bit because I went too vague at first, said something like 'ramp up and contribute to the team' which is basically nothing.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe debugging round where they hand you a broken codebase and a pile of failing tests and basically just watch how you work through it. Less about knowing the answer upfront and more about whether your process is clean under pressure.
  • You're given a small existing codebase with failing tests. Walk through debugging it: identify the bugs, fix them, and iterate until the tests pass, while narrating your reasoning at each step.

“The part that tripped me up was the narration requirement.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe SWE interview with a straightforward coding problem around transaction processing. Nothing too wild, just needed to think through the data carefully.
  • Given a list of transactions where each entry has a sender, a receiver, and an amount, compute the final balance for every user. Only output users whose balance ends up non-zero.

“Pretty much a hash map problem once you see it clearly.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding round for a Software Engineer role. The problem was KYC data validation and you had to manually paste test cases into the input/output fields to run them, which was a bit clunky.
  • Implement a KYC data validation system, handling various input formats and edge cases, with test cases verified through manual I/O.

“The problem itself wasn't too wild but the testing setup was annoying.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

May 2026
Stripe coding round for a software engineer role. It was a twist on the classic worker-task-assignment problem and the added complexity caught me off in a few places, but the design discussion afterward was actually pretty interesting.
  • You're given a worker-task-assignment system where each worker has a set of task types they can handle and each task has a required type. When a task comes in, assign it to the worker who supports that type and becomes available the earliest, breaking ties by worker id. How do you design this, and what's the time complexity?

“The base version of this problem I'd seen before, but the per-skill-type pool thing threw me off initially.”

View Post