Jobs · Management · Iowa

Advanced Manufacturing Engineering Co-Op (Summer/Fall 2027)

Collins Aerospace · Cedar Rapids, IA · 1 mo ago
On-siteManagementFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. No job title heading. Remove boilerplate. We need to parse the posting. Key content: - Date posted, country, location, role type, citizenship requirement, security clearance none. - Intro paragraph: "Are you ready to explore the world of aerospace and defense? Do you want to learn from and collaborate with some of the greatest minds in the industry? At RTX, our internships, co-ops and full-time careers provide an exceptional foundation to work on complex problems, advance your skills and create a safer, more connected world. Discover opportunities to make a difference at RTX." - "What You Will Do" bullet list (responsibilities). Actually bullet list preceded by "* In this position, the co-op will work with a team of engineers to tackle advanced manufacturing projects. Responsibilities include:" then list items. - "What You Will Learn" paragraph. - Qualifications: "Qualifications You Must Have *" bullet list. - "Qualifications We Prefer" bullet list. - Benefits: description of benefits. - Pay: salary range. - Schedule: maybe not explicit; role type is Onsite. Could include Schedule? Not given. So we may not include Schedule section unless there is content. The posting mentions "Onsite" role type, but schedule not explicit. We could include a short paragraph about role type? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real, specific content. For "About the role" we have intro paragraph. For Responsibilities we have bullet list. For Requirements we have citizenship requirement etc. For Qualifications we have must have and preferred. For Skills maybe we could combine? But we have qualifications sections; maybe we treat "Qualifications" as both must have and preferred. Skills could be separate if there is explicit skills list; but we have qualifications that include skills. Could create a Skills section from the preferred qualifications? But better to follow instruction: include sections only when posting has real content. We have content for About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Skills (we could extract from qualifications). But we already have Qualifications section; we could split into Qualifications (must have) and Skills (preferred). However instruction says prefer a few substantive sections over many thin ones. So maybe combine qualifications and skills into one Qualifications section. But they gave example headings including Skills separate. We'll decide to include Qualifications (must have) and Skills (preferred) as separate if they have content. But we need to avoid thin sections. The preferred qualifications list is substantive enough. Thus sections: - About the role (intro paragraph) - Responsibilities (bullet list) - Requirements (citizenship requirement, maybe also location? but location is metadata; we can include as short p) - Qualifications (must have bullet list) - Skills (preferred bullet list) - Benefits (paragraph) - Pay (salary range) Schedule: not given, so omit. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. Let's extract exact text. About the role: The paragraph after "Are you ready to explore..." up to "Discover opportunities to make a difference at RTX." That's the intro. Responsibilities: The bullet list under "What You Will Do". The leading sentence "* In this position, the co-op will work with a team of engineers to tackle advanced manufacturing projects. Responsibilities include:" then list items. We should include that leading sentence as part of responsibilities? Probably yes. We'll put that as a

