Technical Support Engineer applicants have rated the interview process at Google with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 36% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Technical Support Engineer roles take an average of 57 days to get hired, when considering 11 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 38 days.
Common stages of the interview process at Google as a Technical Support Engineer according to 11 Glassdoor interviews include:
Phone interview: 28%
One on one interview: 20%
Skills test: 12%
Background check: 8%
IQ intelligence test: 8%
Other: 8%
Group panel interview: 4%
Drug test: 4%
Personality test: 4%
Presentation: 4%
Here are the most commonly searched roles for interview reports -
Difficult. they arent asking questions relating to this current role that i have applied. when i tried to ask some question like salary, very dismissive. overal i found it totally not enjoyable. dont apply
I applied through college or university. I interviewed at Google (California, MD) in Feb 2026
Interview
Went fine, didn't get the job. The questions were really difficult and they did not give me time to prepare. I don't think they were very good at interviewing. Would not recommend this place to interview at
Great people and challenging questions. The process included about an hour with HR, followed by a second round with the team, making for a well structured and engaging interview experience
I applied through a recruiter. I interviewed at Google (Hyderābād) in Sep 2025
Interview
Very hard DSA round. It was scheduled for a 1-hour interview, but the problem was much more involved and could easily take longer than the allotted time. The question required strong algorithmic thinking, careful handling of edge cases, and the ability to reason through complexity under pressure. It was not just about writing code quickly; the interviewer expected a clear approach, optimizations, and clean implementation despite the time constraint. Overall, it felt like a round designed to test depth in data structures and algorithms rather than a standard timed coding exercise.
Interview questions [1]
Question 1
It was a very hard DSA round with a complex tree-based problem. Although the interview was scheduled for 1 hour, the problem felt like it could easily take much longer to solve fully. It required deep understanding of tree traversal, recursion, state management across nodes, and careful handling of edge cases. The challenge was not just arriving at a working solution, but also optimizing it and explaining the reasoning clearly under time pressure. Overall, it felt like a round meant to test strong problem-solving depth rather than a typical interview-length coding question.