Program Manager IV

We need to output HTML fragment with sections: About the role? Actually we have "Company Overview" and "Purpose". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Title: Program Manager IV (we don't repeat as heading) - Department: CEFD - Last Modified: 8/6/2026 - FLSA Status: Exempt - Location: Remote - MD/DC/VA - Level: P4 - Range: $120,000 - $180,000 (Pay range) - Company Overview (prose) - Purpose (prose) - Responsibilities (list) - Qualifications (list) - Education (list? Actually bullet points) - Experience (list) - About Us (includes drug-free workplace, etc.) - The pay range reflects... (Pay info) - Comtech Telecommunications Corp. is an Equal Opportunity Employer. (EEO boilerplate - remove) - Also "We’re seeking curious..." etc (intro) maybe part of purpose. We need to remove boilerplate: EEO, drug-free workplace? The instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The drug-free workplace is legal? Might be considered boilerplate but it's substantive? It says "This position requires compliance with Comtech’s Drug-Free Workplace Program. Candidates must successfully complete a pre-employment drug screening as a condition of hire. Employees may be subject to random, reasonable suspicion, and post-incident testing. Illegal drug use — including marijuana, regardless of state law — is disqualifying under federal adjudicative guidelines and DoD DFARS requirements." This is legal/HR policy. Might be considered boilerplate but it's specific to the job. However instructions say remove EEO/equal-opportunity/scam-warning boilerplate. Drug-free workplace maybe not explicitly listed but could be considered legal. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So legal boilerplate includes drug-free workplace. So we should remove that section. Also "About Us:" heading includes that drug-free workplace text; we can drop that heading and its content. We need to keep Pay range: The posting states "Range: $120,000 - $180,000" and later "The pay range reflects the expected base salary for this position. Final compensation will be based on role, level, skills, experience, and geographic location." That's specific pay info, so we can include a Pay section. Schedule: Not mentioned. So no Schedule section. Benefits: Not mentioned explicitly. So no Benefits. Skills: Could be derived from qualifications but we have Qualifications section. We could combine Qualifications and Skills? The instruction: Use headings like Skills if there is content. We have qualifications list; we could treat that as Qualifications. We'll include Qualifications heading. Responsibilities heading. About the role? We have Company Overview and Purpose. Could combine into About the role? But we have specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "Company Overview" and "Purpose". We could put them under About the role (or maybe under a heading like About the role). Since we must not invent headings not in list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should use those headings when appropriate. So we can use About the role for company overview + purpose. Responsibilities for responsibilities list. Qualifications for qualifications list (including education, experience, certifications). Pay for pay range. Possibly Requirements? Not separate; we have qualifications. Could also include Requirements heading for things like "Ability to travel ~10%" etc. But we can fold into Qualifications. We must not create sections with filler. So we need to ensure each heading has substantive content. Let's extract content: Company Overview paragraph: "Comtech Telecommunications Corp. is a leading global technology company providing terrestrial and wireless network solutions, next-generation 9-1-1 emergency services, satellite and space communications technologies, and cloud-native capabilities to commercial and government customers around the world. Our unique culture of innovation and employee empowerment unleashes a relentless passion for customer success. With multiple facilities located in technology corridors throughout the United States and around the world, Comtech leverages our global presence, technology leadership, and decades of experience to create the world’s most innovative communications solutions. For more information, please visit www.comtech.com. We’re seeking curious, growth-minded thinkers to help shape our vision, structures, and systems; playing a key role as we launch into our ambitious future. If you’re invigorated by our mission, values, and drive to change the world — we’d love to have you apply." Purpose: "The Program Manager IV will be responsible for managing the successful implementation and delivery of customer satellite communication networks, from solution development through deployment and ongoing service support. The Program Manager IV is also responsible for managing and tracking the ongoing support agreement and renewals." We can combine these under About the role. Responsibilities list: bullet points: - Interface directly with customers as the company’s lead point-of-contact for all program activities, and ongoing support agreements - Deliver successful major end to end communications network deployment. - Manage the activities of the project to ensure budget and schedule criteria are upheld. - Prepare and present project status reports for management, project staff and/or customers. - Achieve customer satisfaction through on-time delivery of service, resolving issues on a timely and proactive basis. - Provide coordination of technical resources within company - Assesses the risks and implements risk mitigation plans as required. - Review status reports prepared by project personnel and modify schedules or plans as required . - Understand and respect that Comtech has customers around the world in different time zones etc. that need immediate attention and problem resolution which can include software releases, software bug fixes, technical bulletins and hardware related issues. Note some grammar issues but we keep as is. Qualifications list: bullet points: - Demonstrated experience leading multi-disciplined, cross functional, matrixed teams. - Experience managing concurrent programs. - Strong communication skills and experience presenting to customers and senior leadership; ability to effectively work and communicate with all levels of management and customers. - Strong working knowledge of business and project management processes and tools such as Ability to develop customer and program enhancing partnerships with internal functional organizations such as Contracts, Finance, Engineering, Supply Chain, Operations and other support functions. - Knowledge of Government procurement, contracting, and standards and specifications. - Proficient in Microsoft Tools (Word, Excel, PowerPoint, Project). - Ability to travel ~10%. Education: "Bachelor’s degree in engineering, business, or related field" Certification: "Program/Project Management Professional ( PgMP /PMP) Certification(preferred)" Experience: "5-10 years of related experience and/or training; or equivalent combination of education and experience." We could combine Education, Certification, Experience under Qualifications or separate Requirements? The instruction: Use headings like Requirements, Qualifications, Skills. We could have Qualifications heading covering all of those (including education, certs, experience). Or we could have Requirements heading for education/experience and Qualifications for skills. But to keep few sections, we can have Qualifications covering all. Pay: we have range and note about final compensation. We should not include fluff like "commensurate with experience". The pay range is specific. We should not include duplicated lines. We need to output only HTML fragment. Structure:

  About the role

  Company overview paragraph + purpose paragraph (maybe two

  or combine). Use

  for prose.

  Responsibilities

  • ... each

  Qualifications

  • ... each

  Pay

  Pay range: $120,000 - $180,000. Final compensation will be based on role, level, skills, experience, and geographic location.

  We should also maybe include location? Not required as heading; could be folded into a short

  under About the role? But location is metadata; instruction: fold minor metadata into a short

  or drop it. We could add a

  after About the role? But we already have About the role with prose; we could add a

  with location and maybe remote. However that might be considered minor metadata; we could include a short

  after the heading? But we must not create extra sections. We could add a

  inside About the role after the overview? But the instruction: "fold minor metadata into a short

  or drop it." So we could add a

  with location, level, etc. inside About the role? Might be okay. Better: After About the role heading, we could have a

  with location and level etc. Then another

  with company overview and purpose? But that splits prose. Might be okay. But we need to preserve all substantive information. Location is substantive. So we should include it. We could do:

  About the role

  Location: Remote - MD/DC/VA. Level: P4.

  Company overview paragraph...

  Purpose paragraph...

  That preserves location and level. We should also include Department? Could be minor metadata; maybe fold into same

  . Add Department: CEFD. Last Modified: 8/6/2026 maybe minor; could drop. FLSA Status: Exempt maybe minor; could drop. We'll include location, level, department. Now ensure we don't repeat job title. Now check for any other sections: Skills? Not separate. Now ensure we don't include boilerplate: EEO, drug-free workplace, etc removed. Now output HTML. Let's craft the content precisely. About the role: First

  : "Department: CEFD. Location: Remote - MD/DC/VA. Level: P4." Second

  : Company overview paragraph as given. Third

  : Purpose paragraph. Now Responsibilities: list each bullet as

• . Qualifications: list each bullet as
• . Need to include education, certification, experience as separate items. Let's extract qualifications bullet points exactly as in text: - Demonstrated experience leading multi-disciplined, cross functional, matrixed teams. - Experience managing concurrent programs. - Strong communication skills and experience presenting to customers and senior leadership; ability to effectively work and communicate with all levels of management and customers. - Strong working knowledge of business and project management processes and tools such as Ability to develop customer and program enhancing partnerships with internal functional organizations such as Contracts, Finance, Engineering, Supply Chain, Operations and other support functions. - Knowledge of Government procurement, contracting, and standards and specifications. - Proficient in