Structural Engineering (Substation) Intern - Summer 2027
for each section. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Must not put Job ID etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, the "Notice To Third Party Agencies", the "About WSP" section maybe? The "About WSP" includes description of company; is that substantive? It might be considered boilerplate but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About WSP" is not explicitly listed as boilerplate to remove, but it's generic company description. However we need to preserve ALL substantive information; does the company description count as substantive? It might be considered not directly about the role but still part of posting. The instruction says "Prefer a few substantive sections over many thin ones." It might be okay to include an "About WSP" section? But the allowed headings are limited to those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like "About WSP". So we must incorporate that info into existing sections if relevant, or drop it if not fitting. The "About WSP" includes description of WSP USA, its services, employee count, etc. That may be considered not directly about the role but could be placed under "About the role" maybe as context. However the instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview under About the role.
We also need to include "Developing Professionals Network" etc under Benefits.
We need to include "Please note that there is no relocation or housing assistance associated with this internship." That could be under Benefits (or maybe under About the role). Since it's a limitation, maybe under Benefits as a note.
We need to include "WSP brings global expertise in power delivery, power generation, and program management—anchored by the acquisition of POWER Engineers, Inc. TRC Companies have now joined WSP, deepening our power practice and expanding our energy advisory and intelligent grid services. We're partnering with clients to shape how energy systems evolve around the world—and we need your help." That's also company info; could be under About the role.
We need to include "As a summer intern, you have the opportunity to participate in our 12-week program scheduled to start on May 17th, 2027. The individual start date of the internship may be flexible." That's schedule.
Now we need to decide what goes into each section.
Let's extract:
About the role: Should include description of internship, location, program, start date, maybe company context. The posting: "This Opportunity WSP USA hosts hundreds of internships across the United States to gain hands-on, meaningful work experience to enhance their education and professional aptitude. Our interns gain exposure to real projects while working side by side with senior staff. Through our Developing Professionals Network, interns gain mentorship, networking opportunities and lifelong career connections. Our Power and Energy Team is seeking a Full-Time Structural Engineering (Substation) Intern to work out of our Freeport, ME office. The following locations will also be considered: Hallowell, ME; Syracuse, NY; Ann Arbor, MI; and New York, NY. This temporary position is seeking individuals currently enrolled in an Undergraduate or Graduate degree program. This internship will be part of the WSP Summer Internship Program. As a summer intern, you have the opportunity to participate in our 12-week program scheduled to start on May 17th, 2027. The individual start date of the internship may be flexible. WSP brings global expertise in power delivery, power generation, and program management—anchored by the acquisition of POWER Engineers, Inc. TRC Companies have now joined WSP, deepening our power practice and expanding our energy advisory and intelligent grid services. We're partnering with clients to shape how energy systems evolve around the world—and we need your help."
We can put that in About the role.
Responsibilities: list of tasks as bullet points.
Requirements: Required Qualifications bullet list.
Qualifications: Preferred Qualifications bullet list.
Skills: Could combine some of the required qualifications that are skills: "Competent interpersonal and communication skills", "Basic proficiency with technical writing, office automation, software, spreadsheets, technology, and tools." Also maybe "Capable of taking direction from leadership, mentors, and managers to executive projects." But that's more ability. We could put skills under Skills section. However we already have Required Qualifications covering many of those. To avoid duplication, we could put skills separate but ensure we don't duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we split content across sections, we must ensure we don't lose any info. It's okay to have overlapping? Probably better to keep each piece in one section. Let's decide:
- About the role: narrative description.
- Responsibilities: bullet list of duties.
- Requirements: bullet list of required qualifications (including enrollment, age, interest, communication skills, direction taking, technical proficiency, safety, work authorization).
- Qualifications: bullet list of preferred qualifications (software experience, Mathcad, prior internship/leadership).
- Skills: maybe we could omit if covered. But the instruction says include a section ONLY when the posting has real, specific content for it. If we already covered skills under Requirements, we could still have a Skills section but would duplicate. Better to omit Skills if no distinct content beyond what's already in Requirements. However the posting does mention "Competent interpersonal and communication skills" and "Basic proficiency with technical writing, office automation, software, spreadsheets, technology, and tools." Those are skills. They are already in Requirements. So we could keep them there and not have a separate Skills section. That would satisfy "Prefer a few substantive sections over many thin ones." So we can omit Skills.
- Benefits: bullet list: mentorship, networking opportunities, lifelong career connections (via Developing Professionals Network). Also note no relocation or housing assistance. Also maybe "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings..." but that's for employees, not necessarily interns. Might be considered generic; but it's still substantive about benefits offered by WSP. However the internship may not be eligible. The posting says "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits..." This is under "About WSP" after the responsibilities. It's not explicitly about interns but could be considered general benefits. To be safe, we could include it under Benefits as it's substantive about WSP benefits. However the instruction says remove boilerplate; this might be considered boilerplate generic benefits description. But it's still specific: medical, dental, vision, disability, life, retirement savings. It's not obviously boilerplate; it's a description of benefits. I'd include it.
- Pay: bullet or prose: "$22.17 - $32.22 per hour". Also note that it's a range based on factors.
- Schedule: bullet or prose: "12-week program scheduled to start on May 17th, 2027. Individual start date may be flexible."
Now we need to output HTML fragment with
headings and appropriate - or
.
We must not include any markdown code fences.
Let's
for prose. We must not repeat job title as heading. Must not put Job ID etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, the "Notice To Third Party Agencies", the "About WSP" section maybe? The "About WSP" includes description of company; is that substantive? It might be considered boilerplate but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About WSP" is not explicitly listed as boilerplate to remove, but it's generic company description. However we need to preserve ALL substantive information; does the company description count as substantive? It might be considered not directly about the role but still part of posting. The instruction says "Prefer a few substantive sections over many thin ones." It might be okay to include an "About WSP" section? But the allowed headings are limited to those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like "About WSP". So we must incorporate that info into existing sections if relevant, or drop it if not fitting. The "About WSP" includes description of WSP USA, its services, employee count, etc. That may be considered not directly about the role but could be placed under "About the role" maybe as context. However the instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview under About the role. We also need to include "Developing Professionals Network" etc under Benefits. We need to include "Please note that there is no relocation or housing assistance associated with this internship." That could be under Benefits (or maybe under About the role). Since it's a limitation, maybe under Benefits as a note. We need to include "WSP brings global expertise in power delivery, power generation, and program management—anchored by the acquisition of POWER Engineers, Inc. TRC Companies have now joined WSP, deepening our power practice and expanding our energy advisory and intelligent grid services. We're partnering with clients to shape how energy systems evolve around the world—and we need your help." That's also company info; could be under About the role. We need to include "As a summer intern, you have the opportunity to participate in our 12-week program scheduled to start on May 17th, 2027. The individual start date of the internship may be flexible." That's schedule. Now we need to decide what goes into each section. Let's extract: About the role: Should include description of internship, location, program, start date, maybe company context. The posting: "This Opportunity WSP USA hosts hundreds of internships across the United States to gain hands-on, meaningful work experience to enhance their education and professional aptitude. Our interns gain exposure to real projects while working side by side with senior staff. Through our Developing Professionals Network, interns gain mentorship, networking opportunities and lifelong career connections. Our Power and Energy Team is seeking a Full-Time Structural Engineering (Substation) Intern to work out of our Freeport, ME office. The following locations will also be considered: Hallowell, ME; Syracuse, NY; Ann Arbor, MI; and New York, NY. This temporary position is seeking individuals currently enrolled in an Undergraduate or Graduate degree program. This internship will be part of the WSP Summer Internship Program. As a summer intern, you have the opportunity to participate in our 12-week program scheduled to start on May 17th, 2027. The individual start date of the internship may be flexible. WSP brings global expertise in power delivery, power generation, and program management—anchored by the acquisition of POWER Engineers, Inc. TRC Companies have now joined WSP, deepening our power practice and expanding our energy advisory and intelligent grid services. We're partnering with clients to shape how energy systems evolve around the world—and we need your help." We can put that in About the role. Responsibilities: list of tasks as bullet points. Requirements: Required Qualifications bullet list. Qualifications: Preferred Qualifications bullet list. Skills: Could combine some of the required qualifications that are skills: "Competent interpersonal and communication skills", "Basic proficiency with technical writing, office automation, software, spreadsheets, technology, and tools." Also maybe "Capable of taking direction from leadership, mentors, and managers to executive projects." But that's more ability. We could put skills under Skills section. However we already have Required Qualifications covering many of those. To avoid duplication, we could put skills separate but ensure we don't duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we split content across sections, we must ensure we don't lose any info. It's okay to have overlapping? Probably better to keep each piece in one section. Let's decide: - About the role: narrative description. - Responsibilities: bullet list of duties. - Requirements: bullet list of required qualifications (including enrollment, age, interest, communication skills, direction taking, technical proficiency, safety, work authorization). - Qualifications: bullet list of preferred qualifications (software experience, Mathcad, prior internship/leadership). - Skills: maybe we could omit if covered. But the instruction says include a section ONLY when the posting has real, specific content for it. If we already covered skills under Requirements, we could still have a Skills section but would duplicate. Better to omit Skills if no distinct content beyond what's already in Requirements. However the posting does mention "Competent interpersonal and communication skills" and "Basic proficiency with technical writing, office automation, software, spreadsheets, technology, and tools." Those are skills. They are already in Requirements. So we could keep them there and not have a separate Skills section. That would satisfy "Prefer a few substantive sections over many thin ones." So we can omit Skills. - Benefits: bullet list: mentorship, networking opportunities, lifelong career connections (via Developing Professionals Network). Also note no relocation or housing assistance. Also maybe "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings..." but that's for employees, not necessarily interns. Might be considered generic; but it's still substantive about benefits offered by WSP. However the internship may not be eligible. The posting says "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits..." This is under "About WSP" after the responsibilities. It's not explicitly about interns but could be considered general benefits. To be safe, we could include it under Benefits as it's substantive about WSP benefits. However the instruction says remove boilerplate; this might be considered boilerplate generic benefits description. But it's still specific: medical, dental, vision, disability, life, retirement savings. It's not obviously boilerplate; it's a description of benefits. I'd include it. - Pay: bullet or prose: "$22.17 - $32.22 per hour". Also note that it's a range based on factors. - Schedule: bullet or prose: "12-week program scheduled to start on May 17th, 2027. Individual start date may be flexible." Now we need to output HTML fragment with
headings and appropriate - or
.
We must not include any markdown code fences.
Let's
. We must not include any markdown code fences. Let's