2027 Summer PE- Intern
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So no heading for "Project Engineer Intern". Use sections as above.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are substantive, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO statements, privacy policy, search firm disclaimer, etc. Also remove repeated lines like "Skanska Equal Employment Opportunity", etc. Also remove background check required? That's substantive? It's a requirement maybe. It says "Background Check Required". That's a condition; we could include under Requirements or maybe as a note. It's substantive; we should keep it. But it's not a boilerplate; it's a condition. We'll keep it.
Also remove duplicated lines: there may be repeated sentences about values etc. We'll deduplicate.
Now craft sections.
About the role: combine intro paragraphs about Skanska, mission, values, location, diversity, etc. We'll produce a
with that content.
Responsibilities: list duties.
- Assist and support Project Manager and Superintendent on assigned projects.
- Work under direct supervision with mentorship.
- Perform routine daily activities.
- Gather and distribute information.
- Gain experience coordinating project activities with direct supervision from Project and/or Operations Manager.
- Perform accounting activities with assistance.
- Perform estimating functions as requested with assistance.
- Other duties as assigned.
- Positions include Engineering, Field Engineering (mechanical or civil), Cost Engineering, Safety Engineering, Estimating, Finance/Accounting, and Equipment/Maintenance. (maybe this is more about role types; could be under Responsibilities or About the role. We'll include under Responsibilities as bullet.)
Requirements: maybe the "Required Qualifications" list.
- Knowledge of basic phases of construction projects.
- Knowledge of mathematics functions (geometry, basic algebra).
- Computer skills (MS Office, HCSS, CGC, etc).
- Ability to perform all work in a timely, professional, and efficient manner while effectively communicating and interacting with customers, clients, subcontractors, and other third parties.
- Ability to present information in a clear and understandable manner in both written and verbal form.
- Background check required.
Qualifications: education requirement.
- Working towards a bachelor's in Construction Management, Engineering, Mechanical Engineering, Civil Engineering, or related field or equivalent through experience.
Skills: maybe overlapping with required qualifications; but we can separate: knowledge of basic phases, math functions, computer skills, communication, presentation. However those are already in Required Qualifications. To avoid duplication, we could treat Required Qualifications as Skills, and Qualifications as education. But the instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide what goes where without duplicating content. We could put:
- Requirements: the list of abilities (knowledge, computer skills, communication, presentation, background check).
- Qualifications: education requirement.
- Skills: maybe the specific technical skills: knowledge of basic phases, math functions, computer skills (MS Office, HCSS, CGC). But that duplicates with Requirements. Better to follow typical pattern: Requirements = mandatory qualifications; Qualifications = preferred or education; Skills = specific abilities. However we must not invent or summarize away detail; we must preserve all substantive info. If we split, we need to ensure we don't lose any info and not duplicate. We could combine Requirements and Qualifications into one section, but the instruction says we can have multiple sections; we just need to not create empty sections. It's okay to have overlapping content? Might be considered duplication but not necessarily prohibited. However better to avoid duplication.
Let's think: The posting has "Project Engineering Intern Required Qualifications:" followed by a list. Then later "Working towards a bachelor's..." is part of that list (the last item). So the list includes education as part of required qualifications. So we can treat the whole list as Required Qualifications. Then we could have a separate Skills section for maybe "knowledge of basic phases, math functions, computer skills" but that's already in the list. Could instead have Skills as the same list but that duplicates.
Maybe we can interpret:
- Requirements: the list of abilities (knowledge, computer skills, communication, presentation, background check).
- Qualifications: education requirement (working towards bachelor's).
- Skills: maybe the specific technical skills: knowledge of basic phases, math functions, computer skills (MS Office, HCSS, CGC). But that duplicates with Requirements partially.
Alternatively, we could combine Requirements and Qualifications into one section called "Requirements" and omit Qualifications and Skills sections if they'd be thin. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. That seems good. We'll omit Qualifications and Skills as separate sections to avoid thin duplication.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
Check if we have content for each:
- About the role: yes.
- Responsibilities: yes.
- Requirements: includes the list of required qualifications (knowledge, math, computer skills, communication, presentation, background check). Also maybe include the various position types? That could be under Responsibilities.
- Benefits: includes medical, dental, vision insurance, 401k, bonus program, employee ownership program, expert guidance, always-on tools, etc.
- Pay: hourly pay range $20/hr to $25/hr.
We should also include location: Texas Regions: San Antonio, Houston, and Dallas. That could be in About the role.
Now we need to format.
We must not include any markdown code fences. Just raw HTML.
Let's craft.
About the role
About the role
then ...
Responsibilities Responsibilities
then - ...
Requirements Requirements
then - ...
Benefits Benefits
then - ...
(or for prose? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So benefits is a list, we can use
- .
Pay
Pay
then ...
Now ensure we preserve all substantive info.
Let's extract exact phrasing.
About the role: We need to include:
- Skanska is searching for a dynamic Project Engineer Intern to join our Texas Regions: San Antonio, Houston, and Dallas.
- This is a great opportunity to start a career with a company that builds things that matter and values its team.
- We are proud to share our culture of diversity and inclusion.
- Our work makes a clear contribution to society and the environment around us.
- We build in many different verticals. Whether we are building schools to provide inspiring spaces for learning, roads to connect communities, or hospitals to care for patients, it all contributes to our purpose – we build for a better society.
- Skanska's values —Be Better Together, Act Ethically and Transparently, Commit to Customer, and Care for Life—are deeply engrained in how we work, which is why our values support and drive our D&I efforts.
We could combine into a paragraph.
Responsibilities: list:
- Assist and support Project Manager and Superintendent on assigned projects.
- Work under direct supervision with mentorship.
- Perform routine daily activities.
- Gather
for prose. We must not repeat job title as heading. So no heading for "Project Engineer Intern". Use sections as above. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are substantive, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO statements, privacy policy, search firm disclaimer, etc. Also remove repeated lines like "Skanska Equal Employment Opportunity", etc. Also remove background check required? That's substantive? It's a requirement maybe. It says "Background Check Required". That's a condition; we could include under Requirements or maybe as a note. It's substantive; we should keep it. But it's not a boilerplate; it's a condition. We'll keep it. Also remove duplicated lines: there may be repeated sentences about values etc. We'll deduplicate. Now craft sections. About the role: combine intro paragraphs about Skanska, mission, values, location, diversity, etc. We'll produce a
with that content. Responsibilities: list duties. - Assist and support Project Manager and Superintendent on assigned projects. - Work under direct supervision with mentorship. - Perform routine daily activities. - Gather and distribute information. - Gain experience coordinating project activities with direct supervision from Project and/or Operations Manager. - Perform accounting activities with assistance. - Perform estimating functions as requested with assistance. - Other duties as assigned. - Positions include Engineering, Field Engineering (mechanical or civil), Cost Engineering, Safety Engineering, Estimating, Finance/Accounting, and Equipment/Maintenance. (maybe this is more about role types; could be under Responsibilities or About the role. We'll include under Responsibilities as bullet.) Requirements: maybe the "Required Qualifications" list. - Knowledge of basic phases of construction projects. - Knowledge of mathematics functions (geometry, basic algebra). - Computer skills (MS Office, HCSS, CGC, etc). - Ability to perform all work in a timely, professional, and efficient manner while effectively communicating and interacting with customers, clients, subcontractors, and other third parties. - Ability to present information in a clear and understandable manner in both written and verbal form. - Background check required. Qualifications: education requirement. - Working towards a bachelor's in Construction Management, Engineering, Mechanical Engineering, Civil Engineering, or related field or equivalent through experience. Skills: maybe overlapping with required qualifications; but we can separate: knowledge of basic phases, math functions, computer skills, communication, presentation. However those are already in Required Qualifications. To avoid duplication, we could treat Required Qualifications as Skills, and Qualifications as education. But the instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide what goes where without duplicating content. We could put: - Requirements: the list of abilities (knowledge, computer skills, communication, presentation, background check). - Qualifications: education requirement. - Skills: maybe the specific technical skills: knowledge of basic phases, math functions, computer skills (MS Office, HCSS, CGC). But that duplicates with Requirements. Better to follow typical pattern: Requirements = mandatory qualifications; Qualifications = preferred or education; Skills = specific abilities. However we must not invent or summarize away detail; we must preserve all substantive info. If we split, we need to ensure we don't lose any info and not duplicate. We could combine Requirements and Qualifications into one section, but the instruction says we can have multiple sections; we just need to not create empty sections. It's okay to have overlapping content? Might be considered duplication but not necessarily prohibited. However better to avoid duplication. Let's think: The posting has "Project Engineering Intern Required Qualifications:" followed by a list. Then later "Working towards a bachelor's..." is part of that list (the last item). So the list includes education as part of required qualifications. So we can treat the whole list as Required Qualifications. Then we could have a separate Skills section for maybe "knowledge of basic phases, math functions, computer skills" but that's already in the list. Could instead have Skills as the same list but that duplicates. Maybe we can interpret: - Requirements: the list of abilities (knowledge, computer skills, communication, presentation, background check). - Qualifications: education requirement (working towards bachelor's). - Skills: maybe the specific technical skills: knowledge of basic phases, math functions, computer skills (MS Office, HCSS, CGC). But that duplicates with Requirements partially. Alternatively, we could combine Requirements and Qualifications into one section called "Requirements" and omit Qualifications and Skills sections if they'd be thin. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. That seems good. We'll omit Qualifications and Skills as separate sections to avoid thin duplication. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check if we have content for each: - About the role: yes. - Responsibilities: yes. - Requirements: includes the list of required qualifications (knowledge, math, computer skills, communication, presentation, background check). Also maybe include the various position types? That could be under Responsibilities. - Benefits: includes medical, dental, vision insurance, 401k, bonus program, employee ownership program, expert guidance, always-on tools, etc. - Pay: hourly pay range $20/hr to $25/hr. We should also include location: Texas Regions: San Antonio, Houston, and Dallas. That could be in About the role. Now we need to format. We must not include any markdown code fences. Just raw HTML. Let's craft. About the role
About the role
then...
ResponsibilitiesResponsibilities
then- ...
Requirements
then- ...
Benefits
then- ...
for prose? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So benefits is a list, we can use
- .
Pay
Pay
then...
Now ensure we preserve all substantive info. Let's extract exact phrasing. About the role: We need to include: - Skanska is searching for a dynamic Project Engineer Intern to join our Texas Regions: San Antonio, Houston, and Dallas. - This is a great opportunity to start a career with a company that builds things that matter and values its team. - We are proud to share our culture of diversity and inclusion. - Our work makes a clear contribution to society and the environment around us. - We build in many different verticals. Whether we are building schools to provide inspiring spaces for learning, roads to connect communities, or hospitals to care for patients, it all contributes to our purpose – we build for a better society. - Skanska's values —Be Better Together, Act Ethically and Transparently, Commit to Customer, and Care for Life—are deeply engrained in how we work, which is why our values support and drive our D&I efforts. We could combine into a paragraph. Responsibilities: list: - Assist and support Project Manager and Superintendent on assigned projects. - Work under direct supervision with mentorship. - Perform routine daily activities. - Gather
- .
Pay