Mechanical Engineer III (Fluid Systems)

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" (company description) maybe as a section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. Content includes: - Who We Are: description of Textron Systems, part of Textron, etc. This is substantive. Could be a section "About the Company" but allowed headings list includes "About the role". Not exactly but we could use "About the role" for role description. However we have "About This Role" heading in original. That is a section heading we can use:

  About the role

  with prose. - Responsibilities: list of duties. - Qualifications: list of requirements. - Skills: maybe not explicit but we have "Advanced proficiency with 3D CAD tools..." etc. Could be part of Qualifications. But we could have a Skills section if we want. However we should avoid thin sections. Could combine Qualifications and Skills? The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications content. We have Skills content (Advanced proficiency with 3D CAD tools, experience with SolidWorks pipe‑routing software is a plus, AI readiness). Could be separate Skills section. - Benefits: we have "How We Care" with list of benefits: Flexible Work Schedules, Education Assistance, Career Development & Training Opportunities, Wellness Program (including Fitness Reimbursement), Medical, Dental, Vision & 401(K) with Company Funding, Paid Parental Leave. Also mention Veteran hiring etc. That's benefits. - Pay: not specified. No pay info. So we should NOT create Pay section. - Schedule: we have "Primary Location US-Louisiana-New Orleans Schedule Full-time". So schedule is Full-time. That's specific content. So we can create Schedule section with that info. - Also we have "Job Level Individual Contributor", "Job Type Experienced", "Shift First Shift", "Job Posting 09/17/2026, 1:00:00 AM". Those are metadata; we can fold into a short

  or drop. Probably include a short paragraph with those details. - Also "How We Care" appears twice duplicated; we need to deduplicate. - Also there is EEO boilerplate at end; remove. - Also "Visit TextronSystems.com & Lycoming.com to read more about who we are and the products we make!" That's part of Who We Are. - Also "This role is in Textron System’s CHOOSE THE APPROPRIATE BUSINESS business area." That's placeholder; we should remove? It's not substantive; it's placeholder text. Should we remove? It's not real specific content; it's placeholder. According to rule: never emit a heading followed by filler/placeholder text. But this is within prose; we should remove that line as it's placeholder. So we should omit that sentence. - Also "Who We Are Textron Systems is part of Textron, a $14 billion, multi-industry company employing 35,000 talented makers, thinkers, creators and doers worldwide. We make things that fly, hover, zoom and launch. Things that move people. Protect soldiers. Power industries. We serve customers in industries spanning aerospace and defense, specialized vehicles, turf care and fuel systems." That's substantive. - Also "About This Role The Senior Fluid Systems Engineer is responsible for designing propulsion and auxiliary fluid systems—including fuel, hydraulics, lubrication, fresh water, pneumatic, and drainage systems—in accordance with program requirements and OEM specifications. This role develops system layouts, writes component and system specifications, performs technical analyses, and collaborates with cross‑functional engineering teams throughout development. The engineer also supports production, testing, and fleet operations by assisting with installation, troubleshooting, system improvements and cost‑reduction initiatives." That's prose. - Responsibilities list: bullet points. - Qualifications list: bullet points. - AI Readiness: could be part of Qualifications or Skills. It's a statement about AI readiness. Could be included in Qualifications as a bullet? It's not a requirement but expectation. Could be placed in a separate section like "Additional Information". But we should avoid thin sections. Could include as a paragraph under Qualifications. - Benefits list: we have bullet list. - Schedule: Full-time. - Also location: US-Louisiana-New Orleans. We need to output only HTML fragment, no /, no markdown. We'll structure:

  About the role

  ... prose about role ...

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...
  Maybe also a

  Skills

  for technical skills: Advanced proficiency with 3D CAD tools such as SolidWorks, CATIA, NX5, or Pro‑E. Experience with SolidWorks pipe‑routing software is a plus. AI readiness: comfortable learning and applying AI-enabled tools, evaluating AI-generated output with sound judgment, using AI in line with company policy and ethical standards. But we could incorporate those into Qualifications as bullet points. However Qualifications currently includes education, years experience, standards, selecting piping components, pressure-drop calculations, sizing ducts, understanding fluid systems, proficiency with 3D CAD tools, experience with SolidWorks pipe‑routing software is a plus, AI readiness. That seems fine to keep as Qualifications. Thus we may not need separate Skills.

  Benefits

  • Flexible Work Schedules
  • Education Assistance
  • Career Development & Training Opportunities
  • Wellness Program (including Fitness Reimbursement)
  • Medical, Dental, Vision & 401(K) with Company Funding
  • Paid Parental Leave

  Schedule

  Full-time

  We also need to include location maybe as part of a short paragraph: "Primary Location: US-Louisiana-New Orleans. Job Level: Individual Contributor. Job Type: Experienced. Shift: First Shift. Posted: 09/17/2026, 1:00:00 AM." Could be a

  after benefits or before schedule. We should not repeat "How We Care" duplicated; we have benefits list already. We need to remove EEO boilerplate. We need to remove duplicated lines: The "How We Care" appears twice; we already have one benefits list. We need to remove "Are you a Military Veteran?" lines? That's part of benefits/veteran hiring; maybe keep as part of benefits? It's a statement about veteran hiring; could be included as a paragraph under Benefits or separate? It's not a benefit per se but a statement. Could be included as a paragraph under Benefits: "Textron is dedicated to hiring military veterans and aims to translate their skills to make an impact on the company." But we should preserve substantive information. The posting includes: "Are you a Military Veteran? Textron's products and services are trusted everyday by those who protect our country. We are dedicated to hiring these Veterans and aim to translate their skills to make an impact on our Company." That's substantive. We'll include as a

  under Benefits or separate section like "Veteran Hiring". But we should avoid thin sections. Could add a paragraph after benefits list. Also there is "Textron is committed to providing Equal Opportunity in Employment..." which is EEO boilerplate; remove. Now we need to ensure we don't include placeholder text: "This role is in Textron System’s CHOOSE THE APPROPRIATE BUSINESS business area." Remove. Also "Visit TextronSystems.com & Lycoming.com to read more about who we are and the products we make!" Keep as part of Who We Are? Actually we didn't include a Who We Are section; we have About the role. The Who We Are description could be a short paragraph before About the role? The instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid having a section like "About the company". But they gave examples; we could add a section "About the company" but not in list. Safer to incorporate that description into About the role paragraph? But About the role should be about the role, not company. However we could add a preceding

  for company description without a heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having prose without heading. But we should prefer few substantive sections. We could add a section "About the company" but not in the list; risk of being considered not following spec. Better to incorporate company description into About the role paragraph as introductory context? Might be okay. Alternatively we could add a heading "About the company" but it's not in the examples; risk of being considered not following spec. I'd rather not add extra heading. Thus we will have:

  About the role

  [company description + role description]

  But that mixes company description with role description; still substantive. Let's craft: About the role paragraph: "Textron Systems is part of Textron, a $14‑billion, multi‑industry company employing 35,000 talented makers, thinkers, creators and doers worldwide. We make things that fly, hover, zoom and launch—products that move people, protect soldiers, and power industries across aerospace and defense, specialized vehicles, turf care, and fuel systems. The Senior Fluid Systems Engineer is responsible for designing propulsion and auxiliary fluid systems—including fuel, hydraulics, lubrication, fresh water, pneumatic, and drainage systems—in accordance with program requirements and OEM specifications. This role develops system layouts, writes component and system specifications, performs technical analyses, and collaborates with cross‑functional engineering teams throughout development. The engineer also supports production, testing, and fleet operations by assisting with installation, troubleshooting, system improvements and cost‑reduction initiatives." That preserves all. Now Responsibilities list: we need to capture each bullet. Original responsibilities: - Design detailed fluid system installations for propulsion and auxiliary systems, including fuel, hydraulic, lubrication oil, fresh water, pneumatic, and drainage systems. - Coordinate supplier subsystem development efforts and participate in supplier design reviews. - Develop and review engineering documentation such as drawings, specifications, analyses, and test reports for accuracy and completeness. - Prepare technical reports for customer submittals. - Execute assigned tasks in alignment with program schedules and budgets. - Coordinate fluid‑system interface requirements with other engineering disciplines. - Identify, track, and mitigate risks associated with craft fluid systems. - Support production, testing, and fielded Navy craft with installation, troubleshooting, and improvements. - Perform additional duties as assigned by management. We'll put each as
• . Qualifications list: - Bachelor of Science in Mechanical Engineering or a related engineering discipline - 5+ years of marine or