Got the offerSoftware Engineering Intern at Google
- Difficulty
- Process took
- 3-4 Weeks
- Rounds
- 3
- Format
- Remote
- Applied via
- Referral
How it went
- Google interviews are fast-paced and time-bound, so it is crucial to practice with that environment in mind.
- Don??t underestimate the importance of edge case discussions, dry runs, and being able to explain your solution with confidence.
What they would tell you
- Google interviews are fast-paced and time-bound, so it is crucial to practice with that environment in mind.
- Don??t underestimate the importance of edge case discussions, dry runs, and being able to explain your solution with confidence.
How to prepare
- Focused deeply on Google-tagged problems, especially on Strings, Graphs, and Heap.
- Practiced mock interviews to get better at thinking + coding under 60-minute constraints.
- Consistency matters more than intensity. Solving one high-quality problem daily helped far more than last-minute cramming.
Round by round
- 1
Technical Interview I60 min
Start with Introduction followed by 2 coding questions and followed by a discussion on internal working of HashMap
- 2
Technical Interview II60 min
Graph traversal problem (medium problem) involving topological sort, interviewer asked detailed conceptual questions about topo sort Graph hard-level problem, only approach and complexity explanation required, no coding I have answered all theoretical questions
- 3
Technical Interview III60 min
Given a heap-based hard problem.Initially struggled, took time to brainstorm. After solving, discussed time & space complexity and dry-run with large input
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.