Software Engineer Intern Interview Experience

I got an OA first, and it was so easy that I finished it in about five minutes even though it was supposed to be ninety, which told me pretty quickly Google was not using that as the real filter. After that I had two technical interviews that were both blank-doc coding rounds where you cannot run code, so the whole thing is about reasoning, asking good questions, and keeping the interviewer engaged while you work. My actual coding questions were both pretty standard LeetCode-medium level, but the follow-up optimizations were where the signal really was, especially when I had to optimize a heap update problem with no hints. Then I went into team matching, which lasted way longer than the technicals and stretched from September into December with multiple team-specific conversations. Those calls were mostly resume-driven, but some were unexpectedly technical, so it felt like the real bottleneck was not passing interviews but getting matched.

I got an OA first, and it was so easy that I finished it in about five minutes even though it was supposed to be ninety, which told me pretty quickly Google was not using that as the real filter. After that I had two technical interviews that were both blank-doc coding rounds where you cannot run code, so the whole thing is about reasoning, asking good questions, and keeping the interviewer engaged while you work. My actual coding questions were both pretty standard LeetCode-medium level, but the follow-up optimizations were where the signal really was, especially when I had to optimize a heap update problem with no hints. Then I went into team matching, which lasted way longer than the technicals and stretched from September into December with multiple team-specific conversations. Those calls were mostly resume-driven, but some were unexpectedly technical, so it felt like the real bottleneck was not passing interviews but getting matched.