Design Engineer II

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. Job Summary: This position supports the airline in-service fleet on repairs of aircraft structure and is responsible for the creation of quality repair solutions in a timely manner from a Design point of view. Duties include performing design efforts for both metallic and non-metallic parts while working in close collaboration with static stress and fatigue colleagues to provide repair solutions. Methods include the use of multiple applications to research aircraft configurations and develop efficient repair solutions to satisfy airworthiness requirements and customers (Airlines/MROs). Primary Responsibilities: list of duties. Additional Responsibilities: other duties as assigned. Qualified Experience and Training: Education, Experience. Qualified Skills: Knowledge, Skills, Demonstrated Capabilities. Physical Requirements: details. Company: Airbus Americas, Inc. Employment Type: US - Direct Hire Experience Level: Professional Remote Type: Flexible Job Family: Structure Design & Integration Job Posting End Date: 09.26.2026 We need to remove boilerplate: EEO, accommodations, notices, etc. We need to include sections only if content present. Potential sections: - About the role (maybe Job Summary) - Responsibilities (Primary Responsibilities + Additional Responsibilities) - Requirements (Education, Experience) - Qualifications (maybe same as Requirements? but we can separate) - Skills (Qualified Skills) - Physical Requirements (maybe as a section? Not in list but we could put under Requirements? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those headings. Physical Requirements could go under Requirements or Qualifications? Probably under Requirements as part of qualifications. But we can also include a separate section if we think it's substantive but not in list; but instruction says use those headings for section headings. It doesn't forbid other headings? 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 content to those. Thus: - About the role: Job Summary. - Responsibilities: Primary Responsibilities + Additional Responsibilities (maybe combine). - Requirements: Education and Experience. - Qualifications: maybe we could treat as same as Requirements? But we need to avoid duplication. Could put Qualifications as "Qualified Experience and Training" maybe? But that is essentially Requirements. Could combine Requirements and Qualifications into one? But they said prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including education, experience, qualifications), Skills. We have no info about Benefits, Pay, Schedule. So we omit those sections. We need to use

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

  for prose. Thus:

  About the role

  This position supports the airline in-service fleet on repairs of aircraft structure and is responsible for the creation of quality repair solutions in a timely manner from a Design point of view. Duties include performing design efforts for both metallic and non-metallic parts while working in close collaboration with static stress and fatigue colleagues to provide repair solutions. Methods include the use of multiple applications to research aircraft configurations and develop efficient repair solutions to satisfy airworthiness requirements and customers (Airlines/MROs).

  Responsibilities

  • Create or modify simple to routine repair tasks autonomously.
  • Review and interpret damage reports of aircraft structures from the Maintenance Repair Organization and develop quality repair solutions with little support.
  • Create or modify technical documents such as: Technical Communications, Technical Dispositions, Repair Instructions, Repair Drawings within various Airbus computer based applications with high quality and efficiency.
  • Understand the priorities of assignments and how this affects workflow.
  • Interface repair requirements with customers and suppliers with a professional attitude.
  • Liaise with Static Stress, F&DT and other appropriate Airbus departments to come up with optimum design solutions for the airline customer.
  • Assists with preparation of various documents using Airbus computer based toolsets (SAP, AirDoc, etc.).
  • Develop and sometimes present materials for team related briefings to internal and/or external customers.
  • Together with other Repair Engineers, be a member of an integrated engineering team, ensuring its strategy, policy and direction is maintained.
  • Provide responses to simple to routine repair queries by giving guidance as required within Airbus Operations and Customer Services in a clear and concise manner.
  • Ensure all tasks and activities are correctly planned, monitored and executed to achieve customer time scales.
  • Identify and support local improvement initiatives to increase team efficiency through process, methods and tools improvements.
  Note: Additional Responsibilities "Other duties as assigned: 5%" we included as last bullet.

  Requirements

  • Education: Required Bachelor of Science (BS) Degree in Engineering (Aero, Civil, Mechanical) with a strong curriculum emphasis on structural design and analysis and mechanics of materials is required.
  • Experience: Required Minimum 3 years total design/analysis experience in airframe design/repair programs. Experience in metallic and/or composite airframe structural repair. Preferred MRO/Fleet Engineering experience, MRB experience.
  • Travel Required: Citizenship: Authorized to work in the US
  But we need to keep "Travel Required: Citizenship: Authorized to work in the US". That's a line. Maybe better to separate: Travel Required: (not given) but Citizenship: Authorized to work in the US. We'll include as bullet.

  Skills

  • Good interpersonal skills, flexibility and adaptability and able to work in a dynamic team environment.
  • Effectively present information and respond to questions from groups of managers, clients, and customers.
  • Applied knowledge of repair and maintenance documentation, techniques and procedures (SRM, NTM, IPC etc.).
  • Ability to interpret and follow verbal and written instructions.
  • Ability to perform work activity tasks in an organized manner with minimal direction once sufficient training has occurred.
  • Ability to read, analyze, and interpret technical procedures and government regulations (SRM, NTM, IPC etc.).
  • Capable of working in a dynamic, fast-paced environment both independently and collectively.
  • Ability to read and interpret engineering drawings and bill of material systems.
  • Ability to write reports and business correspondence effectively.
  • Dependable, self-motivated and accessible.
  • Knowledge of maintenance repair shop practices, equipment and capabilities.
  • Strong computer background, including MS Office application experience (Outlook, Excel, Word, PowerPoint) and Google Suite application experience (Docs, Sheets, Slides, Gmail).
  • Must be able to communicate effectively in English (verbal and written).
  • Preferred: Conversational French and/or German.
  We might also include Physical Requirements but not in headings list. Could we add a section "Requirements" includes physical? Might be okay to add a bullet under Requirements for physical requirements. But we already have Requirements section with education/experience/travel/citizenship. Could add physical requirements as another bullet. Let's add bullet: Physical Requirements: Onsite or remote: Onsite a minimum of 60% of the time at the Wichita Engineering office. Vision: able to see and read computer screens and other electronic equipment with screens, able to read documents, reports and engineering drawings; daily. Hearing: able to hear in order to participate in conversations in person and via teleconference or phone and to hear safety warnings or alarms; daily. Speaking: able to speak in conversations and meetings, deliver information and participate in communications; daily. Equipment Operation (personal computer, telephone, copies, fax machine, and related office equipment and using electronic identification card to enter building floors and internal doors): able to operate most office and personal electronic equipment; daily. Carrying: able to carry documents, tools, drawings, electronic equipment up to 30lbs/14kgs; once a month. Lifting: able to lift documents, tools, drawings, electronic equipment up to 30lbs/14kgs; once a month. Pushing / Pulling: able to push and pull small office furniture and some equipment and tools; once a month. Sitting: able to sit for long periods of time in meetings, working on the computer; daily. Squatting / Kneeling: able to squat or kneel to retrieve or replace items stored on low shelving. Standing: able to stand for discussions in offices; daily. Travel: able to travel independently and at short notice; 10% of the time. Walking (include routine walking such as to a shared printer to retrieve documents): able to walk through office and production areas including uneven surfaces; daily. Personal Protective Equipment required: Required PPE includes, but is not limited to, Safety Shoes, Safety Glasses, Hearing Protection, Respirators/Masks, and/or Protective Gloves as required by site and/or customer site. Administrative position only PPE required: Steel-toed shoes are required for all shop floor visit, appropriate hearing/eye protection may also be required when visiting the shop floor. That's a lot; but we can include as a bullet. But maybe better to keep Requirements section concise; but instruction says preserve ALL substantive information. So we need to include physical requirements somewhere. Could add a separate section "Requirements" that includes education, experience, physical requirements, travel/citizenship. That's okay. Thus Requirements will have multiple bullets: education, experience, travel/citizenship, physical requirements. We'll format physical requirements as a bullet with sub-detail maybe using commas. Let's craft. Also we have Company, Employment Type, Experience Level, Remote Type, Job Family, Job Posting End Date. Where to put? Could be under About the role? Or maybe under Requirements? Not exactly. Could be under About the role as additional context. But we have no specific heading for those. Could add a bullet under About the role? Might be okay. But instruction: "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." So we can fold minor metadata like Company, Employment Type, Experience Level, Remote Type, Job Family, Job Posting End Date into a short

  maybe under About the role or after. Thus after About the role paragraph, we can add a

  with that metadata. Let's do:

  About the role

  This position supports the airline in-service fleet on repairs of aircraft structure and is responsible for the creation of quality repair solutions in a timely manner from a Design point of view. Duties include performing design efforts for both metallic and non-metallic parts while working in close collaboration with static stress and fatigue colleagues to provide repair solutions. Methods include the use of multiple applications to research aircraft configurations and develop efficient repair solutions to satisfy airworthiness requirements and customers (Airlines/MROs).

  Company: Airbus Americas, Inc. | Employment Type: US - Direct Hire | Experience Level: Professional | Remote Type: Flexible | Job Family: Structure Design & Integration | Job Posting End Date: 09.26.2026

  That preserves info. Now we need to ensure we didn't include boilerplate. We removed EEO, accommodations, notices, etc. Check for any leftover boilerplate: