Proposal Writer (mid-senior level)

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "About Peraton" maybe? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The job title is not given explicitly; but we have "About The Role" etc. We need to include sections only when posting has real specific content. We have content: About Peraton (company description) maybe not needed? The instruction says "About Peraton" is likely boilerplate? It's company overview; maybe we can include as a short paragraph? Not a section heading. The instruction says we can fold minor metadata into a short

or drop it. The "About Peraton" could be considered company overview, not required but could be kept as a paragraph before sections? The output should be only HTML fragment; we can include a

with that description? It's not a heading; but we need to preserve all substantive information. The company description is substantive but maybe not required? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep the company description. However, we cannot add headings not requested. We can just put it as a

before sections. Then we have "About The Role" which is a section heading. That matches "About the role" (case). So we should output

About the role

and then the prose under it. Then we have "Position Overview" which could be part of About the role? Might be considered part of same section. But we could treat as part of About the role content. Then "Key Responsibilities" -> Responsibilities section. Then "Collaboration with SMEs, LSAs, and Capture" maybe part of responsibilities. Then "Content Standardization & Reuse" also responsibilities. Then "Professional Collaboration & Growth" also responsibilities. Then "Success Profile" maybe could be Qualifications or Skills? It lists ideal traits. Could be considered Qualifications or Skills. The instruction: we have sections for Qualifications, Skills. We need to decide where to put Success Profile. It describes ideal Proposal Writer: strategic thinker, etc. That's more like qualifications/skills. Could be placed under Qualifications (maybe as a bullet list). But we already have Qualifications section with Minimum Qualifications and Preferred Qualifications. The Success Profile could be considered part of Qualifications (maybe as a separate bullet list). However we must not invent sections; we can include it under Qualifications as additional content. We have "Qualifications" heading with Minimum Qualifications and Preferred Qualifications. That's a section. We have "Details" containing Target Salary Range, Benefits Statement, Application Statements, etc. So we need Pay section (salary range) and Benefits section. Also maybe Schedule? Not present. So we should not create Schedule section. We have Benefits Statement: list of benefits. So we create

Benefits

with

