Glean (CA) Software Engineer interview: difficult DSA problem-solving screen

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 they were checking whether I could reason through the solution instead of recalling a familiar template. The difficulty was described as difficult, and it felt that way. I had to put in more effort than I expected after the recruiter conversation.

I wasn't offered the role, and I felt like I had to work hard for every bit of progress. The interview wasn't hostile, but the problem demanded stronger execution than I brought that day.

Location: South Korea. Overall feedback: Neutral. Offer status: No offer.