Glean Machine Learning Engineer interview questions

3 Machine Learning Engineers have shared notes from their Glean interviews, with the questions they were asked in each round. That is 30% of the 10 Glean interview notes on Screna AI.

3 Machine Learning Engineer interview notes

Glean·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
Did an ML design round at Glean for an MLE role. One question, 60 minutes, focused entirely on computing employee-to-employee distance. Not a ton to say but it was a solid problem that made me think harder than I expected.
  • Design a system to compute the distance between any two employees in an organization.

“This sounds like a graph problem at first and I went straight to org chart traversal, but the more we talked the more it became clear they probably wanted something richer than shortest path on a hierarchy tree.”

View Post

Glean·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Coding screen for an MLE role at Glean. The problem was graph-flavored but dressed up as a train scheduling puzzle, which threw me off a bit at first. Decent interview overall, felt like they wanted to see how you think about reachability and complexity rather than just code.
  • You're given a train schedule as a list of trains, where each train is a list of station names and the index represents arrival time. Implement a function that returns whether a passenger can travel from a start station to an end station, given that passengers can transfer between trains at shared stations even if they arrive at different times (i.e. they can wait). Follow-ups include discussing complexity, finding shortest travel time with wait, and finding all reachable stations from a given start.

“My first instinct was to just do a DFS over stations, but the waiting mechanic made me second-guess myself for a minute.”

View Post

Glean·Machine Learning Engineer·Take-home Assignment

Apr 2026
Glean gave me a 75-minute AI-assisted coding assignment for an ML Engineer role. The task was interesting on paper but I spent way too much of that time just trying to understand what Cursor had even generated.
  • Build a Wikipedia crawler that prioritizes unvisited first-letters of page titles across the alphabet, then falls back to random crawling once all 26 letters are covered. Must respect a rate limit. You can use AI coding tools like Cursor or Claude Code.

“The core idea is clever.”

View Post