Program Manager

We need to output HTML fragment with sections: About the role? The posting includes Position Overview, Position Requirements, Minimum Qualifications, Preferred Qualifications, Work Environment/Physical Requirements, Infinity Benefits, etc. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings appropriately. The posting includes Position Overview (responsibilities), Position Requirements (education, clearance), Minimum Qualifications, Preferred Qualifications, Work Environment/Physical Requirements, Benefits. We need to decide which sections to include based on actual content. We have no explicit Pay or Schedule info (except maybe "On-call availability or after-hours support may be required" but that's not schedule specifics). So we should not create Pay or Schedule sections because they are not stated. We need to include sections only when posting has real specific content. Thus we can have:

About the role

with position overview paragraph.

Responsibilities

maybe combine with overview? But we need to avoid duplication. Could put responsibilities under About the role. But we need to follow instruction: use headings for sections; we can have About the role (overview) and Responsibilities (list of duties). The posting includes responsibilities: "The program manager will oversee technical and management operations, aspects of ground station command and control systems compatibility, resource allocation, infrastructure, systems security, contract performance management, and participate in briefing and meetings. Formulates and enforces work standards, assigns schedules, reviews work discrepancies, and supervises contractor personnel. Assist ground station proposal plans, specifications, financial terms, and business development initiatives. Possess good oral and written communication skills and the ability to conduct business briefings and presentations." We can put that as

• ... but it's a paragraph with multiple sentences. Could split into list items.

  Requirements

  could include Education and Clearance Requirement.

  Qualifications

  could include Minimum Qualifications and Preferred Qualifications.

  Skills

  maybe not needed; we could omit if no specific skills list beyond qualifications. But we have communication skills etc. Could include under Qualifications. Better to follow: About the role, Responsibilities, Requirements, Qualifications, Benefits. We must not create Skills if no dedicated content. We need to preserve all substantive information. Let's extract: Position Overview paragraph: "Infinity is excited about the opportunity to support the Mission System Research and Development Support contract at the Blossom Point Satellite Command and Tracking Facility (BPTF) in Welcome, Maryland. As we prepare for this opportunity, we're looking to connect with members of the incumbent workforce who are interested in joining our team. If you are currently supporting the BPTF mission, we encourage you to submit your resume and explore the opportunity to continue this important mission with us. We also welcome interest from experienced professionals who are not currently assigned to BPTF but have the skills and passion to contribute to this mission. We'd be glad to hear from you and discuss potential opportunities. Join us as we continue to make meaningful and positive impacts to critical national security and space operations programs!" That's overview. Responsibilities: as above. Requirements: Education: Bachelor’s degree in economics, business management, engineering, science discipline or related field and 5 years of experience. Clearance Requirement: Active TS/SCI. Minimum Qualifications: list bullet points. Preferred Qualifications: list bullet points. Work Environment/Physical Requirements: list. Benefits: list. We need to avoid boilerplate like "U.S. Citizenship is required. EOE including disability/vet" etc. That's boilerplate; remove. Also remove "Application Deadline..." etc. Now produce HTML. We'll structure:

  About the role

  ...overview...

  Responsibilities

  • Oversee technical and management operations, aspects of ground station command and control systems compatibility, resource allocation, infrastructure, systems security, contract performance management, and participate in briefing and meetings.
  • Formulate and enforce work standards, assign schedules, review work discrepancies, and supervise contractor personnel.
  • Assist ground station proposal plans, specifications, financial terms, and business development initiatives.
  • Possess good oral and written communication skills and the ability to conduct business briefings and presentations.

  Requirements

  • Bachelor’s degree in economics, business management, engineering, science discipline or related field and 5 years of experience.
  • Active TS/SCI clearance.

  Qualifications

  Minimum Qualifications

  but we only allowed h3 headings. Could we embed as ? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to h3 for sections; we could include Minimum and Preferred as

  subsections? But that would be extra sections. Could combine Minimum and Preferred under Qualifications with

  and maybe label with . That's acceptable. Thus:

  Qualifications

  Minimum Qualifications:

  • Experience managing programs or contracts in a defense, aerospace, or government contracting environment
  • Demonstrated experience overseeing technical operations such as ground systems, command and control, or related mission support systems
  • Strong leadership experience managing schedules, resources, performance, and contractor personnel in a structured environment
  • Excellent written and verbal communication skills with experience delivering briefings, reports, and stakeholder presentations

  Preferred Qualifications:

  • Experience with ground station command and control systems or satellite/space systems operations
  • Prior experience supporting DoD, NRO, NASA, or other government aerospace programs
  • Familiarity with contract performance management, proposal development, and business development activities
  • Experience overseeing infrastructure, systems security requirements, or cross-functional engineering teams

  Work Environment/Physical Requirements

  But we don't have a heading for Work Environment in allowed list. Could we treat as part of Qualifications? Or we could create a section "Work Environment" but not in list; instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map Work Environment content into one of those sections, maybe Qualifications or Responsibilities. Could add a

  Qualifications and include work environment as bullet under Qualifications? Or maybe create a

  Skills? Not appropriate. Better to incorporate Work Environment/Physical Requirements under Qualifications as additional bullet points. Thus under Qualifications we can add a subsection "Work Environment & Physical Requirements" as ... and list. Similarly Benefits section. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We must not include Pay or Schedule. Now craft HTML. Check for any leftover boilerplate: remove "U.S. Citizenship is required. EOE including disability/vet". Remove "To learn more about our company and benefits, please visit: Infinity Careers". Remove "Application Deadline..." etc. Also remove "*Please note, this position is Contingent upon award. Position is slated to begin March-June 2027.*" That's metadata about timing; could be considered schedule? It's not a regular schedule; it's start date range. Could be considered Schedule info? The instruction says do not create Pay/Schedule/Benefits sections unless posting actually states them. This posting does state start date range (March-June 2027). That's schedule info. Should we include a Schedule section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state start date range, which is schedule-related. So we could include a Schedule section with that info. However the instruction also says "Prefer a few substantive sections over many thin ones." Might be okay to include Schedule as a brief section. But we need to decide: The posting includes "*Please note, this position is Contingent upon award. Position is slated to begin March-June 2027.*" That's about timing/contingency. Could be considered schedule. I'd include a Schedule section with that note. But also there is "On-call availability or after-hours support may be required for network incidents" which is schedule-related as well. Thus we can include Schedule section. Pay: not mentioned, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Now ensure we don't repeat job title. Now produce HTML. Let's draft:

  About the role

  Infinity is excited about the opportunity to support the Mission System Research and Development Support contract at the Blossom Point Satellite Command and Tracking Facility (BPTF) in Welcome, Maryland. As we prepare for this opportunity, we're looking to connect with members of the incumbent workforce who are interested in joining our team. If you are currently supporting the BPTF mission, we encourage you to submit your resume and explore the opportunity to continue this important mission with us. We also welcome interest from experienced professionals who are not currently assigned to BPTF but have the skills and passion to contribute to this mission. We'd be glad to hear from you and discuss potential opportunities. Join us as we continue to make meaningful and positive impacts to critical national security and space operations programs!

  Responsibilities

  • Oversee technical and management operations, aspects of ground station command and control systems compatibility, resource allocation, infrastructure, systems security, contract performance management, and participate in briefing and meetings.
  • Formulate and enforce work standards, assign schedules, review work discrepancies, and supervise contractor personnel.
  • Assist ground station proposal plans, specifications, financial terms, and business development initiatives.
  • Possess good oral and written communication skills and the ability to conduct business briefings and presentations.

  Requirements

  • Bachelor’s degree in economics, business management, engineering, science discipline or related field and 5 years of experience.
  • Active TS/SCI clearance.

  Qualifications

  Minimum Qualifications:

  • Experience managing programs or contracts in a defense, aerospace, or government contracting environment
  • Demonstrated experience overseeing technical operations such as ground systems, command and control, or related mission support systems
  • Strong leadership experience managing schedules, resources, performance, and contractor personnel in a structured environment
  • Excellent written and verbal communication skills with experience delivering briefings, reports, and stakeholder presentations

  Preferred Qualifications:

  • Experience with ground station command and control systems or satellite/space systems operations
  • Prior experience supporting DoD, NRO, NASA, or other government aerospace programs
  • Familiarity with contract performance management, proposal development, and business development activities
  • Experience overseeing infrastructure, systems security requirements, or cross-functional engineering teams

  Work Environment & Physical Requirements:

  • Professional, fast-paced, and team-oriented environment
  • Requires adherence to security protocols and