Current phase:
Results announced. See
timeline.
This page contains tips for open source organizations on how to assess and select the right technical writer for their Google Season of Docs project proposal.
Introduction
Open Source Organizations must hire a technical writer to work on their proposed project. Organizations must source their own technical writer. Technical writers interested in working with organizations participating in Google Season of Docs may be found in the Google Season of Docs GitHub repo, and in the #season-of-docs channel in the Write the Docs Slack.
Beginning the process
It is recommended that you begin the process of finding a technical writer as soon as you think you may want to participate in Google Season of Docs.
Assessing a technical writer
It is recommended that you request examples of previously developed documentation from the technical writers you are considering, so that you can focus on evaluating their technical writing skills and experience.
Technical writing skills and experience
Examine the technical writer's prior experience. Ideally, the technical writer should have some prior experience in writing technical documentation for the software industry. One of the goals for Google Season of Docs is to give technical writers the opportunity to get involved with developer-focused products. For that reason, it's not essential that the writer has experience with APIs or SDKs or other developer platforms, even if your project focuses on a developer audience.
Focus on language and communication skills. Evaluate the technical writer's previous work from this point of view. Most importantly: Can you understand what the person wrote? If you want to do an indepth review of the language of the technical writer's work, look for consistency in punctuation and phrasing, correct spelling, and clear language. Is the phrasing simple or complicated? Are the sentences short or do they run on until they become difficult to follow?
Pay attention to doc design and layout. Check the overall layout of the document sample(s). Is the design logical? Can you easily find your way around the document or documentation set? Is there duplication of content or are there obvious gaps?
Hiring a technical writer
Organizations must hire a technical writer and complete the Proof of Technical Writer Hiring Form linked below by May 10, 2023 at 18:00 UTC.
Technical writer hiring phase complete.
Be sure to discuss compensation and a payment schedule with the technical writer prior to hiring. We recommend that organizations create a payment schedule with technical writers based on project milestones, including a payment at project kickoff. Please keep in mind payment dates, which will only happen two times throughout the program, and amounts when creating a payment schedule.
Note: Organizations that have not hired a tech writer and submitted the Proof of Technical Writer Hiring Form by May 10, 2023 at 18:00 UTC will not receive funds on the first disbursement date.