Program Manager II

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. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Required Clearance: Secret Required Education: Bachelor’s Degree Required Experience: Minimum of 10 years of experience" maybe these are metadata; we can fold into short

or drop? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph with clearance, education, experience maybe. But we also have a "Required Qualifications Minimum of 10 years of experience" later. So we need to preserve that info. We need sections: About the role (position description), Responsibilities, Requirements (maybe includes clearance, education, experience?), Qualifications (maybe same as requirements?), Skills (maybe not explicit), Benefits, Pay, Schedule. We have Benefits listed. Pay: there is a "Salary Range" paragraph but says it's a guideline only not guarantee. It says "The pay range for this job is a general guideline only and not a guarantee of compensation or salary." That's not a specific number; it's vague. According to rule: never emit a 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 the posting actually states them. The posting does state a salary range but says it's a guideline only not guarantee. It still states something: "The pay range for this job is a general guideline only..." It does not give actual numbers. That's placeholder? It says it's a guideline only, not a guarantee. It doesn't give a range. So it's effectively not stating a specific range. According to rule, we should not create Pay section unless posting actually states them (specific). Since it's not giving numbers, we should omit Pay section. Schedule: not mentioned. So omit Schedule. Skills: not explicitly listed; maybe we can infer but not given. So omit Skills. Requirements: we have Required Clearance: Secret, Required Education: Bachelor’s Degree, Required Experience: Minimum of 10 years of experience. Also later "Required Qualifications Minimum of 10 years of experience". So we can combine into a Requirements section with those items. Qualifications: maybe we can include the same? But we should avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings list; we can include both if they have distinct content. However the qualifications section only repeats experience. Might be thin. Better to have a single "Requirements" section that includes clearance, education, experience. Then maybe omit Qualifications. About the role: we have Position Description paragraph. Responsibilities: we have a list of typical responsibilities/tasks. Benefits: we have a list. Thus sections: About the role, Responsibilities, Requirements, Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from position description, responsibilities list, benefits list, clearance, education, experience. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, AI tools statement, etc. Remove those. Also remove "About Pingwind" paragraph? That's about the company; is that substantive? It's about the company, maybe we can include as part of About the role? But the instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put company description under About the role? Might be okay. But we need to preserve all substantive information; the About Pingwind paragraph is substantive about the company. Could include in About the role section as a paragraph. We also need to include "Required Clearance: Secret Required Education: Bachelor’s Degree Required Experience: Minimum of 10 years of experience". We can put that as a

  maybe. We need to avoid duplication: The responsibilities list includes many items; we need to preserve them exactly as given? We should not summarize away detail. We'll copy each responsibility as a

