Project Manager (Contract)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. Let's parse the posting. Key sections: - Job Description: Aere you ready... (typo). It's about leading high-stakes aircraft maintenance and repair programs. So we can have an "About the role" paragraph summarizing that. - Responsibilities: The bullet points under "Yuor Challenges:" with subcategories: Key Project Management (60%), Performance & Offers Management (30%), Subcontractor Management (10%). Those are responsibilities. - Requirements: "Your Boarding Pass: (Required for consideration)" includes: Must possess a Bachelor's degree in Business Administration or Program Management field, or equivalent (4) years of applicable experience. Have at least f our (4) years of experience in project management within a production or technical environment. Financial experience for budgeting purposes. Technical experience to comprehend technical data packages. Ability to break complex issues down into manageable work packages. Strong crisis management skills; and even stronger planning skills to prevent crises. Proven Microsoft Office and/or Google Suite skills Some SAP knowledge, or similar. - Preferred Skills: list after "Preferred Skills:" includes: Experience in aircraft completions or maintenance and repair. Knowledgeable in FAA regulations. Project/Program Management Certification A&P An understanding of the aerospace industry, basic aircraft design, mission equipment packages (law enforcement, emergency medical services, utility etc.), and design and certification (FAA) processes & regulations. - Travel Required: Minimal- 10% Domestic and International - Citizenship: Authorized to Work in the US without current or future need for visa sponsorship - Clearance: None - Physical Requirements: long list. - Also note: "This position is a temporary (contract) position with no specific time period but could be extended or shortened as needed. Contractors are employed by a 3rd party vendor and placed on assignment to Airbus in America." That's employment type info. - Benefits, Pay, Schedule: Not explicitly stated. There's no mention of pay, benefits, schedule specifics. So we should NOT include those sections because they'd be empty or placeholder. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. So we omit those. - Also "Working environment" etc could be part of About the role or maybe a separate section like "Working Conditions". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put "Qualifications" maybe for education/experience, and "Skills" for preferred skills. Or combine. We need to decide mapping: - About the role: brief description of role and purpose. - Responsibilities: the three categories with bullet points. - Requirements: mandatory requirements (education, experience, etc.) - Qualifications: maybe could be same as Requirements? But we can treat Requirements as mandatory, Qualifications as preferred? However we have also Skills section for preferred skills. Could put Qualifications for education/experience, Skills for technical/soft skills, and maybe Requirements for something else? But we need to avoid duplication. Better: Use About the role (summary), Responsibilities (duties), Requirements (mandatory qualifications), Skills (preferred skills). Possibly also include a "Qualifications" section for certifications? But we have Preferred Skills includes certifications. Could put those under Skills. Thus we will have sections: About the role, Responsibilities, Requirements, Skills. We must not include Benefits, Pay, Schedule. Now we need to format:

