READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 129 of 153
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A Three-Part Payment/Invoice Matching Problem
Payment and invoice, split into three parts. Invoice is always a list, something like ["invoice-id-1, 100, 2022-01-01", "invoice-id-2, 300, 2022-01-01"]. Payment is just one, something like 'payment-id, 300, paying for: invoice-id-1'. In part one, the payment includes an invoice id, and you're asked to output: "payment-id paid XXX amount for invoice XXX on date XXX" In part two, the payment no lo…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — A Two-Part Deployment Window Scheduler OA I Couldn't Finish
On 9/14 I applied to a mid-level role through a referral and got the OA right away. Honestly it was long and a total slog. Even using Claude I couldn't get it done. Problem background: Stripe needs a scheduler to manage service deployment times. Time is represented as minute_of_week, in the range [0, 10079] (a week has 10080 minutes in total). Input: part: "part1" or "part2" inputCsv: an array of…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — AI Coding, Reconciliation, and a Debugger That Would Not Run
AI coding: It's the rule parser problem from the forum. I used the Opus model and kept talking with the interviewer the whole way through. Honestly, in the moment I couldn't fully understand what the AI wrote either (a lot of the time I have to read Claude's code over and over before I get it, I'm just not that good), but I got the feeling the interviewer was also only half following and just nod…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — Five Onsite Rounds Including a Superhero Dispatch System
The Stripe recruiter reached out saying I could interview for L3, so I figured I'd give it a shot. It wasn't like I absolutely had to go, though, because I'd heard it's really cutthroat. In the end I didn't pass, and it stings a bit — I still feel like I have something to prove. So I wanted to turn that frustration into an interview writeup to help everyone out. Two of the rounds were pretty new…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — New AI Coding, Debug, and Integration Questions
Kind of speechless — I ran into new questions on both the integration round and the debug round, and I also got to try out the newest AI coding format. This was for the Java track. AI coding: In HackerRank, there's an AI chat box where you write prompts based on the requirements to get the code solved. If you try to write it by hand yourself, there's about an 80% chance you won't finish in time —…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — OA, a Great Recruiter, and a Tree-Rendering VO Where I Finished Two Parts
I got the OA the same day I applied, probably a mass send-out. It was almost entirely a math problem, three parts in one hour, and the time was a bit tight. Part 1: Data Center Registration and Health State Management Part 2: Computing the Haversine Distance Part 3: Proximity-Based Routing A few days later I got the usual HR call. They said I did well on the OA, and asked me to briefly go over my…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — OA with the Deployment Window Scheduler, Part 2 Unfinished
This was the OA round. It's the Deployment Window Scheduler problem that has already been posted on the forum. Build a deployment-window scheduler over a recurring 10,080-minute week. Find all deployable time slots. Part 1: the input is <startTime, endTime, type>, where type is either allowed or freeze. Output the deployable time slots <startTime, endTime>. Part 2: the first line of the input is…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — Passport Validation Form Coding Exercise
This problem is basically a passport number validation form. You're given an object that looks something like this: Where L means letters only, D means digits only, and A means alphanumeric (letters or digits). Part 1 – Create a layout. Add a selector with the countries (from the object) as options; add a passport number input field; add a validate button. Part 2 – Create a validate function that…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience: practical coding, design, and project discussion
After a recruiter introduction, I had two long assessment interviews that blended coding and system design. One focused on practical implementation rather than LeetCode, while the other covered system design. The questions felt intended to resemble real engineering work instead of trick puzzles. After I passed that stage, the process became a longer loop. In an integration coding session, I worke…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — Reconciliation, a requests 307 Bug Squash, BikeMap and an AI Exercise, No Offer
Payment / Invoice Reconciliation (problem as I reconstructed it) Part 1: match by the invoice ID in the memo. Parse the payment and invoice strings, use the invoice ID in the payment's memo to find the matching invoice, and return the string the problem specifies. A payment has a payment ID, an amount and a memo; an invoice record has an invoice ID, an amount and a due date. Part 2: add amount ma…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — Three-Part OA on Data Center Routing
Online Assessment Part 1: Data Center Registration and Health State Management Need to implement the following two commands: REGISTER <region> <latitude> <longitude> <capacity>: registers a data center, with a default health state of healthy. SET_HEALTHZ <region> <state>: sets the health state of a given data center (true for healthy, false for unhealthy). Validation rules: Latitude must be in th…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — Three Parts of a KYC Validation Problem
KYC, but verifying things like the company name, URL, abbreviation, and description. The first part was to check whether there was a business name. Skip entries without one. For entries with a name, check whether the remaining columns all have values. If they do, it's verified; otherwise, not verified. The output is verified/not verified and the name, one line at a time in input order. The second…
Interview experiences · Stripe
Stripe Software Engineer Interview Experience — UTC Deployment Windows and a 10-of-11 Assessment
Stripe's online assessment really required a huge amount of code, and the problem was both tedious and long. The problem gives a global UTC timeline covering the 10,080 minutes in one week, along with deployment rules defined in local time. The rules mark deployment as allowed or frozen and each has a corresponding time-zone offset. The task is to find and return the first K qualifying UTC deploy…
Interview experiences · Stripe
Stripe Software Engineer interview: incremental 60-minute assessment
The online assessment was difficult in a particular way: it had multiple parts that built on one another. The full window was 60 minutes, and I was racing the clock while implementing each piece in sequence. I did not advance past it. The assessment seemed designed to mimic real engineering flow, with each section unlocking the next. Once I fell behind, there was little room to recover because la…
Interview experiences · Stripe
Stripe Software Engineer interview with coding, bug squash, API integration, and BQ rounds
After finishing an online assessment, I moved to a coding test that was described as very similar to the previous one. That led to more coding and then a series of work-style rounds: bug squash, API integration, and a BQ round. The process kept adding variety while staying tied to practical engineering work. The later stages seemed designed to test real-world debugging and API work, not just isol…
Interview experiences · Stripe
Stripe Staff Software Engineer Interview Experience — Feature Flag Design and an AI Coding Round, Rejected
I applied for the staff software engineer role. I'm not very strong, and I got rejected very cleanly. After the recruiter screen, they scheduled two rounds of a mini onsite (60 min * 2). The first round was system design. The question was to design a feature flag system, similar to Amazon WebLab. Because I hadn't prepared for it, and I had no systematic approach to open-ended questions, I got stu…
Interview experiences · Stryker
Stryker Account Executive interview: case and director sequence
The process was organized from the start. I went through HR, a manager conversation, a Gallup interview, and an on-site business-case stage with two interviewers. That was followed by a discussion with a director. The Gallup interview and the case were the demanding parts. During the on-site case, I felt real pressure and understood that they were watching how I performed in that format. Still, e…
Interview experiences · Stryker
Stryker Account Executive interview: HR questions and a personality screen
The first HR interview was focused and practical. I discussed strengths and weaknesses, why I wanted to join Stryker and why I'd left previous jobs. The recruiter explained that moving forward would mean several more conversations. After that, I met recruiters and hiring managers, completed a personality screen and had further meetings with the people I'd report to. The sequence felt as though it…
Interview experiences · Stryker
Stryker Account Executive interview: intimidating territory-manager conversation
I began with the territory manager, which felt unusual to me for a medical-sales role. The tone was intimidating. I felt pressed on how hard they needed someone to work, and it came across as condescending compared with conversations in my current work. The questions themselves were straightforward and not overly complex, but the vibe threw me off early. As the process continued, the direct, no-n…
Interview experiences · Stryker
Stryker Software Engineer interview: administrative talent call then manager video
My first step was a talent-acquisition phone call. It was not really technical. We covered administrative and logistical points such as role details, salary range, and similar practical checks. After that, I had a video technical interview with the manager. The tone did not work for me from the beginning. The early talent-scout call never explored my overall background or motivation; it stayed na…
Interview experiences · StubHub
StubHub Senior+ Fullstack Software Engineer II Interview Experience — HR Downgrades the Role, Then an OOD Recommendation Engine
Position: Fullstack Software Engineer II Experience: 7 years YOE Interview with HR: First I had a call with HR, who mostly talked up how small the company is, how big each engineer's scope is, and how they acquired Viagogo in Europe and are working hard to expand. Then they asked me to walk through a project I'd led before. I had originally applied for a Sr. SDE role — I have 7 years of experienc…
Interview experiences · StubHub
StubHub Senior+ Software Engineer Interview Experience — Rejected After Onsite With No Feedback
Coding round: Open discussion about how to improve the recommendation. System design Design an internal chat system for StubHub that also has the ability to send notification emails to customers who haven't logged in for 10 days. Result Two days later I got a notification from the recruiter that I'd failed both the coding and system design rounds. No detailed feedback. For the coding round, I fin…
Interview experiences · Stubhub
Stubhub Software Engineer: 90-Minute CoderPad Interview Cut Short
My process felt rough and uncomfortable from the beginning. I was put straight into a coding exercise on CoderPad with little introduction, and the session became stressful quickly. It was supposed to run for 90 minutes, but the interviewer ended it after about 30 minutes, even though I believed I had solved the problem. The interview atmosphere made things harder. There was a lot of outside nois…
Interview experiences · Stubhub
Stubhub Software Engineer: email-system design and an early coding cutoff
My process started with a friendly recruiter screen about my background and previous work. I could tell the recruiter was listening for specifics, and we went past the scheduled time because I kept adding context. A couple of weeks later, I still hadn’t heard back, and I eventually received an automated rejection. The technical rounds focused more on practical engineering ideas than on algorithms…