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

RipplingSoftware Engineer
Dec 2025

Onsite System Design on a Metrics Monitoring System, Passed

Unlike what I've seen in other write-ups on the forums, I don't know if they changed the question or if there are now two system design question pools for the onsite (Google News / a metrics monitoring system) — I got the monitoring system one. The gist was: collect some user behavior data, like installs / user clicks / etc, and it needed both a real-time view and collection of raw events for a b…

OfferOnsite0
GoogleData Scientist
Dec 2025

Rejected After Two Rounds of Stats and Causal Inference Questions

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

RejectedTechnical ScreenXP0
MetaData Engineer
Dec 2025

Missed the 3-for-3 SQL/Python Bar in a 25+25 Screen

I've actually been pretty happy at my current job and wasn't planning to switch. A Meta recruiter reached out to me a few times, so I figured I'd interview just to see how it would go. Technical round (25 minutes of SQL + 25 minutes of Python) I hadn't grinded LeetCode in a long time. The questions weren't too hard, but they were tricky. The interviewer spoke excellent English and gave me a lot o…

RejectedTechnical Screen0
Two SigmaData Scientist
Dec 2025

Nailed the Good-Pair Expectation Problem, Still Rejected

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

RejectedTechnical ScreenPremium0
PatreonSoftware Engineer
Dec 2025

A Wordle-Style Coding Screen Nobody Warns You About

Not a question from the forum, which surprised me — I'd seen people on the forum say the phone screen here is basically coding rounds, IC/manager rounds, rate limiter, shopping cart, that sort of thing. The problem was roughly a guessing-word game: given a guess word and a target word, mark the status of each position. green: the two chars at this index are the same yellow: the two chars at this…

Technical Screen0
MetaData Engineer
Dec 2025

25 Min SQL, 25 Min Python, and I Only Passed One of Each

I've been pretty happy at my current company and honestly wasn't planning to switch jobs. A recruiter from Meta reached out to me a few times, though, so I went into the interview with a just-try-it-and-see attitude. Technical round (25 min SQL + 25 min Python) I hadn't touched LeetCode in a long time. The questions weren't super hard, but they were tricky. The interviewer spoke excellent English…

Technical Screen0
GoogleSoftware Engineer
Dec 2025

Initially Rejected, Reopened by an HR Mistake, Then a Two-Round Virtual Onsite

Applied after getting a referral on 2025.10.01. Rejected on 2025.10.14. 2025.10.19 — Got an apology email from HR saying the application was mistakenly closed, and they sent me an OA. 2025.10.21 — Completed the OA. 90 minutes, two questions, the same ones that were already known online — very easy. 2025.10.23 — Got the invite for the first two rounds, scheduled for 10.30. 2025.10.30 — Round 1 tec…

In progressOnsite0
GoogleData Scientist
Dec 2025

My Strategy for Passing the Hiring Assessment Personality Test

As the first stage of the interview process, this one's pretty simple — but it would be a shame to get filtered out here. I looked through everything I could find online and combined it with my own experience to put together what I think is the most complete summary out there, to save everyone some time. Just read through this whole post and you should sail through it. What's the Google Hiring As…

Online Assessment0
Glean (CA)Software Engineer
Reported Dec 2025

Glean (CA) Software Engineer interview with six rounds and a DSA setback

I went through six rounds in total: one hiring manager round, two technical rounds, and three cultural rounds. By the later stages, it was clear they were evaluating more than coding, with a strong focus on overall fit. The technical work was difficult for me. I didn’t get past the first technical DSA round because I got tripped up by library differences and mixed up my C++ and Java knowledge whi…

Technical Screen0
StackadaptAccount Executive
Reported Dec 2025

Stackadapt Account Executive interview with shifting final rounds

My experience with the recruiter and recruiting manager was frustrating from the start because the logistics never felt stable. I was repeatedly told I'd be meeting one person, only for the meeting to change at the last minute. It became hard to keep track of who the actual hiring manager was, especially after I went through multiple rounds with people who all had the same title. I also received…

RejectedHR Screen0
PlaidSoftware Engineer
Reported Dec 2025

Plaid Software Engineer interview: CodeSignal OA and two technical rounds

