Real, anonymous reports from people who interviewed for Software Engineer at Glean (CA), newest first and distilled into what to expect across the loop.
I went through a fairly standard Glean software engineer process: a recruiter conversation, then multiple coding rounds, followed by a system design round, and finally a wrap-up discussion with the hiring manager that covered my past work along with a bit of additional technical/system design conversation. The whole sequence felt straightforward and not overly chaotic—just a clear progression from coding to higher-level thinking.
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 generic LeetCode. It was still grounded in DSA knowledge, but what stood out was how much it leaned on problem-solving under the structure of their prompt.
The interview process typically starts with a recruiter conversation, followed by multiple technical rounds, including coding and system design, culminating in a discussion with the hiring manager. The overall sequence is clear and straightforward, although some candidates experienced delays or communication issues.
Candidates face multiple coding rounds that often include LeetCode-style problems, with difficulty levels ranging from medium to difficult. These rounds assess not only problem-solving skills but also the ability to communicate thought processes and adapt solutions in real-time.
The system design round is a critical stage in the interview process, often viewed as a high-stakes evaluation point. Candidates reported that this round required a deeper understanding of design principles and was a common point of rejection.
Interviews often include behavioral questions that assess cultural fit, focusing on past experiences and motivations. The tone of these discussions can vary, with some candidates feeling that their backgrounds were undervalued, particularly if they came from larger companies.
Candidates noted that many rounds, especially the coding and system design, demanded sustained focus and high-quality execution under time constraints. This aspect was crucial for success, with several candidates reflecting on the need for better performance in these high-pressure situations.
Communication throughout the process varies; while some candidates experienced responsive interactions, others faced delays or a lack of follow-up after interviews. This inconsistency can impact the overall candidate experience significantly.