Technical Writer
About the role
... maybe a short paragraph summarizing role.
But we must not repeat job title as heading. So we can start with About the role. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the details from the posting, not just summarize. However we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the details, not omit them. We can keep them as is, maybe in bullet lists. We need to use- for any list of duties/requirements/benefits, and
for prose. Thus for responsibilities we can make a list. Let's extract duties: - Exercises judgement in prioritizing work and uses AI tools for quality checks, peer reviews, and draft content generation. - Proactively identifies and resolves low-to-moderately complex issues and risks. - Focuses on increasing independence in core execution, taking ownership of content quality, ensuring content clarity and ease of content navigation, and supporting strategic initiatives. - Requires moderate supervision; works independently on assigned tasks and content sets. - May come into contact with confidential or sensitive customer information requiring special treatment in accordance with Red Hat policies and applicable privacy laws. - Works with increased independence over time to draft AI-assisted documentation for defined product offerings. - Fully executes all phases of the technical content development lifecycle from content creation, curation, and archiving content for assigned product areas. - Demonstrates ability to understand and incorporate changes based on stakeholder and customer feedback. - Applies strategic knowledge of end users to ensure content maps well to user needs. - Develops content that is technically accurate and user focused. - Ensures accuracy by testing procedures and cross-functional reviews. - Proactively identify and resolve low-to-moderately complex project-related issues and risks early within assigned content area, escalating to appropriate team lead when necessary. - Adheres to required standards for tracking and reporting work. - Uses AI tools for quality checks, peer reviews, draft content. That's a lot; we can group. For Requirements/Qualifications: maybe note about moderate supervision, works independently, handling confidential info. But we could treat that as part of responsibilities. Better to have sections: About the role (summary), Responsibilities (list), Qualifications (maybe note about supervision and confidentiality), Skills (AI tools usage, content development lifecycle, user focus, project management), Benefits (list), Pay (salary range and factors). We must not create sections with placeholder text. Let's craft. About the role: we can use a paragraph that captures the role description: "The Technical Writer 2 exercises judgement in prioritizing work and uses AI tools for quality checks, peer reviews, and draft content generation. Proactively identifies and resolves low-to-moderately complex issues and risks. This level focuses on increasing independence in core execution, taking ownership of content quality, ensuring content clarity and ease of content navigation, and supporting strategic initiatives. Requires moderate supervision; works independently on assigned tasks and content sets. Note: This role may come into contact with confidential or sensitive customer information requiring special treatment in accordance with Red Hat policies and applicable privacy laws." That's a paragraph. Responsibilities: list of duties (maybe combine with above but we can separate). However we must not duplicate content. The About the role paragraph already includes some responsibilities. To avoid duplication, we could keep About the role as a brief overview, and Responsibilities as detailed list. But we must preserve all substantive information; we can split but ensure we don't omit any. Let's include all duties in Responsibilities list, and keep About the role as a short summary (maybe just first sentence). But we need to ensure we don't lose any detail. If we put all details in Responsibilities list, About the role can be a brief generic statement like "The Technical Writer 2 role focuses on creating and maintaining technical documentation with increasing independence, using AI tools, and ensuring content quality and user focus." That might be considered summarizing, but we risk losing detail. However the instruction says do NOT summarize away detail. So we should not omit details. So better to put all details in Responsibilities list and not have About the role duplicate. But we need an About the role section per instruction: use
for section headings (e.g. About the role, Responsibilities...). It says "include a section ONLY when the posting has real, specific content for it". So we need About the role section only if there is real specific content. The posting does have a description of the role; we can treat that as About the role content. So we can put the role description there (the paragraph we wrote). Then Responsibilities can be a list of specific duties (maybe overlapping). But we must avoid duplication? The instruction does not forbid duplication, but we should preserve all substantive information; duplication is okay as long as we don't omit. However we might be repeating same content; that's okay but could be considered redundant. It's not prohibited. However we might want to avoid duplication to keep concise but still preserve all info. The instruction says "do NOT invent or summarize away detail". Duplication is not summarizing away; it's repeating. It's allowed. Thus we can have About the role paragraph with the role description (maybe the first few sentences). Then Responsibilities list with bullet points covering all duties. Qualifications: maybe we have note about moderate supervision, works independently, handling confidential info. Could be separate. Skills: maybe AI tools usage, content development lifecycle, user focus, project management. But we could also put those under Responsibilities. Given the instruction to prefer a few substantive sections over many thin ones, we should combine where possible. Thus maybe we have sections: About the role, Responsibilities, Benefits, Pay. We can embed qualifications and skills within Responsibilities. Let's see: The posting includes "Note: This role may come into contact with confidential or sensitive customer information requiring special treatment in accordance with Red Hat policies and applicable privacy laws." That's a qualification/requirement. Could be included in Responsibilities as a bullet. Thus we can have:
About the role
The Technical Writer 2 exercises judgement in prioritizing work and uses AI tools for quality checks, peer reviews, and draft content generation. Proactively identifies and resolves low-to-moderately complex issues and risks. This level focuses on increasing independence in core execution, taking ownership of content quality, ensuring content clarity and ease of content navigation, and supporting strategic initiatives. Requires moderate supervision; works independently on assigned tasks and content sets. Note: This role may come into contact with confidential or sensitive customer information requiring special treatment in accordance with Red Hat policies and applicable privacy laws.
Responsibilities
- Works with increased independence over time to draft AI-assisted documentation for defined product offerings.
- Fully executes all phases of the technical content development lifecycle from content creation, curation, and archiving content for assigned product areas.
- Demonstrates the ability to understand and incorporate changes based on stakeholder and customer feedback.
- Applies strategic knowledge of end users to ensure content maps well to user needs.
- Develops content that is technically accurate and user focused.
- Ensures accuracy by testing procedures and cross‑functional reviews.
- Proactively identifies and resolves low‑to‑moderately complex project‑related issues and risks early within the assigned content area, escalating to the appropriate team lead when necessary.
- Adheres to required standards for tracking and reporting work.
- Uses AI tools for quality checks, peer reviews, and draft content generation.
Benefits
- Comprehensive medical, dental, and vision coverage
- Flexible Spending Account - healthcare and dependent care
- Health Savings