Google

  www.google.com
  www.google.com

Google Technical Writer Jobs & Careers

Hiring? Post a Job
14 job openings Back to all jobs

Show:  All Results Last 7 Days
21 days ago

Technical Writer

Google Changhua County, Taiwan

• Interact with Google Data Center teams as well as contractors and vendors to produce multiple types of professional writing and documentation… Google


21 days ago

Technical Writer, Analytics Developers

Google Mountain View, CA

• Lead all documentation efforts for Google Analytics Developer Documentation. • Improve the quality, breadth, and effectiveness of content that… Google


7 days ago

Technical Writer, Display Ads

Google Waterloo

Display Ads is one of the most complex and business-critical systems at Google. The engineers on this team… Google


21 days ago

Technical Writer, Developer Products

Google Sydney +3 locations

• Write technical documentation for our external developer audience, such as API referen… Google


21 days ago

Technical Writer, Hardware Operations

Google Atlanta, GA, USA Council Bluffs, IA

• Plan, research, and write documentation for projects of moderate to high complexity and scope. • Edit, revise, and restructure a wide range of… Google


21 days ago

Technical Writer, Android Partner Engineering

Google Mountain View, CA

Android Partner Engineering is looking for a technical writer who can take a wealth of internal documents, APIs,… Google


21 days ago

Technical Writer, Manager, Developer Platform

Google Mountain View, CA

and lending specific content expertise. As a Technical Writer, you will… Google


21 days ago

Technical Writer, Site Reliability Engineering

Google Mountain View, CA

Site Reliability Engineer (SRE) technical writers document internal Google infrastructure, team processes and… Google


21 days ago

Outside Plant (OSP) Technical Writer

Google Mountain View, CA

Google is always striving to innovate and our Fiber­-to-­the-­Home (FTTH) program is no exception. We're building one of the fastest national… Google


16 days ago

Technical Writer, Internal Software Engineering

Google Mountain View, CA, USA Seattle, WA

s, tutorials for software developers, API programming guides, and more. • Respond to technical questions from Google engineers about the subject… Google


Google Reviews

2,810 Reviews
4.4
2,810 Reviews
Rating Trends

Recommend to a friend
Approve of CEO
Google Co-Founder & CEO Larry Page
Larry Page
1,553 Ratings
  1. 97 people found this helpful  

    Great balance between big-company security and fun, fast-moving projects

    • Comp & Benefits
    • Work/Life Balance
    • Senior Management
    • Culture & Values
    • Career Opportunities
    Current Employee - Software Engineer III in New York, NY
    Current Employee - Software Engineer III in New York, NY

    I have been working at Google full-time (more than an year)

    Pros

    * If you're a software engineer, you're among the kings of the hill at Google. It's an engineer-driven company without a doubt (that *is* changing, but it's still very engineer-focused).
    * The perks are amazing. Yes, free breakfast, lunch, an dinner every weekday. Aaaaaamazing holiday parties (at Waldorf Astoria, NY Public Library, MoMA, etc.); overnight ski trips to Vermont; overnight nature trips to the Poconos in the summer; summer picnics at Chelsea piers; and on and on and on. I don't see this going away unless the company starts hurting financially.
    * Speaking of which, the company is doing quite well, which reflects in bonuses and equity grants.
    * There a huge diversity of work ranging from defending independent journalism worldwide (Google Project Shield) to crisis response during disasters (see Maps during Hurricane Sandy or Tsunamis), to the best machine learning experts and projects in the world, to more mundane revenue-driving projects in advertising, there's really something for everybody.
    * It's easy to move around within the company as long as you're in good standing (the vast majority of engineers are).
    * The company is amazingly open: every week Larry Page and Sergey Brin host what's called TGIF where food, beer, wine, etc. is served, a new project is presented, and afterward there's an open forum to ask the executives anything you want. It's truly fair game to ask anything, no matter how controversial, and frequently the executives will be responsive.
    * No, nobody cares if you use an iPhone, Facebook, shop with Amazon, stream using Spotify, or refuse to use Google+. The company is amazingly open and flexible.

    Neither pro nor con, but general information on work-life balance, promotions, and advancement.
    * Work life balance can be what you want it to be on most teams. (Some teams are in more competitive sectors and require more crazy hours all the time - but very few of them). If you do what's expected, you'll be fine at least for a handful of years. Working a roughly 40 hour work week is possible, and many people do it. There are also people who are hyper-motived and work like crazy just because they love it, or because they're competitive, or they want to get a promotion. If you work 40 hour weeks without putting in anything extra, you'll fall behind them as they advance and you stand still - and maybe that doesn't matter, so it works out for everybody. But at least know where you would realistically stand.
    * If you excel and work your butt off, you'll be compensated and promoted. If you let yourself be a code monkey, and just sit coding with your head down all day, you'll be fine but won't advance. A big complaint from some Googlers is about not being able to advance "even at Google" with pure coding. Sure, if you're the uber genius who created MapReduce and Bigtable, you're going to advance like a rocket without having to do anything but coding; but if you're like most engineers at Google -- smarter than average, but just average compared to other Googlers -- you're just a good coder and not revolutionary. Code monkeys are important to actually get stuff done, and to be sure you absolutely need to be a good coder as a software engineer (it's the minimum requirement), but code monkeys won't advance because they're not leaders and they're easy to replace. To get promoted you need to lead and do more than just code. There are plenty of ways to lead other than being an official tech lead, so this isn't actually _that_ hard, so the real point is just that you can't just sit there coding what other people tell you to code all day and expect to advance.

    Cons

    * It *is* becoming larger, and with it comes growing pains: bureaucracy, slow to respond to market threats, bloated teams, cross-divisional tension (though nothing remotely approaching that of Microsoft's internal tension).
    * The quality of the engineers is possibly dropping, but possibly not. It's hard to get real metrics, because as the absolute number of people grows, naturally the number of bad apples grows; as a percentage it's supposedly the same as it ever was, but with larger numbers of poorer quality engineers it just _feels_ like things might be changing for the worse.
    * Also with growth means more internal-confidential data leaks (again, because of the raw numbers of people) -- product announcements being ruined, etc. That means the company has to be tighter-lipped internally to avoid leaks, which makes things less open. It's still an amazingly open place, but less so than it was even a couple years ago. The good thing is they recognize it and actively look to improve things because they know how important it is to keep the good culture.

    Advice to ManagementAdvice

    Keep the focus on the user. Everything else will follow.

    Recommends
    Positive Outlook
    Approves of CEO

Work at Google? Share Your Experiences

Google

 
Click to Rate
or