Stripe

Stripe Software Engineer Onsite Coding Questions

138+ questions from real Stripe Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.

138
Questions
8
Topic Areas
10+
Sources

What does the Stripe Onsite Coding round test?

The Stripe onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.

Top Topics in This Round

Stripe Software Engineer Onsite Coding Questions

Implement a system to manage users' email subscriptions. Requirements: 1. Implement functionality to add users to a subscription list. 2. Implement functionality to remove users from the subscription

Stripe Software Engineer Virtual Onsite Interview Experience

Greedy, Backtracking, Graph, Stripe, Onsite 2026

The Stripe VO interview experience was great. The questions were all based on real-world payment and transaction scenarios, which really tested the ability to abstract and optimize practical problems.

Stripe SWE onsite interviews:Need guidance

Onsite, Bug Squash, Integration, Stripe 2026

I have tech programming, bug bash and integration rounds(really anxious for these last rounds :( ) Any suggestions on how/what to focus/prepare on? Thanks in advance!

Stripe Onsite Fulltime Software Engineer Interview Experience with Python

System Design,Oop,Behavioral,General Experience 2025

VO Rounds 5 The following content requires a score of 200 or higher. You can already view it. Programming: Email sub-question, an old question. The guy from abc was very nice. He spent the first 15 mi

Ledger System

System Design,Sql,Databases,Concurrency,Fintech 2025

Ledger System Design ## What We Need to Build We need to design a ledger service for a payment platform. This service tracks money for merchants (online business owners). When a platform processes p

Stripe Onsite Software Engineering Interview Experience and Rounds Overview

Onsite, Integration, Bug Squash, Heap, Stripe, Phone Screen 2025

**Phone Screen** Solved two parts. In the second part, identified a missing edge case and explained the fix verbally before time expired. Successfully cleared this round. **Round 1: Programming Exerci

Stripe Interview Experience: Invoice Reconciliation Coding Onsite Round

Strings, Arrays, Parsing, Stripe, Implementation 2025

**Invoice Reconciliation** **Problem Statement** Businesses frequently receive standalone payments that must be reconciled with open customer invoices. The objective is to develop a program that match

Stripe virtual onsite new graduate interview

General Experience,Interview Prep 2025

I have my stripe virtual onsie interview scheduled next week. It will be having two rounds coding exercise and bug squash. I chose the language as python, can anyone give me tips how to prepare for it

Stripe SWE on-site interview tips

Onsite, Bug Squash, Integration, Stripe, New Grad 2025

Hi, I have a stripe virtual onsite interview cmg up. This is for a New grad position. What to expect and how to prepare for this round? They said I’ll have a bug squash and integration round. Any sugg

Stripe post-HM round interview response also anyone know the response time?

Onsite, Integration, Bug Squash, Behavioral, Stripe 2025

Finished my last interview (30 minute HM chat) with Stripe recently for a new grad position in the US. Does anyone know the response time after that? Also a review of my onsite and HM rounds. Don't ta

#1169 Invalid Transactions

Arrays,Hash-Table,Sorting,Strings,Simulation

LeetCode #1169: Invalid Transactions. Difficulty: Medium. Topics: Array, Hash Table, String, Sorting. Asked at Stripe in the last 6 months.

LeetCode #2303: Calculate Amount Paid in Taxes. Difficulty: Easy. Topics: Array, Simulation. Asked at Stripe in the last 6 months.

#2043 Simple Bank System

Arrays,Hash-Table,Design,Simulation

LeetCode #2043: Simple Bank System. Difficulty: Medium. Topics: Array, Hash Table, Design, Simulation. Asked at Stripe in the last 6 months.

LeetCode #1604: Alert Using Same Key-Card Three or More Times in a One Hour Period. Difficulty: Medium. Topics: Array, Hash Table, String, Sorting. Asked at Stripe in the last 6 months.

## Problem Build a reusable `Accordion` component in vanilla JavaScript (or React). Each section has a header and collapsible content. Only one section can be open at a time. Clicking an open header collapses it. **Requirements:** - Toggle open/closed state on header click. - Only one panel open at a time (single-expand mode). - Keyboard accessible: Enter/Space opens/closes; Arrow keys navigate between headers. - Animate expand/collapse with CSS transitions on `max-height`. ```html <!-- Expected DOM structure --> <div class="accordion"> <div class="accordion-item"> <button class="accordion-header" aria-expanded="false">Section 1</button> <div class="accordion-panel" hidden>Content 1</div> </div> ... </div> ``` ```javascript function initAccordion(container) { // wire up event listeners and ARIA attributes } ``` **Example behavior:** ``` Click "Section 1" -> panel 1 opens, aria-expanded=true Click "Section 2" -> panel 2 opens, panel 1 closes Click "Section 2" again -> panel 2 closes ``` ## Follow-ups 1. How would you support multi-expand mode as a configuration option? 2. What ARIA attributes are required for full screen reader compatibility? 3. How do you handle dynamic content added to panels after initialization? 4. How would you write a unit test for the keyboard navigation behavior?

## Round 1 - System Design ## Problem Design the frontend architecture for a real-time analytics dashboard used by 50,000 concurrent enterprise users. The dashboard displays live charts, filterable data tables, and drill-down panels — all updating every 10 seconds. **Scope (clarify before diving in):** - What is the expected data volume per user per update cycle? - Does the app need to work offline? - What browser support matrix is required? ## Key Areas to Cover **State Management** - How do you structure global vs. local component state? - What state management library (Redux, Zustand, Jotai) fits this scale and why? **Real-Time Data** - WebSocket vs. SSE vs. polling for 10s updates. - How do you handle reconnections gracefully without UI flicker? **Performance** - Virtual scrolling for large tables (100k+ rows). - Chart rendering: Canvas vs. SVG at high data density. - Bundle splitting and lazy loading for dashboard panels. **Component Architecture** - Design a composable filter system that multiple panels share. - How do you isolate panel failures so one broken widget does not crash the dashboard? ## Follow-ups 1. How do you test real-time behavior in a CI environment without a live WebSocket server? 2. What monitoring would you add on the client side to detect and report rendering performance regressions? 3. How would you handle role-based visibility (some panels only visible to admins)?

Implement a small **integration exercise**: based on provided interface/data-source contracts, quickly fetch/transform/aggregate data and output results in the required format. Typical requirements:

Design and implement an **Email Notification Scheduler**. The system receives scheduling requests, each with: - `userId` - `notificationType` - `sendAt` (scheduled time) - `payload` Implement the sc

You are given two kinds of payment-related text records (e.g., invoices and payments/events). Each record is a string containing multiple fields. You need to: 1. **Parse** each record into structured

## Problem: API Integration (Call a REST API and Aggregate Results) Write a program that calls a third-party REST API and aggregates the results. Use the public PokeAPI for practice: `https://pokeap

What to Expect in the Stripe Onsite Coding Round

The Stripe Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 138+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.

Reports tagged with the Onsite Coding round at Stripe show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.

How To Prepare for This Specific Round

Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.

Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.

Onsite Coding Round Timing and Format

The Onsite Coding round at Stripe typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.

Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.

Common Failure Modes in This Round

Reports tagged "no hire" at Stripe Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.

The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.

See All 138 Questions from This Round

Full question text, answer context, and frequency data for subscribers.

Get Access