How to crack Google season of docs 2022 application stage

According to Google, Season of Docs provides support for open source projects to improve their documentation and allows professional technical writers to gain experience in open source. Together we raise awareness of open source, docs, and technical writing.

This program is essential in bringing writers to the open-source world and also supporting open-source organizations to develop their docs; as an experienced technical writer, this program will help you understand the following:

  • Help you understand how to contribute to open source.

This article will walk you through cracking the season of the docs application process in 2022.

From my experience as a season of docs technical Writer for Gnome foundation in 2020, the application process is different because I applied through the Google team and was reviewed by them. But now, you apply to the organization directly.

The points below will help you get accepted into one of the organizations.

  1. Have a technical writing experience or written articles/projects

To see the list of accepted organizations, visit this link

Have a technical writing experience or written articles/projects

This point is significant to the accepted organizations because they need an experienced technical writer to help them improve their docs and make them easier to maintain. It will be difficult for organizations to accept a total beginner because that will require them to start teaching you the basics.

If you want to be accepted as a technical writer with no working experience, see the below points.

  • Have written articles on medium, Dev.to or Hashnode

Have experience building documentation using static site generators

You might be wondering what a static site generator; a static website generator is a simple markup that uses a language like Markdown or HTML, data (in JSON, YAML, or TOML format), and templates. Then, it combines them with tools like Handlebars, Liquid, or Nunjucks to generate the pages of a website.

Most organizations in Google’s season of docs use static site generators to build their documentation site, so they will expect you to know it. Mautic project is an example of one organization that uses doc as code to build their documentation. If you check the link above, you will find out that they use sphinx for documentation.

So it will be beneficial if you know how to build a simple static site generator and host them for live testing.

Visit this link to learn how to build a simple static site generator using 11ty.

Read about the company and follow up with the mentor

Some organizations drop their mentor email or slack or discord username, making it easy to reach out to them. To make the mentor see you as a potential technical writer, you will have to do the following:

  • Read about the organization and the project.

The points above will make the mentor know you, and that’s a good thing 😉.

Note: Make sure your Writer’s profile is good-looking because they will likely check you out if they think you are a potential technical writer.

Join their Community channel

Some organizations allow you to join their community channels like Discord or Slack, enabling them to communicate easily with the applicants. as an applicant, you need to stand out among the crowd by doing the following:

  • Start using their project and let it know to them

Pray to God 🙏

Pray to God for his Grace to be accepted among others because sometimes organizations accept technical writers with little or no experience.

1 Corinthians 15:10

How to apply

You send a statement of interest to the respective organizations.

Step 1: Visit the season of docs participants page

Visit this link

Step 2: Select your preferred organization

Click on your preferred organization and search for the statement of interest section.

Example:

If you are a Technical Writer and you are interested to contribute to Casbin community for Google Season of Docs 2022, Please send your proposal (by following the template of writing the statement of interest from Google) to our mail at: admin@casbin.org , and then introduce yourself after joining our Casbin Gitter.im channel for connecting.

For more info about the example above visit this link

Step 3: Add your information to their page

Some organization requires you to add your information on their page after ending your statement of interest.

An example is this link

According to Indeed.com, a statement of interest for a job is a simple, one-page letter usually sent to a hiring official that describes who you are, why you’re drawn to their company, and how you can benefit their team.

Note: Another name for a statement of interest is a cover letter.

The organizations require this from you to make the application process easier for them.

Example of statement of interest:

Dear Hiring Manager,

I’m excited to apply for the Technical Writer position. As an organized, focused, proactive, creative, and detail-oriented individual, I have a proven record of meeting deadlines and maintaining the communication chain to ensure that projects run smoothly. I have written and edited numerous technical documents, including:

  • White paper tutorials.

In addition, I believe in my varied skills in designing doc sites using (Eleventy, Mkdocs, Docsify, Vuepress, Readme, Gitbook, Atlassian Confluence, Open API Spec, Hugo, DITA, Markdown, Asciidoc) and experience in open source technical writing / Software development would make me a great fit for this position.

At Nylas, I worked as a documentation developer contractor to plan, develop, and design their documentation site from scratch using Eleventy, Javascript, Rapidoc, and Algolia search. I focused primarily on document changes to ensure that the electronic documentation was edited to reflect each software update. In addition, I coordinated projects with the executive team to ensure that every task was completed and meetings went smoothly. As a result, I improved the turnaround time by an average of three days for each update.

Thank you for your time and consideration. I look forward to hearing about the Technical writing position.

Samples of work done by me:

https://beginnerblockchain.netlify.app/

https://about.codecov.io/blog/code-coverage-for-android-development-using-kotlin-jacoco-github-actions-and-codecov/

https://geth.ethereum.org/docs/getting-started

https://wise4rmgodadmob.medium.com/how-to-tag-a-docker-image-on-codefresh-1d63709d9cdc

https://developer.nylas.com/

https://wise4rmgodadmob.medium.com/

https://wise4rmgod.github.io/Jetpack-Compose-Tutorial/

https://wise4rmgod.github.io/Firebase-Android-Tutorials/#/

API Documentation:

1) https://app.swaggerhub.com/apis-docs/wise4rmgod/DummyAPI/0.1

2) https://developer.nylas.com/docs/api/

My timezone: (GMT+1)

WriteTheDoc Member

My LinkedIn and Github profiles below

https://linkedin.com/in/wisdom-nwokocha-76212a77/

https://github.com/wise4rmgod?tab=repositories

Sincerely,

Nwokocha wisdom Maduabuchi

In the statement of interest, include projects/ articles that involve what the organization you are applying to is using.

Conclusion

Season of docs 2022 projects are fantastic, and the organizations behind those projects are doing a great job. Working on any of the projects will help you gain experience and connect with fabulous people.

Good luck to all the applicants. 🥳🥳🥳🥳🔔🔔🔔😍

Let’s connect on
Twitter: https://twitter.com/Joklinztech
LinkedIn: https://www.linkedin.com/in/wisdom-nwokocha-76212a77/
Youtube channel: https://www.youtube.com/channel/UCGh4vu4cVz72cvgFG2QHnWQ

--

--

A software engineer with considerable experience in mobile development, native Android, and IOS development(Xcode), flutter dev, technical writing and community

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Nwokocha Wisdom Maduabuchi

A software engineer with considerable experience in mobile development, native Android, and IOS development(Xcode), flutter dev, technical writing and community