then

  • items. List items: - Taking ownership of project tasks and managing time and resources to meet goals and milestones. - Planning and implementing automation capital projects. - Researching, evaluating, and testing new technologies to improve quality and productivity on the shop floor. - Providing engineering guidance to optimize equipment use and manufacturing techniques. - Integrating automation solutions into factory systems and improving production processes. - Implementing Smart Factory technologies and adding digital data acquisition to legacy test equipment. - Analyzing manufacturing data and creating dashboards to display metrics for operations teams. Requirements: Citizenship requirement: "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." Also maybe mention "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required". Also security clearance none/not required. Could include that as part of requirements. Also location maybe but we can drop minor metadata. We'll include citizenship and security clearance. Qualifications (must have): bullet list under "Qualifications You Must Have *". Items: - Actively pursuing a bachelor’s or master’s degree in Mechanical, Electrical, Aerospace, Systems, or Manufacturing Engineering through the completion of the internship/co-op session. - Earned a minimum of 30 credit hours prior to the start of the internship/co-op session. - Solid understanding of engineering principles. - Familiarity with Microsoft Office tools, Lean principles, and concepts. - Experience delivering presentations and using design software such as SolidWorks or Siemens NX. Skills (preferred): bullet list under "Qualifications We Prefer". Items: - Minimum 3.0 GPA - Certifications in robotics (e.g., ABB, Fanuc), LabVIEW, and/or PLCs. - Knowledge of control systems and coding (e.g., Ignition, LabVIEW, MATLAB, Ladder Logic). - Experience with data acquisition equipment and controllers (e.g., cDAQ, PLC). - Ability to analyze test data and design testing processes, including verifying measurement systems and performing gage R&R. - Familiarity with 3D modeling, laser cutting, and vision systems. Benefits: paragraph: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement. Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance. This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and benefits will apply." Pay: "The salary range for this role is 37,000 USD - 82,000 USD. The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills." We could combine that into a

    . Schedule: not present. We must not include boilerplate like EEO, privacy policy, application instructions, etc. Remove lines like "Learn More & Apply Now", "Please ensure the role type defined below is appropriate for your needs before applying to this role." etc. Also remove "Date Posted: 2026-09-24 Country: United States of America Location: US-IA-CEDAR RAPIDS-105 ~ 400 Collins Rd NE ~ BLDG 105 Position Role Type: Onsite U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. Security Clearance Type: None/Not Required Security Clearance Status: Not Required". We need to keep citizenship requirement and maybe mention role type Onsite? Could be part of About the role? But we can include a short p about role type? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include a short p with location and role type? But location is minor metadata; we could drop it. However we might keep a short p about role type Onsite? Not required. The posting includes "Position Role Type: Onsite". Could be considered minor metadata; we could drop. But we might keep a short p: "This is an Onsite position requiring U.S. citizenship." That combines role type and citizenship. However citizenship already in Requirements. We could keep role type in About the role? Might be redundant. Better to keep a short p under Requirements: "U.S. citizenship is required (only U.S. citizens authorized to access information). Position is Onsite." That includes both. But we must not invent info; we can combine. Let's craft HTML:

    About the role

    Are you ready to explore the world of aerospace and defense? Do you want to learn from and collaborate with some of the greatest minds in the industry? At RTX, our internships, co-ops and full-time careers provide an exceptional foundation to work on complex problems, advance your skills and create a safer, more connected world. Discover opportunities to make a difference at RTX.

    Responsibilities

    In this position, the co-op will work with a team of engineers to tackle advanced manufacturing projects. Responsibilities include:

    • Taking ownership of project tasks and managing time and resources to meet goals and milestones.
    • Planning and implementing automation capital projects.
    • Researching, evaluating, and testing new technologies to improve quality and productivity on the shop floor.
    • Providing engineering guidance to optimize equipment use and manufacturing techniques.
    • Integrating automation solutions into factory systems and improving production processes.
    • Implementing Smart Factory technologies and adding digital data acquisition to legacy test equipment.
    • Analyzing manufacturing data and creating dashboards to display metrics for operations teams.

    Requirements

    U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. This is an Onsite position.

    Qualifications

    You must have:

    • Actively pursuing a bachelor’s or master’s degree in Mechanical, Electrical, Aerospace, Systems, or Manufacturing Engineering through the completion of the internship/co-op session.
    • Earned a minimum of 30 credit hours prior to the start of the internship/co-op session.
    • Solid understanding of engineering principles.
    • Familiarity with Microsoft Office tools, Lean principles, and concepts.
    • Experience delivering presentations and using design software such as SolidWorks or Siemens NX.

    Skills

    Preferred qualifications:

    • Minimum 3.0 GPA
    • Certifications in robotics (e.g., ABB, Fanuc), LabVIEW, and/or PLCs.
    • Knowledge of control systems and coding (e.g., Ignition, LabVIEW, MATLAB, Ladder Logic).
    • Experience with data acquisition equipment and controllers (e.g., cDAQ, PLC).
    • Ability to analyze test data and design testing processes, including verifying measurement systems and performing gage R&R.
    • Familiarity with 3D modeling, laser cutting, and vision systems.

    Benefits

    Hired applicants may be eligible for benefits, including but not

Similar jobs