Technical Writer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes "Who We Are" (company description) and description of role, responsibilities, skills and experience, education, qualifications, why Tria (benefits/culture). No explicit Pay or Schedule. So we should not create Pay or Schedule sections. Benefits: there is mention of "top-tier benefits package" but not specific details; that is vague. The rule says: never create Benefits section unless posting actually states them. It says "top-tier benefits package to invest in your physical, mental, and financial health and wellness". That's still vague but it's a statement about benefits. Might be considered real content? It's not specific like health insurance, 401k, etc. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits package, albeit generic. I'd include a Benefits section with that statement. However we must avoid filler like "commensurate with experience". This is not filler. So we can include Benefits with that sentence. We also need About the role heading? The posting includes description of role after "Who We Are". Could treat that as About the role. We'll include About the role section with the paragraph(s) describing the role. Responsibilities: there is a "Responsibilities" heading in the posting with bullet points. We'll capture that. Skills And Experience: heading "Skills And Experience". We'll treat as Skills section. Education: there is Education heading. Could be part of Requirements or Qualifications? The posting also has Qualifications heading after Education? Actually after Education there is "Qualifications" heading with list. So we have Education and Qualifications separate. We'll follow the allowed headings: Requirements, Qualifications, Skills. Education could be part of Requirements or Qualifications. But we have both Education and Qualifications headings in posting. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't list Education as allowed; we should fold Education into Requirements or Qualifications. Probably Requirements includes education. We'll put education under Requirements. Qualifications: we have a Qualifications heading with list. We'll output that. Skills: we have Skills And Experience heading; we'll output Skills. Benefits: we have Why Tria? includes benefits package statement; we can put Benefits. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes CCPA statement at end; that's legal boilerplate; we should remove it. Also "California Consumer Privacy Act (CCPA)" etc. Remove. Also remove "Who We Are" maybe treat as About the role? Actually "Who We Are" is company description; could be part of About the role? But we already have About the role for the position description. Could also include a short company overview under About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely refers to role description, not company. But we could include company description as part of About the role? Might be okay. However we could also omit company description if not needed? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the "Who We Are" paragraph. Where to put? Could be part of About the role section preceding role specifics. We'll include it there. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

About the role

Who We Are Tria Federal delivers ... (the who we are paragraph) ... The Technical Writer will work directly ... (rest of role description).

But we need to ensure we don't duplicate sentences. Let's extract the relevant text. Original "Who We Are" paragraph: "Who We Are Tria Federal delivers digital services and technology solutions that support the health and safety of veterans, service members and civilians. For two decades, federal agencies have relied on Tria companies to advance their critical missions and modernize their systems, so that they can uphold their commitment to the American people. Today, we are pushing the boundaries of possibility through partnerships and investments in artificial intelligence and emerging technologies, developing solutions for the biggest challenges that government will face tomorrow. We are proud to employ and support military veterans who bring mission-first mindset, technical expertise, and leadership qualities that strengthen our work. Veterans, transitioning service members, and military spouses are strongly encouraged to apply." Then after that: "Tria Federal is seeking an experienced Technical Writer – Acquisition & Policy Documentation Specialist to support the Department of Veterans Affairs (VA), Veterans Health Administration (VHA), Veteran Community Care Program. The Technical Writer will work directly with Government leaders, acquisition professionals, contracting personnel, program managers, healthcare subject matter experts, policy owners, and technical teams to develop clear, accurate, actionable, and compliant acquisition and policy documentation. The position will have a particular focus on supporting the Government in the development and refinement of Requests for Proposals (RFPs), Performance Work Statements (PWSs), Statements of Work (SOWs), Statements of Objectives (SOOs), acquisition planning documents, evaluation criteria, policies, Standard Operating Procedures (SOPs), operational guidance, governance documents, and executive-level written products. The successful candidate will be able to take complex or initially ambiguous information from multiple stakeholders and transform it into structured Government documentation that clearly communicates requirements, responsibilities, performance expectations, decision authority, and intended outcomes. This position requires more than proofreading and formatting. The Technical Writer will serve as an active documentation partner, facilitating working sessions, asking clarifying questions, identifying inconsistencies and gaps, organizing requirements, managing document-development cycles, and helping Government stakeholders produce documents that are understandable, internally consistent, traceable, and operationally actionable." We'll combine into one paragraph maybe split into multiple

but rule says use

for prose. Could have multiple

under same section. That's fine. Next Responsibilities: we have a heading "Responsibilities" then bullet list. We'll output

Responsibilities

then

