Google phone interview experience

Anonymous User
1373
Sep 09, 2025
Sep 09, 2025

I recently interviewed for a US-based L4 position at Google.

The interview started with 15-20 minutes of discussion based on my resume (projects, etc.), Interviewer was particularly interested with the academic projects which involved concepts of distributed design.
After which we moved on to the coding problem. The problem was very similar to this one: https://leetcode.com/discuss/post/1118304/google-phone-screen-rate-limiter-by-anon-ckr8/
.

It was a pretty straightforward question. I was able to come up with a solution in about 10 minutes and did a dry run. Interviewer asked about the complexity I answered it would be O(1) but the interviewer asked with scale would it be really constant time. The interviewer seemed really interested if I understand things at the low level.
By the time I finished, we were almost out of time, and the interviewer didn’t ask any follow-up questions or variations.

Since this was for an L4 role, I’m a little concerned. The coding question felt too simple for the level, and I’m not sure if the lack of follow-ups is a good or bad sign.

Has anyone else faced something similar? Do simple questions (with no follow-ups) still lead to positive outcomes, or is that usually a red flag?

Comments (3)