READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 128 of 153
Interview experiences · Steven Douglas Associates
Steven Douglas Associates Software Engineer interview experience
The HireVue video interview was time-boxed and unforgiving. I read each prompt, thought, and recorded a camera response with little total time and no way to ask clarifying questions. The behavioral questions were ordinary, but the real pressure came from a coding challenge added near the end of that same limited window. It felt unlike normal live coding. The editor was unexplained, and I had to w…
Interview experiences · Stone
Stone Data Analyst interview: approved, then left waiting for months
I had a very quick conversation with HR, then was told I had passed and should wait for the position to open. The offer seemed clear and matched the job description. The interview itself was objective and respectful, with questions that fit the role, and the timeline was within what they had indicated. I felt calm about it. What knocked the wind out of me was everything after that. I had supposed…
Interview experiences · Stonex Group
Stonex Group Software Engineer interview: arrays, graphs, and multi-round pressure
I went through an intense multi-round process. It began with an online assessment, moved into a technical evaluation with level 1 and level 2 stages, and ended with an HR round. The questions felt medium to hard, and arrays and graphs came up repeatedly. It did not feel like a quick screen. It felt more like they were testing how I handled harder problem patterns under pressure. I did not receive…
Interview experiences · Strava
Strava Software Engineer Interview Experience — Phone Screen: Climb Detection on Elevation Samples, Then Tolerating Partial Descents
Climb Detection Given an array of elevation samples taken at regular intervals, return the [startIndex, endIndex] of the first climb. Return [] if no climb exists. Part 1 — Strict Climb A climb: Starts when elevation begins increasing. Can stay flat. Cannot decrease. Ends at the highest elevation reached during the climb. Example: [3, 2, 1, 0, 0, 1, 2, 2, 3, 5, 10, 10, 7, 15] → [4, 10] Part 2 — T…
Interview experiences · Stripe
Stripe Account Executive interview: rushed mock discovery call
It began like a normal recruiter screen, then moved straight into back-to-back meetings with a peer and the hiring manager. A short mock discovery call was on the schedule, but the manager arrived late. We ran out of time before I could properly debrief the exercise, so the day felt rushed instead of considered. The silence after the meetings left a strange aftertaste. I was told the interviews w…
Interview experiences · Stripe
Stripe Backend Engineer interview: HackerRank parsing and data-processing assessment
I encountered Stripe through an online assessment that was not the usual LeetCode format. It had multiple parts on HackerRank and concentrated on parsing and data processing rather than graph problems or dynamic-programming patterns. I could not quantify the difficulty precisely, but it seemed to care more about how I handled text and data transformations than fast algorithm tricks. The assessmen…
Interview experiences · Stripe
Stripe Data Engineer Interview Experience — A Two-Part CSV Transaction Fee Coding Problem
The screening interview started with the interviewer giving a very brief self-introduction, and then we went straight into the coding section. Part 1 was: given a CSV string of transactions, parse out each person's fee. Questions I asked the interviewer: What are the specific fee calculation rules for different transaction types and payment providers? For example, do payment transactions with car…
Interview experiences · Stripe
Stripe Data Engineer Interview Experience — Three Shipping-Cost Coding Rounds, All Repeats
This company is still tough — the interview pace is tight, very practical, and it's mainly evaluating your coding ability, system design, and culture fit. Let me briefly go over one of my Stripe VO rounds; it was pretty intense. The interviewer opened with a bit of small talk where we introduced ourselves, then he described what he does at Stripe and walked through the overall interview process.…
Interview experiences · Stripe
Stripe Data Scientist Interview Experience — Phone Screen, Then a Three-Question Take-home Under a Week
Still waiting for the final result, but I wanted to share my experience so far. A recruiter from Stripe had reached out to me directly before, so I didn't need to talk to HR again for this role — I went straight into the first round phone screen. A week later I was notified that I'd moved on to the written assessment, with a one-week time limit. I had to submit a presentable result along with the…
Interview experiences · Stripe
Stripe Data Scientist Interview Experience — Rejected for 'Not Detailed Enough' After a Full Onsite Loop
I was interviewing for a DS role while still employed elsewhere. The overall process was decent, and after the interviews I felt pretty good about how it went, but in the end I still got a fail. Two rounds said my answers weren't detailed enough. Personally I think I was already quite detailed, and there wasn't a single question I couldn't answer or got wrong. Has anyone gotten similar feedback b…
Interview experiences · Stripe
Stripe Data Scientist Interview Experience — SQL ETL Case Study Under Time Pressure
The team was already pretty familiar with my background, so the interview wasn't set up to be too difficult. Tech part: They gave me a case and had me build an ETL process based on it. (If the interviewer asks whether it would still run under different scenarios, you'd better think it over again — there's a good chance you missed something.) It was a Zoom video interview, and I wrote SQL code on…
Interview experiences · Stripe
Stripe Data Scientist Interview Experience — The Interviewer Kept Calling It "Terrific," Then Came the Rejection
I got the rejection letter within two days! They said something like: being more precise about this role, which means they sometimes have to reject candidates who are very impressive. I compared emails with a friend and it turns out this line is an old script Stripe likes to reuse. Not sure, but I have a feeling they ultimately wanted someone with a finance background that fits fintech better. I…
Interview experiences · Stripe
Stripe Frontend Engineer Interview Experience — Passed the 45-Minute Live Coding Phone Screen
I want to share my recent phone screen experience with Stripe's frontend team. The role was a remote Frontend Engineer position, and I got into the process through a friend's referral. Things moved pretty fast — when scheduling the interview, the recruiter sent over the coding guide and prep focus areas right away. The phone screen was 45 minutes of live coding. The interviewer was a senior front…
Interview experiences · Stripe
Stripe Intern Software Engineer Interview Experience — Invoice Matching Screen, a Bikemap Integration VO, and an SF Offer
I got the internship last year. Since my timeline was pretty late, I decided to share it with everyone this year instead. Hope it helps anyone who's in the process right now. 12/1/2025 OA 12/2 phone screen invite 12/8 team screen, the payment invoice question. "Part 1 is matching by invoice id; pay attention to handling the case where there's no match. Part 2 builds on part 1 and adds amount matc…
Interview experiences · Stripe
Stripe New Grad Interview Experience — First-Round Onsite With Two Invoice-Matching Problems
We started with mutual self-introductions — no deep dive into past projects. Then came two coding problems based on one scenario; the problem statements and the amount of code weren't small. At the end I got to ask the interviewer some questions. Q1: Given an invoice ID embedded in a payment memo, match it against the invoice list and output the result. My approach: parse the payment string to pu…
Interview experiences · Stripe
Stripe New Grad Software Engineer Interview Experience — A 60-Minute Payment State-Machine OA
Stripe new grad SWE OA. I did it about a week ago, and my memory is a little hazy. It was basically a state machine + OOP. Sharing this to save everyone some time. 60 minutes, progressing through levels. Nothing difficult algorithmically, but there really was a lot of code to write. A payment system, using command-line-style instructions. One detail worth mentioning: every command has the same nu…
Interview experiences · Stripe
Stripe Senior Software Engineer Interview Experience — Bug-Hunt, AI-Pairing, and Map-Drawing Rounds, No System Design
I've already forgotten what the phone screen was, but it wasn't hard. The onsite loop was really different from other companies — felt different from what I'd seen and from other people's experiences too. Round 1 was a bug-hunting round, roughly three problems. Make sure you set up your IDE and install the plugins ahead of time — the details are in the email. (I wasn't careful and didn't read the…
Interview experiences · Stripe
Stripe Senior+ Software Engineer Interview Experience — AI-Assisted Phone Screens, Rejected After Four Onsite Rounds
Two phone screens, coding with AI. My feeling is that you basically just need to show your ability to interact with AI — let the AI write all the code, and your job is mainly to review it, ask it what algorithm to use, how to design the functions and classes, and then once the code is done you comment on the problems with what it wrote. That's basically fine. I don't remember the actual problem.…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A Five-Part OA Simulating a Connection Load Balancer
This was a connection management simulation question for a Jupyter Server — essentially implementing a simplified connection router / load balancer that manages connection state across multiple backend target servers based on different request types (CONNECT, DISCONNECT, SHUTDOWN, etc.). It's not a big system design question. It's more of a small-scale system design / stateful system simulation —…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A Fresh OA on Deployment Window Scheduling
Fresh OA! The question was to build a deployment time window scheduler. Time is represented uniformly as minutes within a week, in the range 0 to 10079: 0 means Monday 00:00, 60 means Monday 01:00, and 10079 means Sunday 23:59. All intervals are left-closed, right-open [start, end). There are two kinds of windows in the input: allowed: times when deployment is permitted freeze: times when deploym…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A Fuzzy User-Matching Screen, Then a Three-Part VO
I recently interviewed at Stripe. The overall process was clear, so I wanted to share it for anyone else prepping for Stripe. I felt like I did so-so on the second round. Phone Screen (Coding, 45min) You're given a bunch of user data, where each row represents a user record. Each record has: id name email company Each field has its own similarity weight, for example: name weight = 0.2 email weigh…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A Month of No-Shows Before a Tight Three-Part Python Screen
Timeline: Early July, first round was an HR phone call — the interviewer showed up a few minutes late. Mostly asked about location, discussed salary and compensation, my previous work experience, why I chose Stripe. (Though she did mention Stripe supports fully remote, which was a nice touch.) After that we agreed to schedule the technical phone screen, but then they sent the wrong email template…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A Month of Scheduling Delays, Then a Tight Three-Part Coding Screen
Timeline: Early July: first HR phone call, interviewer was a few minutes late. Mainly asked about location, discussed compensation, my past work experience, why I chose Stripe. (But they mentioned Stripe supports fully remote, which is pretty nice) After that, they agreed to schedule a technical phone screen, but then sent the wrong email template again — it took me a week and two reminders to ge…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A New Coding Question, a Blank Editor, Never Reached Part 3, and Didn't Pass the Phone Screen
It seemed like a new question — I don't think the interviewer had interviewed with this one much before 😅, he wasn't very familiar with it either. Communication took quite a while, and sometimes the shadow and the interviewer disagreed with each other 😅 Part 1 gave a main() and a function header — you just had to implement the function. The interviewer initially said the output was an integer, bu…