Construction Project Engineer Intern
McKinstry · Seattle, WA · 4 wk ago
Administrative$24/hrFull-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 specific content. Remove boilerplate, EEO, etc. Must preserve all substantive info.
Let's parse the posting:
- Intro: "Thank you for your interest in interning with McKinstry! We are proud and excited to offer summer internships for 2027 across several of our different office locations and are currently seeking a Construction Project Engineer Intern to join our construction team in Seattle, WA. McKinstry is innovating the waste and climate harm out of the built environment and creating lasting impact. Together, we’re building a thriving planet. Buildings are a leading contributor to the climate crisis, generating nearly 40% of total global energy-related carbon emissions. We’re making a lasting impact on our industry and within our communities by addressing the climate, affordability and equity crises through: renewables and energy services engineering and design construction and facility services To get where we’re going, we need big thinkers, problem solvers and collaborative mindsets. Does that sound like you? Our B.L.U.E. (Build, Learn, Understand, Enrich) Summer Internship Program is purposefully designed to inspire your imagination and help you guide your career with purpose. You’ll be an integral part of McKinstry with hands-on experience, mentorship and a healthy dose of fun. Our program delivers depth and real experience so that you can truly evaluate potential career paths within the work we do."
That's about the role / program description. Could be "About the role" or maybe "About the internship". We'll use "About the role".
- "What we look for in our Construction Project Engineer Interns:" then bullet list of requirements/qualifications.
List:
- Must be pursuing or have a degree in Construction Management, Mechanical Engineering, or a related field.
- Sophomore student standing or higher required.
- Availability in Summer 2027 (May/June start until August/September depending on school); part-time availability after Summer preferred
- Excellent written and verbal communication skills.
- Must be detail-oriented, well organized, and possess excellent follow-up skills.
- Must be self–motivated, able to multi‐task, and work independently.
- Ability to read and interpret construction plans, specs, contracts, proposals, estimates, and other regularly encountered items.
- Intermediate knowledge of Microsoft Office Suite - Word, Excel, PowerPoint, Outlook, and Visio required; working knowledge of SharePoint and MS Project preferred.
- Must be 18 years of age or older
These are qualifications/requirements. Could split into "Requirements" and "Qualifications" but we can combine. The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content fits which.
We have:
- Requirements: maybe eligibility: pursuing degree, sophomore standing, availability, 18+.
- Qualifications: maybe degree, etc. But we can just put all under "Requirements" or "Qualifications". Better to separate: "Requirements" for eligibility (standing, availability, age). "Qualifications" for degree, skills. "Skills" for technical abilities (Microsoft Office, reading plans, etc). But we need to avoid thin sections.
Let's see content:
- Must be pursuing or have a degree in Construction Management, Mechanical Engineering, or a related field. (Qualification)
- Sophomore student standing or higher required. (Requirement)
- Availability in Summer 2027 (May/June start until August/September depending on school); part-time availability after Summer preferred (Requirement/Schedule? Actually schedule info)
- Excellent written and verbal communication skills. (Skill)
- Must be detail-oriented, well organized, and possess excellent follow-up skills. (Skill)
- Must be self–motivated, able to multi‐task, and work independently. (Skill)
- Ability to read and interpret construction plans, specs, contracts, proposals, estimates, and other regularly encountered items. (Skill)
- Intermediate knowledge of Microsoft Office Suite - Word, Excel, PowerPoint, Outlook, and Visio required; working knowledge of SharePoint and MS Project preferred. (Skill)
- Must be 18 years of age or older. (Requirement)
Then responsibilities list:
"What are our Construction Project Engineer Interns responsible for:" then bullet list:
- Communicating with clients and project resources (subcontractors, vendors, trades) and document discussions, outcomes and decisions.
- Coordinating equipment procurement with the purchasing department and vendors.
- Supporting the Request for Proposal (RFP) process.
- Working with various internal and external teams while on jobsite.
- Attending team management meetings.
- Communicating and coordinating with McKinstry subcontractors, including the routing of any correspondence.
- Communicating with Project Manager and Project team for daily duties.
- Maintaining drawings, daily correspondence with trades, schedules, RFI logs, submittal logs, and superintendent daily reports.
- Assisting in the client and subcontractor change order process.
- Creating Requests for Information (RFI)
- Processing, reviewing, logging, and distributing submittals.
- Publishing Operations and Maintenance Manuals for the client.
- Other duties as assigned
That's responsibilities.
Pay: "The hourly rate for this role is $24/hr."
Schedule: Not explicitly given besides availability summer 2027 May/June start until August/September depending on school; part-time after Summer preferred. That's schedule info. Could be placed under Schedule section.
Benefits: Not mentioned besides maybe mentorship, hands-on experience, fun, etc. But those are program description. Could be considered benefits? The instruction says only include Benefits section if posting actually states them. It does mention "hands-on experience, mentorship and a healthy dose of fun." That's a benefit. Also "Our program delivers depth and real experience". Might be considered benefits. However, we need to see if we should create a Benefits section. The posting does not list typical benefits like health insurance, etc. But it does mention experiential benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state some benefits (hands-on experience, mentorship, fun). So we could include a Benefits section with those points.
But we need to avoid filler like "commensurate with experience". Not present.
Thus sections:
- About the role (intro paragraph)
- Responsibilities (list)
- Requirements (maybe eligibility: sophomore standing, availability, age, 18+)
- Qualifications (degree pursuit)
- Skills (communication, detail-oriented, self-motivated, ability to read plans, MS Office, SharePoint/MS Project)
- Pay (hourly rate $24/hr)
- Schedule (availability summer 2027 May/June start until Aug/Sept depending on school; part-time after Summer preferred)
- Benefits (hands-on experience, mentorship, healthy dose of fun, depth and real experience, evaluate career paths)
But we need to avoid too many thin sections. Could combine Requirements and Qualifications into one "Requirements" section, and Skills into another. However the instruction says prefer a few substantive sections over many thin ones. So we could have:
- About the role
- Responsibilities
- Requirements & Qualifications (combined)
- Skills
- Pay
- Schedule
- Benefits
That's 7 sections.
But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. If we combine, we might violate using those headings? The instruction: "use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, EEO, etc. Must preserve all substantive info.
Let's parse the posting:
- Intro: "Thank you for your interest in interning with McKinstry! We are proud and excited to offer summer internships for 2027 across several of our different office locations and are currently seeking a Construction Project Engineer Intern to join our construction team in Seattle, WA. McKinstry is innovating the waste and climate harm out of the built environment and creating lasting impact. Together, we’re building a thriving planet. Buildings are a leading contributor to the climate crisis, generating nearly 40% of total global energy-related carbon emissions. We’re making a lasting impact on our industry and within our communities by addressing the climate, affordability and equity crises through: renewables and energy services engineering and design construction and facility services To get where we’re going, we need big thinkers, problem solvers and collaborative mindsets. Does that sound like you? Our B.L.U.E. (Build, Learn, Understand, Enrich) Summer Internship Program is purposefully designed to inspire your imagination and help you guide your career with purpose. You’ll be an integral part of McKinstry with hands-on experience, mentorship and a healthy dose of fun. Our program delivers depth and real experience so that you can truly evaluate potential career paths within the work we do."
That's about the role / program description. Could be "About the role" or maybe "About the internship". We'll use "About the role".
- "What we look for in our Construction Project Engineer Interns:" then bullet list of requirements/qualifications.
List:
- Must be pursuing or have a degree in Construction Management, Mechanical Engineering, or a related field.
- Sophomore student standing or higher required.
- Availability in Summer 2027 (May/June start until August/September depending on school); part-time availability after Summer preferred
- Excellent written and verbal communication skills.
- Must be detail-oriented, well organized, and possess excellent follow-up skills.
- Must be self–motivated, able to multi‐task, and work independently.
- Ability to read and interpret construction plans, specs, contracts, proposals, estimates, and other regularly encountered items.
- Intermediate knowledge of Microsoft Office Suite - Word, Excel, PowerPoint, Outlook, and Visio required; working knowledge of SharePoint and MS Project preferred.
- Must be 18 years of age or older
These are qualifications/requirements. Could split into "Requirements" and "Qualifications" but we can combine. The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content fits which.
We have:
- Requirements: maybe eligibility: pursuing degree, sophomore standing, availability, 18+.
- Qualifications: maybe degree, etc. But we can just put all under "Requirements" or "Qualifications". Better to separate: "Requirements" for eligibility (standing, availability, age). "Qualifications" for degree, skills. "Skills" for technical abilities (Microsoft Office, reading plans, etc). But we need to avoid thin sections.
Let's see content:
- Must be pursuing or have a degree in Construction Management, Mechanical Engineering, or a related field. (Qualification)
- Sophomore student standing or higher required. (Requirement)
- Availability in Summer 2027 (May/June start until August/September depending on school); part-time availability after Summer preferred (Requirement/Schedule? Actually schedule info)
- Excellent written and verbal communication skills. (Skill)
- Must be detail-oriented, well organized, and possess excellent follow-up skills. (Skill)
- Must be self–motivated, able to multi‐task, and work independently. (Skill)
- Ability to read and interpret construction plans, specs, contracts, proposals, estimates, and other regularly encountered items. (Skill)
- Intermediate knowledge of Microsoft Office Suite - Word, Excel, PowerPoint, Outlook, and Visio required; working knowledge of SharePoint and MS Project preferred. (Skill)
- Must be 18 years of age or older. (Requirement)
Then responsibilities list:
"What are our Construction Project Engineer Interns responsible for:" then bullet list:
- Communicating with clients and project resources (subcontractors, vendors, trades) and document discussions, outcomes and decisions.
- Coordinating equipment procurement with the purchasing department and vendors.
- Supporting the Request for Proposal (RFP) process.
- Working with various internal and external teams while on jobsite.
- Attending team management meetings.
- Communicating and coordinating with McKinstry subcontractors, including the routing of any correspondence.
- Communicating with Project Manager and Project team for daily duties.
- Maintaining drawings, daily correspondence with trades, schedules, RFI logs, submittal logs, and superintendent daily reports.
- Assisting in the client and subcontractor change order process.
- Creating Requests for Information (RFI)
- Processing, reviewing, logging, and distributing submittals.
- Publishing Operations and Maintenance Manuals for the client.
- Other duties as assigned
That's responsibilities.
Pay: "The hourly rate for this role is $24/hr."
Schedule: Not explicitly given besides availability summer 2027 May/June start until August/September depending on school; part-time after Summer preferred. That's schedule info. Could be placed under Schedule section.
Benefits: Not mentioned besides maybe mentorship, hands-on experience, fun, etc. But those are program description. Could be considered benefits? The instruction says only include Benefits section if posting actually states them. It does mention "hands-on experience, mentorship and a healthy dose of fun." That's a benefit. Also "Our program delivers depth and real experience". Might be considered benefits. However, we need to see if we should create a Benefits section. The posting does not list typical benefits like health insurance, etc. But it does mention experiential benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state some benefits (hands-on experience, mentorship, fun). So we could include a Benefits section with those points.
But we need to avoid filler like "commensurate with experience". Not present.
Thus sections:
- About the role (intro paragraph)
- Responsibilities (list)
- Requirements (maybe eligibility: sophomore standing, availability, age, 18+)
- Qualifications (degree pursuit)
- Skills (communication, detail-oriented, self-motivated, ability to read plans, MS Office, SharePoint/MS Project)
- Pay (hourly rate $24/hr)
- Schedule (availability summer 2027 May/June start until Aug/Sept depending on school; part-time after Summer preferred)
- Benefits (hands-on experience, mentorship, healthy dose of fun, depth and real experience, evaluate career paths)
But we need to avoid too many thin sections. Could combine Requirements and Qualifications into one "Requirements" section, and Skills into another. However the instruction says prefer a few substantive sections over many thin ones. So we could have:
- About the role
- Responsibilities
- Requirements & Qualifications (combined)
- Skills
- Pay
- Schedule
- Benefits
That's 7 sections.
But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. If we combine, we might violate using those headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings when appropriate. It doesn't forbid combining, but we should use headings only when we have content for them. If we combine Requirements and Qualifications, we could still have both headings but each with content; but that would be thin maybe. Better to have separate headings if we have distinct content.
We have content for Requirements (sophomore standing, availability, age). Qualifications (degree). Skills (various). So we can have three separate sections.
Thus final HTML:
About the role
About the role
... intro paragraph ...
Responsibilities
- ... ...
Requirements
- Sophomore student standing or higher required.
- Availability in Summer 2027 (May/June start until August/September depending on school); part-time availability after Summer preferred
- Must be 18 years of age or older
Qualifications
- Must be pursuing or have a degree in Construction Management, Mechanical Engineering, or a related field.
Skills
- Excellent written and verbal communication skills.
- Must be detail-oriented, well organized, and possess excellent follow-up skills.
- Must be self–motivated, able to multi‐task, and work independently.
- Ability to read and interpret construction plans, specs, contracts, proposals, estimates, and other regularly encountered items.
- Intermediate knowledge of Microsoft Office Suite - Word, Excel, PowerPoint, Outlook, and Visio required; working knowledge of SharePoint and MS Project preferred.
Pay
The hourly rate for this role is $24/hr.
Schedule
Availability in Summer 2027 (May/June start until August/September depending on school); part-time availability after Summer preferred.
Benefits
- Hands‑on experience
- Mentorship
- Healthy dose of fun
- Program delivers depth and real experience to evaluate potential career paths within the work we do