Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4433 stories

Likes earn the author +10 XP for the first 3 likes each day

DoorDashSoftware Engineer
Apr 2026

Passed Coding, Failed the Project Deep-Dive

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
SalesforceSoftware Engineer
Apr 2026

Five Onsite Rounds, Every One Circles Back to Multi-Tenancy

Sharing my interview experience with Salesforce. My impression of this company is very different from consumer-product companies: the problems themselves aren't going for difficulty, but almost every round eventually circles back to "what if this system is shared by a lot of customers." Multi-tenancy, permissions, and configurability ran through the whole interview. There was also a whole round d…

Onsite0
MicrosoftSoftware Engineer
Apr 2026

Four Rounds, Best Vibe I Had All Year

Four rounds, overall a really relaxed vibe. Posting my Microsoft interview experience to give back to the forum. Bottom line up front: this was the most comfortable-feeling interview I had all year. The interviewers were pretty much all friendly, nobody tried to trip me up on purpose, and when I got stuck they'd proactively throw me a rope. The questions were medium difficulty, but they cared a l…

Onsite0
TransUnionData Scientist
Apr 2026

Video OA Then a One-Hour Technical Screen

Locked — open it to unlock the full story with XP.

Technical ScreenXP0
GoogleSoftware EngineerNew Grad
Apr 2026

Two Onsite Rounds, a Cross-Country Flight, and a Wait for Team Match

My R1 report is here. On Friday I finally did the R1 BQ that had gotten postponed earlier, and then HR reached out on Monday to schedule R2. I flew in from the Midwest to Mountain View, and after finishing R2, flew straight back — I was exhausted. Interview 1 Given an array representing a gold chain, where each number is the weight of one link. You need to remove one link, reconnect the chain, an…

In progressOnsite0
AttentiveSoftware EngineerNew Grad
Apr 2026

Coding and System Design Blended Into One 75-Minute Screen

It was 75 minutes long. They said it would be coding + system design, but in practice the two were mixed together, and the questions were pretty scattered and casual. The last 5 minutes were reverse behavioral questions, where I got to ask them things. The problem wasn't quite like a LeetCode problem — they didn't clearly spell out what the input was. They wanted me to design it myself and then j…

Technical Screen0
UberData ScientistSenior+
Apr 2026

Five Onsite Rounds, One a Surprise Clustering Question

Round 1: past project deep dive. Not much to say about this kind of subjective round. I feel like I explained it well, but that doesn't mean I won't still get rejected. Round 2, coding: we spent 25 minutes going over my resume. The coding question was: given an integer, find the next palindrome integer greater than it. I'd never seen this before. The question is pretty abstract — you can't even e…

Onsite0
BytedanceSoftware Engineer
Apr 2026

Content Moderation Design With an ML Infra Twist

Locked — open it to unlock the full story with XP.

OnsiteXP0
NotionData Engineer
Apr 2026

DAG Coding, an Xfn Chat, and a Brutal Data Modeling Round

Locked — open it to unlock the full story with XP.

OnsiteXP0
Garner HealthSoftware Engineer
Apr 2026

Scaling an Appointment Booking System

My Garner Health interview was a system design round. The first question was to design an appointment booking system where patients could search for doctors and book appointments. I discussed the core Patient, Doctor, and Appointment data models; how to query a doctor's available time slots; and how to book or cancel an appointment. The design also needed to prevent multiple patients from booking…

Technical Screen0
VerkadaSoftware Engineer
Apr 2026

Motion Thresholds Across Multiple Cameras

I could not answer Part 2 and was rejected. Part 1 — Single Camera Imagine that a camera installed in your building can detect motion. The camera outputs a stream of timestamps and a value indicating the motion intensity at each time. You collect this data and want to determine the periods when the motion was at or above a given threshold. Write a function that takes an array of sorted (timestamp…

RejectedTechnical Screen1
CohereSoftware Engineer
Apr 2026

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…

RejectedTechnical Screen0
FigmaSoftware Engineer
Apr 2026

Breezed Through the Legendary Layer Question, Blanked on the Easy One

A premium story — unlock it to read the full loop.

RejectedOnsitePremium0
UberSoftware Engineer
Apr 2026

A Tournament-Ranking Question and the Interviewer's Wrong Hints

The interviewer's tone was very friendly. For the second question though, I think it's genuinely hard to come up with if you haven't seen something like it before — the corner cases are rough. I went through about six months of interview experience posts and didn't see this question anywhere. It's not even in the LeetCode Uber tag. The problem: [1, 2, 3, 4, 5, 6, 7, 8] represents ranks, where a s…

Technical Screen0
PerplexityData Scientist
Apr 2026

A Stratified Sampling Coding Screen, Then a Next-Day Rejection

Locked — open it to unlock the full story with XP.

RejectedTechnical ScreenXP0
BobyardSoftware Engineer
Apr 2026

Five Rounds From a Take-Home to a Four-Person Panel Onsite

Five rounds total. Round 1 is about your resume and experience. They have a technical recruiter who asks about some tech details. They asked a few common coding questions: if you find the frontend is loading slowly, how do you fix it? If you find a prod bug, how do you handle it? Round 2 is a take-home project. They ask you to design the frontend, backend, and DB for a comment system, satisfying…

Onsite0
MetaSoftware EngineerSenior+
Apr 2026

E5 Full Loop with a Card-Deck AI Coding Round

Recruiter reachout came in late February. After that, every step got scheduled about a month out — the whole process moved at a pretty relaxed pace. Phone Screen LC 65 (medium; also the second question from a 12/4 compiled coding list on the forum). VO (virtual onsite) Coding: LC 121; LC 199 AI coding: a card deck problem BQ: favorite project (scope/complexity) / conflict resolution / moving fast…

Onsite0
GoogleSoftware Engineer
Apr 2026

A Stuck-Keyboard String Matching Question With Three Follow-Ups

Locked — open it to unlock the full story with XP.

Technical ScreenXP0
AmazonSoftware Engineer
Apr 2026

Four Onsite Rounds From Ride-Hailing System Design to a Pub/Sub OOD Question

Phone Screen Coding: Merge products by category. Given a bunch of tuples representing two products being in the same category, with transitivity, find how many categories there are in the end and the size of each group. Classic Union-Find — I solved it with BFS instead and it also passed. Onsite (4 rounds) System Design: Design a ride-hailing app. The core focus was on high-frequency GPS writes f…

Onsite0
UberSoftware Engineer
Apr 2026

Missed the OA's Iterative-DFS Trick But Still Advanced

Today's technical screen: 5-minute self-introduction, then 20 minutes of coding: Given a 2D grid with empty cells, robots, obstacles, and a target like [1, 1, 2, 2] — this represents each robot's distance to the nearest obstacle in the up, left, down, right directions respectively, indexed accordingly. Output a list of robot locations that fit this criteria. Then a 30-minute deep dive on one of m…

In progressTechnical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP