Web Solutions Engineer applicants have rated the interview process at Google with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Web Solutions Engineer roles take an average of 23 days to get hired, when considering 4 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 Web Solutions Engineer according to 4 Glassdoor interviews include:
One on one interview: 40%
Phone interview: 40%
Presentation: 20%
Here are the most commonly searched roles for interview reports -
1- Telephone interview with recruiter about resume and the position.
2- Technical hangout interview ( one coding interview)
3 - Onsite interview ( 1- system design 2 -coding 3- behavioral)
So this job title was confusing for me to prepare. however it came out to be like SWE interview. However maybe it would be different for others and have linux and OS questions too.
I applied through an employee referral. The process took 5 weeks. I interviewed at Google
Interview
The interview process was a disorganized string of calls and email chains with 1-2 week lapses mixed in between. Despite multiple polite emails sent every few days about commitments for information they were going to provide nothing was received. Afterward hoping that maybe my rep was on vacation or busy I politely emailed her again and copied her manager. After which I got a hasty email that it was received and that she would provide the info soon.
After another 1 week lapse no info, I got a random email on a Monday from another hr rep that informed me that my onsite interview was scheduled in an hour (would you be able to make the 1 hour drive and find childcare without notice, please?) Needless to say I was rescheduled, hoping this was the last of the janky process. On the date of the onsite, multiple scheduling conflicts happened hours before my interview. 2/3 of my interviewers were swapped out and replaced with new Google hangout interviewers. When it came time for the interview the Google interviewers were not able to paste code into the shared doc... So precious time was wasted trying to write down the question and test cases even before I had a chance to understand it. The questions were simple (albeit vague because they just got pulled into this an hour before). The onsite went very well technically and non-technically besides. The entire process is riddled with smiles and hope, but the rejection was swift and without explanation (due to google policies).
Interview questions [1]
Question 1
linked lists, write APIs, scalability and data limits, recognizing data structures in word problems, optimizing time and space complexity of simple functions.