Technical Editor, Proposals

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. We need to parse the job posting. Content: - Worker Type Regular Summary Job Description (maybe ignore) - Job Description paragraph: "The Technical Editor supports proposal development by reviewing and refining written content to ensure clarity, accuracy, consistency, and compliance. This role works closely with proposal managers, writers, and subject matter experts to produce persuasive, customer-focused, and high-quality proposal materials that align with company and solicitation standards." - Position Responsibilities: list of bullet-like sentences separated by periods? Actually they are sentences separated by periods but not bullet list. We need to treat as list items? The instruction: Use

  • for any list of duties/requirements/benefits. So we need to extract each duty as a list item. Responsibilities sentences: 1. Edit and proofread proposal content for grammar, clarity, consistency, and compliance. 2. Ensure all materials adhere to solicitation instructions, evaluation criteria, and company style guides. 3. Collaborate with proposal teams to improve structure, flow, and readability. 4. Verify data accuracy, terminology consistency, and proper document formatting. 5. Support color team reviews (Pink, Red, Gold) and integrate feedback into final versions. 6. Maintain version control and ensure quality and consistency across all volumes. - Basic Qualifications (Required Skills & Experience): list items: Education: Bachelor’s degree in English, Communications, Technical Writing, Journalism, or related field Experience: 8+ years of editing experience preferably in DoD proposal or technical environments. Strong editing, grammar and writing abilities Proficiency in MS Word, PPT, and Adobe Acrobat Excellent attention to detail, organization, and time management. Ability to manage multiple projects under tight deadlines. - Other Qualifications & Desired Competencies: list items: Experience editing government or corporate proposals (RFP/RFQ responses) Familiarity with AP or Chicago style and MS Teams and SharePoint. Knowledge of Shipley or similar proposal methodologies. TS Clearance - Physical Demands: maybe not needed as a section? Could be part of Requirements? But we have sections: Requirements, Qualifications, Skills. We could map Basic Qualifications to Requirements? Or Qualifications? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which content goes where. "About the role" could be the initial job description paragraph. "Responsibilities" is the list of duties. "Requirements" could be the Basic Qualifications (required skills & experience). Or maybe "Qualifications" for other qualifications? But we have both Requirements and Qualifications headings. We need to split content appropriately. We have Basic Qualifications (Required Skills & Experience) and Other Qualifications & Desired Competencies. Could treat Basic as Requirements, Other as Qualifications. Skills could be extracted from those (like proficiency in MS Word etc.) but we could also put skills under Skills heading. However we must not create thin sections; prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But we have to follow headings only if content exists. We could put Requirements (Basic Qualifications) and Qualifications (Other Qualifications) both as separate sections if they have substantive content. That's okay. Skills: we could extract specific skills like "Strong editing, grammar and writing abilities", "Proficiency in MS Word, PPT, and Adobe Acrobat", "Excellent attention to detail, organization, and time management.", "Ability to manage multiple projects under tight deadlines.", "Experience editing government or corporate proposals (RFP/RFQ responses)", "Familiarity with AP or Chicago style and MS Teams and SharePoint.", "Knowledge of Shipley or similar proposal methodologies.", "TS Clearance". But many of those are already in qualifications. Might be redundant. Better: Use Requirements for Basic Qualifications (education, experience). Use Qualifications for Other Qualifications & Desired Competencies. Use Skills for maybe the specific skill proficiencies (like MS Word, AP/Chicago style, etc.) but that may be thin. Could combine Skills into Qualifications. But we must not create sections with filler/placeholder. If we create Skills section, we need to have substantive content. We could list skills like "MS Word, PowerPoint, Adobe Acrobat", "AP/Chicago style", "MS Teams, SharePoint", "Shipley methodology". That's substantive. Pay: The posting includes "The Salary Range For This Role Is $80,500 - $123,000". So we need a Pay section with that info. Schedule: The posting mentions benefits: "AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." So schedule info: "a 9/80 work schedule". That's a schedule detail. So we can create Schedule section with that. Benefits: The posting includes benefits list: medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown. Also maybe more? That's it. So Benefits section. We also have clearance info: TS Clearance (maybe part of Qualifications). Also ITAR requirement etc. That's legal/boilerplate? The ITAR requirement is substantive? It says "This position requires access to information that is subject to compliance with ITAR/EAR...". That is a requirement (citizenship). Might be considered a qualification (U.S. person). Should we include? It's not boilerplate; it's a specific requirement. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ITAR requirement might be considered legal but it's a job requirement. Might be kept? The instruction says remove legal boilerplate. ITAR requirement is legal but it's a condition of employment. Might be considered boilerplate? Not sure. The posting also includes "Principals only need apply. NO agencies please." That's application instruction, should be removed. Also "About AV" section is company description, maybe could be considered boilerplate? It's not required to remove but could be considered fluff. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About AV" is not explicitly listed to remove, but it's not substantive job content; it's company marketing. Might be considered boilerplate? Not sure. Safer to remove it as it's not directly about the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About AV is substantive about company but not about the role. Might be considered not needed. I'd remove it to keep focus. Also "We are proud to be an EEO/AA Equal Opportunity Employer..." is EEO boilerplate, remove. Also "ITAR" at end maybe duplicate. Thus final sections: - About the role (h3) with paragraph from job description. - Responsibilities (h3) with ul list of duties. - Requirements (h3) with ul list of Basic Qualifications. - Qualifications (h3) with ul list of Other Qualifications & Desired Competencies. - Skills (h3) maybe with ul list of specific skills (MS Word, PowerPoint, Adobe Acrobat, AP/Chicago style, MS Teams, SharePoint, Shipley methodology). Could also include "Strong editing, grammar and writing abilities", "Excellent attention to detail, organization, and time management.", "Ability to manage multiple projects under tight deadlines." But those are more abilities. Might be okay. - Benefits (h3) with ul list: medical, dental vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown. However schedule is also in Benefits; but we also have Schedule section separate. Might duplicate. Better to put schedule in Schedule section, and benefits exclude schedule. Benefits: medical, dental vision, 401K with company matching, paid holiday shutdown. Schedule: 9/80 work schedule. - Pay (h3) with p: $80,500 - $123,000. - Schedule (h3) with p: 9/80 work schedule. We must not create sections with filler. All have content. Check for duplication: Benefits list includes medical, dental vision, 401K with company matching, paid holiday shutdown. Good. Now ensure we don't include any boilerplate like EEO, etc. Now produce HTML fragment: no or . Just the sections. We'll need to wrap each section in appropriate tags:

    About the role

    ...

    etc. For lists:
    • ...
    . Make sure to close tags. Let's draft. About the role paragraph: "The Technical Editor supports proposal development by reviewing and refining written content to ensure clarity, accuracy, consistency, and compliance. This role works closely with proposal managers, writers, and subject matter experts to produce persuasive, customer-focused, and high-quality proposal materials that align with company and solicitation standards." Responsibilities list items as above. Requirements list items: Education: Bachelor’s degree in English, Communications, Technical Writing, Journalism, or related field; Experience: 8+ years of editing experience preferably in DoD proposal or technical environments.; Strong editing, grammar and writing abilities; Proficiency in MS Word, PPT, and Adobe Acrobat; Excellent attention to detail, organization, and time management.; Ability to manage multiple projects under tight deadlines. Qualifications list items: Experience editing government or corporate proposals (RFP/RFQ responses); Familiarity with AP or Chicago style and MS Teams and SharePoint.; Knowledge of Shipley or similar proposal methodologies.; TS Clearance. Skills list items: Could be: Strong editing, grammar and writing abilities; Proficiency in MS Word, PowerPoint, and Adobe Acrobat; Excellent attention to detail, organization, and time management.; Ability to manage multiple projects under tight deadlines.; Experience editing government or corporate proposals (RFP/RFQ responses); Familiarity with AP or Chicago style; Proficiency with MS Teams and SharePoint; Knowledge of Shipley or similar proposal methodologies.; TS Clearance. But that duplicates qualifications. Maybe better to not have Skills section; combine skills into Qualifications. But we already have Qualifications. Could we omit Skills? The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and keep Requirements and Qualifications only. But we need to decide if we need Skills. The posting does not have a separate "Skills" heading; we could infer skills from qualifications. But we can still create a Skills section if we have substantive content not already covered. However it may be thin. I'd rather omit Skills to avoid thin sections. Then we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Check if any section is empty: all have content. Now ensure we didn't include any boilerplate like "Principals only need apply. NO agencies please." removed. Also removed "About AV" and EEO statements. Check for duplicated lines: we have not duplicated. Now produce HTML. Make sure to use proper punctuation inside

    and

  • . No extra spaces. Let's