Google SWE internship 2026
Summary
I interviewed for a Google SWE Internship, successfully passing the first technical round which involved a string and unordered map problem. The second round presented a more complex variation of the median of a data stream problem on subarrays, which I eventually solved but was ultimately rejected due to taking too much time and perceived nervousness. I learned the importance of confidence and careful reading of questions.
Full Experience
Recently, i got the chance to interview at Google for their SWE Internship 2026. The recruiter had reached out to me through mail saying that they would like to interview me for further processes.
First, i had a small chat with HR, it was a friendly discussion about what language i'm comfortable for the next round and explaining one of my projects. I noted that they wanted to verufy your leetcode account and remarked on the number of questions solved. 400+ seems to be a good number for them.
Technical Round-1: 45 mins, but cut short to around 35-40 mins due to interviewer's busy-schedule.
Due to google's policy, disclosing questions isnt allowed. But it was a medium level string-unordered-map question with some tweaks in a storing rotated order of string too. This round went good, she had asked me TC, SC, optimisations and edge cases. However understanding the question was slightly tricky.
I cleared this round!
Technical Round-2: 45 mins
It was similar to round-1 but the interviewer was a little stricter and the question was similar to median of a data-stream, but here the datastream consisted of all subarrays in order. (Not disclosing the exact question, the question was worded slightly more complicated and it took me time to understand what it meant). I took too much time to understand the question and find the approach as it was relatively tougher than the original problem. I was able to get the solution by the end and the code seemed to be perfect. I was really nervous during my interview and wasn't sure about my approach. I believe this is why i got rejected.
Verdict: rejected :(
But i learnt a lot in this process and I'm grateful for this opportunity as it came out of the blue! It was an amazing experience overall! Everything happens for a reason and I believe something better awaits! Key-takeaways: be confident in your approach and read the question very carefully! Just solving the question doesnt make you safe, you should be more confident and stern that what you're saying is right so that the interviewer doesnt cross question everything you're saying!
Hope this helps someone! Thanks and all the best!! Something better awaits!
Interview Questions (1)
The problem was similar to finding the median of a data stream, but the data stream consisted of all subarrays in order. The question was worded slightly more complicated, and it took me time to understand what it meant. I found this question relatively tougher than the original 'median of a data stream' problem.
Preparation Tips
I had solved 400+ LeetCode questions, which seemed to be a good number for Google. Key-takeaways from the interview included being confident in my approach and reading the question very carefully, understanding that just solving a question isn't enough; confidence and conviction in one's solution are also crucial.