real interview stories, told over a cup of tea ♡
Glean (CA) Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
7 results
- Glean (CA) Backend Engineer interview: rejection after system designGlean (CA) · Backend Engineer · Other · May 2026Rejected
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…
- Glean (CA) Software Engineer interview: difficult DSA problem-solving screenGlean (CA) · Software Engineer · Technical Screen · May 2026
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…
- Glean (CA) Software Engineer: practical coding and system design onsiteGlean (CA) · Software Engineer · Technical Screen · Mar 2026
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…
- Glean (CA) Solutions Engineer hiring manager interview rescheduledGlean (CA) · Solutions Engineer · Other · Mar 2026
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…
- Glean (CA) Backend Engineer interview: multiple one-hour DSA roundsGlean (CA) · Backend Engineer · Other · Feb 2026
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…
- Glean (CA) Software Engineer interview where timing decided the outcomeGlean (CA) · Software Engineer · Dec 2025Rejected
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…
- Glean (CA) Software Engineer interview with six rounds and a DSA setbackGlean (CA) · Software Engineer · Technical Screen · Dec 2025
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…