Candidates applying for Software Developer roles take an average of 21 days to get hired, when considering 1 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 Software Developer according to 1 Glassdoor interviews include:
Skills test: 33%
Phone interview: 33%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
Process 1:
**********
- The Challenge Phase.
Problem: you are given two-armed Balances one each are you can put weight and
other balances. Return the minimum weight you add on each arm of each balance
to make the whole structure balanced.
- First Interview.
Problem 1: Given two strings (Text & pattern) return true if the pattern
exists in the text.
Problem 2: Given List of Strings. Return a list of lists of Strings where
each to anagram Strings in the input list exist in the same list in the output list.
- Second Interview.
Problem 1: Implement a data structure that supports two methods
(Insert(int x),getMedian())
Problem 2: Given a 2D boolean array. Return the length of the biggest square
where all elements inside it is true.
- Third Interview.
It was a culture fit with a lot of HR questions
(Ex: how do you see managment?, When do you say that "Today is a good day of
work"?, what about teamwork?,talk about a project you did?) but at the end
there were two problems also:
Problem 1: Given a list of integers, Print out all triples that sums to zero.
Problem 2: Given a sorted circular integer vector. Implement the search on
such a structure.
Interview questions [1]
Question 1
Make a perfect Random7() function to produce numbers from 1 to 7 using Random5() function which is perfect.
I applied online. The process took 1 day. I interviewed at Google
Interview
HR called to arrange interview. Spoke to a very nice guy who explained the position. We went through some programming topics (networks etc) and some fairly in depth unix admin style questions.
Interview questions [1]
Question 1
How do I find the owner of a block of shared memory
I applied through a recruiter. The process took 2 weeks. I interviewed at Google (Mountain View, CA) in Jan 2011
Interview
I was contacted by a YouTube recruiter by phone - presumably after he saw my resume on LinkedIn.
After a phone screen, I was called in for a round of in-person interviews. It was around 6 people over about 4 hours. From my understanding, Google usually goes through multiple on-site interviews, but since I already had an offer from a major competitor, I convinced them to speed up the process and make do with only one on-site. I got the offer about 2 weeks later and accepted it.
The questions were standard CS algorithm/design/coding questions, but cumulatively were definitely the hardest round of questions I've ever faced. I don't remember them any more, but they really made me think. Google lives up to it's tough-as-nails-interviews reputation.
Interview questions [1]
Question 1
The phone screen was the hardest. It was something that involved two separate concepts - one was a dynamic programming algorithm and the other was a trie data structure - and somehow combining them to make up the answer. I don't remember the exact question, but somehow it involved storing the words in a dictionary into the trie structure and then using the algorithm to determine something...