Google technical writer, 3 months in

A number of people have asked me what it’s like to be a technical writer at Google. I became a Googler three months ago. Now, as my manager remarked so eloquently, “the Noogler sheen is wearing off” and I’m settling down to regular Googliness. So, what’s it like?

That’s a hard question to answer. It’s empowering, scary, fun, frustrating, invigorating, tiring… All the usual things you’d expect in a new job, and then some. I love it. Most days. 😉

To answer the question, I’ve started by jotting down some random thoughts, followed by a “day in the life” ramble. I hope this gives you a good idea of what I get up to.

But there’s no typical tech writing role at Google

Google campus, Mountain View

Google campus, Mountain View

I’ve just returned from an internal Google technical writing conference called Burning Pen. It was awesome! Approximately 200 writers attended, from all over Google. We  congregated at the Googleplex in Mountain View, California. There were two days of sessions, running two streams all day each day. I met many great people and learned a lot about what other Google writers are doing.

It struck me that we’re all doing vastly different things: writing text on user interfaces (such as the labels on Google Maps), creating and curating content for Zagat reviews, developing API and developer-focused documentation (that’s my role), documenting internal tools for Google engineers and other staff, writing online help for Gmail and other consumer products, and more.

Random thoughts – what’s it like to be a Google technical writer?

It’s “technical”. I’m an API technical writer on Google Maps, which means that I show developers how to use the application programming interfaces (APIs) to integrate Google Maps into their own applications. As well as APIs, we document other developer products such as SDKs (software development kits) and other frameworks. We need to think like engineers, and understand what sort of thing external engineers will need to know about our products.

It’s fast, exciting, challenging, all-encompassing. My laptop is never far away, and I hack away at change lists between meetings, presentations, and bites to eat. While waiting for a plane, I fix a quick bug. While on the bus, I start triaging my email.

Team work is what makes the Google world turn. There’s always someone to turn to when I have a question. I get the impression I’ll be hacking and inventing with other people throughout my career here.

Like all technical writers, I like to feel that my work is valued. I definitely get that feeling here. I’m part of a team of people who rely on each other to get the job done. Documentation is a core part of the product, not an afterthought.

Work comes in small chunks. It’s a never-ending flow, but I get to tick things off regularly. For me, that’s very satisfying.

There’s plenty of opportunity to get in the zone and write. Yes, there are meetings and activities. Sometimes the “fire hose” of information can be overwhelming, but I learned quickly to filter the flow so that I get only what’s relevant to me.

Everyone has an opinion, and most people express theirs strongly. I sometimes need a loud voice and a touch of stubbornness to make my opinion heard.

Travel opportunities abound. I’ve been here three months, and already flown to Mountain View twice. My first visit was just a week after I started work.

There are good opportunities to make your mark. I’ve already presented a session at an internal Google conference.

More? Intensely interesting technologies. Vast scale. Innovation. The good feeling that I’m part of a company that’s making a difference in the world, and that cares very much that that difference is for the good.

A day in the life

I arrive early, around 7:30 in the morning. But I’m nowhere near the first to come in. People drift in at all times of the day – whatever suits them.

Bare feet, coffee, Big Red

Coffee machine

Big Red at Google Sydney

I drop off my laptop at my desk, and make a beeline for the coffee machine. On my way past a certain meeting room, I smile at a pair of bare feet. For some reason, there’s always a guy in that meeting room at that time of day, relaxing in a chair and chatting with someone via a Google Hangout. All I can see is his feet and ankles, because the rest of the glass is shaded. I’m guessing he’s talking to family somewhere on another continent, and very early in the morning is the best time to catch them.

Next stop Big Red, for a heart-punching cup of coffee. Big Red is the famous coffee machine in the Sydney office. Rumour has it that she was the first ever machine at Google Sydney. People treat her with pride and no little protectiveness.

Email, plans, mice and men

Armed with a cup of coffee, I read and respond to my email. There’s a lot of it. Email is our primary communication tool. I use Gmail’s special inbox categories to filter messages from people, notifications from various tools, and messages from special interest groups and forums.

Next I set out a plan for the day, in the full knowledge that things are likely to change and my plan will join those of other mice and men.