• each benefit. Pay: Target Salary Range: $104,000 - $166,000. Also note about overtime etc. We'll include that as prose under Pay. We must not include application instructions, EEO, etc. So remove "Application Statements", "EEO", etc. We must not include duplicated lines. We need to preserve all substantive info: company description, About the role content, Position Overview, Responsibilities (including sub-bullets), Success Profile (maybe under Qualifications), Qualifications (minimum and preferred), Benefits, Pay. We must not add extra sections like Skills unless there is specific content. There's no explicit Skills section; but we could treat Success Profile as Skills? However we already have Qualifications. The instruction says use headings for Skills if posting has real specific content for it. The posting does not have a separate Skills heading; but we could infer that Success Profile is about skills. However we should not create a Skills section unless the posting actually states them. The posting does have "Success Profile" which lists attributes; that could be considered skills. But we already have Qualifications; maybe we can put Success Profile under Qualifications as a paragraph. That would preserve info without creating a new Skills heading. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and benefits, so we include Pay and Benefits. Schedule: not stated, so omit. Now we need to format lists: For responsibilities, we have multiple bullet-like paragraphs. We'll convert each bullet point into
• inside a
  . The responsibilities are described in paragraphs with sentences; we can treat each sentence as a list item? The instruction: Use
  • for any list of duties/requirements/benefits. So we need to identify lists. The responsibilities section includes multiple bullet points each starting with a bold heading? Actually the text: Key Responsibilities Content Quality & Integration Develop clear, compliant, and evaluator-aligned proposal sections. Ensure assigned content meets RFP requirements and follows Peraton proposal standards. Identify gaps or issues within assigned sections and collaborate with SMEs and volume leads to resolve them. Support content integration across volumes by maintaining consistent messaging and terminology. Content Development & Storytelling Write and edit proposal narratives primarily for technical and management sections. Translate SME-provided information into concise, customer-focused responses. Incorporate value propositions, discriminators, and metrics as directed by volume leads. Collaborate with graphics teams to ensure effective alignment between narrative and visuals. Collaboration with SMEs, LSAs, and Capture Work with SMEs and solution architects to gather inputs and refine technical or management content. Participate in content planning sessions, interviews, and color team reviews as needed. Deliver high-quality drafts that reflect guidance from SMEs, proposal managers, and solution leads. Support alignment across multiple contributors to ensure consistent tone and messaging. Content Standardization & Reuse Contribute to reusable content libraries, boilerplate, templates, and past performance summaries. Maintain version control and adhere to team writing standards and processes. Suggest improvements to content organization, clarity, and structure where appropriate. Professional Collaboration & Growth Engage proactively with reviewers and incorporate feedback efficiently. Support surge efforts during high-volume proposal periods. Build skills in content planning and solution interpretation under guidance from senior team members. We could treat each bold line as a subsection heading, but we are not to add extra headings beyond the allowed ones. However we could keep them as plain text within
  • ? The instruction says use
    • for any list of duties/requirements/benefits. So we can make each duty as a list item, maybe grouping under subheadings not needed. We'll just make each sentence a list item. That may be many items but okay. Similarly for Qualifications: Minimum Qualifications list includes multiple bullet-like sentences. We'll make each as
    • . Preferred Qualifications also list. Benefits: list of benefits: medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, company paid holidays. We'll make each as
    • . Pay: we will have a

      with the salary range and additional notes. Now we need to exclude boilerplate: "About Peraton" maybe we keep as a paragraph before sections. It's not a heading; it's okay. We must not include "Application Statements", "EEO", etc. We must not include "Details" heading; we will extract Pay and Benefits from there. Now produce HTML fragment:

      About Peraton Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure.

      About the role

      Join Peraton's Proposal Content Development team and contribute to producing high-quality, mission-critical federal proposals. We are expanding our team of disciplined, collaborative writers who thrive in fast-paced environments and take pride in delivering clear, compliant, evaluator-focused content. This role offers mid-level writers the opportunity to work closely with solution architects, SMEs, and proposal leaders to develop strong technical and management narratives that strengthen our competitive positioning. If you love the challenge of translating complex solutions into compelling, evaluator-focused narratives that drive competitive advantage, we want to hear from you.

      Position Overview The Proposal Writer plays a central role in developing compliant, compelling content across technical, management, staffing, resumes, and past performance volumes. This writer works under the guidance of volume leads and in collaboration with Subject Matter Experts and Lead Solution Architects to develop sections, refine content, and ensure alignment with win themes and proposal standards. The Proposal Writer does not manage direct reports but contributes to content development best practices and maintains consistency across deliverables.

      Responsibilities

      • Develop clear, compliant, and evaluator-aligned proposal sections.
      • Ensure assigned content meets RFP requirements and follows Peraton proposal standards.
      • Identify gaps or issues within assigned sections and collaborate with SMEs and volume leads to resolve them.
      • Support content integration across volumes by maintaining consistent messaging and terminology.
      • Write and edit proposal narratives primarily for technical and management sections.
      • Translate SME-provided information into concise, customer-focused responses.
      • Incorporate value propositions, discriminators, and metrics as directed by volume leads.
      • Collaborate with graphics teams to ensure effective alignment between narrative and visuals.
      • Work with SMEs and solution architects to gather inputs and refine technical or management content.
      • Participate in content planning sessions, interviews, and color team reviews as needed.
      • Deliver high-quality drafts that reflect guidance from SMEs, proposal managers, and solution leads.
      • Support alignment across multiple contributors to ensure consistent tone and messaging.
      • Contribute to reusable content libraries, boilerplate, templates, and past performance summaries.
      • Maintain version control and adhere to team writing standards and processes.
      • Suggest improvements to content organization, clarity, and structure where appropriate.
      • Engage proactively with reviewers and incorporate feedback efficiently.
      • Support surge efforts during high-volume proposal periods.
      • Build skills in content planning and solution interpretation under guidance from senior team members.

      Qualifications

      Success Profile The ideal Proposal Writer is: A strategic thinker with excellent writing discipline. Skilled at balancing creativity with compliance. Comfortable leading content development without formal people management. Highly organized and able to guide cross-volume consistency. Proactive, collaborative, and solution-oriented.

      Minimum Qualifications Bachelors and 5+ years of experience supporting federal proposals, including technical and management volumes (or equivalent professional writing experience). 4 years of additional experience will be considered in lieu of degree. Deep understanding of the proposal development lifecycle Strong ability to synthesize SME input into clear, compelling narrative