Senior Engineer, Mechanical Design Engineering (Onsite)
for each section heading.
We must use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove lines like "Learn More & Apply Now!", "Please ensure the role type...", "As part of our commitment...", etc. Also remove EEO statement at end. Remove "Privacy Policy and Terms". Remove "Date Posted:" maybe? It's metadata; could be folded into short
or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include date posted, location, citizenship requirement maybe in a short
under About the role? Or we could have a small paragraph at top with metadata. But we must not create a heading for metadata. Probably include a short
after the opening? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have a leading
for metadata like location, date posted, citizenship requirement. Then sections.
Let's extract substantive content:
About the role: The paragraph starting "At Collins Aerospace, we’re developing innovative technologies..." up to "...If you’re ready to work on challenging aerospace applications and make a measurable impact through innovative mechanical design, we want you to join us in shaping the future of aerospace."
We should keep that as prose.
Responsibilities: bullet list from "What You Will Do". Each bullet is a sentence.
List them:
- Design and review mechanical components and assemblies using SolidWorks, balancing performance, cost, manufacturability, safety, and quality requirements.
- Perform thermal and structural analyses using ANSYS Workbench to evaluate product performance and support design decisions.
- Conduct fatigue and durability assessments, including stress-life and strain-life methodologies, to develop product life predictions.
- Develop technical documentation and engineering reports and participate in conceptual, preliminary, and detailed design reviews.
- Collaborate within Integrated Project Teams (IPTs) to develop cost-effective designs that meet customer expectations, quality standards, and business objectives.
- Apply Design for Manufacturability (DFM) principles to optimize designs for efficient, repeatable, and cost-effective production across multiple manufacturing processes.
- Identify, assess, and mitigate design risks, including developing Failure Modes and Effects Analyses (FMEAs) and implementing design improvements.
- Provide technical support throughout the product lifecycle, including troubleshooting production and field issues and determining appropriate dispositions for non-conforming hardware.
- Develop engineering solutions for Maintenance, Repair & Overhaul (MRO) activities, including repair concepts and supporting technical documentation.
- Partner with manufacturing, operations, quality, and other engineering disciplines to resolve technical challenges and improve product performance.
- Develop and implement engineering procedures and standard work to improve design consistency, team efficiency, and overall engineering quality.
Requirements: Must include citizenship requirement: "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required". Also maybe "Security Clearance Type: None/Not Required" but that's not a requirement; it's just info. Could be included but not required. We'll include citizenship requirement.
Also "Qualifications You Must Have" is a set of qualifications: degree in STEM unless prohibited and min 5 years prior relevant experience OR advanced degree and min 3 years OR no degree 9 years experience. That's a qualification, could be under Requirements or Qualifications. The instruction: sections: Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = mandatory qualifications. Qualifications = preferred qualifications. Skills = specific technical skills. We'll allocate:
- Requirements (
Requirements
): list mandatory items: citizenship requirement, education/experience criteria (the "You Must Have").
- Qualifications (Qualifications
): preferred qualifications list.
- Skills (Skills
): maybe list of specific technical proficiencies: SolidWorks, ANSYS Workbench, GD&T, DFMA, metallic joining (brazing/welding), fatigue analysis (stress-life/strain-life), design optimization methods/tools, MS Word/Excel, communication, programming aptitude VB/Python.
But some of those overlap with preferred qualifications. We could keep Qualifications as the "Qualifications We Prefer" list (which includes many of those). Then Skills could be a concise list of technical skills extracted. However we must not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is allowed? It says remove duplicated lines. So we should avoid duplicating the same exact lines. If we list same content in two sections, that's duplication. Better to split: Qualifications section contains the "Qualifications We Prefer" bullet list. Skills section could contain a concise list of technical skills not already covered? But many are covered. Perhaps we can omit Skills section and just have Qualifications cover both preferred and skills. But the instruction says we can include sections only when posting has real specific content for it. It doesn't require us to have all sections. So we can omit Skills if we feel it's redundant. However we might still want to include Skills as a separate section if we can extract distinct skill items not already in Qualifications. The Qualifications We Prefer list includes:
- Proficiency with SolidWorks; experience with ANSYS Workbench strongly preferred.
- Ability to read and interpret engineering drawings and familiarity with GD&T.
- Experience applying Design for Manufacturing and Assembly (DFMA) principles to mechanical designs.
- Knowledge of metallic joining processes, including brazing and welding.
- Experience performing stress-life and strain-life fatigue analyses for metallic components.
- Familiarity with design optimization methods and tools.
- Working knowledge of Microsoft Word and Excel for technical documentation and data analysis.
- Strong verbal, written, and technical communication skills, with the ability to collaborate effectively in a cross-functional team environment.
- Programming aptitude in Visual Basic and/or Python is a plus.
These are essentially skills. So we could treat this as Skills section. Then Qualifications section could be the mandatory education/experience criteria plus citizenship. That seems logical: Requirements = mandatory qualifications (citizenship, education/experience). Qualifications = preferred qualifications (the list). Skills maybe not needed. But we could still have Skills as a subset but would duplicate. Better to omit Skills.
Thus sections: About the role (p), Responsibilities (ul), Requirements (ul), Qualifications (ul), Benefits (ul), Pay (p). No Schedule.
Check for any other substantive content: "Position Role Type: Onsite" - we could include that in metadata paragraph. Also location and date posted.
We'll create a leading with metadata: "Posted: 2026-09-15. Location: West Des Moines, IA, USA. Role type: Onsite. U.S. citizenship required." That preserves info.
Now ensure we don't include boilerplate like "Learn More & Apply Now!", "Please ensure the role type...", "As part of our commitment...", EEO statement, Privacy Policy, etc.
Now produce HTML fragment.
We must not use markdown code fences. Just raw HTML.
Let's craft:
Posted: 2026-09-15. Location: West Des Moines, IA, USA. Role type: Onsite. U.S. citizenship required.
About the role
At Collins Aerospace, we’re developing innovative technologies that are redefining what’s possible in aerospace and defense. We’re looking for a Mechanical Design Engineer who is excited to solve complex engineering challenges, turn concepts into high-performance products, and work across the full product lifecycle. In this role, you’ll have the opportunity to take ownership of mechanical design activities—from concept development and analysis through production support and fielded products. You’ll use tools such as SolidWorks and ANSYS Workbench to develop and validate robust designs, apply advanced engineering principles to predict product performance and life, and work closely with cross-functional teams to deliver solutions that meet customer, quality, cost, and schedule requirements. You’ll be part of an Integrated Project Team (IPT) where your engineering expertise will directly influence product performance, manufacturability, reliability, and cost. This is an ideal opportunity for an engineer who enjoys hands-on problem solving, collaborating with manufacturing and operations, and seeing their designs move from concept to production and into service. If you’re ready to work on challenging aerospace applications and make a measurable impact through innovative mechanical design, we want you to join us in shaping the future of aerospace.
Responsibilities
- Design and review mechanical components and assemblies using SolidWorks, balancing performance, cost, manufacturability, safety, and quality requirements.
- Perform thermal and structural analyses using ANSYS Workbench to evaluate product performance and support design decisions.
- Conduct fatigue and durability assessments, including stress-life and strain-life methodologies, to develop product life predictions.
- Develop technical documentation and engineering reports and participate in conceptual, preliminary, and detailed design reviews.
- Collaborate within Integrated Project Teams (IPTs) to develop cost-effective designs that meet customer expectations, quality standards, and business objectives.
- Apply Design for Manufacturability (DFM) principles to optimize designs for efficient, repeatable, and cost-effective production across multiple manufacturing processes.
- Identify, assess, and mitigate design risks, including developing Failure Modes and Effects Analyses (FMEAs) and implementing design improvements.
- Provide technical support throughout the product lifecycle, including troubleshooting production and field issues and determining appropriate dispositions for non-conforming hardware.
- Develop engineering solutions for Maintenance, Repair & Overhaul (MRO) activities, including repair concepts and supporting technical documentation.
- Partner with manufacturing, operations, quality, and other engineering disciplines to resolve technical challenges and improve product performance.
- Develop and implement engineering procedures and standard work to improve design consistency, team efficiency, and overall engineering quality.
Requirements
- U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract).
for prose. We must preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove lines like "Learn More & Apply Now!", "Please ensure the role type...", "As part of our commitment...", etc. Also remove EEO statement at end. Remove "Privacy Policy and Terms". Remove "Date Posted:" maybe? It's metadata; could be folded into short
or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include date posted, location, citizenship requirement maybe in a short
under About the role? Or we could have a small paragraph at top with metadata. But we must not create a heading for metadata. Probably include a short
after the opening? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have a leading
for metadata like location, date posted, citizenship requirement. Then sections. Let's extract substantive content: About the role: The paragraph starting "At Collins Aerospace, we’re developing innovative technologies..." up to "...If you’re ready to work on challenging aerospace applications and make a measurable impact through innovative mechanical design, we want you to join us in shaping the future of aerospace." We should keep that as prose. Responsibilities: bullet list from "What You Will Do". Each bullet is a sentence. List them: - Design and review mechanical components and assemblies using SolidWorks, balancing performance, cost, manufacturability, safety, and quality requirements. - Perform thermal and structural analyses using ANSYS Workbench to evaluate product performance and support design decisions. - Conduct fatigue and durability assessments, including stress-life and strain-life methodologies, to develop product life predictions. - Develop technical documentation and engineering reports and participate in conceptual, preliminary, and detailed design reviews. - Collaborate within Integrated Project Teams (IPTs) to develop cost-effective designs that meet customer expectations, quality standards, and business objectives. - Apply Design for Manufacturability (DFM) principles to optimize designs for efficient, repeatable, and cost-effective production across multiple manufacturing processes. - Identify, assess, and mitigate design risks, including developing Failure Modes and Effects Analyses (FMEAs) and implementing design improvements. - Provide technical support throughout the product lifecycle, including troubleshooting production and field issues and determining appropriate dispositions for non-conforming hardware. - Develop engineering solutions for Maintenance, Repair & Overhaul (MRO) activities, including repair concepts and supporting technical documentation. - Partner with manufacturing, operations, quality, and other engineering disciplines to resolve technical challenges and improve product performance. - Develop and implement engineering procedures and standard work to improve design consistency, team efficiency, and overall engineering quality. Requirements: Must include citizenship requirement: "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required". Also maybe "Security Clearance Type: None/Not Required" but that's not a requirement; it's just info. Could be included but not required. We'll include citizenship requirement. Also "Qualifications You Must Have" is a set of qualifications: degree in STEM unless prohibited and min 5 years prior relevant experience OR advanced degree and min 3 years OR no degree 9 years experience. That's a qualification, could be under Requirements or Qualifications. The instruction: sections: Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = mandatory qualifications. Qualifications = preferred qualifications. Skills = specific technical skills. We'll allocate: - Requirements (
Requirements
): list mandatory items: citizenship requirement, education/experience criteria (the "You Must Have"). - Qualifications (Qualifications
): preferred qualifications list. - Skills (Skills
): maybe list of specific technical proficiencies: SolidWorks, ANSYS Workbench, GD&T, DFMA, metallic joining (brazing/welding), fatigue analysis (stress-life/strain-life), design optimization methods/tools, MS Word/Excel, communication, programming aptitude VB/Python. But some of those overlap with preferred qualifications. We could keep Qualifications as the "Qualifications We Prefer" list (which includes many of those). Then Skills could be a concise list of technical skills extracted. However we must not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is allowed? It says remove duplicated lines. So we should avoid duplicating the same exact lines. If we list same content in two sections, that's duplication. Better to split: Qualifications section contains the "Qualifications We Prefer" bullet list. Skills section could contain a concise list of technical skills not already covered? But many are covered. Perhaps we can omit Skills section and just have Qualifications cover both preferred and skills. But the instruction says we can include sections only when posting has real specific content for it. It doesn't require us to have all sections. So we can omit Skills if we feel it's redundant. However we might still want to include Skills as a separate section if we can extract distinct skill items not already in Qualifications. The Qualifications We Prefer list includes: - Proficiency with SolidWorks; experience with ANSYS Workbench strongly preferred. - Ability to read and interpret engineering drawings and familiarity with GD&T. - Experience applying Design for Manufacturing and Assembly (DFMA) principles to mechanical designs. - Knowledge of metallic joining processes, including brazing and welding. - Experience performing stress-life and strain-life fatigue analyses for metallic components. - Familiarity with design optimization methods and tools. - Working knowledge of Microsoft Word and Excel for technical documentation and data analysis. - Strong verbal, written, and technical communication skills, with the ability to collaborate effectively in a cross-functional team environment. - Programming aptitude in Visual Basic and/or Python is a plus. These are essentially skills. So we could treat this as Skills section. Then Qualifications section could be the mandatory education/experience criteria plus citizenship. That seems logical: Requirements = mandatory qualifications (citizenship, education/experience). Qualifications = preferred qualifications (the list). Skills maybe not needed. But we could still have Skills as a subset but would duplicate. Better to omit Skills. Thus sections: About the role (p), Responsibilities (ul), Requirements (ul), Qualifications (ul), Benefits (ul), Pay (p). No Schedule. Check for any other substantive content: "Position Role Type: Onsite" - we could include that in metadata paragraph. Also location and date posted. We'll create a leadingwith metadata: "Posted: 2026-09-15. Location: West Des Moines, IA, USA. Role type: Onsite. U.S. citizenship required." That preserves info. Now ensure we don't include boilerplate like "Learn More & Apply Now!", "Please ensure the role type...", "As part of our commitment...", EEO statement, Privacy Policy, etc. Now produce HTML fragment. We must not use markdown code fences. Just raw HTML. Let's craft:
Posted: 2026-09-15. Location: West Des Moines, IA, USA. Role type: Onsite. U.S. citizenship required.
About the role
At Collins Aerospace, we’re developing innovative technologies that are redefining what’s possible in aerospace and defense. We’re looking for a Mechanical Design Engineer who is excited to solve complex engineering challenges, turn concepts into high-performance products, and work across the full product lifecycle. In this role, you’ll have the opportunity to take ownership of mechanical design activities—from concept development and analysis through production support and fielded products. You’ll use tools such as SolidWorks and ANSYS Workbench to develop and validate robust designs, apply advanced engineering principles to predict product performance and life, and work closely with cross-functional teams to deliver solutions that meet customer, quality, cost, and schedule requirements. You’ll be part of an Integrated Project Team (IPT) where your engineering expertise will directly influence product performance, manufacturability, reliability, and cost. This is an ideal opportunity for an engineer who enjoys hands-on problem solving, collaborating with manufacturing and operations, and seeing their designs move from concept to production and into service. If you’re ready to work on challenging aerospace applications and make a measurable impact through innovative mechanical design, we want you to join us in shaping the future of aerospace.
Responsibilities
- Design and review mechanical components and assemblies using SolidWorks, balancing performance, cost, manufacturability, safety, and quality requirements.
- Perform thermal and structural analyses using ANSYS Workbench to evaluate product performance and support design decisions.
- Conduct fatigue and durability assessments, including stress-life and strain-life methodologies, to develop product life predictions.
- Develop technical documentation and engineering reports and participate in conceptual, preliminary, and detailed design reviews.
- Collaborate within Integrated Project Teams (IPTs) to develop cost-effective designs that meet customer expectations, quality standards, and business objectives.
- Apply Design for Manufacturability (DFM) principles to optimize designs for efficient, repeatable, and cost-effective production across multiple manufacturing processes.
- Identify, assess, and mitigate design risks, including developing Failure Modes and Effects Analyses (FMEAs) and implementing design improvements.
- Provide technical support throughout the product lifecycle, including troubleshooting production and field issues and determining appropriate dispositions for non-conforming hardware.
- Develop engineering solutions for Maintenance, Repair & Overhaul (MRO) activities, including repair concepts and supporting technical documentation.
- Partner with manufacturing, operations, quality, and other engineering disciplines to resolve technical challenges and improve product performance.
- Develop and implement engineering procedures and standard work to improve design consistency, team efficiency, and overall engineering quality.
Requirements
- U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract).