Google Interview Experience - Software Engineer Intern | takeUforward
Google
Software Engineer Intern
3 Rounds
5 Problems
Selected
0
AnonymousUnder Graduate Student
Posted on: 199 days ago
Difficulty levelMedium-Hard
Interview modeRemote
Apply levelWalk-in
Interview timeline2-3 Weeks
Interview rounds
Overall Experience
Preparation Tips
Practice Data Structures & Algorithms (DSA) Thoroughly : Try to complete Strivers sheet first to get a strong grip on concepts and then practice company wise question
Learn Graph deeply : Google is known to ask graph question so get a strong grip on graph
Simulate the Interview Environment : Practice coding in Google Docs or plain text editors
General advice
Clarity is key: Always start by explaining your approach before jumping into code
Use descriptive variable names when coding in documents (e.g., movieRatings, not mr)
Edge cases matter: Always think and mention how your solution handles edge cases
Ask clarifying questions: If the problem statement isn’t 100% clear, confirm the assumptions, you can ask if input is sorted or not , or constraints etc
Optimize only after correctness: Write a working brute-force solution first, then work on optimizing it if time allows.
Google
Software Engineer Intern
3 Rounds
5 Problems
Selected
0
AnonymousUnder Graduate Student
Posted on: 199 days ago
Difficulty levelMedium-Hard
Interview modeRemote
Apply levelWalk-in
Interview timeline2-3 Weeks
Interview rounds
Overall Experience
Preparation Tips
Practice Data Structures & Algorithms (DSA) Thoroughly : Try to complete Strivers sheet first to get a strong grip on concepts and then practice company wise question
Learn Graph deeply : Google is known to ask graph question so get a strong grip on graph
Simulate the Interview Environment : Practice coding in Google Docs or plain text editors
General advice
Clarity is key: Always start by explaining your approach before jumping into code
Use descriptive variable names when coding in documents (e.g., movieRatings, not mr)
Edge cases matter: Always think and mention how your solution handles edge cases
Ask clarifying questions: If the problem statement isn’t 100% clear, confirm the assumptions, you can ask if input is sorted or not , or constraints etc
Optimize only after correctness: Write a working brute-force solution first, then work on optimizing it if time allows.