• . Similarly benefits list: we need to preserve each benefit item. Let's extract responsibilities list: Typical Responsibilities/Tasks: - Provide overall planning, direction, leadership, and oversight for major programs, systems development efforts, and research or technology initiatives - Manage large, complex, multi-year programs consisting of multiple sub-programs, projects, and tasks - Define the overall program structure, objectives, priorities, and organizational approach necessary to meet agency and mission requirements - Develop and direct short- and long-range program plans to support successful program execution - Formulate, guide, and direct the technical approach and overall program strategy - Coordinate and negotiate with agency and activity personnel to identify and obtain the personnel, funding, equipment, and other resources required for program execution - Establish and manage technical milestones, performance objectives, and program deliverables - Develop, maintain, and control program schedules to ensure activities and milestones remain on track - Establish, monitor, and control program budgets and costs throughout the program lifecycle - Monitor overall program performance and take appropriate action to address schedule, cost, resource, or technical issues - Coordinate activities across program teams and sub-programs to ensure efforts remain integrated and aligned with overall program objectives - Maintain accountability for the overall success and execution of the program in support of organizational and agency requirements We'll keep each as
• . Benefits list: - Eleven Federal Holidays - Paid Time Off accrued each pay period - Parental Leave - Three medical plan choices with generous employer contribution - Dental and Vision Insurance - Company paid Short-Term and Long-Term Disability - Company paid Life and AD&D Insurance - 401k with competitive matching and vesting schedule - Continuing education assistance - Short Term / Long Term Disability & Life Insurance (duplicate? Actually appears twice; we need to deduplicate? The instruction: remove duplicated lines. So we should not duplicate. We'll keep one entry for Short Term / Long Term Disability & Life Insurance, but we already have separate entries for Short-Term and Long-Term Disability and Life and AD&D Insurance. The duplicate line "Short Term / Long Term Disability & Life Insurance" seems redundant; we can drop it. - Medical, Dependent Care and Commuter Flexible Spending Accounts - Employee Assistance Program - Wellness benefits include Calm Health app and WellHub gym subsidy (formerly GymPass) - 529 College Savings Plan - Legal Insurance - Pet Insurance We need to ensure we didn't miss any: also "Company paid Short-Term and Long-Term Disability" and "Company paid Life and AD&D Insurance". Also "Short Term / Long Term Disability & Life Insurance" duplicate; drop. Now About the role: Position Description paragraph: "PingWind is seeking a Program Manager II (PM) who will provide technical, analytical, and lifecycle support to the Maritime Electronic Warfare Systems Division (MEWSD) for critical U.S. Navy Electromagnetic Warfare (EW), Decoy, and Surface Electronic Warfare Improvement Program (SEWIP) systems. This role supports cradle-to-grave activities, including engineering, technology transition, installation, logistics, product support, test and evaluation, sustainment, maintenance, and repair. The PM II will integrate logistics, data science, reliability and maintainability engineering, and operations research to analyze and model complex systems, improve operational availability, and support data-driven decisions. This position directly contributes to optimizing warfighting capability, system readiness, reliability, and lifecycle performance while balancing mission requirements, performance, and cost." Also we have "About Pingwind" paragraph: "PingWind is focused on delivering outstanding services to the federal government. We have extensive experience in the fields of cybersecurity, development, IT infrastructure, supply chain management and other professional services such as system design and continuous improvement. PingWind is a VA CVE certified Service-Disabled Veteran-Owned Small Business (SDVOSB) and SBA HUBZone Certified with offices in Washington DC and Northern Virginia. www.PingWind.com" We can include that as part of About the role maybe as a second paragraph. Now Requirements: we need to include clearance, education, experience. Also maybe "Required Qualifications Minimum of 10 years of experience" is duplicate; we can note experience already. We'll make a

  with: "Required Clearance: Secret; Required Education: Bachelor’s Degree; Required Experience: Minimum of 10 years of experience." We could also add "Required Qualifications: Minimum of 10 years of experience" but that's duplicate; we can omit duplicate. Now we must not include any boilerplate like EEO, AI tools, etc. Now output HTML fragment only. Structure:

  About the role

  Position description paragraph.

  About Pingwind paragraph.

  Responsibilities

  • ...
  ...

  Requirements

  Required Clearance: Secret; Required Education: Bachelor’s Degree; Required Experience: Minimum of 10 years of experience.

  Benefits

  • ...
  ...
  Make sure no extra whitespace issues. Check for any duplicated lines: we removed duplicate Short Term / Long Term Disability & Life Insurance. Check benefits list for any other duplicates: "Company paid Short-Term and Long-Term Disability" and "Short Term / Long Term Disability & Life Insurance" we removed latter. Also "Company paid Life and AD&D Insurance" is separate. Now ensure we didn't miss any benefit: "Continuing education assistance" present. "401k with competitive matching and vesting schedule". "Medical, Dependent Care and Commuter Flexible Spending Accounts". "Employee Assistance Program". "Wellness benefits include Calm Health app and WellHub gym subsidy (formerly GymPass)". "529 College Savings Plan". "Legal Insurance". "Pet Insurance". Also "Eleven Federal Holidays". "Paid Time Off accrued each pay period". "Parental Leave". "Three medical plan choices with generous employer contribution". "Dental and Vision Insurance". Good. Now check responsibilities list for any duplicates: none. Now ensure we didn't include any boilerplate like "Veterans are encouraged to apply" etc. That's near the end after salary range. That's a line: "Veterans are encouraged to apply". That's not boilerplate? It's a statement encouraging veterans; could be considered substantive? It's not a standard EEO but it's a specific encouragement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Veterans are encouraged to apply" is not exactly EEO but could be considered a encouragement; but it's not a legal boilerplate. However it's near the bottom after salary range and before EEO statement. It might be considered part of the posting; we could keep it. But the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This line is not exactly EEO but it's a encouragement. I'd lean to keep it as substantive? However it's a short line; we could incorporate into About the role or Requirements? But it's not a requirement. It's more like a note. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it if it's substantive. However it's not a heading; we could put it in