The interview process included:
The onsite portion was the most ridiculous, especially the two-hour assignment. Is it really fair to judge an engineer based on the amount of code produced in just two hours?
The interviewer in the coding round was pompous. He didn't know how to conduct an interview and seemed in a hurry to get over with the problem.
System design was related to the main engineering product they had built. This was a reasonable round, in my opinion.
The coding question was related to arrays or strings.
By the time the two-hour assignment arrived, I was mentally exhausted. It was related to task concurrency.
I had already made up my mind not to join them anyway. The office has horrible logistics and felt like a call center.
The following metrics were computed from 10 interview experiences for the Glean Software Engineer role in United States.
Glean's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having negative feelings for Glean's Software Engineer interview process in United States.