
Stripe software engineer candidates describe practical, work-like interviews: multi-part coding, bug-squash, API integration, and a hiring-manager or behavioral conversation. Some also report a payments-focused design discussion.
$190K
Avg. Base Comp
$290K
Avg. Total Comp
4-6 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Stripe's software engineer loop as closer to a working session than a puzzle contest. Many report an online assessment or phone screen, then an onsite or virtual onsite that combines multi-part coding, a bug-squash round, and an integration round with a behavioral or hiring-manager conversation. Reports vary on how many rounds there are, from four to as many as six.
The coding questions often start simple and grow in stages. Candidates mention payment-flavored problems such as invoice totals, idempotency-key handling, retry logic, and flight-route parsing that ends in Dijkstra. One candidate also reports an interval problem that was a LeetCode-medium in disguise. Pace and clean code seem to matter: one candidate solved the first of two string-parsing tasks and learned that wasn't enough.
The bug-bash round asks you to work in code you didn't write, such as failing tests in a repository, a Python template engine, or a page of Ruby. Practice narrating your debugging aloud. The integration round, as candidates describe it, means writing code against an existing codebase or API.
Several reports touch on payments reliability: idempotency, duplicate requests, failed attempts, and what happens when a downstream service goes down. One candidate was asked for an extra design round after the onsite, so ask your recruiter whether design is included. Outcomes in this evidence are mostly rejections, with a few candidates still waiting.
Synthesized from 130 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Stripe process.
The first thing I'd want someone to know is that the proctoring comes before any human shows up, and it is intense. The platform recorded everything: keystrokes, cursor movement, pupil movement, background noise, even coughing and sneezing. It asked for a passport or driver's license, a scan of my room, mic and camera on the whole time, and screen sharing. It also tracked which tabs and apps were open. I came away feeling watched like a suspect rather than assessed like a candidate, and it made the whole thing feel strangely exposed before I'd spoken to anyone.
Live interview. The live interview was where the real difficulty showed up. The interviewer gave me one or two very long questions, each with a lot of parts, and I only had 45 to 60 minutes depending on who I got. Based on similar problems I'd built in my own projects, the full problem was solvable in about 90 minutes, so the time limit was the main challenge. The question was technical and multi-step, and the length meant I had to keep a growing list of requirements in my head while still building a working solution.
The day as a whole was long. The technical sessions ran back to back, and switching context repeatedly made it hard to hold focus. Some interviewers were rude and unprofessional, which made the stretch even more draining. The exhaustion was harder to manage than any single question.
I did not receive an offer.
Prep tip from this candidate
Practice long, multi-part problems under a hard 45 to 60 minute limit, since the time given was well short of what the full problem needed. Also set up your ID, room scan, and screen sharing ahead of time so the recorded proctoring stage doesn't eat into your focus.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Stripe
Write a query to get the total three-day rolling average for deposits by day
| Question | |
|---|---|
| Last Transaction | |
| Payments Received | |
| Scrambled Tickets | |
| Over 100 Dollars | |
| Google Maps Improvement | |
| Unique Work Days | |
| String Mapping | |
| The Brackets Problem | |
| Payment Data Pipeline | |
| Subscription Retention | |
| Split Data Without Pandas | |
| Max Width | |
| Resumable Fact Table Load | |
| Annual Retention | |
| Hurdles In Data Projects | |
| User System Response Times | |
| Dijkstra implementation | |
| Digital Library Borrowing Metrics | |
| Success Measurement | |
| Descending Alphanumeric Sorting | |
| Choosing Between Python and SQL | |
| DDoS Attack Response | |
| Messenger Payments | |
| Stop Words Filter | |
| ATM Robbery | |
| Digital Classroom System Design | |
| Portfolio Platform Architecture | |
| Daily Approval Rates | |
| Meta in an Emerging Market |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report an initial call about their experience and motivation, sometimes with recruiter-provided preparation documents. Some describe this call turning technical quickly, so it may be wise to be ready to code from the start.
Candidates report a HackerRank-style assessment or a live screen with parsing, JSON, interval, or route-finding problems. The prompts often add requirements in stages. One candidate found the assessment's real-world framing misleading and met a standard interval problem.
Onsite coding is described as multi-part, with correctness, readable code, and pace all mattering. Reported themes include payments logic, idempotency keys, retries, and extending a function as requirements change. Some candidates describe it as less abstract than classic algorithm drills.
Several candidates report debugging an existing repository, including failing tests, hidden bugs in an open-source library, or Ruby code reviewed aloud. The integration round, as described, involves writing code against an API or a codebase. Narrating your reasoning is commonly mentioned.
Candidates report a manager or behavioral conversation with follow-ups on ownership and ambiguity. Some mention system design on topics like webhook delivery, backups, or payment retries. One candidate was asked for a separate design round after the onsite, so confirm with your recruiter.