Sr. Technical Writer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: About Us (maybe About the role?), Position Summary (maybe About the role), Essential Duties & Responsibilities (Responsibilities), Experience And Skills (Requirements/Qualifications/Skills), Preferred Skills & Qualifications (maybe Skills), Job Benefits (Benefits). No explicit Pay or Schedule. So we should not include Pay or Schedule sections.
We must not repeat job title as heading. Use for each section heading. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement and note about job description not comprehensive etc. Those are boilerplate; we should remove them. Also "Please note, this job description does not cover..." is boilerplate; remove. Also "We are an equal opportunity employer..." remove.
We need to keep: The final compensation offer will be determined by factors... That's about compensation but not specific numbers; it's vague. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The compensation statement is vague but it's still stating something about compensation. However it's not a specific number or range; it's generic. The rule says never create Pay section unless posting actually states them. It does state something about compensation: "The final compensation offer will be determined by factors such as the candidate’s skills, qualifications, experience, geographic location, and other relevant factors." That's still vague but it's a statement about compensation. Should we include a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation, albeit vague. However also the rule earlier: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This statement is similar to "commensurate with experience". It's vague. I'd interpret that we should not create a Pay section because it's not specific. So we omit Pay.
Benefits: we have specific benefits listed: 3 weeks PTO, 8 paid holidays, 5 additional days for life events, free medical/dental/vision/life insurance/disability, 401(k) with 100% match up to 4%, Professional Membership Reimbursement, Employee Referral bonus. Those are specific, so include Benefits section.
Schedule: none.
Thus sections: About the role (maybe combine About Us and Position Summary?), Responsibilities, Requirements, Qualifications, Skills, Benefits. However we need to avoid thin sections. Could combine Requirements and Qualifications into one? But the instruction says use headings for those specific names if we have content. We have Experience And Skills (which includes requirements like citizenship, degree, years experience, aptitude, etc.) and Preferred Skills & Qualifications (which includes industry experience and additional tech). Could treat Experience And Skills as Requirements/Qualifications, and Preferred Skills & Qualifications as Skills. Or we could have Requirements (mandatory) and Preferred Skills (optional). Let's map:
- About the role: could include Mission, About Us, Position Summary. That's substantive.
- Responsibilities: Essential Duties & Responsibilities.
- Requirements: Experience And Skills (the mandatory list: US citizenship, Bachelor's degree, 15+ years experience, aptitude, experience researching, experience with at least one XML editor, experience writing DITA/XML, in-depth knowledge of standards, excellent interpersonal skills, proven ability to write for both audiences, experience working independently/team, proficiency in budget/scope/deadlines). That's a list.
- Skills: Preferred Skills & Qualifications (industry experience, additional apps/tech). Could be Skills.
- Benefits: Job Benefits.
We should not duplicate content. Ensure we preserve all details.
We need to format lists as
- . For prose, use
.
We need to avoid repeating job title heading.
We need to output only HTML fragment.
Let's craft:
About the role
Our Mission: We aim to be the leading provider of content management software and expertise, helping clients create, manage, publish, and deliver high-value content.
About Us: Contiem, Inc. is a global Component Content Management System (CCMS) and expertise partner. We specialize in creating, managing, and delivering high-value content - technical documentation, eLearning, online help, visualizations, training materials, etc. We continuously challenge the status quo and empower organizations by delivering effective content solutions that help clients achieve their business objectives. Contiem headquarters is located in Annapolis, MD, with additional locations in the US and internationally in Sutton, UK, Chennai, India, and Sydney, Australia. Our elite team of subject matter experts works closely with clients to assess, optimize, and transform their content objectives and operations. Our global team allows us to support clients in 40 countries, including many of the world's largest companies and iconic brands, from various industries such as Publishing, Consumer Products, Healthcare, Technology, and Financial Services.
Position Summary: Contiem is seeking a Senior Technical Writer to lead and enhance the quality of documentation across our diverse client portfolio. This position requires someone who excels at managing multiple projects and embraces continuous learning. The ideal candidate brings 15+ years of technical writing experience, thrives in a fast-paced environment, and can confidently support clients with varying standards and expectations. They demonstrate strong writing skills and the ability to adapt their expertise to evolving client needs.
Then Responsibilities:
Responsibilities
- Take a big-picture view of large amounts of content, determining the content information model and the best way to simplify the authoring process for this content.
- Collaborate with subject matter experts (SMEs), project managers, and the writing team to ensure the documentation aligns with the prescribed standards and is communicated to the appropriate audience.
- Lead documentation projects from planning through publication. Effectively manage timelines, especially when handling multiple projects or clients. This includes keeping the project managers informed of developments and roadblocks.
- Create and update technical documentation for assigned products and projects for clients as required. Documentation could include Product Manuals, IOMs, SOPs, software user guides, and online help resources such as FAQs, knowledge base articles, and help desk content.
- Ensure documents are accurate and follow the clearly defined standards by the client and Contiem.
- Proofread their peers’ work, following Contiem or client guidelines, when applicable. Provide appropriate, comprehensive feedback and accept and incorporate feedback into their own work.
- Utilize content management systems to create and manage documentation.
- Advocate for the user experience by ensuring documentation is intuitive, helpful, and aligned with product design.
- Mentor and help develop the skill sets of junior writers to contribute to the growth of the documentation team.
- Learn new skills and implement new practices and procedures as required by Contiem or the client.
- Be detail-oriented and follow the best practices and principles of good technical writing.
- Other duties as assigned.
Then Requirements:
Requirements
- U.S. citizenship.
- Bachelor’s degree in technical writing, journalism, communications, or related field.
- 15+ years of experience in technical writing, with technical writing being your primary job function.
- Aptitude for understanding mechanical and electronic products.
- Experience with researching and gathering relevant technical data from subject matter experts such as engineers, field service personnel, and developers, as well as from internal documents such as CAD drawings and design documents.
- Experience using at least one of the following applications: oXygen Editor, Arbortext, or XMetal.
- Experience with writing documentation in DITA/XML.
- In-depth knowledge of standards and best practices for writing assembly, installation, operation, and maintenance documentation.
- Possess excellent interpersonal and general business communication skills.
- Proven ability to write for both technical and non-technical audiences.
- Experience working independently as well as in a team-oriented, collaborative environment.
- Proficiency working in an environment driven by budget, scope, and deadlines across multiple clients/projects.
Then Skills (Preferred):
Skills
- Experience in one of the following industries: manufacturing, industrial, government, publishing, healthcare, technology, consumer products, software, IT documentation, and business & financial services.
- Additional experience using the following applications and technologies is preferred: Adobe InDesign, Microsoft Word, Adobe Acrobat Professional, Visual Studio Code, NotePad++ or related editor, Jira and/or GitHub, REST API’s, JSON, Confluence, Adobe Illustrator, Photoshop, MadCap Flare, Markdown, FrameMaker, Microsoft Visio, Microsoft PowerPoint, Articulate 360.
Then Benefits:
Benefits
- 3 weeks of PTO, 8 paid holidays, 5 additional days for life events such as adoption, childbirth, and marriage.
- Free medical, dental, vision, life insurance and disability coverage.
- 401(k) with 100% match of up to 4% of contributions and with immediate vesting.
- Professional Membership Reimbursement.
- Employee Referral bonus.
We must not include any extra text. Ensure no markdown fences. Just raw HTML.
Check for any leftover boilerplate: we removed EEO statement and note about job description not comprehensive. Good.
Check for any duplicated lines: we didn't duplicate.
Check that we didn't include Pay or Schedule sections. Good.
Check that we didn't include any filler like "commensurate with experience". We didn't.
All substantive info preserved: Mission, About Us, Position Summary, Responsibilities, Requirements, Skills, Benefits.
Check that we kept the bullet about "Other duties as assigned." Yes.
Check that we kept the bullet about "Experience using at least one of the following applications: oXygen Editor, Arbortext, or XMetal." Yes.
Check that we kept the bullet about "Experience with writing documentation in DITA/XML." Yes.
Check that we kept the bullet about "In-depth knowledge of standards and best practices for writing assembly, installation, operation, and maintenance documentation." Yes.
Check that we kept the bullet about "Possess excellent interpersonal and general business communication skills." Yes.
Check that we kept the bullet about "Proven ability to write for both technical and non-technical audiences." Yes.
Check that we kept the bullet about "Experience working independently as well as in a team-oriented, collaborative environment." Yes.
Check that we kept the bullet about "Proficiency working in an environment driven by budget, scope, and deadlines across multiple clients/projects." Yes.
Check that we kept the bullet about "U.S. citizenship." Yes.
Check that we kept the bullet about "Bachelor’s degree in technical writing, journalism, communications, or related field." Yes.
Check that we kept the bullet about "15+ years of experience in technical writing, with technical writing being your primary job function." Yes.
Check that we kept the bullet about "Aptitude for understanding mechanical and electronic products." Yes.
Check that we kept the bullet about "Experience with researching and gathering relevant technical data from
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement and note about job description not comprehensive etc. Those are boilerplate; we should remove them. Also "Please note, this job description does not cover..." is boilerplate; remove. Also "We are an equal opportunity employer..." remove. We need to keep: The final compensation offer will be determined by factors... That's about compensation but not specific numbers; it's vague. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The compensation statement is vague but it's still stating something about compensation. However it's not a specific number or range; it's generic. The rule says never create Pay section unless posting actually states them. It does state something about compensation: "The final compensation offer will be determined by factors such as the candidate’s skills, qualifications, experience, geographic location, and other relevant factors." That's still vague but it's a statement about compensation. Should we include a Pay section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation, albeit vague. However also the rule earlier: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This statement is similar to "commensurate with experience". It's vague. I'd interpret that we should not create a Pay section because it's not specific. So we omit Pay. Benefits: we have specific benefits listed: 3 weeks PTO, 8 paid holidays, 5 additional days for life events, free medical/dental/vision/life insurance/disability, 401(k) with 100% match up to 4%, Professional Membership Reimbursement, Employee Referral bonus. Those are specific, so include Benefits section. Schedule: none. Thus sections: About the role (maybe combine About Us and Position Summary?), Responsibilities, Requirements, Qualifications, Skills, Benefits. However we need to avoid thin sections. Could combine Requirements and Qualifications into one? But the instruction says use headings for those specific names if we have content. We have Experience And Skills (which includes requirements like citizenship, degree, years experience, aptitude, etc.) and Preferred Skills & Qualifications (which includes industry experience and additional tech). Could treat Experience And Skills as Requirements/Qualifications, and Preferred Skills & Qualifications as Skills. Or we could have Requirements (mandatory) and Preferred Skills (optional). Let's map: - About the role: could include Mission, About Us, Position Summary. That's substantive. - Responsibilities: Essential Duties & Responsibilities. - Requirements: Experience And Skills (the mandatory list: US citizenship, Bachelor's degree, 15+ years experience, aptitude, experience researching, experience with at least one XML editor, experience writing DITA/XML, in-depth knowledge of standards, excellent interpersonal skills, proven ability to write for both audiences, experience working independently/team, proficiency in budget/scope/deadlines). That's a list. - Skills: Preferred Skills & Qualifications (industry experience, additional apps/tech). Could be Skills. - Benefits: Job Benefits. We should not duplicate content. Ensure we preserve all details. We need to format lists as
- . For prose, use
. We need to avoid repeating job title heading. We need to output only HTML fragment. Let's craft:
About the role
Our Mission: We aim to be the leading provider of content management software and expertise, helping clients create, manage, publish, and deliver high-value content.
About Us: Contiem, Inc. is a global Component Content Management System (CCMS) and expertise partner. We specialize in creating, managing, and delivering high-value content - technical documentation, eLearning, online help, visualizations, training materials, etc. We continuously challenge the status quo and empower organizations by delivering effective content solutions that help clients achieve their business objectives. Contiem headquarters is located in Annapolis, MD, with additional locations in the US and internationally in Sutton, UK, Chennai, India, and Sydney, Australia. Our elite team of subject matter experts works closely with clients to assess, optimize, and transform their content objectives and operations. Our global team allows us to support clients in 40 countries, including many of the world's largest companies and iconic brands, from various industries such as Publishing, Consumer Products, Healthcare, Technology, and Financial Services.
Position Summary: Contiem is seeking a Senior Technical Writer to lead and enhance the quality of documentation across our diverse client portfolio. This position requires someone who excels at managing multiple projects and embraces continuous learning. The ideal candidate brings 15+ years of technical writing experience, thrives in a fast-paced environment, and can confidently support clients with varying standards and expectations. They demonstrate strong writing skills and the ability to adapt their expertise to evolving client needs.
Then Responsibilities:Responsibilities
- Take a big-picture view of large amounts of content, determining the content information model and the best way to simplify the authoring process for this content.
- Collaborate with subject matter experts (SMEs), project managers, and the writing team to ensure the documentation aligns with the prescribed standards and is communicated to the appropriate audience.
- Lead documentation projects from planning through publication. Effectively manage timelines, especially when handling multiple projects or clients. This includes keeping the project managers informed of developments and roadblocks.
- Create and update technical documentation for assigned products and projects for clients as required. Documentation could include Product Manuals, IOMs, SOPs, software user guides, and online help resources such as FAQs, knowledge base articles, and help desk content.
- Ensure documents are accurate and follow the clearly defined standards by the client and Contiem.
- Proofread their peers’ work, following Contiem or client guidelines, when applicable. Provide appropriate, comprehensive feedback and accept and incorporate feedback into their own work.
- Utilize content management systems to create and manage documentation.
- Advocate for the user experience by ensuring documentation is intuitive, helpful, and aligned with product design.
- Mentor and help develop the skill sets of junior writers to contribute to the growth of the documentation team.
- Learn new skills and implement new practices and procedures as required by Contiem or the client.
- Be detail-oriented and follow the best practices and principles of good technical writing.
- Other duties as assigned.
Requirements
- U.S. citizenship.
- Bachelor’s degree in technical writing, journalism, communications, or related field.
- 15+ years of experience in technical writing, with technical writing being your primary job function.
- Aptitude for understanding mechanical and electronic products.
- Experience with researching and gathering relevant technical data from subject matter experts such as engineers, field service personnel, and developers, as well as from internal documents such as CAD drawings and design documents.
- Experience using at least one of the following applications: oXygen Editor, Arbortext, or XMetal.
- Experience with writing documentation in DITA/XML.
- In-depth knowledge of standards and best practices for writing assembly, installation, operation, and maintenance documentation.
- Possess excellent interpersonal and general business communication skills.
- Proven ability to write for both technical and non-technical audiences.
- Experience working independently as well as in a team-oriented, collaborative environment.
- Proficiency working in an environment driven by budget, scope, and deadlines across multiple clients/projects.
Skills
- Experience in one of the following industries: manufacturing, industrial, government, publishing, healthcare, technology, consumer products, software, IT documentation, and business & financial services.
- Additional experience using the following applications and technologies is preferred: Adobe InDesign, Microsoft Word, Adobe Acrobat Professional, Visual Studio Code, NotePad++ or related editor, Jira and/or GitHub, REST API’s, JSON, Confluence, Adobe Illustrator, Photoshop, MadCap Flare, Markdown, FrameMaker, Microsoft Visio, Microsoft PowerPoint, Articulate 360.
Benefits
- 3 weeks of PTO, 8 paid holidays, 5 additional days for life events such as adoption, childbirth, and marriage.
- Free medical, dental, vision, life insurance and disability coverage.
- 401(k) with 100% match of up to 4% of contributions and with immediate vesting.
- Professional Membership Reimbursement.
- Employee Referral bonus.
- . For prose, use