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.