Interview prep / Google
What Google is documented or reported to ask, by category. Each statement links to where we read it.
Candidates report a roughly 60-minute phone screen on data structures and algorithms (medium-level problems), then coding rounds in the onsite loop.
Reported by candidates (source linked)Interview Kickstart: How Google hires software engineers ↗ read Oct 2026
Two recent India L3 candidate reports describe technical interviews in the loop; one reports two onsite technical rounds after a virtual technical round. This is a role- and level-specific pattern, not a universal Google schedule.
Reported by candidates (source linked)LeetCode Discuss: Google India L3 interview experience, offer accepted ↗ read Nov 2026
The onsite loop is described as including coding interviews, sometimes written in a shared document.
Reported by candidates (source linked)MentorCruise: The Google interview process ↗ read Oct 2026
Find the length of the longest strictly increasing subsequence in an array where neighbouring chosen values also satisfy a constraint, for example differ by exactly 1, and then by at most k. As a follow-up, return the indices of the subsequence.
Reported by candidates (source linked)LeetCode Discuss ↗LeetCode Discuss ↗
Reworded by StackHike; this is not the company's own text.
Interviewers are reported to score general cognitive ability: how you reason through a role-related problem, not what you already know. Hiring-committee review follows.
Reported by candidates (source linked)Business Insider: What Google grades interviewees on ↗ read Oct 2026
System design interviews are reported as part of the onsite loop for engineering roles; how many rounds depends on role and level.
Reported by candidates (source linked)Interview Kickstart: How Google hires software engineers ↗ read Oct 2026
A recent India L3 candidate report describes a separate virtual Googliness round, while another India L3 report describes situational work-style questions in the Google Hiring Assessment; candidates should treat this as reported experience, not a guaranteed step.
Reported by candidates (source linked)LeetCode Discuss: Google SWE II (L3) interview experience, India 2026 ↗ read Nov 2026
Behavioral and hypothetical questions assess leadership and 'Googleyness' (comfort with ambiguity, collaboration, doing the right thing). Candidates are reported to have been turned down on this even after strong technical rounds.
Reported by candidates (source linked)MentorCruise: The Google interview process ↗ read Oct 2026
Tell me about the most challenging project or feature you have built. What made it hard, and what did you learn, technically and as a person?
Reported by candidates (source linked)LeetCode Discuss ↗GeeksforGeeks ↗
Reworded by StackHike; this is not the company's own text.