Program Engineering Manager III

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 need to parse the job description. We need to avoid repeating job title as heading. No Job ID etc. We need to preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to include sections only when posting has real specific content. Let's extract content: - About the role: The description includes introductory paragraphs about BAE Systems, mission, flexible work environment, etc. Also "Our flexible work environment provides you a chance to change the world without giving up your personal life." Also "We put our customers first – exemplified by our mission: “We Protect Those Who Protect Us®.”" Also "Electronic Combat Solutions (ECS) has technology, engineering and program teams..." Also "BAE Systems Electronic Solutions is looking for a Program Engineering Manager (PEM)." Also description of PEM role: leads engineering effort, technical responsibility, etc. That seems like About the role. - Responsibilities: List of specific job responsibilities: "Partner with the Program Manager, Chief Engineer and functional staff to develop and deliver products and systems that meet our customer needs." etc. Many bullet-like sentences. We'll put them in

• . - Required Education, Experience, & Skills: This is a section. It includes: "Requires qualified candidates to hold an active Secret security clearance with the ability to obtain Special Access Program clearances and DoW Top Secret. Bachelor's Degree and 12 years work experience or equivalent experience. Experience in engineering development of complex electronic systems and the transition to manufacturing. Project engineering management including organizational design, planning, estimating, design management, and product verification." - Preferred Education, Experience, & Skills: includes DoW Top Secret Clearance preferred, previous job experience operating within a Special Access Program environment, experience developing and delivering within a digital engineering ecosystem, experience leading or collaborating with cross-site, cross-business unit teams, experience leading diverse multi-disciplinary teams in the solution of complex technical problems, demonstrated leadership skills (soft skills, strategic thinking, business acumen, building teams, building customer relationships), strong planning and organizational skills with ability to diagnose, resolve complex problems and develop improved methods to increase program efficiency, proven written and oral communication skills, including presentation skills, strong team building skills that enable collaboration and coordination within and across teams, functions, and other business units. - Pay Information: "Full-Time Salary Range: $150370 - $255630 Please note: This range is based on our market pay structures. However, individual salaries are determined by a variety of factors including, but not limited to: business considerations, local market conditions, and internal equity, as well as candidate qualifications, such as skills, education, and experience." - Employee Benefits: paragraph describing benefits: health, dental, vision insurance; health savings accounts; 401(k); disability coverage; life and accident insurance; employee assistance program; legal plan; other perks including discounts; leave programs: paid time off, paid holidays, paid parental, military, bereavement, applicable federal and state sick leave; company recognition program; other incentives may be available based on position level and/or job specifics. - Schedule: The posting mentions: "Because of the need for consistent, in-person collaboration and/or the requirement to perform all work onsite due to the nature of this particular role, it will be performed full time on site. This means work will be conducted on location at a BAE Systems facility 100% of the time." So schedule: full-time on-site. - About BAE Systems Electronic Systems: This is more company overview; could be part of About the role or separate section? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can treat "About BAE Systems Electronic Systems" as part of About the role (maybe we can include it there). We should not create extra sections not listed. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to avoid duplication: The responsibilities list includes repeated sentences? Let's extract unique responsibilities. From text: "Partner with the Program Manager, Chief Engineer and functional staff to develop and deliver products and systems that meet our customer needs." "Partner and collaborate across all the disciplines, functions, and business areas to effectively support engineering across the enterprise." "Meet cost, schedule and technical performance for projects through their life cycle." "Ensure preparation and approval of competitive engineering bids that are executable, meet established price-to-win targets, and grow the business." "Serve as overall customer (internal / external) engineering point of contact for the project." "Identify and support the development of critical skills and resources." "Develop and maintain measures related to engineering performance." "Ensure proper application of process based on the size and complexity of the project." "Establish goals, performance standards, budgets and staffing plans." "Improve processes and skills that accelerate program execution and improve quality." "Lead and develop others." We'll list each as
• . Now Required Education, Experience, & Skills: We'll put as
  • items? The instruction: Use
    • for any list of duties/requirements/benefits. So for requirements we can list each requirement as
    • . However the text is a paragraph; we can split into bullet points. List: - Hold an active Secret security clearance with the ability to obtain Special Access Program clearances and DoW Top Secret. - Bachelor's Degree and 12 years work experience or equivalent experience. - Experience in engineering development of complex electronic systems and the transition to manufacturing. - Project engineering management including organizational design, planning, estimating, design management, and product verification. Preferred Education, Experience, & Skills: list similarly. - DoW Top Secret Clearance preferred. - Previous job experience operating within a Special Access Program environment. - Experience developing and delivering within a digital engineering ecosystem. - Experience leading or collaborating with cross-site, cross-business unit teams. - Experience leading diverse multi-disciplinary teams in the solution of complex technical problems. - Demonstrated leadership skills (soft skills, strategic thinking, business acumen, building teams, building customer relationships). - Strong planning and organizational skills with the ability to diagnose, resolve complex problems and to develop improved methods to increase program efficiency. - Proven written and oral communication skills, including presentation skills. - Strong team building skills that enable collaboration and coordination within and across teams, functions, and other business units. Benefits: list bullet points. - Health, dental, and vision insurance - Health savings accounts - 401(k) savings plan - Disability coverage - Life and accident insurance - Employee assistance program - Legal plan - Discounts on home, auto, and pet insurance - Paid time off - Paid holidays - Paid parental leave - Military leave - Bereavement leave - Applicable federal and state sick leave - Company recognition program (monetary or non-monetary recognition awards) - Other incentives may be available based on position level and/or job specifics. Pay: we can put as

      with the salary range and note. Schedule: we can put as

      stating full-time on-site. Now About the role: we need to include prose describing role and company mission etc. We'll combine the introductory paragraphs and the description of PEM role (leading engineering effort etc.) into a

      or multiple

      . The instruction: Use

      for prose. We can have multiple

      under the heading. We must not repeat job title as heading. So we will not have a heading for "Program Engineering Manager". We'll just have About the role heading. We need to ensure we don't include boilerplate like "This position will be posted for at least 5 calendar days..." etc. That's application instructions? Actually it's about posting duration; we should remove as per instruction: remove application instructions. So we drop that. Also remove duplicated lines: we need to check for duplicates. The text includes some repeated sentences? Eg "The PEM is the decision authority between the Chief Engineer and engineering team and is responsible for developing the overall technical solution for the system." appears twice? Actually earlier: "The PEM is the decision authority between the Chief Engineer and engineering team and is responsible for developing the overall technical solution for the system." and later: "The PEM is expected to influence the design, development, test and verification. In addition, the PEM is responsible for identifying and communicating technical risks and opportunities between the design team, Chief Engineer and program management team." Not duplicate. There's also "The PEM provides technical responsibility and leadership to cross-functional teams through the design, development, fielding, and support of the system." and "The PEM represents the technical team to project managers, functions, and executive leadership, and provides responsibilities for developing the overall technical solution for a product or system." Slightly similar but not exact duplicate. We'll keep all substantive info; we can keep both. Now produce HTML fragment:

      About the role

      ... paragraphs ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Preferred Qualifications

      maybe we should use "Qualifications" heading for preferred? The instruction list includes Qualifications and Skills separate. But we have both Required Education, Experience, & Skills (requirements) and Preferred Education, Experience, & Skills (preferred). We could map Required to Requirements, Preferred to Qualifications, and Skills maybe separate? However the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put required and preferred. Could put required under Requirements, preferred under Qualifications, and maybe Skills under Skills? But we have skills listed in both required and preferred. Could combine skills under Skills heading. However we must not invent sections lacking content. We have content for skills (both required and preferred). Could create Skills section listing skills (both required and preferred). But then we would duplicate content. Better to follow the instruction: Use headings for those sections only if posting has real specific content for it. The posting has sections: Required Education, Experience, & Skills and Preferred Education, Experience, & Skills. We could map Required to Requirements, Preferred to Qualifications, and maybe Skills not needed separately because skills are covered in those. But we could also create Skills section listing skills from both required and preferred. However that would be duplicative and maybe not needed. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine Required and Preferred into Requirements and Qualifications respectively, and omit Skills. Or we could create Skills section with the skill items from both required and preferred, and then Requirements only for education/experience/clearance. But the posting lumps education, experience, skills together. Safer to follow the headings given: Requirements for required education/experience/skills; Qualifications for preferred education/experience/skills; Skills maybe we could omit if no distinct skills separate. But we have skill items in both; we could still put them under Requirements and Qualifications. That seems acceptable. Thus:

      Requirements

      • Active Secret security clearance with ability to obtain Special Access Program clearances and DoW Top Secret.
      • Bachelor's Degree and 12 years work experience or equivalent experience.
      • Experience in engineering development of complex electronic systems and the transition to manufacturing.
      • Project engineering management including organizational design, planning, estimating, design management, and product verification.

      Qualifications

      • DoW Top Secret Clearance preferred.
      • Previous job experience operating within a Special Access Program environment.
      • Experience developing and delivering within a digital engineering ecosystem.
      • Experience leading or collaborating with cross-site, cross-business unit teams.