• each bullet. We need to capture all bullet points under Responsibilities. Let's extract them. From posting: "Responsibilities Acquisition and RFP Development Support Government acquisition teams in developing, editing, organizing, and maintaining acquisition documentation throughout the pre-solicitation and solicitation lifecycle.Facilitate working sessions with Government program, acquisition, contracting, financial, clinical, technical, and operational SMEs to gather and document requirements.Translate Government mission and operational requirements into clear, concise, measurable, and enforceable acquisition language.Draft and/or edit:Requests for Proposals (RFPs)Performance Work Statements (PWSs)Statements of Work (SOWs)Statements of Objectives (SOOs)Acquisition plans and supporting documentationRequirements documentationMarket research and industry-analysis reportsInstructions to offerorsTechnical and management evaluation criteriaQuality Assurance Surveillance Plans (QASPs)Performance requirements and standardsDeliverable descriptionsContract transition and operationalization documentationHelp Government stakeholders distinguish between mission outcomes, functional requirements, performance requirements, deliverables, and prescribed solutions.Review acquisition documents for completeness, consistency, clarity, duplication, conflicting requirements, undefined terminology, and ambiguous language.Support traceability between program requirements, PWS/SOW sections, deliverables, performance standards, and evaluation criteria.Maintain document comment matrices and facilitate adjudication of comments from program offices, contracting, legal, technical SMEs, and other stakeholders.Assist acquisition teams with document configuration management, version control, approval tracking, and solicitation-readiness reviews. Policy and Operational Documentation Research, draft, edit, and maintain Government policies, directives, SOPs, operational guidance, desk procedures, governance documents, and implementation materials.Translate complex statutes, regulations, contract requirements, Government policies, leadership decisions, and program requirements into understandable operational guidance.Work with policy owners and SMEs to clearly define:Purpose and scopeAuthorities and referencesRoles and responsibilitiesDecision rightsBusiness rulesRequired proceduresExceptionsEscalation pathwaysDocumentation requirementsPerformance measuresCompliance requirementsFacilitate policy-development sessions to identify gaps, conflicting interpretations, undefined ownership, and areas requiring Government decisions.Ensure policies and procedures distinguish between mandatory requirements, recommended practices, guidance, and locally determined processes.Develop current-state and future-state workflow documentation in coordination with operational SMEs.Develop and maintain SOPs, workflow narratives, process guides, implementation playbooks, FAQs, job aids, and quick-reference materials.Establish document review and maintenance schedules to ensure policies and procedures remain current as contracts, organizations, systems, and regulatory requirements evolve.Support implementation of new policies through communications, training materials, stakeholder guidance, and change-management documentation." We need to split into sensible bullet items. The original had no punctuation between items; we need to infer bullet boundaries. Could break at capital letters after a period? The text is messy. However we must preserve ALL substantive information; we can't invent or summarize away detail. We could keep as a single
  • with the whole block? That would lose bullet separation but still preserve info. The rule: Use
    • for any list of duties/requirements/benefits. If we treat the whole as one list item, it's still a list but not ideal. Better to split where there are clear periods. Let's attempt to split by periods that end a sentence. I'll copy the responsibilities block and manually split. Block: "Acquisition and RFP Development Support Government acquisition teams in developing, editing, organizing, and maintaining acquisition documentation throughout the pre-solicitation and solicitation lifecycle. Facilitate working sessions with Government program, acquisition, contracting, financial, clinical, technical, and operational SMEs to gather and document requirements. Translate Government mission and operational requirements into clear, concise, measurable, and enforceable acquisition language. Draft and/or edit: Requests for Proposals (RFPs) Performance Work Statements (PWSs) Statements of Work (SOWs) Statements of Objectives (SOOs) Acquisition plans and supporting documentation Requirements documentation Market research and industry-analysis reports Instructions to offerors Technical and management evaluation criteria Quality Assurance Surveillance Plans (QASPs) Performance requirements and standards Deliverable descriptions Contract transition and operationalization documentation Help Government stakeholders distinguish between mission outcomes, functional requirements, performance requirements, deliverables, and prescribed solutions. Review acquisition documents for completeness, consistency, clarity, duplication, conflicting requirements, undefined terminology, and ambiguous language. Support traceability between program requirements, PWS/SOW sections, deliverables, performance standards, and evaluation criteria. Maintain document comment matrices and facilitate adjudication of comments from program offices, contracting, legal, technical SMEs, and other stakeholders. Assist acquisition teams with document configuration management, version control, approval tracking, and solicitation-readiness reviews. Policy and Operational Documentation Research, draft, edit, and maintain Government policies, directives, SOPs, operational guidance, desk procedures, governance documents, and implementation materials. Translate complex statutes, regulations, contract requirements, Government policies, leadership decisions, and program requirements into understandable operational guidance. Work with policy owners and SMEs to clearly define: Purpose and scope Authorities and references Roles and responsibilities Decision rights Business rules Required procedures Exceptions Escalation pathways Documentation requirements Performance measures Compliance requirements Facilitate policy-development sessions to identify gaps, conflicting interpretations, undefined ownership, and areas requiring Government decisions. Ensure policies and procedures distinguish between mandatory requirements, recommended practices, guidance, and locally determined processes. Develop current-state and future-state workflow documentation in coordination with operational SMEs. Develop and maintain SOPs, workflow narratives, process guides, implementation playbooks, FAQs, job aids, and quick-reference materials. Establish document review and maintenance schedules to ensure policies and procedures