Interview Experiences

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

Share yours, earn XP

127 stories

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

GoogleBusiness Analyst
Reported Jul 2026

Google Business Analyst interview: technical screening and product communication

The interview loop felt fairly standard for Google, but I needed confidence at every stage. After speaking with a recruiter, I had a technical screen. The interviewer asked me to introduce myself, explain what I knew about the company and say why I wanted the role. We then moved to coding questions. The interviewer stayed relaxed as I worked. My impression was that they wanted me to keep steady a…

RejectedTechnical Screen0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview: varying difficulty and interviewer tone

One Google path started with an online assessment and then an interview if accepted. My question was LeetCode medium to hard, although I had heard that others received easier ones. My first interviewer was somewhat rude, which made it harder to stay comfortable and confident while working through the problem. I also encountered a recruiter-led path with a pre-interview stage followed by two short…

Online Assessment0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview: four scenario-heavy technical rounds

I expected a standard coding and behavioral loop, but Google put me through four technical deep dives that were much more scenario heavy. I presented a real customer issue, then completed a cognitive-analysis-style round that asked how I would begin thinking about large-scale infrastructure. The next technical discussions covered infrastructure or platform and AI-related problem solving. I was ex…

Technical Screen0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview

The process began with a background questionnaire and an online interview with DSA and behavioral rounds. The DSA question was practical rather than a typical LeetCode problem, and I handled it well. Later, the onsite questions were closer to LeetCode, a shift I had not studied enough for. A system-design mock also felt mismatched because its problem did not resemble what I saw later. Scheduling…

Technical Screen0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview: hardware panel and uneven technical difficulty

The interview focused on technical depth rather than only classic software problem solving. The panel was made up of hardware engineers, and the topics ranged across VLSI, analog work, and design engineering. It felt like a real technical discussion, and the interviewers seemed to engage with my answers instead of waiting for a memorized response. One question genuinely threw me off because it fe…

0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview: unclear live DSA communication

This interview was hard in a particular way. It was not only the complexity of the DSA questions, but also the interaction with the interviewer. I got directional array questions involving dynamic programming, though I could not clearly recall the full second part of the problem afterward. The interviewer did not speak clearly enough for me to ask clarifying questions effectively. I spent extra m…

Technical Screen0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview: compact developer algorithm loop

I went through a full-loop format with an online assessment and a recruiter call before the technical rounds. Once I reached the developer loop, I had to solve medium-to-hard LeetCode-style problems, and it felt designed to test real problem solving from start to finish. The structure became intense and compact after the earlier screening steps. The interview was essentially developers only, with…

Online Assessment0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview: referral, six coding questions, and support

A referral started my loop and moved me to a recruiter call sooner than I expected. The process then had three coding rounds, each with two LeetCode-style questions, a system-design interview, and a behavioral interview. The overall vibe sat in the middle: challenging but not cruel. In the coding rounds, I needed to solve cleanly, communicate clearly, and handle follow-ups instead of treating the…

Technical Screen0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer Interview Experience: A one-hour two-problem OA and eliminatory DSA rounds

This was a fast onsite-style process centered heavily on DSA. I started with an OA containing two data-structures-and-algorithms problems to solve in about an hour. The time pressure made it intense, and I noticed there was no audio or video proctoring. Then I went into the interview portion for the onsite opportunity. The interviews focused only on DSA, with medium-to-hard LeetCode-style problem…

Online Assessment0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer Interview Experience: Median of two sorted arrays and autocomplete design

I expected the technical rounds to be tougher, but the interview felt much easier than I thought it would. The first main question was finding the median of two sorted arrays, and I got through it fairly quickly. Then the conversation moved to a system-design problem about building autocomplete for a search engine. The coding questions were written in a shared document rather than an editor where…

OfferTechnical Screen0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview for a PhD ML-focused role with spam-classifier design

I interviewed for a PhD SWE, ML-focused role, and the first real test came in the first interview round. It combined an ML domain section with behavioral questions. In the ML part, I was asked to design a spam classifier and write pseudocode for a bi-gram model. My recruiter had told me the domain round would connect to my projects, but the questions were more design-focused than I expected. When…

Rejected0
GoogleSoftware Engineer
Reported Jul 2026

Google Software Engineer interview with four rounds and onsite C++ implementation

The process felt steady and not especially punishing. I started with a recruiter phone call and, about a week later, a technical screen. There were four interview rounds in total: two coding rounds, a behavioral round, and a system-design round. The coding was LeetCode-style medium algorithm and data-structure work, with the usual need to communicate clearly, get the code right, and think through…

Technical Screen0
GoogleSoftware EngineerNew Grad
Jun 2026

Three EU Onsite Rounds, Then Stuck in Team Matching

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

In progressOnsiteXP0
GoogleSoftware EngineerSenior+
Jun 2026

Three Coding Rounds, One BQ Round, and a Declined L3 Downgrade

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

WithdrewOnsitePremium1
GoogleSoftware Engineer
Jun 2026

Two Technical Rounds, Meeting Room II and Top K Variant

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

Technical ScreenXP0
GoogleSoftware Engineer
Jun 2026

A Cake-Splitting Binary Search and a Mahjong Hand Puzzle

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

In progressTechnical ScreenXP0
GoogleSoftware Engineer
Reported Jun 2026

Google Software Engineer interview: language-library technical round

A recruiter first reached out, then I had a scheduled technical round. Early on, the interviewer focused on a very specific library connected to the language I had chosen. I could not fully remember the details on the spot, and that threw me off. The process then expanded into several technical rounds: DSA interviews, a high-level design discussion, and a Googliness-style behavioral interview. Th…

Technical Screen0
GoogleBackend Engineer
Reported Jun 2026

Google Backend Engineer interview: behavioral detail and impact

I went through Google's behavioral and HR round for a Backend Engineer role, and it put surprising weight on the details. The conversation followed the familiar behavioral format: how I would respond, how clearly I could explain my thinking, and how I connected my experience to the kind of work Google cares about. I found that precision mattered more than simply sounding confident. I kept checkin…

HR Screen0
GoogleBusiness Analyst
Reported Jun 2026

Google Business Analyst data interview with DSA and modeling pressure

My first substantial technical step was data-heavy and more intense than I expected. The data interview included DSA and modeling questions, and the bar was reasoning under pressure, not just getting a final answer. One example looked like a simple arithmetic statement at first but was actually wrong, so I had to deal with that confusion while staying accurate. The interviewer continued with inte…

RejectedTechnical Screen0
GoogleResearch ScientistSenior+
May 2026

Three Research Chats and an Unexpected Rejection

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

RejectedOnsiteXP0

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