Technical Writer applicants have rated the interview process at Google with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 52% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Technical Writer roles take an average of 52 days to get hired, when considering 27 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 Writer according to 27 Glassdoor interviews include:
Phone interview: 34%
One on one interview: 21%
Presentation: 13%
Group panel interview: 9%
Skills test: 7%
Background check: 5%
Drug test: 4%
Personality test: 4%
Other: 4%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 5 weeks. I interviewed at Google in Jan 2016
Interview
I didn't get this job, but it was close. I'm writing this review because there is a lack of information for technical writers that want to interview at Google. Onward, Peeps!
The process:
Two writing assignments, one phone screen, and one in-person interview.
The in-person interview team:
Three technical writers, two developers, one person to commiserate with over lunch.
The type of things I was asked to do by the technical writers:
-My writing process
-Re-write a chunk of text.
The type of things I was asked to do by the developers:
-Interpret a chunk of code on a whiteboard.
-Write a chunk of code on a whiteboard.
-Write a product outline based on an SME interview.
Don't be like this flunky and assume because you've written and worked with code, the developer portion of the interview will be easy. To hit your interview out of the ballpark...
(1) Assume the developers are going to ask you to code something. And not super easy things like "what does int i = 2 + 3 equal?" Study recursion. I wasn't expecting coding questions in the interview and hadn't brushed up on these sorts of questions. Don't make my mistake. Brush up!
(2) Assume the developers are going to ask you to interpret some code. And again, not something super easy like "what does int i++ mean?". Brush up on data structures and how to pass them around.
(3) Take control of the SME interview. Make sure you don't get side-tracked. Make it clear to your SME that you need short, discreet answers. Be tough! I wasn't and we drove off into a ditch, never to be found again. Don't make that mistake!
(4) Make sure your writing submissions have lots of code samples. If you don't have anything that shows off how awesome your skills are, get thee to GitHub and write something for an open-source project you believe in.
Interview questions [1]
Question 1
Without getting into specifics... writing process, interpret code sample, write code sample, write doc outline
Interview process was quick and very professional. Result declaration takes a lot of time sometimes.
Questions were mostly technical and situation based. It was a difficult round.
However, it was a great experience.
Interview questions [1]
Question 1
They asked me mostly about technical questions and management skills.
I applied online. The process took 2 weeks. I interviewed at Google (Bengaluru) in Feb 2024
Interview
It was good and they asked core questions and took a thorough assessment. Seamless procedure must say. However, the approach of the respective person can be better. Overall the experience was good
I applied online. I interviewed at Google (Hyderābād)
Interview
Once written was clear, i was called for in person interview. they asked about the various concepts we use in documents, different kind of guides. got stuck with the maintenance aspect of the document cycle
Interview questions [1]
Question 1
they asked about the various concepts we use in documents