Tools, travel, chocolate

My primary tools for tracking work are the issue tracker and the code review tool used by the Google engineers. The documentation lives in the same repository as the code, and follows the same workflow. The software tools are in house and tend to be a bit idiosyncratic. But once you’ve got the hang of them, they’re satisfying to use.

My dashboards on the issue tracker and code review tools show me what I’m doing, what I’m scheduled to do, and what I’ve done recently. They also offer a good way of collaborating with other writers, engineers and product managers – especially with people who are on a different continent.

Meetings are also a big thing, to consolidate plans and designs and make decisions. We meet in person, via video conferencing, and via Google Hangouts.

Here’s a weird thing that happens often: I’ll talk to someone via video conferencing one day, because they’re a few thousand miles away, and then they’ll arrive at my desk the next day and pick up the conversation as if nothing happened in between. People are travelling all the time. They often don’t even tell you they’re about to hop on a plane. It’s just the way things are.

Back to tools. I also use Remember The Milk to remind me to do things like complete my weekly report, prepare for a weekly catchup meeting (which people call a “sync”), or buy a couple of chocolate fudge brownies from the nearby Pulse cafe on Friday. They’re to die for.

Words, code, markup

Must you be able to write code, to be a technical writer at Google? That’s a much-debated point. I think it depends on the role within Google. For my role, I’d say you’d be at a disadvantage if you couldn’t hack some code together.

Most of what we create is words. We write in HTML or Markdown, depending on our choice and on the existing format if we’re updating a document.

We also craft code samples. For a developer wanting to use our APIs and frameworks, a code sample speaks a thousand words. A technical writer will usually ask an engineer for help with the code samples, but we need to lick the code into shape and judge its usefulness as an illustrative example.

My first big project was to refactor some documentation for the Google Maps JavaScript API and build out the code samples. I blogged about the results: Refactoring overlays in the Google Maps JavaScript API documentation.

APIs, Linux, the colour purple

As someone who documents APIs, I get to play with code. I do a lot of command-line stuff, which is quite different from the wiki-based work that was the focus of my previous role. The tools I use now don’t have the power of the wiki in terms of integration with social media, rich text editing, and ease of use for non-technical people. But there’s a satisfying cleanness and simplicity to command-line input and text editors.

Did you know you can colour your Linux command window? Did you even want to know that? Heh heh, it’s the kind of thing I rejoice in now. 😉 Mine is currently purple with yellow text and blue highlights. I swap to a black-on-white window when I’m forced to use a Linux line editor. Most of the time, I use a text editor (Komodo) on my Mac to edit the documentation files. We’re free to use the tools of our choice, when it comes to text editors, IDEs, image manipulation tools, browsers, and so on.

Location, location, location

Sydney skyline

Sydney skyline

The Google Sydney office is in one of the most beautiful spots in the world. This picture shows the view from the balcony that surrounds the canteen.

The San Francisco office has a stunning outlook on Bay Bridge. The GooglePlex in Mountain View is restful, green, leafy and colourful. Those are the only three offices I’ve seen so far.

Three months, three offices. Not too shabby. I hope to see many more.

Food, food, food

Yes, the rumours you’ve heard are true. There’s food everywhere. We have a couple of “micro kitchens” on every floor. A micro kitchen is actually quite large, and boasts at least two types of coffee machine, a fridge full of drinks, shelves of snacks and fruit.

Each building also has a “café”, which is a deluxe staff canteen serving a full breakfast and lunch. Some cafés serve dinner too, for people who are working late. The lunch consists of a well-stocked salad bar, soups, a full cooked meal of a different variety every day, and at least two types of dessert. Amazing.

People talk about the “Google 15” – that’s the 15 pounds you gain when you join Google!

Did that answer the question?

Please feel free to ask questions by adding comments to this post. I’ll answer as best I can, as a Google technical writer three months into the role.

About Sarah Maddox

Technical writer, author and blogger in Sydney

