Manager, Operations Project Mgmt

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must include only sections with real content. Must not include boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the job posting. Key sections: - Summary: "Worker Type Regular Summary Job Description The Manager, Operations Project Management plays a significant role..." This is description. Could be "About the role" maybe. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading with the description paragraph. - Responsibilities: list of duties. Use

• . - Basic Qualifications (Required Skills & Experience): list of qualifications. Could be under "Requirements" or "Qualifications". The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide. Probably combine basic qualifications under "Requirements" or "Qualifications". Since they have "Basic Qualifications (Required Skills & Experience)" and "Other Qualifications & Desired Competencies". We could have "Requirements" for basic qualifications, and "Preferred Qualifications" maybe under "Qualifications". But we must only include sections when posting has real specific content. We have both. We also have "Physical Demands", "Environmental Conditions", "Special Requirements", "Clearance Level", "The Salary Range For This Role Is $117,500 - $179,250", "Benefits: AV offers an excellent benefits package...". Also "ITAR Requirement" etc. But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ITAR requirement may be considered substantive? It's about citizenship requirement. Might be considered part of Special Requirements. The posting includes "Special Requirements U.S. Citizen, U.S. Permanent Resident (Green Card holder) or asylee/refugee status as defined by 8 U.S.C. 1324b(a)(3) required.Must be able to travel within the Continental U.S. and internationally when required." That's substantive. Also "Clearance Level No Clearance" maybe not needed? It's minor metadata; could be folded into short p or dropped. Probably drop. Salary range: we should include Pay section with that range. Benefits: we have benefits description. Schedule: not explicitly mentioned; maybe not include. We must not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive information: responsibilities list, qualifications list, other qualifications, physical demands, environmental conditions, special requirements, salary, benefits, maybe ITAR requirement (but that is covered by special requirements). Also "About AV" description maybe could be under "About the role" or separate "About the company". But instruction says use headings like About the role, Responsibilities, etc. Could include "About the company" but not in list. Probably better to put the company description under "About the role" or maybe a separate "About the company" but not required. Since they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can stick to those. The company description could be part of About the role? Might be okay to include as a paragraph under About the role. We must not repeat job title as heading. So no heading for Manager, Operations Project Management. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's structure:

  About the role

  ... description ...

  Responsibilities

  • ...
  ...

  Requirements

  ... basic qualifications ... maybe as list?

  Could be list. But we have both Basic Qualifications and Other Qualifications & Desired Competencies. Could combine into Requirements and Preferred Qualifications? But we only have headings list: Requirements, Qualifications, Skills. Could use Requirements for basic qualifications, Qualifications for other qualifications, Skills maybe not needed. However we have many skill-like items in qualifications (communication, analytical, etc.). Could put them under Skills. Better: Use Requirements for basic qualifications (education, experience). Use Qualifications for other qualifications & desired competencies (the bullet list). Use Skills maybe not needed; but we could put communication etc under Skills. But we already have them in Other Qualifications. Might be redundant. Let's decide: Use Requirements for basic qualifications (education, experience). Use Qualifications for other qualifications & desired competencies (the list). Use Skills maybe not needed; we can omit if no specific skills section besides those already covered. But we have "Project Management proficiency and related experience" etc in basic qualifications; those are skills. But okay. We'll include:

  Requirements

  • Bachelor’s degree required (Business, Manufacturing Management, Engineering or related field or equivalent combination)
  • Advanced degree, MBA or MS preferred
  • Minimum of 8 years of relevant experience required
  • Minimum of 3 years of experience in a leadership role
  • Aerospace and/or Defense experience preferred
  • Proficient in using manufacturing software systems and tools, such as ERP, MES, and data analytics platforms
  • Project Management proficiency and related experience
  • Knowledge in manufacturing principles, processes, and technologies
  • Strong understanding of quality management systems and best practices, such as ISO 9001
  • Excellent verbal and written communication skills
  • Excellent organizational and managerial skills
  • Ability to set long-term goals and communicate them to others
  • Ability to motivate and organize multiple efforts to accomplish goals
  But note some of those are also skills; but okay. Then

  Qualifications

  for Other Qualifications & Desired Competencies list. List items: - Excellent written and verbal communication skills (duplicate but okay) - Strong analytical, critical thinking and interpersonal skills, with the ability to speak and write persuasively - Experience working with cross-functional teams; ability to develop and maintain internal and external trusting, professional relationships - Uses vision to think beyond the immediate situation, explore multiple potential paths, and adapt decision-making style based on the situational circumstances - Inspires, motivates, and empowers people to deliver organizational goals, while also delivering value back to employees - Brings organizational values to life using personality, uniqueness, and the creation of a shared vision - Champions the process of change and promotes a culture of quick adaptation while helping others deal with the effects of change - Takes ownership and responsibility for assigned tasks - Is committed to learning from mistakes and driven to improve and enhance performance of oneself, others, and the company - Focuses on teamwork and puts the success of the team above one's own interests We could deduplicate communication skill but it's okay. Then

  Physical Demands

  maybe not in allowed headings but we could include as a paragraph under Requirements? But instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings but said use those for section headings. Probably we should stick to those. Physical Demands could be folded into a short p under Requirements or maybe under Qualifications? But it's not a skill. Could be under Requirements as a note. However we might add a separate section if we think it's substantive. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could add Physical Demands as its own section if it's substantive. But we need to decide. Similarly Environmental Conditions, Special Requirements, Clearance Level, Salary, Benefits. We definitely need Pay and Benefits sections. Schedule: not mentioned, so omit. We could add a section "Special Requirements" for citizenship and travel. We could add "Physical Demands" and "Environmental Conditions" maybe as a combined "Working Conditions" section. But to keep few sections, we could incorporate Physical Demands and Environmental Conditions into a short paragraph under Requirements or Qualifications. Better: Add a section "Working Conditions" with Physical Demands and Environmental Conditions. But the instruction didn't list Working Conditions as example; but it's okay as long as we use

  . However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are typical but not exhaustive. I'd stick to those to be safe. Thus we need to fit all substantive info into those sections. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put Physical Demands and Environmental Conditions under Requirements or Qualifications as a note. Special Requirements (citizenship, travel) could be under Requirements as well. Pay section: salary range. Benefits section: benefits description. Schedule: not present, omit. Skills: we could put some skill items under Skills, but we already have many in Requirements and Qualifications. Might be redundant. Maybe we can restructure: Requirements = basic qualifications (education, experience). Qualifications = other qualifications & desired competencies. Skills = specific skills like communication, analytical, project management, ERP, etc. But we already have many of those in basic qualifications. Could move them to Skills. Let's try: - About the role: description paragraph. - Responsibilities: list. - Requirements: education, experience, aerospace/defense preference, leadership years. - Skills: proficiency in ERP/MES, project management, manufacturing principles, quality management (ISO 9001), communication, organizational, goal setting, motivating. - Qualifications: other qualifications & desired competencies list (analytical, cross-functional, vision, inspire, values, change champion, ownership, learning, teamwork). - Benefits: benefits description. - Pay: salary range. We also need to include Special Requirements (citizenship, travel). Could be folded into Requirements as a note: "Must be U.S. citizen, permanent resident, asylee/refugee; must be able to travel domestically and internationally." Physical Demands and Environmental Conditions could be added to Requirements as a note: "Ability to sit, stand, stoop, reach, lift up to 10 lbs., hand/wrist dexterity; may require travel; office environment with climate control; possible outside exposure while traveling." Clearance Level "No Clearance" maybe not needed. Thus we cover all. Now produce HTML. We must not include any markdown fences. Let's craft. First, About the role paragraph: combine the summary and maybe the "About AV" description? The "About AV" is company description; could be included as part of About the role? Might be okay but could be lengthy. The instruction: preserve ALL substantive information. So we should include the "About AV" paragraph as well. Where to put? Could be under About the role as a second paragraph. Thus About the role will have two paragraphs: first the job description summary, second the company description. Now Responsibilities: list each duty as

  . Ensure we capture all responsibilities from the list. Let's extract responsibilities list: - Manage the activities and performance of Operations Project Management professionals and/or supervisors, providing direction, guidance, and accountability for team results. - Oversee the development and implementation of project plans, including timelines, budgets, and resources, to ensure operational efficiency and project success. - Coordinate cross-functional teams to ensure project components are executed according to plan, including procurement, manufacturing, and quality control. - Oversee vendor and supplier activities