Open Badges Technical Writer Full-time

Mozilla Open Badges Technical Writer

Mozilla Open Badges is an open source project that kicked off in 2010 with the goal of reimagining credentials for the 21st century. Since then the open badges community has grown considerably along with our service offerings and code base. We are looking for a technical writer that will drive tools and best practices adoption by providing clear, concise and accurate documentation for our products and services. As an open source project, the documentation is intended for an external audience and should be able to communicate information without relaying on heavy technical jargon.

You will work on a variety of projects working with many members of the team including technical, product, branding/marketing in order to update /clean up existing documentation, create or update FAQs, draft onboarding documentation for new products and services, and putting together product announcements.

Responsibilities:

Define and execute documentation plans.
Own and maintain existing documentation. This includes working with team members to organize, improve and update existing documentations and articles.
Write documentation to support adoption of our tools and services.
Support architects and engineers with developing architectural diagrams.

Position Details:

This is a short-term, part-time contract position, with the potential of extending and moving to full-time depending on the work.
The technical writer will report to the Open Badges Technical Lead, Chris McAvoy.

Scope of Work:

Work closely with the engineering, product and marketing teams to understand the products and documentation needs (ongoing).
Review and clean up existing technical documentation (ongoing).
Write documentation for BadgeKit adoption and onboarding with cities as primary use case (Jan-Mar 2014).
Develop documentation for full suite of BadgeKit product offerings (Jan-Mar 2014) which include:
Badge issuing API docs
Badge assessment API docs
Badge discover API docs

Key Qualifications:

Several years in the technical field with relevant, practical experience.
Experience in editing and writing for technical documents.
Ability to manage multiple competing priorities in a fast-paced, constantly changing environment.
Aptitude to learn new technologies quickly, and then synthesize your learning to explain to others.
Ability to write in a range of styles and tones, from highly technical to conversational prose.
Proven teamwork skills and flexibility.
Ability to work in a distributed environment.