Posted on 29 October 2013, in Google, technical writing and tagged , , . Bookmark the permalink. 59 Comments.

  1. Thanks Sarah – nice to hear of the change. You have historically been such a big advocate for wiki based tech docs, does the change of scenery alter your take on that in any way?

    • Hallo Josh, it’s nice to “see” you!

      I think a wiki is a great fit for documentation where there’s a need for collaboration by people from different job roles, and where feedback and discussion are important inputs into the documentation. The more advanced wikis offer solutions for version control and content reuse. The resulting documentation can also look very pretty. And the workflow can be as simple or as complex as you need.

      Still, there’s no perfect documentation solution, and no one solution that fits all use cases. A tech writer will work with the stakeholders to define requirements, and match the capabilities offered by the available tools.

      I’m an advocate for wiki-based tech docs, where the wiki and the requirements are a good match. 🙂


      • Hey Sarah – so nice to see you settling in so well. Appreciate the feedback; was curious given your change of scenery.

      • Vlad (ex NSWP)

        I am also a big advocate of wikis for technical and business collaboration, and I use and promote (internally, where I work) the use of Confluence, However, for years, I have been disappointed with what appears to me to be a deliberate lack of interest by Atlassian in taking things to the next functional and quality level. Confluence has very annoying fundamental limitations. The UI is quite rough in places. I am currently using v5.2.5, and have used it for many years. It’s as if Atlassian has taken the Microsoft road to concentrating on adding on useless features (presumably because of feedback from their marketing department), but ignoring the need to do a serious revamp of the UI and the need to add 21st Century functionality. It’s better than Sharepoint though, for most purposes. I just wish there was something better than Confluence. It is primitive compared to what it could be. BTW, I generally don’t work in places that have the budget or time or inclination to hire a talented Confluence script language coder that can add functionality to Confluence that should already exist in Confluence in the first place.

      • @Vald – sorry to hear you’re not happy with the direction the Confluence team has taken. As the head of marketing for Confluence at Atlassian I can assure you that our product roadmap is driven by a group of talented product managers with many years of experience in the collaboration and software development space.

        What we focus on is based both on mass customer feedback (you can submit and vote on feature requests on our public issue tracker), countless customer interviews and face-to-face conversations, and our own beliefs on what we feel is important.

        With regard to Confluence’s UI, we recently completed a major redesign of both the interface and user experience with our release of Confluence 5.0 in February of this year (see

        On the topic of functionality, we followed up the redesign of Confluence with an overhaul of the content creation experience, focusing on bundling out of the box solutions to common business problems to help users get started faster and see value sooner. You can learn more about his release here:

        If you’re looking to extend Confluence’s functionality further then I encourage you to browse the Atlassian Marketplace ( where you’ll find hundreds of add-ons – both commercial and free – that add extra capabilities to Confluence including publishing workflows, powerful content exporters, and diagramming tools.

        As someone who worked with Sarah for many years at Atlassian, it’s great to see her enjoying her new role at Google. Thanks for sharing, Sarah.


  2. This is my favourite bit “Documentation is a core part of the product, not an afterthought.”

  3. What a great summary, Sarah. Thanks for sharing! Those FF miles must be piling up 😉

    • Hallo Rhonda
      Yes! I’m such a fan of Air New Zealand. Excellent service and good fresh air in the cabin. It makes a huge difference to my experience of the flight, and the way I feel when I get off the plane.

  4. Vlad (ex NSWP)

    Interesting & informative blog.

  5. Hey Sarah, I’m from San Francisco, moved to Stockholm for a tech writer job 2 years ago, introduced Confluence to myself and my office…we now have 2 instances and over 15k pages on our Confluence intranet. Your book has been a huge help. Thank you so much!..Oh and I studied for a year at Sydney Uni back when, um, dinosaurs roamed the earth. Professional question…I am looking to find another company/tech writer that contends with almost entirely customized, high-end software. I want to see how they handle documentation. Our issues: documentation can’t be freely available on the internet – must be behind a firewall. Yes, one could label all the modularized pieces of documentation in Confluence but how to maintain with customers changing their configuration frequently and just one tech writer…Would love to find another company with similar challenges. Any ideas on where I could connect with someone like that (conferences are good, couldn’t convince my company to send me to the SF Atlassian conference…Maybe they suspected me of trying to get a free ticket home!) Thanks for any suggestions. 🙂

    • Hallo Kristin

      It’s nice to “meet” you! I’m so glad the book has helped, and you’re enjoying Confluence. Sydney Uni is gorgeous. I studied at Cape Town University (South Africa) but I’ve been to a few events and lectures at Sydney Uni.

      Your question is an interesting one. There certainly are companies dealing with such modularised documentation. A good example is auto manufacturers. I think a good place to get in touch with the technical writers is Technical Writing World:

      Twitter is also good, using the tag #techcomm. I’ll send out a tweet now and see if anyone responds with a comment on this post.


  6. Mrs.Haddox,
    I am an early college high school student who will simultaneously be given a high school diploma and an associates degree when I graduate. I like to write, and I am interested in becoming a technical writer. For my very first college class I have a job shadowing project, and I would like to ask if I could interview you by phone, email, or any Skype like resource to do my project. Thank you for reading this and I hope you can help me with my project.

    • Hallo Lindsay

      I’m sorry, but I’m not able to take part in an interview. I wonder if there are any technical writers working near you, with whom you could do some job shadowing? For example, if there’s a large company that employs technical writers, they may be able to offer you a short work-experience placement where you could shadow a technical writer. For contacts and ideas, Technical Writing World is a very good site:


  7. Aw, my little tech writing department’s all grown up now…[Hi Sarah. Saw this due to Jed linking to it. As he can confirm, I was, as I put it, the first general Eng tech writer at Google (Sara was a few months before me but in Services, and Lana was on the Search Appliance) back 10.5 years ago. Things have definitely changed since then…]

  8. I was a former technical writer for Altium Limited for some 10 years and I worked on generating small code examples mostly in Delphi/ObjectPascal and some in Javascript from the APIs of the powerful Altium Designer package. I used many different authoring tools like RoboHelp, Microsoft Help, Microsoft HTML Help, Confluence, custom HTML and PDF based documentation.

    Currently I am working in a vastly different sector; human services! But I have been playing around with Python and Javascript/jQuery lately. I also dabbled with Processing just for fun.

    I am thinking of restarting my technical writing career. So what do you suggest to get my skills up to scratch so I can get to work for Google one day.

    I have been reading/watching your blogs and the positions at Google Sydney. Wow. The environment sounds fantastic.I am wondering if there are any deaf technical writers or engineers at Google. As I am a deaf person myself 🙂


    • Hallo David

      Thanks for visiting my blog! I see you’ve already dropped in on the post about becoming an API tech writer. And that dabbling in Python is exactly the right thing to do. I’d also get a working knowledge of Java – enough to be able to read and explain code, and give advice on best practices. The most important thing, though, is to have a passion for technology and tech writing. There are tech writers in many different areas in Google, though in Sydney we’re focused on APIs and developer tools.

      I don’t personally know of any deaf tech writers here. Google strives for and actively promotes diversity and equal opportunities for its employees. You’ve probably come across this page already in your research:

      It’s great that you’re planning to get back into tech writing. It’s the best job. 🙂


      • I don’t know if they’re still there, but there were several deaf engineers at Google in Mountain View back when I was there in 2003-2007, one of whom I knew socially with respect to chatting, having lunch together, etc. although I didn’t work with him on anything. My understanding was that Google paid for sign interpreters to be with them during working hours, but I didn’t inquire in depth about how that worked, and don’t know if that’d still be the case today.

  9. Hello Sarah,
    very nice post!

    After reading it, I’m considering applying for this position, but I’m not a native English speaker. Would that be a deal breaker?
    (I do have some experience in technical writing in my language).

    Thanks for your insight. 🙂

    • Hallo Quique
      Having English as a second language isn’t a deal breaker. Fluent and correct written English is a requirement, of course. Judging by the language in your comment, it sounds as if you have a good command of English. 🙂 I’d encourage you to apply for the position currently open in Sydney. I’ll email you personally about it.

  10. Hi Sarah,

    I’m excited to see that you’re at Google! I used to lead the developer doc team there. I left because I wanted to pursue community documentation. Now you’re there, and I’m working with the Nokia developer community, and reading your book for the second time. It’s a small world. Enjoy Google!


    • Hallo Jen
      It’s lovely to hear from you! I love the title of your blog, WTFM. 😉 I’m thoroughly enjoying my role at Google. How is the Nokia developer community treating you? That sounds like a very challenging and fascinating role too! I guess you spend much of your time at

      • Hi Sarah,
        I’m glad you’re happy at Google! Yes, that’s right. I spend my time on the discussion boards and wiki there. I love working with the Nokia developer community. I’m humbled by the generosity of people who spend their free time sharing their knowledge with others. And working with wiki docs is a lot of fun. People share some pretty neat tricks and workarounds.
        Take care,

  11. Jonathan Couchman

    You mentioned your work on Google Maps. When I try to find places in countries that use other alphabets (China, Russia,, etc.) that are mentioned in online newspapers (SFChronicle, NYTImes,, etc.), Google Maps can’t always recognize the word or spelling. Can your people program for variant spellings in English so that places mentioned by API and Reuters and other news services can always be located? This is often so frustrating.

  12. Sayonee Ghosh Roy

    Hello Sarah,

    I just happened to stumble upon your blog while researching on technical writing. Could you tell me what qualifications/work experience Google looks for in its writing hires? Would they recruit someone just out of college? I graduate in August with a Bachelors in Computer Science and Engineering, so I was just scouting for career options.

    Thank you for your time!

    • Hallo Sayonee
      I’d recommend that you go ahead and submit an application, explaining that you’ve just graduated and are keen on a tech writing role. The recruiting team are awesome, and they’ll know if there are an graduate opportunities at the moment. They’ll also give great advice on the requirements and any further studying you may like to look at.

      • Sayonee Ghosh Roy

        Thank you for replying, Sarah 🙂
        I happen to be from India, so are there any hurdles I need to cross as an international applicant? And do I apply on Google’s Career Site or through some other channel?

      • Hallo Sayonee
        I’ll email you to continue the discussion. 🙂

  13. Zack Pseudonymous

    Sarah, thank you so much for writing about your experiences at Google and for offering such sound advice to so many people.

    I’ve been working as an API technical writer for about 10 years. In 2009, however, I had to take some time off to deal with some significant family emergencies. I left Silicon Valley and moved back to be with my family in a small town in the south. Of course there weren’t any opportunities there for technical writers; I used the time as best I could by taking some math computer science classes in the post-baccalurate program of the local university, which in fact has a decent program.( I am in fact contemplating doing a second Masters degree in CS.)

    Now, I’ve moved back to a large city and was overjoyed that Google contacted me. I had always wanted to work for them and I have worked for many big name software companies (Sun, Microsoft, etc.).

    Initially it went well Google but after I submitted my writing samples the team decided to pass. I don’t really blame them. I’m having trouble getting a good set of samples together.

    Some of the better samples I had were, for security reasons, hard copy only; I lost them because of the chaotic way I ended up moving back home. I didn’t have a wide selection to begin with because so many of the places I’ve worked for had security issues and did not allow me to take samples.

    At other places, I started on projects that failed due to sudden industry changes — like the iPhone quickly killing off its some of its competitors –so the samples from those projects were also unsatisfactory.

    I don’t think I can make the samples I have much better. Obviously I no longer have access to the original code. My programming skills are strong, by the way; at least good enough to get top grades in 3rd year undergraduate CS classes. (I’m an ABD — an all-but-PhD — in the humanities from a top school, but that’s another story…)

    So I’m wondering what I can do to improve my chances next time around with Google or with another company. The internal recruiter says that he will continue to look for opportunities for me, because I have a strong background, and I actually think he was not just being polite.

    For new samples I’m thinking perhaps that I should document something else, on my own. Again, something very much focused on APIs and SDKs. It’s the work I love to do. I’m strongest in C++ and Java but I wouldn’t mind at all learning a new language in the process of creating new samples. (In fact I have signed up for an online class for iOS/Swift).

    Do you think this would be a good strategy? Would Google be open to reading something that wasn’t actually written on the job? And, finally — and most importantly — do you have any concrete suggestions about what I might go about documenting, and where I can find the source for it?

    I’ve been out of the industry since 2009 and I need the practice. And I’d be very appreciative if you could point me to something or suggest a project that would help me stand out, show off my technical skills, and demonstrate that in spite of my time off I can work on the tech that people are using right now.


    • Hallo Zack

      Thanks so much for telling your story here. The Google recruiters are an excellent source of information, so if you already have this good relationship with one of them, don’t hesitate to ask him for advice. The fact that he’s said he’ll keep looking for a suitable position is a very good indicator. I agree with you, that the recruiter wouldn’t just say that to be polite. They’re keen to get the right people for the company.

      I have a couple of suggestions to get experience and some work samples. Firstly, you could take part in a doc sprint covering an open source product. Two organisations well-known for running open, public sprints are Mozilla and

      The other idea is to look for a startup company which would be keen to have your expertise free of charge. I don’t know what happens in your area, but here in Sydney we have a few organisations that offer office accommodation, services and networking to foster the startup community. An example is Fishburners: Perhaps you could contact the organisers of such a community space, and see if they’re amenable to your turning up and offering your services to the “residents”. I’ve been to Fishburners and was very impressed by both the organisation itself and the number and calibre of startups in residence.


  14. Zack Pseudonymous


    Thanks for the excellent suggestions! I will certainly look into them.

  15. Hello Sarah:

    Thanks for the great information! I just recently applied for four different tech writing positions at Google. I’m a college student majoring in Technical Communications, and I’ve taken some computer programming courses, just enough to call myself a novice… but I love it!

    The positions I applied for were for Tech Writer of…

    Android Partner Engineering…
    Hardware Operations…
    and Site Reliability Engineering.

    Is there anything you could tell me about these positions? I’d greatly appreciate it!

    – Xavier

    • Hallo Xavier
      Welcome to a fun, challenging and rewarding career! Those are four quite different roles. The first two are software-focused and most probably focus on educating external developers, the third will probably involve documenting hardware configurations for internal engineers, and the last will also focus on an internal audience. I’ll email you to find out what specific questions you have.

  16. Hi Sarah,

    Firstly, thank you!! Your site is such a haven for those of us who exclaim, “Wait a minute. I can *write* about how computers work for living?!?”

    I recently applied to two Technical Writing positions w/ Google and sadly didn’t pass the first stage — even with an employee referral and writing samples 😦 The recruiter commented that though I had the education and professional technical experience, they’re looking for very specific requirements. I often wonder if the fact I’ve never held a formal Technical Writing position is a fault. However, I’ve written documentation throughout my career as a developer/analyst.

    Any thoughts you might have would be greatly appreciated! If you’re too busy, I completely understand.

    Regardless, all the best!

    • Hallo Lisa

      I’m sorry to hear you didn’t get into those two positions. I can’t comment on the specifics, because there is a wide variety of tech writing roles at Google, each with differing requirements. The best thing to do is keep the conversation going with your contacts in the recruitment team. They’ll know if there are any other roles available that would be a good fit for you.

      All the best to you too! I do hope you find the perfect role.


      • Hi Sarah,

        Thank you so much for replying! And thank you for your advice. In fact I was wondering whether or not to contact them in the near future!

        I definitely will now 🙂

        All the best,

  17. Hello Sarah,
    Its great to see Technical writers are given respect. In most of the places, documentation comes at the very end!
    I am also a technical writer and very much interested in working at Google. It is definitely “The Place” to work!
    Can you please help me how to go about it?


  18. I just want to know what kind of resume leads to becoming a Googler? I would love the opportunity even to intern there as a technical writer

    • Hallo neuravinci

      I dropped in on your blog. Very cool! It’s fascinating how many technical writers do other types of writing too.

      As far as getting a role at Google is concerned, the best thing is to take a look at the roles currently advertised and follow the instructions to submit an application. Even if none of the roles fits you exactly, it’s worth submitted your resume along with a covering letter explaining what you’re looking for. In your case, you could mention that you’re interested in an internship, and ask for one of the recruitment team to get in touch with you.

      To answer your specific question about the resume: My recommendation is that your resume should be clear and concise in describing your current skills and experience. The resume or covering letter should also demonstrate a keen interest in technology and a love of technical communication.


  19. Great blog, Sarah! Thanks for an insider’s view of Google. That is so kind and generous of you! I’m a Stanford grad and tech writer in LA, CA. I also work at the movie studios and am happy to see you write fiction. Maybe we can swap expertise sometime (I analyze stories for the studios to buy and make into movies, but I’d like to be a tech writer at Google : ).

    • Hallo RJ
      It’s nice to meet you. 🙂 Analysing stories for potential movies sounds like a very cool job. It’d be fun to swap experiences. Do you ever have the chance to attend any tech writing conferences – for example, are you by any chance planning to attend Write the Docs in Portland, OR, in May this year? I’m glad you enjoyed this post about Google. I’m now 2.5 years in, and it’s still fun, challenging, and an ever surprising role.

  20. Hello Sarah,

    I hit upon your blog and it’s a treasure trove of information! Thank you for your services to the writerkind. 🙂 Please keep ’em coming,

    Sarah, I’m writing to you because I’m in the same waters as another poster. On and off, I have applied to 3-4 TW openings at Google in the last year. I really thought that I was a great match to a couple positions and had a good chance, but I never get called. (I have been a writer for over 15 years and I’m really good at what I do. I think. :-D) How do I get a callback? Sometimes I wonder if Google really even look at resumes submitted over the Net.

    Any thoughts you might have would be of great help. I know that you hear from loads of people with the same question. So, please feel free to ignore. 🙂

    Have a great day.

  21. EEK. Sorry about the gross typo. “Please keep ’em coming,” should be “Please keep ’em coming.” Period, not comma.

    • Hallo Emm
      I’m sorry to hear that you haven’t received a reply from the recruitment team. I’ll let them know about your comment.

      Thanks for your nice words about my blog. 🙂

  22. Hello, I am trying to become a googler like you and I was hoping to get some advice about what kind of qualifications I should have. Do you have any pointers for me?

  23. Hi Sarah, Thanks for sharing. It’s good to know what it’s like to be a technical writer at other high tech companies. As a technical writer myself, I feel like it’s more than ‘writing’ technical information nowadays. I wonder whether the technical writers at Google have been involved in any social media channels, such as creating videos for youtube, joining in some external user communities, publishing any other content, etc.

    • Hallo Mu Han

      It’s nice to hear from you. There are quite a few tech writers who’re active on social media channels. It’s a varied role, and many people enjoy sharing information and experiences with other tech writers. The “medium of the day” changes with time. Blogging seems to stick around, although people move to different platforms. The aptly-named is quite popular at the moment. A number of tech writers hang out in the “Write the Docs” channel on Slack too.

      Tech writers are also active on GitHub, and places where people ask questions, such as Stack Overflow. I’ve been to user group meetings and other events with customers, primarily to see how people are using our products. I’ve also created a few YouTube videos on how to use the products.


  24. Hi Sarah, Thanks for sharing your experiences. I enjoyed reading the blog and trust you are still having fun in the role. I am about to start my first tech writing role. What advice do you have for someone who is new to the profession? How good at coding do you need to be? What types of technical writing do not require a high level of coding ability?

    • Hallo Christina

      Congratulations on getting your first tech writing role! My advice for people starting out in a new role is to spend plenty of time listening to your stakeholders and agreeing on their requirements before you jump into creating docs. I do hope there are other tech writers at the organisation who can help you learn your way around. If there are small tasks you can do to start off with, that’d be ideal.

      Tech writing is a wide and varied role. Since you ask about coding, I’m assuming your new role is in the software industry, rather than other industries such as medical or aviation. If you’re documenting user interfaces or business processes, there’s less need to be able to code. My role is in documenting APIs and developer tools, where coding skill is much more important.

      Have fun in your new role!

  25. Hi Sarah,

    It’s great to read about your work and experience at Google. I’m actually looking to apply for the tech writer opening at the Sydney office and was wondering if I could ask you a few questions through email. If you’re on the interviewing panel, I hope that this isn’t cheating!

  1. Pingback: How Tech Comm Keeps Business Healthy (and Growing) - 3di Information Solutions: technical communication, translation and localization

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: