Senior Technical Writer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must preserve all substantive info. We need to parse the posting. Key content: - Title: Senior Technical Writer (but we don't repeat as heading) - Location: Salt Lake City, Utah - Job ID: 51387 (metadata, can be folded into short p or dropped) - We are seeking a skilled Compliance Technical Writer to join our team. This role will support the ongoing maintenance, updating, and documentation of standard operating procedures, ensuring all materials meet regulatory, policy, and compliance requirements. The Compliance Technical Writer will play a critical part in producing documentation that reflects the highest standard of clarity, precision, and alignment with organizational and compliance expectations. You will be responsible for auditing and evaluating current knowledge‑management content, identifying compliance gaps, and ensuring all documents are accurate, consistent, compliant, and easy to use. This includes validating procedures that adhere to internal policies, external regulatory standards, and established compliance frameworks. The successful candidate will collaborate closely with technical staff and compliance partners to update existing documentation and create new materials when necessary. The ideal candidate will have experience with compliance policies and procedures, strong analytical skills, and excellent written and verbal communication skills. - Who are we? HID powers the trusted identities... (company description). This is about the company, maybe "About the company" but not required heading. Could be part of "About the role"? Might be separate but we can include as a paragraph under "About the role" or maybe separate "About the company". Not required heading but we can include as prose. - Then "As our Senior Technical Writer, you’ll support HID’s success by:" followed by bullet list of duties. Those are responsibilities. - Then "Your Experience and Background include:" list of qualifications/skills. - Then "What we can offer you:" list of benefits. - Then "Why apply?" with bullet points (Empowerment, Innovation, Integrity) maybe more like benefits/culture. - Then more company info about HID, ASSA ABLOY group etc. Could be considered "About the company". Might be optional. - Also includes statements about immigration sponsorship not available, equal opportunity, etc. Those are boilerplate to remove. - Also includes "We make it easier for people to get where they want to go!" etc. Might be fluff but could be considered company description. We need to decide sections: - About the role: could include overview of role, location, maybe company description? Usually "About the role" includes description of what the role entails. We have a paragraph at start describing role. Could put that. - Responsibilities: the bullet list after "As our Senior Technical Writer, you’ll support HID’s success by:" (multiple bullet points). We'll put each as

. - Requirements: maybe the "Your Experience and Background include:" list (skills, experience). Could be split into Requirements and Qualifications and Skills. But we need to decide which sections to include based on content. We have sections: Experience and Background (includes ability to engage in technical discussions, experience generating PDF/HTML, strong writing, etc). Also includes "3-6 years of experience..." etc. Also includes "B.A. in English..." etc. Also includes "Clear understanding of SDLC..." etc. Also includes "Proficiency with defect tracking systems..." etc. Also includes "Experience in SAFe Agile..." etc. We could categorize: - Requirements: maybe the mandatory items: 3-6 years experience, B.A. preferred, ability to engage in technical discussions, strong writing, etc. - Qualifications: maybe education, certifications. - Skills: maybe technical skills like PDF/HTML, SharePoint, JIRA, Git, etc. But we need to avoid thin sections. Could combine into one "Requirements and Qualifications" but we must use headings exactly as allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with substantive content. We have Benefits: "What we can offer you:" includes Competitive salary and rewards package, Competitive benefits and annual leave offering, allowing for work-life balance, A vibrant, welcoming & inclusive culture, Extensive career development opportunities and resources to maximize your potential, To be a part of a global organization that is pioneering the hardware, software and services that allow people to confidently navigate the physical and digital worlds. Also "Why apply?" includes Empowerment, Innovation, Integrity bullet points. Those could be part of Benefits or separate but we can include them under Benefits as they are offerings. Pay: Not explicitly stated; only "Competitive salary and rewards package" but no specific numbers. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary and rewards package" which is a statement about pay, albeit not specific. Is that enough? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary and rewards package". That is a statement about pay, albeit vague. Should we include Pay section? The instruction: "Prefer a few substantive sections over many thin ones." Also "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive salary and rewards package" is not filler like "commensurate with experience"? It's somewhat generic but still a statement. Might be okay to include Pay section with that sentence. Schedule: Not mentioned. No schedule info. So we should not include Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't repeat job title as heading. Good. We need to fold minor metadata (Location, Job ID) into a short p or drop it. We can include location in About the role paragraph. We must remove boilerplate: EEO, immigration sponsorship, equal opportunity, etc. Also remove duplicated lines (like the repeated line about HID Global IAM products protect more than 85 million user identities appears twice). We'll keep only one. We must preserve all substantive information. So we need to keep company description, role description, responsibilities, experience/background, benefits, pay statement. We must not include application instructions, etc. Now craft HTML. We'll start with

About the role

then a

containing role overview and location. Then

Responsibilities

then

• ... each duty. Then

  Requirements

  then
  • ... maybe the mandatory experience and ability items. Then

    Qualifications

    then
    • ... education, BA preferred, etc. Then

      Skills

      then
      • ... technical skills: PDF/HTML, SharePoint, JIRA, Git, etc. Then

        Benefits

        then
        • ... benefits list. Then

          Pay

          then

          Competitive salary and rewards package.

          We must ensure not to include filler like "commensurate with experience". In the qualifications we have "B. A. in English, Journalism, Communications, or related fields preferred; commensurate experience will be considered." That includes "commensurate experience will be considered." That's filler? It's somewhat generic but it's part of the posting. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . It refers to headings with filler text, not necessarily prohibiting the phrase inside content. However, we might want to avoid including that phrase if it's considered filler. But it's part of the qualifications sentence. The instruction: "Prefer a few substantive sections over many thin ones." It doesn't say to remove that phrase from content. It says never emit a heading followed by filler/placeholder text. So as long as we have a heading with substantive content, it's okay if the content includes that phrase. However, we might want to rephrase to avoid filler? But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the exact phrase? It says preserve ALL substantive information; do NOT invent or summarize away detail. The phrase "commensurate experience will be considered." is substantive? It's a qualifier but maybe considered filler. However, it's part of the original posting. I'd keep it. Now let's extract specifics. About the role paragraph: We have: "We are seeking a skilled Compliance Technical Writer to join our team. This role will support the ongoing maintenance, updating, and documentation of standard operating procedures, ensuring all materials meet regulatory, policy, and compliance requirements. The Compliance Technical Writer will play a critical part in producing documentation that reflects the highest standard of clarity, precision, and alignment with organizational and compliance expectations. You will be responsible for auditing and evaluating current knowledge‑management content, identifying compliance gaps, and ensuring all documents are accurate, consistent, compliant, and easy to use. This includes validating procedures that adhere to internal policies, external regulatory standards, and established compliance frameworks. The successful candidate will collaborate closely with technical staff and compliance partners to update existing documentation and create new materials when necessary. The ideal candidate will have experience with compliance policies and procedures, strong analytical skills, and excellent written and verbal communication skills." Also location: Salt Lake City, Utah. Job ID: 51387 (metadata). We'll include location in paragraph maybe at end: "Location: Salt Lake City, Utah." Could drop Job ID. Now responsibilities list from "As our Senior Technical Writer, you’ll support HID’s success by:" bullet points: - Developing, updating, and maintaining compliance and technical documentation, including policies, procedures, standards, guidelines, and supporting materials to ensure alignment with regulatory, contractual, and internal control requirements. - Providing input on Certificate Policy (CP) and Certification Practices Statements (CPS) for the ongoing support of various Public Key Infrastructure (PKI) programs. - Serving as the point of contact for teams on Policy related questions. - Auditing existing documentation for accuracy, completeness, consistency, compliance gaps, and alignment with frameworks such as SOC 2, internal security policies, and governance requirements; recommending improvements where needed. - Translating complex compliance and technical concepts into clear, concise, accessible content suitable for both technical and non‑technical audiences across the organization. - Ensuring version control and document governance, maintaining accurate historical records, tracking revisions, and supporting annual or periodic policy reviews. - Supporting internal and external audit activities, providing documentation updates, clarifications, and evidence as required. - Monitoring regulatory and industry changes, ensuring documentation is updated proactively to reflect new requirements, risks, or best practices. - Creating templates, style guides, and documentation standards that promote consistency, clarity, and compliance across all controlled documents. - Coordinating reviews and approvals with compliance officers, risk owners, security staff, and leadership to ensure timely publication of updated materials. - Maintaining documentation repositories and knowledge‑management systems, ensuring content is easy to navigate, searchable, and accessible to authorized users. - Identifying content gaps and process inefficiencies, recommending enhancements to improve compliance, usability, and operational effectiveness. - Assisting in drafting compliance communications, training materials, and guidance documents to support policy rollout and awareness campaigns. Now requirements list from "Your Experience and Background include:" but we need to separate into Requirements, Qualifications, Skills. Let's parse the list: - Ability to engage in technical discussions and understand complex technical concepts. - Experience generating PDF and HTML online help deliverables. - Strong writing and editing skills, with a keen eye for detail and accuracy. - Experience creating instructional documentation for both technical and non-technical users. - Ability to analyze explicit and implicit product requirements and determine the appropriate ways to address documentation needs. - Excellent written and verbal communication skills, with