Manufacturing Engineer II
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions.
We need to decide sections: Probably "About the role" could be the introductory paragraph describing mission and role. Then "Responsibilities" list from Job Core Responsibilities. Then "Qualifications" list from Qualifications. Then "Skills" maybe from qualifications? But we can combine. The instruction: Use headings for those specific labels if content exists. We have content for Responsibilities, Qualifications, maybe Skills (they mention computer skills, interpersonal, etc). Benefits: they have competitive package details. Pay: they mention Competitive Compensation, Participation in Annual Incentive Program, but not specific numbers. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They do state Competitive Compensation, Participation in Annual Incentive Program, Benefit & Retirement Plans etc. So we can include Benefits section. Pay maybe we can include as part of Benefits? But they have separate heading "Competitive Compensation". Could create Pay section with that content. Schedule: they mention "May need to work variable schedule(s) and additional hours as necessary." Also "Regular, consistent, and punctual attendance is required." That's schedule info. So we can include Schedule section.
We must not repeat job title as heading. No Job ID.
We must output only HTML fragment, no /, no markdown fences.
We need to preserve all substantive info; not invent or summarize away detail. So we need to include the details exactly as given, but we can format as lists.
We need to remove boilerplate: EEO, Drug-Free Workplace, export compliance, etc. Also remove "Come join the Parker Aerospace Team!" maybe that's part of benefits intro; we can keep as part of Benefits section? It's a call to action; maybe considered boilerplate? It's not legal/EOO; it's a marketing line. Might keep as part of Benefits intro. But we can keep it as a paragraph before benefits list.
We need to ensure we don't include duplicated lines.
Let's extract sections:
Intro/About the role: The first paragraph(s) up to "This role will be expected to lead CAPEX projects..." Actually the marketing statement and then description of role. Let's capture:
"Org Marketing Statement At Parker Aerospace, we develop technologies and innovative solutions that enable reliable, efficient and increasingly sustainable flight for the lifecycle of the aircraft, including aftermarket support. Our passionate people with deep engineering expertise, together with our breadth of differentiated technologies, ensure that we make the extraordinary happen and continue to shape the future of aviation in partnership with our customers. As a member of our team, you are instrumental in fulfilling our mission: 'Enabling Engineering Breakthroughs that Lead to a Better Tomorrow.' Pursuing a career at Parker presents unlimited opportunities for both professional and personal development. Working with some of the most brilliant minds in the industry, your contributions will be pivotal in developing innovative technologies and products, significantly contributing to Parker’s goal of addressing the world’s most pressing engineering challenges. At Parker, our team members belong, matter and make a difference. Our Manufacturing Engineering team is seeking a highly motivated individual with responsibilities that will include managing current Manufacturing Engineering documents and execution of special projects, New Product Introductions (NPI) in a production project management capacity and act as a liaison between Design Engineering and the production floor. This role will be expected to lead CAPEX projects to reduce production costs via automation and/or process improvements. Will need to work with both suppliers and internal customers to problem-solve items relating to new and legacy components. Provide operations technical and manufacturing support as required for both new and mature programs. The position will include manufacturing engineering support for final assembly operations in Danville and eventually review/disposition non-conforming product, with a focus on product reliability and customer satisfaction."
That's a lot; we can keep as About the role paragraph(s). Might split into two paragraphs but okay.
Responsibilities: list under "Job Core Responsibilities". We need to capture each bullet line. They are sentences separated by line breaks. We'll make - each.
Responsibilities list:
- Manage and execute special projects such as cost reduction, automation and CAPEX projects
- Manage components through production for new programs.
- Support new product introductions through the design review, build and qualification stages.
- PPAP elements such as PFMEA, PFD (process flow diagrams)
- Create infrastructure in BSD business systems to support new programs.
- MRB (Material Review Board) – Review and disposition parts. Able to provide justification for how to handle each non-conformance and follow the parts through the process to ensure proper handling of the non-conforming product.
- Work with other departments to understand cause and effect of major and minor non-conformances.
- Review/prepare/manage Manufacturing Engineering documentation.
- Works to gain overall knowledge and proficiencies with Aerospace specifications and regulations.
- Support production of our global manufacturing operations by following
- Perform trouble shooting and problem solving both alone and within larger groups with varying difficulties.
- Provide Manufacturing decisions on processes based on various company specifications and experience in a timely manner.
- Conduct investigations to determine root cause and preventative measures for various in-service failures.
- Regular, consistent, and punctual attendance is required.
- May need to work variable schedule(s) and additional hours as necessary.
- Candidates must be willing to travel as required.
Note: Some lines may be incomplete like "Support production of our global manufacturing operations by following" seems truncated; but we keep as is.
Qualifications: list after "Qualifications". Let's capture:
- Bachelor degree in Engineering required (Mechanical or Aerospace preferred)
- Minimum 2 years of Engineering experience
- Effective interpersonal, verbal and written communication and process document skills.
- Strong computer skills required. Proficient in the use of Microsoft Word, Excel and PowerPoint.
- Ability to work independently and interface with cross-functional disciplines including suppliers, design engineering, quality and procurement; using excellent interpersonal skills to drive tasks to completion.
- Goal oriented with the capability to drive results.
- Schedule and execute to ensure adherence to business and customer requirements.
- Ability to define problems, collect data, establish facts, and draw valid conclusions.
- Strong attention to detail.
- Excellent organizational and time management skills with the ability to multi-task while under pressure.
- Demonstrated experience with SAP or other ERP system a plus.
- Continuous Improvement training/experience preferred
- Excellent Project Management skills for successful project delivery is desirable.
- 3D modeling basics to create various tools or fixtures (Catia V5, or Autodesk inventor)
- Experience with FDM 3D printing with knowledge of design for 3D printing and print bed layout optimization.
Skills: Could be derived from qualifications but we might not need separate Skills section if content overlaps. However we have headings for Skills; we could create a Skills section listing things like interpersonal, communication, computer skills, problem solving, etc. But to avoid duplication, maybe we just have Qualifications and Skills combined? The instruction: Use headings for those specific labels if content exists. We have content that could be considered Skills: interpersonal, verbal/written communication, computer skills, ability to work independently, goal oriented, problem solving, attention to detail, organizational/time management, etc. Many of those are already in Qualifications. To avoid duplication, we could still create a Skills section with those items, but that would repeat content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we could keep Qualifications as is and not create Skills section if we think Qualifications already covers skills. But the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require us to use all; only when posting has real specific content. Since we have skills content, we could make a Skills section. But we need to ensure we don't lose any info. If we put skills in Skills section, we might need to remove them from Qualifications to avoid duplication? But we could keep them in both; still preserving all info (duplicated). Might be okay but could be considered redundant. I'd rather not duplicate; we can treat Qualifications as containing both qualifications and skills. But then we would not have a Skills heading, which is allowed if no specific content for Skills beyond what's in Qualifications. However the posting does have explicit skill statements; but they are within Qualifications. I'd say we can keep Qualifications and not add Skills.
Benefits: we have details after "Come join the Parker Aerospace Team! Our competitive package includes:" then list.
Let's capture benefits:
- Competitive Compensation
- Participation in Annual Incentive Program
- Benefit & Retirement Plans
- Comprehensive coverage for medical, prescription drugs, dental, vision, voluntary optional life, accident insurance, hospital indemnity insurance and critical illness insurance with competitive premium cost.
- 401(k) Plan with company matching contributions at 100% of the first 5% of pay
- Company provided defined-contribution retirement plan with annual contribution equal to 3% of pay
- Career development and tuition reimbursement
- Other benefits including paid parental leave, short and long-term disability programs, adoption assistance, a Care.com membership and financial planning assistance are provided at no cost to you.
- Supplemental benefit programs including identity protection, legal protection, and pet wellness are available at competitive rates.
- Paid Time Off and 13 Company-Paid Holidays.
Pay: The posting mentions Competitive Compensation, Participation in Annual Incentive Program. Could treat as Pay section. But we already have Competitive Compensation in Benefits. Could make Pay section with "Competitive Compensation" and "Participation in Annual Incentive Program". However that would duplicate. Maybe better to have Benefits section include all those, and not have separate Pay. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Competitive Compensation etc. So we could have Benefits section; Pay maybe not needed if we consider compensation part of benefits. But they explicitly list Competitive Compensation as a benefit. I'd keep Benefits only.
Schedule: we have "Regular, consistent, and punctual attendance is required." and "May need to work variable schedule(s) and additional hours as necessary." Also maybe travel. We'll put in Schedule section.
We also need to include maybe "Requirements" heading? Not used; we have Qualifications.
We must not include boilerplate: EEO, Drug-Free Workplace, export compliance, etc. Also remove "Come join the Parker Aerospace Team!"? That's a marketing line but could be kept as part of Benefits intro. I'd keep it as a paragraph before benefits list.
Now construct HTML:
About the role
Org Marketing Statement At Parker Aerospace, we develop technologies and innovative solutions that enable reliable, efficient and increasingly sustainable flight for the lifecycle of the aircraft, including aftermarket support. Our passionate people with deep engineering expertise, together with our breadth of differentiated technologies, ensure that we make the extraordinary happen and continue to shape the future of aviation in partnership with our customers. As a member of our team, you are instrumental in fulfilling our mission: 'Enabling Engineering Breakthroughs that Lead to a Better Tomorrow.' Pursuing a career at Parker presents unlimited opportunities for both professional and personal development. Working with some of the most brilliant minds in the industry, your contributions will be pivotal in developing innovative technologies and products, significantly contributing to Parker’s goal of addressing the world’s most pressing engineering challenges. At Parker, our team members belong, matter and make a difference. Our Manufacturing Engineering team is seeking a highly motivated individual with responsibilities that will include managing current Manufacturing Engineering documents and execution of special projects, New Product Introductions (NPI) in a production project management capacity and act as a liaison
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require us to use all; only when posting has real specific content. Since we have skills content, we could make a Skills section. But we need to ensure we don't lose any info. If we put skills in Skills section, we might need to remove them from Qualifications to avoid duplication? But we could keep them in both; still preserving all info (duplicated). Might be okay but could be considered redundant. I'd rather not duplicate; we can treat Qualifications as containing both qualifications and skills. But then we would not have a Skills heading, which is allowed if no specific content for Skills beyond what's in Qualifications. However the posting does have explicit skill statements; but they are within Qualifications. I'd say we can keep Qualifications and not add Skills.
Benefits: we have details after "Come join the Parker Aerospace Team! Our competitive package includes:" then list.
Let's capture benefits:
- Competitive Compensation
- Participation in Annual Incentive Program
- Benefit & Retirement Plans
- Comprehensive coverage for medical, prescription drugs, dental, vision, voluntary optional life, accident insurance, hospital indemnity insurance and critical illness insurance with competitive premium cost.
- 401(k) Plan with company matching contributions at 100% of the first 5% of pay
- Company provided defined-contribution retirement plan with annual contribution equal to 3% of pay
- Career development and tuition reimbursement
- Other benefits including paid parental leave, short and long-term disability programs, adoption assistance, a Care.com membership and financial planning assistance are provided at no cost to you.
- Supplemental benefit programs including identity protection, legal protection, and pet wellness are available at competitive rates.
- Paid Time Off and 13 Company-Paid Holidays.
Pay: The posting mentions Competitive Compensation, Participation in Annual Incentive Program. Could treat as Pay section. But we already have Competitive Compensation in Benefits. Could make Pay section with "Competitive Compensation" and "Participation in Annual Incentive Program". However that would duplicate. Maybe better to have Benefits section include all those, and not have separate Pay. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Competitive Compensation etc. So we could have Benefits section; Pay maybe not needed if we consider compensation part of benefits. But they explicitly list Competitive Compensation as a benefit. I'd keep Benefits only.
Schedule: we have "Regular, consistent, and punctual attendance is required." and "May need to work variable schedule(s) and additional hours as necessary." Also maybe travel. We'll put in Schedule section.
We also need to include maybe "Requirements" heading? Not used; we have Qualifications.
We must not include boilerplate: EEO, Drug-Free Workplace, export compliance, etc. Also remove "Come join the Parker Aerospace Team!"? That's a marketing line but could be kept as part of Benefits intro. I'd keep it as a paragraph before benefits list.
Now construct HTML:
About the role
Org Marketing Statement At Parker Aerospace, we develop technologies and innovative solutions that enable reliable, efficient and increasingly sustainable flight for the lifecycle of the aircraft, including aftermarket support. Our passionate people with deep engineering expertise, together with our breadth of differentiated technologies, ensure that we make the extraordinary happen and continue to shape the future of aviation in partnership with our customers. As a member of our team, you are instrumental in fulfilling our mission: 'Enabling Engineering Breakthroughs that Lead to a Better Tomorrow.' Pursuing a career at Parker presents unlimited opportunities for both professional and personal development. Working with some of the most brilliant minds in the industry, your contributions will be pivotal in developing innovative technologies and products, significantly contributing to Parker’s goal of addressing the world’s most pressing engineering challenges. At Parker, our team members belong, matter and make a difference. Our Manufacturing Engineering team is seeking a highly motivated individual with responsibilities that will include managing current Manufacturing Engineering documents and execution of special projects, New Product Introductions (NPI) in a production project management capacity and act as a liaison