Interview Experiences

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

Share yours, earn XP

153 stories

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

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
GoogleData ScientistSenior+
Nov 2025

Rejected Everywhere Else Before Landing an All-Strong-Hire DSR Offer

I've read some experience posts on the forum before, and this is my way of giving back — my first post, sharing some of my own experience here. Some background first: I'm at a big company, I've been coasting for several years, and I felt like I was wasting away, so I planned to switch jobs earlier this year. It didn't go well though — I got rejected at the hiring manager round, then coding/SQL ro…

OfferOnsite0
GoogleSoftware Engineer
Nov 2025

A Behavioral Screen on Team Leadership, Answered via Scrum

Was it last month or the month before? The interviewer was young. The main questions were: Talk about one of your projects Some hypothetical questions around team playing and leadership — for example, if you were the team lead, how would you handle someone on the team blowing past a deadline, or how would you assign roles when the team runs into a new problem that nobody on the team is familiar w…

Technical Screen0
GoogleSoftware Engineer
Nov 2025

Right-Side View BFS, Then a Pure Behavioral Round

R1: Technical interview. The interviewer was a senior frontend engineer. We did a bit of small talk up front, then went straight to the coding link. Q1: Given a binary tree, output all the nodes visible from the right side. I used BFS — each round, take all the nodes at the current level, output the last one, then push all the nodes of the next level into the queue. Q2: Given two arrays arr1 and…

HR Screen0
GoogleData Scientist
Oct 2025

A Two-Part Invoice Matching Coding Screen

We started with quick self-introductions on both sides — no deep-dive project questions. Then came two coding questions built around a single scenario; the questions and the amount of code involved weren't trivial. At the end I got to ask the interviewer some questions. Q1: Given the invoice ID inside a payment's memo, find the matching invoice in the invoice list and output the result. My approa…

Technical Screen0
GoogleSoftware EngineerNew Grad
Oct 2025

A Wordle-Style Word-Guessing Coding Problem and a BQ Marathon

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

OnsiteXP0
GoogleSoftware EngineerNew Grad
Oct 2025

Rejected the Same Night After Round 1

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

RejectedTechnical ScreenXP0
GoogleData Scientist
Oct 2025

Two Back-to-Back Screens, No Coding

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

Technical ScreenXP0
GoogleData Scientist
Oct 2025

Four Technical Rounds, One Interviewer Showed Up Late and Never Apologized

Overall the interview questions were pretty hard, but the interviewers were mostly friendly and did a good job guiding you along (except for one round). Google's interviews feel hard to prepare for — unlike Meta, which has a ton of interview writeups floating around. I think it really comes down to what you've built up over time. Technical: Statistics Question 1: Assume we have a sample with 100…

Onsite0
GoogleData Scientist
Oct 2025

Phone Screen Plus Five Onsite Rounds, Passed HC

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

OfferOnsiteXP0
GoogleData Scientist
Oct 2025

SQL, Metrics, and Modeling Across Two Rounds

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

In progressTechnical ScreenXP0
GoogleData Scientist
Oct 2025

Two Case-Study Rounds, No Coding, Rejected After 3 Days

Round 1: Measurement & Modeling Concepts A case study: Google Meet has a big customer who complains that meetings keep dropping/disconnecting. They ask how you'd analyze and solve this problem, how you'd put together an analysis plan, and how you'd estimate the impact. If it's affecting retention, how do you build a model to predict retention (contract renewal)? How do you evaluate models, what a…

RejectedTechnical Screen0
GoogleData Scientist
Oct 2025

A Brutal CRR SQL Question with LAG and 4-5 CTEs

This isn't a super fresh write-up, but while I was prepping I noticed there weren't many Data Scientist interview experience posts here, so I'm sharing mine. First was the HR phone screen — we talked a bit about projects I'd worked on before and they asked about my SQL and Python experience. I passed and got scheduled for the first round. The first round had two sessions: they said it would be on…

RejectedTechnical Screen0
GoogleData Scientist
Oct 2025

Five Rounds Covering Stats, Modeling, R, and a Battery-Life Case Study

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

OnsiteXP0
GoogleData Scientist
Oct 2025

Second-Round Onsite, One Interviewer Cancels via Late-Night Email

About a month or two ago I did my first round, which had two sessions, but I honestly don't remember what was covered. I guess I didn't do well, because there was no follow-up. Last week I suddenly heard that I'd be moving on to a second round. The second round was supposed to have three sessions, but the interviewer for one of them wasn't available and canceled on me by email in the middle of th…

In progressOnsite0
GoogleEngineering Analyst
Oct 2025

Trust Team Onsite, Two SQL Rounds and a BQ

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

OnsiteXP0
GoogleData ScientistSenior+
Oct 2025

Cold-Called Into the DSR Track, All Strong Hire

I'd read a small handful of interview reports, and even those helped a lot. A bit of background first: I'm at a big company, I've been coasting for a few years, and it started to feel like I was wasting my time, so at the start of this year I decided to look for a new job. It wasn't smooth — I got rejected by hiring managers, rejected on coding or SQL, rejected at onsite, rejected at the final ro…

OfferOnsite0
GoogleSoftware Engineer
Oct 2025

A Sliding Window Question I Couldn't Crack

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

Technical ScreenXP0
GoogleSoftware Engineer
Sep 2025

Cracking the 111-Statement Personality Screen

Google has recently started requiring candidates to fill out a kind of psychometric test that checks their tendencies and behaviors in a work environment — things like communication style, collaboration, and problem-solving ability. This helps them judge whether a candidate has the knowledge, skills, and abilities needed to succeed at the company. Because of the sheer volume of applications they…

HR 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