My process started with an OA on CodeSignal, which was straightforward enough to complete. After that, I had a technical interview and a final round with a very specific rhythm: two technical interviews back to back, followed by one behavioral segment. The whole experience felt positive. The interviewers were genuinely friendly and engaged with my answers. They seemed interested in understanding…

OfferOnline Assessment0
StackadaptAccount Executive
Reported Dec 2025

Stackadapt Account Executive interview: 10-day project and presentation

The process felt more rigorous than I expected from the outside. After a recruiter screen, I interviewed with a Director about a week later. The conversation focused heavily on scenarios, and I also got deeper industry knowledge questions than I was ready for. The pacing and format changed as the rounds went on. Next was a project and presentation round with a Director and a Manager. I had 10 day…

OfferHR Screen0
IMCNetwork Engineer
Reported Dec 2025

IMC Network Engineer interview: modern C++ and multicast protocol questions

My process began with an asynchronous online interview and a technical test. The main technical portion started with a deeper discussion focused heavily on C++. It felt intense from the beginning. The interviewers were welcoming enough, but the questions went well beyond surface-level knowledge and dug into modern C++. I went through additional rounds, and the later stages became even more specia…

Online Assessment0
RemitlySoftware Engineer
Reported Dec 2025

Remitly Software Engineer interview with a six-week scheduling delay

Recruiter coordination set the tone for me. It took more than six weeks to make initial contact, and the interview timeline kept getting canceled, rescheduled, and then disappearing again. Even after I completed a recruiter screen, the next steps didn't move smoothly. I had to chase updates, and eventually the process went quiet. There wasn't much clarity about what happened after the early techn…

Technical Screen0
BrexAccount Executive
Reported Dec 2025

Brex Account Executive interview: timed prospecting and discovery role-play

I went through a recruiter screen first, followed by conversations with managers and a panel-style component. The process felt fairly standard for sales, with a clear sequence from one step to the next. The recruiting team communicated well, and the overall tone was professional. The people I spoke with were generally nice. The more intense part was the live sales work. I completed a timed, scena…

RejectedHR Screen0
Glean (CA)Software Engineer
Reported Dec 2025

Glean (CA) Software Engineer interview where timing decided the outcome

The interview process felt smooth from start to finish. The recruiter was responsive, and communication during the interviews went well. I stayed engaged and clear while working through the questions. The interview fell in the difficult range. The main issue was timing: I couldn't solve the question within the allotted time. The interview wasn't chaotic or confusing. It felt more like a performan…

Rejected0
RoktSoftware Engineer
Reported Dec 2025

Rokt Software Engineer interview with onsite coding, design, and leadership rounds

My process started with online aptitude and personality testing, followed by a behavioral evaluation and a one-way video interview where I recorded answers to a prompt. After those early steps, I was invited to an in-person onsite sequence with multiple parts. In the later rounds, the technical work shifted toward live problem solving and deeper evaluation. I worked through standard algorithmic c…

Online Assessment0
BairesDevFrontend Engineer
Reported Dec 2025

BairesDev Frontend Engineer interview with lengthy automated assessments

The process relied heavily on assessments, and it felt endless. Even after I completed the suggested tests successfully, there was no guarantee that I would reach the role. I found the funnel hard to trust, especially because the test materials and knowledge seemed outdated compared with the latest framework versions. Much of the process was machine evaluated. It started with a long block of prob…

No responseOnline Assessment0
DatavantSoftware Engineer
Reported Dec 2025

Datavant Software Engineer interview with debugging and system design rounds

The process started when a recruiter reached out on LinkedIn. I sent over my CV, completed an HR screening call, and then moved into debugging. The technical work focused on debugging code and getting the tests to pass. I got most of them through, but I ran out of time while trying to fix one of the last issues. I was surprised to receive an invitation to the next round after that time squeeze. T…

RejectedHR Screen0
DatavantSoftware Engineer
Reported Dec 2025

Datavant Software Engineer interview: debugging, coding, and system design

The process started with recruiter outreach. After a quick call about logistics and my background, I was invited to a coding round that focused entirely on debugging. We worked with a pre-existing file, and I passed that round, which moved me to an interview with the hiring manager. The manager was easy-going and spent real time answering my questions. They seemed distracted at the beginning beca…

No responseTechnical 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