for each section heading. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: percentages, bullet points, etc. Let's extract details. About the role: The paragraph: "Airbus Helicopters is seeking a Project Manager to own the end-to-end execution of our aircraft maintenance, repair, and overhaul (MRO) projects. Operating at the intersection of operations, engineering, and customer relations, you will ensure critical aircraft repair campaigns and customer contracts are delivered on schedule, within budget, and to the highest technical standards. This position is a temporary (contract) position with no specific time period but could be extended or shortened as needed. Contractors are employed by a 3rd party vendor and placed on assignment to Airbus in America." Also mention location: Columbus, MS (eastern border of Mississippi). Also mention team focus etc. Could include that. We'll create a paragraph summarizing. Responsibilities: We have three categories with percentages and bullet points. We need to preserve bullet points exactly as given (maybe rephrase slightly but keep meaning). Use

  • . We'll create subheadings? Not allowed; only headings are the main sections. Within Responsibilities we can have paragraphs or lists. Could embed subheadings as bold? Not specified; we can just list items. We'll create a
    with each responsibility item. Might be long; but okay. We need to include the percentages? Could include as part of each item text. Let's list: Key Project Management (60%): - Lead aircraft maintenance and repair programs involving multifunctional teams. - Align business objectives and contract requirements with engineering, operations, procurement, and repair site resources - Establish landmarks and monitor adherence to master plans and schedules, proactively identify problems and develop solutions such as allocation of resources or adjusting contractual specifications - Drive performance to plan and achieve schedule, delivery, and financial commitments - Propose and run customer agreements/contracts. - Create weekly communication routines with all interested parties for on-going contracts. - Represent our company with our customers and lead program to meet contractual requirements, including delivery schedules, cost, and technical specifications - Lead teams to address program risk and issues; create, maintain and drive action plans to closure. - Establish Repair Campaign plans and re-plans including capacity assessments and operator maintenance schedules Performance & Offers Management (30%): - Develop a business capture plan in collaboration with the sales team. - Propose offers aligned with financial performances target and the AH Group strategy. - Aid in the development of a reliable and financial OP. (maybe "OP" stands for Operating Plan? Keep as is) - Create and maintain reliable aircraft metrics for financial performance, customer satisfaction and to measure forecasting traceability and accuracy. - Develop and implement forecasting and planning schedules. - Track schedules to ensure 100% on time completion. - Identify problems that impact timely delivery, ability to achieve margins, or are areas of inconsistency in the business. - Keep the project team, customer and leadership informed on changing project landmarks. Subcontractor Management (10%): - Focal point for all subcontractor interaction. - Coordinate activities with subcontractor to assure schedules & needs are communicated and adhered to. - Coordinates activities between subcontractor and supporting functions, such as spares supply management, supporting back shop activities and design office support. - Monitor subcontractor performance, such as schedule adherence and quality performance. - Ensure adherence to supplier improvement and action plans as needed. - Receive/ approve subcontractor proposals & invoices for projects. - Conduct periodic program performance and subcontractor performance reviews. - Mitigate discrepancies and resolve issues to facilitate project success. - Track data results including burn downs and projections and facilitate resolution of open issues We need to keep the exact phrasing; some have typos like "landmarks" maybe meant "milestones". Keep as is. Now Requirements (mandatory): From "Your Boarding Pass: (Required for consideration)": - Must possess a Bachelor's degree in Business Administration or Program Management field, or equivalent (4) years of applicable experience. - Have at least f our (4) years of experience in project management within a production or technical environment. (typo "f our" -> "four". We'll keep as "four (4) years".) - Financial experience for budgeting purposes. - Technical experience to comprehend technical data packages. - Ability to break complex issues down into manageable work packages. - Strong crisis management skills; and even stronger planning skills to prevent crises. - Proven Microsoft Office and/or Google Suite skills - Some SAP knowledge, or similar Also maybe include "Travel Required: Minimal- 10% Domestic and International" could be under Requirements? It's a requirement. Could be placed under Requirements or maybe a separate section but we don't have a heading for travel. Could include in Requirements as a bullet. Citizenship: Authorized to Work in the US without current or future need for visa sponsorship Clearance: None (maybe not needed to include as it's none; but it's substantive? It says "Clearance: None". Could include but it's basically stating no clearance required. Might be considered minor metadata; we could drop as per instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." Clearance: None is minor metadata; we could drop. Physical Requirements: long list; could be included under Requirements or maybe a separate section but we don't have a heading for physical requirements. Could include under Requirements as a list. We need to preserve ALL substantive information; we cannot drop physical requirements unless we consider them minor metadata? They are substantive. So we need to include them somewhere. Since we lack a specific heading, we can include them under Requirements as a list. Thus Requirements will contain many items: education, experience, financial, technical, ability, crisis management, planning, MS Office, SAP, travel, citizenship, physical requirements. We should keep them as bullet points. Now Skills (preferred skills): From "Preferred Skills:" list: - Experience in aircraft completions or maintenance and repair. - Knowledgeable in FAA regulations. - Project/Program Management Certification - A&P - An understanding of the aerospace industry, basic aircraft design, mission equipment packages (law enforcement, emergency medical services, utility etc.), and design and certification (FAA) processes & regulations. Also maybe include "Some SAP knowledge, or similar" already in requirements; but that's fine. We'll put these as bullet list under Skills. Now we need to ensure we don't include boilerplate like EEO, legal, etc. We'll strip those. Now produce HTML fragment:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Skills

    • ...
    ...
    Make sure no extra sections. Now craft the About the role paragraph: combine description. Paragraph: "Airbus Helicopters is seeking a Project Manager to own the end-to-end execution of our aircraft maintenance, repair, and overhaul (MRO) projects. Operating at the intersection of operations, engineering, and customer relations, you will ensure critical aircraft repair campaigns and customer contracts are delivered on schedule, within budget, and to the highest technical standards. This position is a temporary (contract) role with no fixed duration, subject to extension or shortening as needed, and contractors are employed by a third‑party vendor and placed on assignment to Airbus in America. The role is based in Columbus, MS, where the team builds and services the UH‑72A Lakota for the U.S. Army and the H‑125 for civil and commercial customers, focusing on quality, productivity, and safety." We need to preserve all substantive info: mention location, team focus, etc. That's fine. Now Responsibilities list: we need to include the percentages maybe as part of each category heading inside list items? Could make each category as a paragraph then list. But we only allowed
    • for list. Could we have headings inside list? Not prohibited but better to keep simple: each bullet is a responsibility. We'll include the percentage in the bullet text. Let's create bullets: - Key Project Management (60%): Lead aircraft maintenance and repair programs involving multifunctional teams. - Align