Glean interview notes, page 1 of 3

“The waiting mechanic is the part that trips people up.” The rest of the author's notes on Machine Learning Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the merge-from-the-back approach, which is fine but they clearly wanted more.” The rest of the author's notes on Software Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic backtracking problem and I knew it, but I still fumbled the visited-cell tracking for a second.” The rest of the author's notes on Software Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew 2048 as a game but had never thought about coding the move logic.” The rest of the author's notes on Software Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was Dijkstra but then I realized the waiting mechanic made it weird.” The rest of the author's notes on Machine Learning Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic backtracking, I knew it.” The rest of the author's notes on Software Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with just left-slide since that felt easiest to reason about, got that working, then tried to rotate the board to reuse the same logic for other directions.” The rest of the author's notes on Frontend Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The core implementation felt manageable once I mapped out the tile-shifting logic on a 4x4 grid.” The rest of the author's notes on Software Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This question sounds broad until you realize they want the whole framework, not just 'pick a metric.' I started with the north-star metric and worked outward, covering acquisition through retention, but I fumbled a bit when they pushed on causal inference.” The rest of the author's notes on Data Scientist interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This was a follow-up, so I was already a bit drained.” The rest of the author's notes on Software Engineer interview at Glean, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.