I applied through a recruiter. The process took 3 months. I interviewed at Google
Interview
Recruiter reached out to me via linkedin
First was a recruiter phone call, going through my resume no technical questions
Then I got booked for a hangout interview with a member of the team. He was very nice. The interview turned out well. Be prepared for DNS, DHCP, TCP/IP, linux/Unix troubleshooting, code debugging, technical troubleshooting
I cleared this stage and I was booked for onsite which was 3 back to backs 45 min each hangouts. I was asked to code on one of them. Medium leetcode knowledge is acceptable. Technical troubleshooting interview was very ambiguous, but you'll pass this if you explain your way of thinking. Manager interview was the easiest, I was asked behavioral questions only.
Interview questions [1]
Question 1
top, latency, why is network slow, data structures, general troubleshooting, dhcp, dns, tcp/ip
I applied through other source. The process took 1 day. I interviewed at Google (San Jose, CA) in Aug 2019
Interview
The phone screener peppered questions at a frightening pace. They were multiple choice, but some of the answers where not exactly correct. What port does ftp use? They wanted one port, but the answer is two ports. They did not specify passive. Questions involved programing, SQL, basic networking, and some theory.
I applied online. The process took 3 months. I interviewed at Google
Interview
I've applied to the position online.
The process started with a phone screening interview, then a first round interview with a TSE.
After clearing up the first round, I had proposed a second one which is composed of one coding interview, one troubleshooting interview, and one behavioral interview.
Interview questions [1]
Question 1
I was asked to fix a program that contained some bugs. I had to find the issues there, and come up with algorithmic improvements