READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 49 of 153
Interview experiences · Citadel
Citadel Software Engineer Interview Experience — Two First Rounds and Progressive Matrix Questions
I asked a lot of people, and they all said they had two first-round interviews. I received both as well, but I did not make it to the second round. The first one: I was asked only one question: share some especially difficult problems you worked on recently and explain them. For the coding portion, a prefix tree or trie was enough to solve it. The question was very similar to a search suggestion…
Interview experiences · Citadel
Citadel Software Engineer Interview Experience — Two OA Problems I Couldn't Solve Optimally
I wrote up my Citadel interview experience around this time last year too, and it was pretty easy back then. This time I got the OA invite and just went ahead and did it, and I ended up not finding the optimal solution for either problem, haha. If anyone has ideas, let's discuss. Problem 1 Given an array arr of n integers, for a triplet of 1-based indices i[1], i[2], i[3] (1 ≤ i[1] ≤ i[2] ≤ i[3]…
Interview experiences · Clipboard Health
Clipboard Health Account Executive interview: two sales-focused rounds
My process felt fairly straightforward compared with what I'd heard from other job searches. After applying, I completed two interview rounds. The questions were mostly sales focused, covering how I thought about pitching, handling sales scenarios, and presenting my approach. The interviews didn't feel overly technical or unusually difficult. What surprised me most was how manageable the experien…
Interview experiences · Clipboard Health
Clipboard Health Frontend Engineer, repository take-home and debugging follow-up
I went through a largely take-home-driven process that was somewhere between average and difficult. It usually started right after I applied and often ended with a rejection after little actionable feedback. For the automated or online take-home, I cloned a provided repository, often involving Node.js, NestJS, React, or a backend API, and built logic to calculate results in the style of "top work…
Interview experiences · Clipboard Health
Clipboard Health Product Manager interview with a ride-sharing pricing case study
After I applied, I received a case study in which I acted as a product manager at another ride-sharing company. The focus was finding an optimal pricing strategy. I had to submit the work before moving to the next step. After I turned it in, I had an interview that went deeply into what I’d written, especially the reasoning behind my decisions. The interviewer seemed interested in stress-testing…
Interview experiences · Clipboard Health
Clipboard Health Product Manager interview: written case study followed by quantitative follow-ups
Right after applying, I received a lengthy case study and had to submit my reasoning in writing. It wasn't a short prompt. I spent real time analyzing it and preparing a document that explained my approach and the steps I took. After submitting the write-up, I was invited to interview. During the live conversation, the interviewer pressed me with follow-up questions that weren't fully covered in…
Interview experiences · Clipboard Health
Clipboard Health Software Engineer interview: assessment-first process with documentation review
I interviewed for a Software Engineer role through an assessment-first process that moved quickly into interviews. The first step was a coding and logic assessment. If the results looked promising, I was scheduled for later interviews. In one interview, we discussed what I had done in the take-home assignment and how I had approached the problem. I then completed another documentation-style asses…
Interview experiences · Clipboard Health
Clipboard Health Software Engineer interview with a timed technical PR assessment
I went through a mostly take-home and async process, and I never really spoke with engineers. The evaluation felt opaque. First, I received emails with a repo-linked task and had roughly an hour to complete it, without any direct interaction with the company. In another step, I was given a GitHub repo and a repo or PR-style task. The focus was on the backend or frontend depending on the role, and…
Interview experiences · Clipboard Health
Clipboard Health Software Engineer interview with PR and TDD work
I interviewed for a Software Engineer role through a difficult, multi-step technical process. It included pull request work and written technical thinking before I was turned down. I submitted code through a pull request and then had a follow-up interview that referred to a technical design document. I completed a TDD-style write-up for a feature and then went through another PR or related assign…
Interview experiences · Clipboard Health
Clipboard Health Software Engineer interview with two API scripts
I interviewed for a Software Engineer role with an overall average difficulty. I spent a short burst writing scripts and then waited. For the assignment, I wrote two API scripts after being brought into a process that referenced "top workers/workplaces" data. I submitted them and waited. Afterward, I had a follow-up interview where they reviewed what I produced. I didn't receive an offer, and I'm…
Interview experiences · Clipboard Health
Clipboard Health Software Engineer take-home PR review
I completed an async take-home PR-style submission. I cloned the repository, followed the specification, created a pull request, and submitted it. The review felt abrupt, and the feedback didn’t clearly explain what I should change. I received a rejection citing "attention to detail" and saying that I hadn’t followed the task requirements, but it didn’t include specific pointers. I didn’t move fo…
Interview experiences · Cloud Big Data Technologies
Cloud Big Data Technologies Software Engineer Interview: A harder onsite coding round
I went through a Google-style, DSA-heavy loop that became much harder at the onsite level and ended in rejection. I passed the recruiter or phone screen, where the bar felt lower and the focus was role fit and coding ability. I then completed multiple DSA and coding interviews in a standard LeetCode-style format, with follow-ups about optimizing or implementing similar solutions. At the onsite, t…
Interview experiences · Cloudflare
Cloudflare Account Executive interview with a mock discovery call
From the recruiter call onward, the process moved quickly, though it was also confusing at times. I met multiple interviewers, including hiring managers and people from different functions. Some of them seemed impatient, as if they were looking for a specific "sales-ready" trait instead of trying to get to know me conversationally. The recruiter was nice, but the introductions and context weren’t…
Interview experiences · Cloudflare
Cloudflare Account Executive interview with manager call and sales role-play
I started with a manager call, followed by a second-stage sales role-play. Product knowledge mattered a lot, and I needed to know Cloudflare's products well to do well. The role-play didn't feel like an easy warm-up. It was a genuine evaluation of how I thought and sold. The process was tough for me. I didn't move on after the sales role-play, so it ended earlier than I'd expected. My impression…
Interview experiences · Cloudflare
Cloudflare Frontend Engineer interview with a repeated system design round
I went through an extensive sequence that started with conversations with the hiring manager and engineering manager about my background, then moved into several live coding and architecture or system design exercises. The later technical stages included an "orange cloud" behavioral interview, PM and cross collaboration rounds, and a final C-level executive conversation about why I wanted the job…
Interview experiences · Cloudflare
Cloudflare Software Engineer Interview Experience — HM Chat, HR Screen, Then a Key-Value Store Round Where AI Wrote My Crypto
The HM round was basically both sides chatting about background. The HM gave a lot of intro about the team — the team mainly uses Go. HR screen, about two weeks later. They walked me through the interview process and collected some info about my relevant experience, but it was mostly them introducing the interview and what the team does. Scheduled for about a week after that. I could use search,…
Interview experiences · Cloudflare
Cloudflare Software Engineer Interview Experience — Two-Month Wait, Then Advanced to Technical the Same Night
I applied in mid-September. I got an HR outreach in late November, and this week (early December) I had my interview — the first round was with the hiring manager. They mainly asked experience-related questions: Why Cloudflare Do you have any experience using Cloudflare products? Introduce a recent project Technical details of the project Have you ever contributed to any production code? Have you…
Interview experiences · Cloudflare
Cloudflare Software Engineer interview with Battleship coding and Austin office tour
My process took long enough that it started to feel like the goalposts were moving. It began with a hiring manager call, followed by a live coding round where I built a Battleship-style game. Then came a larger loop with an "orange cloud" behavioral interview, a debugging discussion, a system design conversation, and a PM-focused interview. I also had another hiring manager conversation that incl…
Interview experiences · Cloudflare
Cloudflare Solutions Engineer: missed interviews and scheduling problems
My process started normally enough with an interview with the hiring manager, followed by a live coding round that was scheduled for later. The people involved on the technical side seemed cool and friendly. I wasn't as nervous as I expected because the interviewers were engaged and explained what they worked on. The recruiter and coordination side made the experience much harder. There were sche…
Interview experiences · CloudKitchens
CloudKitchens Software Engineer Interview Experience — In-Memory Cloud Storage Coding Question
This was a bit different from the other report on this same file storage question. The first two parts were about the same: create a file, create a user. The third part was about adjusting capacity — when you reduce a user's capacity, you need to consider deleting the largest-size files. The fourth part was about compressing and decompressing a file. One thing to watch out for: Level 2's requirem…
Interview experiences · Cockroach Labs
Cockroach Labs Software Engineer Interview Experience — Time Based Key-Value Store and a Choose-Your-Own System Design
LeetCode 981: Time Based Key-Value Store Design a timestamp-based key-value store data structure that supports set(key, value, timestamp) and get(key, timestamp). It tests whether you can bring down the time complexity of get by optimizing the data structure. The recommended direction is a hash table combined with arrays (e.g. unordered_map<string, vector<pair<int, string>>>), using binary search…
Interview experiences · Cognitiv
Cognitiv Software Engineer Interview Experience — High-Bar Technical Screen, Rejected Over Spark and C#
Cognitiv is a small startup that works with ads data. They were opening a new office in Canada, so they were hiring. After the recruiter interview, the first round was scheduled with the hiring manager. They asked BQ questions along with technical experience questions related to what the team needed — things like how to handle data duplication, Spark-related questions, how to scale data... If you…
Interview experiences · Cohere
Cohere Software Engineer Interview Experience — Rejected at the ML System Design Round
I interviewed for a role on the agent platform team. The process was: OA -> HM call (behavioral) -> system design -> VO (two rounds of debugging and coding). The OA was basic Python string parsing. The only tricky part was the last question, where the argument you're passed is callable — you need to print the function's name, its input/output format, and the expected result. You need to know whic…
Interview experiences · Coinbase
Coinbase Data Scientist Interview Experience — Case Study, SQL, and a Live Python EDA Round
Part 1: case study plus SQL and Python. The case: an e-commerce company wants to send personalized emails to boost conversion rate. How do you measure success? It was basically the standard A/B test process — define the metrics, figure out how to calculate the sample size, all of that. There was a follow-up at the end: suppose we ran the experiment and saw conversion rate go up 20%, we thought it…