Google

I applied for the Google SWE Intern role through the off-campus process and honestly didn't expect the interview call to come so quickly. I first had a short recruiter call where we discussed my projects, coding profiles, preferred programming language and some background questions. After that, I was scheduled for the technical rounds. Similar Google off-campus experiences report this recruiter/phone screen followed by DSA-focused interviews. The first technical round was around 45 minutes. After a quick introduction, the interviewer shared the problem on Google Docs. The question was based on a **binary tree**, and I had to explain my approach before writing the code. I started with the obvious DFS idea, then the interviewer added a follow-up that changed the requirement. I initially got a little stuck, but after discussing the constraints, I was able to modify the solution. The interviewer also asked me to dry-run it and explain the time and space complexity. The second round was more interesting for me. I got a **greedy-based problem** that looked simple initially but had a tricky observation. I spent a few minutes trying the wrong direction before explaining my thoughts aloud. The interviewer gave me a small hint, and that was enough for me to identify the intended approach and finish the implementation. A similar 2025 Google India experience describes a binary-tree problem in one round and a tricky greedy problem in the other. After the interviews, I had to wait for the final update. When the selection mail finally came, it honestly felt unreal. The biggest thing I learned from the process was that Google wasn't just checking whether I knew DSA—the interviewer was watching how I reasoned, communicated, handled hints and adapted when the problem changed.