These job descriptions are examples. Looking for work?

Find JobsFind Jobs

Technical Writer

0 people like this description

Our team works for one of the largest IT departments in the world that has some of the most difficult security challenges on the planet. We are normally in the top five attack vectors by all hackers worldwide. When a tech writer writes something here it could be literally viewed by millions of people. They are the authoritative voice (or pen) of the client company. This is emerging tech, brand new features, automation, bots, machine learning, artificial intelligence – really cool stuff.

Skillset is the primary motivator for this need.
This person will be working on three major types of documentation. The three major types are:
1. Security Design Review to make sure that the service itself actually meets requirements – it’s standards and policies.
2. Position Paper: It may be secure, but IT may have a specific position on how it is configured, deployed, operated, conditionally turning on or off certain features for the better protection of the client company.
3. Evangelism approach – writing outward reaching papers.
This role will be responsible for: evaluate, opinion and evangelism outputs where our product is the focus. Much of this is tech writing, but it involves interview skills, assessment based on criteria and the ability to write professional publications that can used not just for their original intended purpose, but scale out and be used in wikis and articles and blogs and all sorts of external publications. It’s a lot like bringing on a diplomat with writing skills. This is an enablement position – if there is something wrong with a product that we find, we are equally responsible to go back to that product team and help them understand our real world case and get them to address it through better features and improvements.


This role will have a 60/30/10 ratio:
30% of the time will be spent interviewing, identifying and collecting resources – either people or process or documentation that will be used for a paper.
60% of the time will be spent actually writing the documents.
10% of the time will be spent tracking the projects, communicating them out to stakeholders, getting other people to review and ensure correctness.

The ideal candidate should be able to verbally and through written means defend how a feature works for the purposes of risk mitigation. For example, that may be being articulate about the security features of product or service we are looking at.

If they don’t meet the requirements, they should be experienced enough with encryption or identity access to write an effective, actionable bug to bring it into alignment.
The ideal candidate will need to have the skills and talent to converse with engineering, but they will not be leading any meetings. They need to understand how to convince product teams with positivity to share and emote the value of what the tech writer is trying to do to the product team so they want to participate.

These job descriptions are examples. Looking for work?

Find JobsFind Jobs