Interview Experiences

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

Share yours, earn XP

7 stories

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

Glean (CA)Software Engineer
Reported May 2026

Glean (CA) Software Engineer interview: difficult DSA problem-solving screen

My process started with a recruiter reach-out where we talked through the setup and the overall interview process. After that, I had a technical screen that felt more "in-house" than a generic LeetCode interview. It still relied on DSA knowledge, but the prompt put more emphasis on problem-solving within its structure. The question required me to apply data structures and algorithms. I could tell…

Technical Screen0
Glean (CA)Backend Engineer
Reported May 2026

Glean (CA) Backend Engineer interview: rejection after system design

I interviewed for a backend focused role and was rejected after the system design round. The early stages weren't where the process ended. The later system design evaluation was the point at which I didn't make it through. The overall sequence matched what I'd heard from friends: a fairly consistent process that eventually led to the same system design stage. That round felt high stakes. The earl…

RejectedOther0
Glean (CA)Solutions Engineer
Reported Mar 2026

Glean (CA) Solutions Engineer hiring manager interview rescheduled

My process started well. The team was responsive early on, and after the initial setup, everything seemed to move smoothly. During the hiring manager portion, though, the interviewer joined about 55 minutes late, which forced a reschedule. I completed the interview after that, but then I never really heard back from the recruiter or hiring manager. I followed up multiple times and received no sta…

Other0
Glean (CA)Software Engineer
Reported Mar 2026

Glean (CA) Software Engineer: practical coding and system design onsite

A recruiter reached out to me, and the first technical screening round involved a middle-to-hard LeetCode-style problem. After that, I moved into an onsite loop with three rounds: two coding rounds and one system design round. One coding round involved another LeetCode-style problem. The other was more open-ended and practical. I spent most of the time coding while the interviewer checked in only…

Technical Screen0
Glean (CA)Backend Engineer
Reported Feb 2026

Glean (CA) Backend Engineer interview: multiple one-hour DSA rounds

I started with an introductory round with the hiring manager and then met with the head of engineering. After that came multiple coding and DSA rounds, each lasting around an hour. The setup felt condensed but clear. They moved from conversation into hands-on technical evaluation pretty quickly. The process was described as difficult, and the structure reflected that. Instead of one challenge, I…

Other0
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
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

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