Technical Editor, Proposals

We need to output HTML fragment with sections: About the role? Actually we have job description summary. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not put Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions, duplicated lines. We need to parse the posting. Key content: - Job type: Regular (maybe not needed) - Summary: Job Description: 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 bullet points: - Edit and proofread proposal content for grammar, clarity, consistency, and compliance. - Ensure all materials adhere to solicitation instructions, evaluation criteria, and company style guides. - Collaborate with proposal teams to improve structure, flow, and readability. - Verify data accuracy, terminology consistency, and proper document formatting. - Support color team reviews (Pink, Red, Gold) and integrate feedback into final versions. - Maintain version control and ensure quality and consistency across all volumes. - Basic Qualifications (Required Skills & Experience): - 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: - 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: - Ability to work in an office environment (Constant) - Required to sit and stand for long periods; talk, hear, and use hands and fingers to operate a computer and telephone keyboard (Frequent) - Clearance Level: Top Secret - The Salary Range For This Role Is $80,500 - $123,000 - 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. For more information about our company benefit offerings please visit: http://www.avinc.com/myavbenefits. We also encourage you to review our company website at http://www.avinc.com to learn more about us. - About AV: paragraph describing company. - EEO etc: we need to remove boilerplate EEO/equal-opportunity etc. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statements. - Also remove "Principals only need apply. NO agencies please." That's application instruction? Probably remove. - Also remove "ITAR Requirement ..."? That's legal? Might be considered legal/boilerplate? It's about compliance; maybe keep? The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. ITAR requirement is legal but maybe relevant to role? It's a requirement. Might be considered substantive? It's about eligibility. Could be considered a qualification? Might keep as part of qualifications? But it's a legal requirement. The instruction says remove legal boilerplate. However ITAR requirement is specific to the role; but it's still legal. I'd lean to keep it as part of "Other Qualifications" maybe? But we already have Other Qualifications & Desired Competencies includes TS Clearance. ITAR requirement is separate. Might be considered a qualification: "must qualify as a U.S. person under ITAR/EAR". That is a requirement. Could be included under Requirements or Qualifications. Since we have a Qualifications section maybe we can include it there. But we need to decide sections: We have About the role (summary), Responsibilities, Requirements (maybe Basic Qualifications), Qualifications (Other Qualifications & Desired Competencies), Skills (maybe proficiency etc), Benefits, Pay, Schedule (9/80 work schedule mentioned). Also we have Physical Demands maybe could be part of Requirements? Not a standard heading; we could include under Requirements or maybe omit if not fitting headings. The instruction: Use headings only for those listed; we can create sections only if posting has real specific content for them. We can include Physical Demands under Requirements maybe as a list item? But we must not invent headings not listed. So we can embed physical demands under Requirements as a list item. Similarly, Clearance Level Top Secret could be under Requirements or Qualifications. Salary Range: we have Pay section. Benefits: we have Benefits section. Schedule: we have 9/80 work schedule mentioned under Benefits; but schedule could be separate section if we have info. The posting mentions "a 9/80 work schedule". That's schedule info. So we can create Schedule section with that detail. We must not create sections with filler like "commensurate with experience". We have actual data. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can reorganize into headings and lists. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

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

• Edit and proofread proposal content for grammar, clarity, consistency, and compliance.
• Ensure all materials adhere to solicitation instructions, evaluation criteria, and company style guides.
• Collaborate with proposal teams to improve structure, flow, and readability.
• Verify data accuracy, terminology consistency, and proper document formatting.
• Support color team reviews (Pink, Red, Gold) and integrate feedback into final versions.
• Maintain version control and ensure quality and consistency across all volumes.

Requirements

• Bachelor’s degree in English, Communications, Technical Writing, Journalism, or related field
• 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
• Ability to work in an office environment (constant)
• Required to sit and stand for long periods; talk, hear, and use hands and fingers to operate a computer and telephone keyboard (frequent)
• Top Secret clearance
• Must qualify as a U.S. person under ITAR/EAR (or be eligible for an export license)

But we need to separate Skills maybe? The instruction includes Skills heading. We could put technical skills under Skills: Proficiency in MS Word, PPT, Adobe Acrobat, familiarity with AP/Chicago style, MS Teams, SharePoint, knowledge of Shipley methodology. Also editing abilities etc. However we already have many under Requirements. Might be better to split: Requirements for education/experience, Skills for technical proficiencies, Qualifications for other desired competencies (like TS clearance, proposal experience). But we have overlapping. We need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. We need to decide what goes where. Let's extract: - About the role: summary paragraph. - Responsibilities: list as above. - Requirements: education, years experience, ability to manage multiple projects, etc. Also maybe physical demands? Could be under Requirements. - Skills: proficiency in MS Word, PPT, Adobe Acrobat; strong editing, grammar, writing abilities; excellent attention to detail, organization, time management; familiarity with AP or Chicago style; MS Teams and SharePoint; knowledge of Shipley or similar proposal methodologies. - Qualifications: other qualifications & desired competencies: experience editing government or corporate proposals (RFP/RFQ responses); TS Clearance; maybe ITAR requirement. - Benefits: medical, dental vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown, link to benefits page, link to company website. - Pay: salary range $80,500 - $123,000. - Schedule: 9/80 work schedule (though already in Benefits). But we could still have Schedule section with that detail; but we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid duplication. However we could put schedule info only under Schedule and not repeat under Benefits. But Benefits also mentions 9/80 work schedule; we could keep it there and not have separate Schedule. But we need to include Schedule section only if posting has real specific content for it. It does: "a 9/80 work schedule". So we could have Schedule section with that detail, and Benefits section without that phrase (maybe just medical, dental vision, 401K, paid holiday shutdown). However we must preserve all substantive information; if we remove the phrase from Benefits, we still have it in Schedule, so it's preserved. That's okay. Thus Benefits: medical, dental vision, 401K with company matching, paid holiday shutdown. plus links. Schedule: 9/80 work schedule. Now we need to ensure we don't create sections with filler. All sections have real content. Now we need to remove boilerplate: EEO statements, "Principals only need apply. NO agencies please.", "ITAR Requirement" maybe we kept as qualification. The ITAR requirement paragraph is long; we need to preserve substantive info: that the position requires access to ITAR/EAR info, applicants must qualify as U.S. person under ITAR/EAR, or be approved for export license; job offer conditional on obtaining export license; definition of U.S. person; some positions require current US citizenship due to contract requirements. That's substantive. We should keep that info, maybe under Qualifications or Requirements as a note. We need to not include legal boilerplate? The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. The ITAR requirement is legal but it's a requirement for the role; it's not boilerplate? It's specific. I'd keep it. Now we need to ensure we don't include duplicated lines. We'll avoid repeating. Now produce HTML. Let's craft:

About the role

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

• Edit and proofread proposal content for grammar, clarity, consistency, and compliance.
• Ensure