Process Improvement Engineer 2027 Summer Internship
EducationVolunteer
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 specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "General Dynamics Electric Boat provides an unparalleled learning experience for college students, offering practical exposure in the defense industry alongside expert engineers, shaping the future of submarine innovation. General Dynamics Electric Boat is one of the only two shipyards that produce submarines for the US Navy and there’s never been a better time to join. The US Navy has a demand for cutting-edge naval capability and technology never seen before, and Electric Boat is the vanguard—designing, building, and maintaining the most advanced submarines in the world. Our work is mission-critical work in supporting the U.S. Navy and strengthening national security. This program requires a minimum commitment of 8 weeks during the Summer 2027 Season. Participation in this program requires medical screening, passing a drug test and background check. This is not a remote opportunity. This position is located at the Groton, CT location and you will need reliable transportation and housing for the duration of your intern assignment."
- Then "About D201 – Process Improvement Engineering" heading (but we treat as section maybe "About the role"? Actually we need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have "About D201 – Process Improvement Engineering" which is about the team mission. Could be "About the role". We'll put that under About the role
.
Then "Role Overview" paragraph: "In this role, you will help apply logical, data‑driven, and collaborative problem‑solving methods to real challenges within submarine manufacturing at Groton. You will work directly with Continuous improvement professionals, shipbuilders, and teams across the organization, gaining hands‑on experience in problem solving and learning how world‑class submarines are built. Interns will assist the Continuous Improvement staff in investigating processes, gathering data, facilitating team discussions, and supporting efforts that reduce lead times, improve quality, lower costs, and enhance safety in manufacturing and outfitting areas. A key challenge you’ll help address is the complexity of Electric Boat’s high‑mix, low‑volume production environment. Unlike traditional assembly lines with repetitive processes, submarine construction involves thousands of unique tasks and extensive coordination. Interns will learn how to apply foundational Lean Six Sigma tools in situations where the goal is not simply streamlining linear flow, but improving communication, teamwork, and system‑level coordination across diverse trades and activities. Selected interns will receive instruction in Lean Six Sigma principles and will be supported in applying these tools within Electric Boat’s unique Continuous Improvement approach. This role is designed to give you meaningful exposure to complex manufacturing, hands‑on learning opportunities, and the chance to support teams as they solve some of the most challenging constraints in submarine production."
That could be "Responsibilities". We'll put under Responsibilities
.
Then "Required Qualifications" list: bullet points.
- Must be 18 years of age or older
- US citizenship is required
- Must be able to successfully pass a medically supervised drug screen and background check
- Must be enrolled full-time at a college or university
- At minimum students must have completed their Freshman year prior to the start of the internship
- Must be available to work 40 hours per week for a minimum eight (8) consecutive weeks between May 2027 to September 2027
- Selected candidates will be responsible for establishing housing and reliable transportation for the duration of their intern assignment
These are qualifications. Could be under Qualifications
or Requirements. The spec says we have both Requirements and Qualifications sections. We need to decide where to put content. Usually "Required Qualifications" is qualifications. "Preferred Experience" etc could be under Skills or Requirements? Let's see.
After Required Qualifications, there is:
"Pursuing a Bachelor or Masters Degree in Operations Management, Business Administration, Business Analytics, Organizational Leadership, Industrial Organizational Psychology, Mechanical Engineering, Industrial Engineering, or Engineering Management"
That's also a qualification (preferred? Actually it's under "Preferred Experience"? Wait reading: The text: "Pursuing a Bachelor or Masters Degree in Operations Management, Business Administration, Business Analytics, Organizational Leadership, Industrial Organizational Psychology, Mechanical Engineering, Industrial Engineering, or Engineering Management Preferred Experience in team leadership or collaborative problem solving Education or experience with Lean, Six Sigma, Kaizen, Toyota Production Systems, or other related continuous improvement approaches is highly desired Experience with project management Skills Skills Strong interpersonal and emotional intelligence skills Persistent, patient, and kind Demonstrated ability to close out projects on-time with desired results Able to combine initiative with professionalism to accomplish difficult tasks Motivated, performance driven individual with strong leadership skills"
It seems formatting messed. Let's parse:
After "Selected candidates will be responsible for establishing housing and reliable transportation for the duration of their intern assignment" there is line break then:
"Pursuing a Bachelor or Masters Degree in Operations Management, Business Administration, Business Analytics, Organizational Leadership, Industrial Organizational Psychology, Mechanical Engineering, Industrial Engineering, or Engineering Management"
Then "Preferred Experience in team leadership or collaborative problem solving"
Then "Education or experience with Lean, Six Sigma, Kaizen, Toyota Production Systems, or other related continuous improvement approaches is highly desired"
Then "Experience with project management"
Then "Skills" (maybe heading?) then list:
"Strong interpersonal and emotional intelligence skills"
"Persistent, patient, and kind"
"Demonstrated ability to close out projects on-time with desired results"
"Able to combine initiative with professionalism to accomplish difficult tasks"
"Motivated, performance driven individual with strong leadership skills"
Thus we have:
- Preferred qualifications: degree fields.
- Preferred experience: team leadership/collaborative problem solving.
- Preferred experience: Lean Six Sigma etc.
- Experience with project management.
- Skills: list of soft skills.
Thus we can have sections: Qualifications (required), Preferred Qualifications (maybe under Qualifications or Requirements?), Skills.
But spec only allows sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to put required qualifications under Qualifications, and preferred qualifications/experience under Requirements? Or we could combine required and preferred into Qualifications, and put skills under Skills. Requirements could be things like availability, commitment, location, etc. However we have location and commitment already in intro; but we could put them under Requirements.
Better: Use Qualifications for required qualifications (citizenship, age, enrollment, etc). Use Requirements for things like availability (40 hrs/week, 8 weeks, housing/transportation). Use Skills for the soft skills list. Use About the role for the mission/team description. Use Responsibilities for role overview.
We must not create sections with filler. Benefits, Pay, Schedule: we have no explicit benefits, pay, schedule details besides schedule (40 hrs/week, 8 weeks). That's schedule info. So we could create a Schedule section with that detail. However schedule info is also in qualifications/requirements. But we can still create Schedule section if we have specific schedule info. The spec says: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states: "Must be available to work 40 hours per week for a minimum eight (8) consecutive weeks between May 2027 to September 2027." That's schedule. So we can include a Schedule section with that.
Benefits: not mentioned. Pay: not mentioned. So omit those.
Thus sections:
- About the role (h3)
- Responsibilities (h3)
- Requirements (h3) maybe containing: housing/transportation requirement, location? Actually location is in intro; but we could include location under Requirements or About the role. Let's put location and housing/transportation under Requirements.
- Qualifications (h3) containing required qualifications (citizenship, age, enrollment, freshman year, etc) plus preferred degree fields? Might be better to put preferred degree under Qualifications as well (they are qualifications). But we already have Required Qualifications heading; we could keep all qualifications under Qualifications.
- Skills (h3) containing soft skills list.
- Schedule (h3) containing 40 hrs/week, 8 weeks, May-Sept 2027.
We must not repeat job title. No extra headings.
We must preserve all substantive info. Ensure we don't lose any details.
Let's extract each piece.
Intro paragraph: includes mission-critical work, etc. That could go under About the role? Actually About the role should contain description of the team/mission. The intro includes general company description; maybe we can include that in About the role as well. But we already have About D201 – Process Improvement Engineering which is more specific. We'll combine both: About the role includes the intro paragraph plus the About D201 mission.
Thus About the role content:
- General Dynamics Electric Boat provides an unparalleled learning experience for college students, offering practical exposure in the defense industry alongside expert engineers, shaping the future of submarine innovation. General Dynamics Electric Boat is one of the only two shipyards that produce submarines for the US Navy and there’s never been a better time to join. The US Navy has a demand for cutting-edge naval capability and technology never seen before, and Electric Boat is the vanguard—designing, building, and maintaining the most advanced submarines in the world. Our work is mission-critical work in supporting the U.S. Navy and strengthening national security. This program requires a minimum commitment of 8 weeks during the Summer 2027 Season. Participation in this program requires medical screening, passing a drug test and background check. This is not a remote opportunity. This position is located at the Groton, CT location and you will need reliable transportation and housing for the duration of your intern assignment.
- About D201 – Process Improvement Engineering: Our mission is to enable the success of the shipbuilders of Groton Shipyard to be safe and successful as they build and test the most advanced vessels in the US Navy. You will use techniques and strategies from Lean, Six Sigma, Continuous Improvement, Theory of Constraints, team facilitated problem solving, and culture transformation to create breakthrough improvements in span times, quality, and performance. This team guides organizations in developing and implementing improvement strategies and creating tangible & significant improvements.
We need to ensure we don't duplicate location/housing/transportation if we also put them under Requirements. But we can keep them in About the role; it's okay to have some overlap? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid duplication. However we could keep location/housing/transportation under Requirements and not repeat in About the role. But the intro includes that info; we could move it to Requirements and keep About the role focused on mission/team. Let's do that.
Thus About the role content: company description, mission-critical work, program commitment 8 weeks Summer 2027, medical screening, drug test, background check, not remote. Plus About D201 – Process Improvement Engineering mission.
We'll keep location/housing/transportation under Requirements.
Now Responsibilities: role overview paragraph.
Now Requirements: location Groton, CT; need reliable transportation and housing for duration; maybe also mention that it's not remote (but that's covered). Also mention minimum commitment 8 weeks? Actually that's schedule. We'll put schedule separate. So Requirements: location, transportation, housing.
Also maybe mention that participation requires medical screening, passing drug test and background check? That could be under Requirements as well (pre-employment checks). But we already have that in About the role; we could move to Requirements to avoid duplication. Let's decide: Keep medical screening, drug test, background check under Requirements (makes sense). Then About the role will not include those.
Thus About the role: company description,