The process was super long and stretched out, which was to be expected based on what I’d heard online. I was very excited to get an initial response, then had to spend a few days coordinating over email with the recruiter. This involved filling out forms with information and providing lists of interview times that worked for me. Finally, the interview was scheduled for a week out.

The interview itself was straightforward, a one-on-one screener conducted over Google Meet using a shared code editor. (While this technically was Google Docs, it was a specialized section designed for conducting phone code interviews, complete with syntax highlighting and other standard code editor features.)

After the interview, I didn’t hear back for two more weeks. My recruiter eventually informed me that I had passed the screener and performed well, but Google had decided they no longer wanted to hire for the role.

Even though it was a front-end role, it was a general, language-agnostic coding question, similar to LeetCode.

The question regarded changes in strings and using data structures to find the longest chain of changes.