Stripe interview notes, page 10 of 35

“I fumbled this a bit.” The rest of the author's notes on Software Engineer interview at Stripe, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the obvious stuff, hashmaps keyed by user id pointing to sets of role ids, roles pointing to sets of permission strings.” The rest of the author's notes on Software Engineer interview at Stripe, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Spent the first few minutes just trying to scope it down because bookkeeping can mean a hundred different things.” The rest of the author's notes on Software Engineer interview at Stripe, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is where I spent most of my mental energy.” The rest of the author's notes on Software Engineer interview at Stripe, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The left join part was fine, I had that logic pretty quick.” The rest of the author's notes on Software Engineer interview at Stripe, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Jumped into it within an hour of getting the link, probably not my smartest move but I was anxious.” The rest of the author's notes on Software Engineer interview at Stripe, Online Assessment (OA) round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The base system wasn't bad to reason through but SHUTDOWN is where it gets messy.” The rest of the author's notes on Software Engineer interview at Stripe, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to just patch the user object when I hit a change date, but that blew up the structure I'd built in the previous part.” The rest of the author's notes on Software Engineer interview at Stripe, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The core model felt straightforward until I started thinking about where to compute the totals.” The rest of the author's notes on Software Engineer interview at Stripe, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Seemed simple at first, just set a value in a dict and return true or false.” The rest of the author's notes on Software Engineer interview at Stripe, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.