READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 50 of 153
Interview experiences · Coinbase
Coinbase Senior Data Scientist Interview Experience — SQL, A/B Test Design, and a BTC Volatility Case
Background: Bachelor's degree in China + Master's in the US, Statistics / Data track 3+ years of data analysis / risk-control experience (mostly finance-related) Applied for: Data Scientist – Risk / Product Analytics (remote) Overall Process HR Screen → SQL & Stats → Product Case → Hiring Manager → Team Fit The whole process took about 4 weeks. Not super fast, but the feedback at each stage was p…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — A 45-Minute Phone Screen Building a URL Shortener
Sharing my backend phone screen with Coinbase. The process was a recruiter call, then the phone screen got scheduled about a week later, 45 minutes long. The question was to build the core logic of a URL shortener service, with the following requirements: Support generating short links Support automatically redirecting when a short link is visited Short links need an expiration time Concurrent ac…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — A Coding-Heavy OA on the Cloud Storage Problem
I just finished Coinbase's OA. Overall I felt the problems weren't that hard, but there was a huge amount of code to write. If you hadn't prepared for it ahead of time, I don't think a normal person could finish the whole thing on first sight. This kind of test is honestly ridiculous, damn it — it really feels like they're just hunting for code monkeys. The problem was the cloud_storage one that'…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — Crypto System Design, a Handwritten Iterator, and a Food Delivery Coding Round
Virtual onsite: System Design -> Pretty much the same as a version of this question that's been reported before. It's designing a crypto currency trading system, with a third-party exchange, using a sync API to interact with that third-party exchange. I had prepared something similar before. But the interview still had some stumbling — I felt my understanding was a bit off, and only figured it ou…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — Four Onsite Rounds, Mostly Production Code Not LeetCode
This company's interview format is pretty different from everywhere else, so it's worth writing up on its own. Of the four rounds, only one was a traditional coding round in the usual sense — the rest were all "here's a small requirement, write code that could ship to production." They use their own online environment, where you can run tests and also look things up in the docs. So pure template…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — Mempool Block-Mining Problem in the First Technical Round
A former coworker referred me, and HR contacted me about three weeks later. The first round was technical. Part one Cryptocurrency "mining" is the operation where a "miner" places "transactions" in a candidate "block". Each block has a fixed size B = 100. At any point in time there is a set of transactions available for mining in an unordered array called the mempool. A transaction can be describ…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — OA Full Marks, Then Rejected After the Virtual Onsite Coding Rounds
OA was a geography question. I solved all 4 questions and got a perfect score. VO BQ — not like a normal BQ, more like a conversation. The interviewer dove deep into how I'd improve my projects. I don't know why, but after about 20 minutes he seemed to lose interest. He asked if I had any questions for him. After I asked, he went back to asking me about projects where I used a lot of different ap…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — Rejected After Onsite Over a Debugging Nitpick
Round 1: crypto order system, pretty similar to other write-ups already on the forum. I had to parse the input myself and write my own test cases. I got to level 2 — after I finished the tests, the output had no issues, but I wasn't given level 3. Round 2: the "generate NFT" question, also already posted on the forum. Also had to define and parse the input myself — I used JSON. I finished the fir…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — Stuck on Debounce in the Autocomplete Round
Technical phone screen (1 round) It was a pure whiteboard-style coding round — I had to implement an autocomplete feature for an input box. Requirements: debounce, async fetch, and rendering the results. Follow-up: support keyboard navigation (up/down arrow keys to switch), highlight the selected item, and submit on Enter. I got stuck right at the debounce part — I couldn't get the event handler…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — System Design, Two Coding Rounds, and a PIP I Didn't Mention to the Recruiter
HR: Basically just chatted about my general situation. But I didn't tell the recruiter that I'm no longer at Amazon — over the last year and a half I wasn't very proactive at my previous company, and I didn't really listen to my manager, and I got PIP'd in May. (Should I be more upfront with the recruiter about this? If I actually get an offer, will the company find out during the background chec…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — Three OAs, a Block-Mining Coding Round, and Two AI-Assisted Rounds
I heard Coinbase had layoffs today. Not sure how that'll affect hiring. Sigh, hope everyone's okay. The people I dealt with, including HR, were all really nice. Sharing my previous interview experience — the whole process. HR reached out asking if I wanted to interview with Coinbase (I'd applied 4 years ago but never went further in the process — they might still have had my info), so I went ahea…
Interview experiences · Coinbase
Coinbase Software Engineer Interview Experience — Two OAs and a 90-Minute Database Design Coding Test
There were two OAs total. One was a personality test and an aptitude test. The personality test had over a hundred questions, and some of them repeat — be careful not to contradict yourself between them. The aptitude test was very tight on time: figure relations, quantitative relations, vocabulary fill-in-the-blank, that kind of thing. It's hard to finish in time, so just guess when you have to.…
Interview experiences · Coinbase
Coinbase Staff Frontend Engineer Interview Experience — Four Onsite Rounds, Rejected on System Design
I interviewed in March. I couldn't find a virtual onsite interview writeup for Coinbase Frontend Staff level on the forum. There were four rounds total. The questions themselves weren't that hard, but the bar was high. Tech Execution: Write a dropdown component. I'd suggest looking at a UI library's props beforehand, something like Ant Design. In this round you need to pay attention to reusable d…
Interview experiences · Color Health
Color Health New Grad Software Engineer Interview Experience — AI-Assisted OA and Pair Programming
Color Health new graduate interview experience. Timeline I applied to this role twice. I received no response after the first application in mid-April. After applying a second time in late July, the recruiter reached out on August 5. August 7: received the online assessment. August 12: the recruiter replied that I had passed the assessment and scheduled a screening call. August 13: recruiter scre…
Interview experiences · Commure
Commure Software Engineer Interview Experience — HM Accused Me of Using AI
I applied online, and about a week later a recruiter reached out and set up a 30-minute meeting. It was pretty standard stuff — they just introduced the role. A bit more than a week after that, they reached out again: the next step was the HM interview. The HM's camera and mic both seemed to be having issues. The video was really blurry and the audio kept cutting in and out. He started by introdu…
Interview experiences · Composio
Composio New Grad Fullstack Engineer Interview Experience — AI-Assisted Take-Home Plus a One-Take Code Walkthrough Video
I'm an OSU CS master's student, graduating in December 2026. Process. It's on a platform called Litmus. You run litmus init and that starts a 150-minute timer that can't be paused. The problem: you're given an API catalog with a few hundred tools (each with full input/output JSON Schema), and you write a generator that automatically infers the dependency graph between tools — i.e. which tool's mi…
Interview experiences · Confluent
Confluent Account Executive interview and the IBM acquisition
I started with a recruiter conversation about how the recent IBM acquisition might affect hiring. The recruiter was transparent, but I came away with more uncertainty than clarity, especially about what the acquisition would mean for the day-to-day work in the Inside Sales role. In the later interviews, I kept asking for specifics: how the role fit into the larger sales organization, what the KPI…
Interview experiences · Confluent
Confluent Account Executive interview with a defense-sector role mismatch
My experience started with a recruiter who seemed supportive, but the initial description of the role, especially its stated focus on the defense sector, didn't match what I later heard from the interviewers. That mismatch made me wary of how clearly the role had been defined. Once I entered the interviews, it was hard to pin down the day-to-day responsibilities and scope. Both conversations star…
Interview experiences · Confluent
Confluent Frontend Engineer: JavaScript, React, and rolling-window data access
The process started with a recruiter chat and quickly moved into interviews tied to practical work instead of abstract puzzles. The recruiter call covered my background and expectations, after which I took a frontend coding challenge. That round focused on JavaScript and React. I also had a UI design discussion that moved into broader system basics before shifting to behavioral questions and team…
Interview experiences · Confluent
Confluent Senior Software Engineer Interview Experience — A Linux-Heavy Super Day With No Feedback
Role: Confluent - Senior Software Engineer - Cloud Traffic Screen: look up a word in a given file — each line of the document is one sentence. First find a word in the document, then as a follow-up find a phrase/sentence in it. Just talked through the approach at a high level; optimizing with a hashmap was enough. The feedback said I needed hints. VO (super day) — Specialty: intense grilling on L…
Interview experiences · Confluent
Confluent Senior Software Engineer Interview Experience — Passed Both Codings, Failed Both System Designs
The technical screening round overall was pretty simple. They give you a function query signature and have you determine whether there's a registered function that matches it. Later on this expands to cases involving optional arguments and variable number of arguments. The onsite had four rounds total. The first coding round was to implement something like printing the last N lines of a file, alo…
Interview experiences · Confluent
Confluent Software Engineer Interview Experience — HackerRank, Sudoku, Machine Coding and a DevProd Values Round
Online Assessment A 60-minute HackerRank test with 3 coding problems. Phone Interview (DSA Round) Verify Sudoku (check whether a Sudoku board is valid) Solve Sudoku Machine Coding Round Find word in a list of documents (find a specific word in a list of documents). Find Phrase in the same sequence they appear in list of documents (find a phrase in the list of documents, with the words in the give…
Interview experiences · Confluent
Confluent Software Engineer interview: LeetCode-focused technical rounds over several weeks
My interviews followed a fairly standard sequence of two or three steps. I started with an initial recruiter screen, moved into technical interviews, and later had a behavioral or manager-focused conversation. The period from my first interview to the final decision lasted a couple of weeks, while the rounds themselves were usually quick and back to back. The early stage was a coding-focused tech…
Interview experiences · Confluent
Confluent Software Engineer interview with a four-round virtual onsite
A recruiter reached out to me on LinkedIn, and the process started with a coding conversation with a senior engineer. That round went really well. I finished confidently, and the interviewer seemed genuinely impressed. What followed felt chaotic and stressful. I was moved into a virtual onsite almost immediately. It covered four rounds over two days, including coding, a hiring manager discussion,…