Senior Project Engineer - Data Center Construction
McKinstry · Dallas, TX · 3 wk ago
Administrative$36.48–$61.97/hrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions.
We need to parse the posting.
Let's extract content:
Intro paragraph: "Build the future, spark innovation and align your career with purpose. 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? The Opportunity with McKinstry McKinstry is looking for a Senior Project Engineer - Data Center Construction to join our Data Center Innovations division in Dallas, TX. This role is responsible for overseeing the delivery of complex projects, with responsibility for fiscal outcomes, technical quality, and stakeholder coordination from initiation through closeout."
That's about the role. Could be "About the role" section.
Then "Additional responsibilities may include:" then bullet list items under Project Coordination, Documentation, Safety.
We need to list responsibilities as
- . Should we separate categories? Probably just list each bullet as li.
Let's extract each bullet:
Project Coordination:
- Serve as the on-site point of contact for clients, subcontractors, vendors, and field personnel as needed.
- Support Request for Proposal (RFP) processes.
- Coordinate equipment procurement with the purchasing department and outside vendors to order and expedite material.
- Assist in the development of scope of work for subcontractors.
- Oversee the scheduling and coordination of trades.
- Assist with project controls, including reviewing and substantiating subcontractor billings, drafting subcontract and purchasing agreements, assisting with client billings, and assuming responsibility for project fiscal performance with oversight of the Project Manager.
- Assist in preparation of monthly project accounting review.
- Manage and ensure accuracy of cost issue logs.
Documentation:
- Maintain drawings, daily correspondence with trades, schedules, RFI logs, submittal logs, and Superintendent daily reports.
- Create and respond to Requests for Information (RFI).
- Create site-specific work plans.
- Process, review, log, and distribute submittals.
- Create and publish Operations and Maintenance Manuals for clients.
- Obtain detailed knowledge of contract, drawings, and specifications for assigned projects.
- Maintain cost issue logs.
Safety:
- Assess site safety and implement actions to prevent injury to property and personnel.
- Uphold and communicate McKinstry safety standards.
- Coordinate with the Safety Team to create and communicate site safety plans.
- Perform other duties as assigned.
Now "What You Need To Succeed at McKinstry:" then bullet list:
- Proficiency in all Construction Project Engineer responsibilities.
- BA/BS in Construction Management, Mechanical Engineering, Electrical Engineering, Architecture, Facilities Management, or comparable degree.
- 2 years of Project Engineer role equivalent required.
- Knowledge of construction management, commercial building process, and financial acumen required.
- Experience on large data center projects in preferred.
- Professional Engineer (PE) and LEED professional designations preferred.
We need to decide sections: Requirements, Qualifications, Skills. The posting lumps them but we can split: Requirements could be the bullet list? Qualifications could be degree and experience? Skills could be proficiency etc. But we must not create sections with filler. We need to see if we have specific content for each.
We have:
- Proficiency in all Construction Project Engineer responsibilities. (Skill)
- BA/BS in ... (Qualification)
- 2 years of Project Engineer role equivalent required. (Requirement)
- Knowledge of construction management, commercial building process, and financial acumen required. (Skill/Requirement)
- Experience on large data center projects in preferred. (Preference)
- Professional Engineer (PE) and LEED professional designations preferred. (Qualification/Certification)
We could combine into a single "Requirements" section with bullet list. Or we could have "Qualifications" for degree and certifications, "Skills" for proficiency and knowledge, "Requirements" for years experience. But we need to avoid thin sections. Perhaps better to have one "Requirements" section containing all bullet points. That would be substantive.
Then "PeopleFirst Benefits" section: list benefits.
We need Benefits section: The posting includes:
"PeopleFirst Benefits When it comes to the basics, we have you covered:
- Competitive pay
- 401(k) with employer match and profit-sharing plan
- Paid time off and holidays
- Comprehensive medical, prescription, dental, and vision with low or zero deductible options and low out of pocket maximums
People come first at McKinstry, and we go beyond the basic benefits with:
- Family formation benefits, including adoption and IVF assistance
- Up to 16 weeks paid parental leave
- Transgender inclusive benefits
- Commuter benefits
- Pet insurance
- “Building Good” paid community service time
- Learning and advancement opportunities via McKinstry University
- McKinstry Moves onsite gyms or reimbursement for remote workers
See benefit plan documents for complete details."
We should include Benefits section with those bullet points.
Pay: The posting includes: "The pay range for this position is $36.48 - $61.97 per hour; however, base pay offered may vary depending on job-related knowledge, skills, and experience. This position is considered non-exempt and will be paid hourly. A bonus may be provided as part of the compensation package, in addition to a full range of medical, financial, and/or other benefits, dependent on the position offered. Base pay information is based on market location."
Thus we have Pay info. Should we create Pay section? Yes, we have specific content: pay range, hourly, non-exempt, bonus possible.
Schedule: No explicit schedule info (like full-time, shift). Not present. So we should not create Schedule section.
About the role: we have introductory paragraph describing role and mission. Could be About the role.
Responsibilities: we have the detailed bullet list.
Requirements/Qualifications/Skills: we have bullet list under "What You Need To Succeed at McKinstry:" which we can treat as Requirements.
Benefits: as above.
Pay: as above.
We must not repeat job title. Not include Job ID etc.
We must not include boilerplate like EEO, drug-free workplace, etc. Remove those.
We must not include application instructions.
We must not include duplicated lines.
Now produce HTML fragment: use
for section headings. Use
- for any list of duties/requirements/benefits. Use
for prose. We need to decide which sections to include: About the role, Responsibilities, Requirements, Benefits, Pay. Check if we have content for each: - About the role: we have introductory paragraph(s) describing McKinstry mission and the role. That's prose. - Responsibilities: we have bullet list under Additional responsibilities may include: plus subheadings Project Coordination, Documentation, Safety. Could we keep subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? Probably we should not add extra headings beyond those; but we could keep the bullet list as is without subheadings. However we might lose some categorization but it's okay. We'll just list all responsibilities as
- . - Requirements: bullet list under "What You Need To Succeed at McKinstry:" (we can treat as Requirements). Could also split into Qualifications and Skills but we can keep as Requirements. - Benefits: bullet list under PeopleFirst Benefits. - Pay: prose about pay range. We must not include Schedule. Now ensure we preserve all substantive information. Let's capture all details. About the role prose: Should we include the mission statements? Yes. Let's extract the About the role paragraph exactly: "Build the future, spark innovation and align your career with purpose. 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? The Opportunity with McKinstry McKinstry is looking for a Senior Project Engineer - Data Center Construction to join our Data Center Innovations division in Dallas, TX. This role is responsible for overseeing the delivery of complex projects, with responsibility for fiscal outcomes, technical quality, and stakeholder coordination from initiation through closeout." We need to ensure we didn't miss any sentences. There's a line break after "services". It says "through: renewables and energy servicesengineering and designconstruction and facility services". There's missing spaces but we keep as is. Now Responsibilities: we need to include all bullet points exactly as given. Let's list them: Project Coordination: - Serve as the on-site point of contact for clients, subcontractors, vendors, and field personnel as needed. - Support Request for Proposal (RFP) processes. - Coordinate equipment procurement with the purchasing department and outside vendors to order and expedite material. - Assist in the development of scope of work for subcontractors. - Oversee the scheduling and coordination of trades. - Assist with project controls, including reviewing and substantiating subcontractor billings, drafting subcontract and purchasing agreements, assisting with client billings, and assuming responsibility for project fiscal performance with oversight of the Project Manager. - Assist in preparation of monthly project accounting review. - Manage and ensure accuracy of cost issue logs. Documentation: - Maintain drawings, daily correspondence with trades, schedules, RFI logs, submittal logs, and Superintendent daily reports. - Create and respond to Requests for Information (RFI). - Create site-specific work plans. - Process, review, log, and distribute submittals. - Create and publish Operations and Maintenance Manuals for clients. - Obtain detailed knowledge of contract, drawings, and specifications for assigned projects. - Maintain cost issue logs. Safety: - Assess site safety and implement actions to prevent injury to property and personnel. - Uphold and communicate McKinstry safety standards. - Coordinate with the Safety Team to create and communicate site safety plans. - Perform other duties as assigned. We should keep them as list items; maybe we can keep the subheadings as plain text? But we shouldn't add extra headings. Could we keep them as part of the list items? Eg we could have a
- Serve as the on-site point of contact... etc. The subheadings "Project Coordination:" etc are not list items but could be considered as part of the prose? The instruction says use
- for any list of duties/requirements/benefits. So we could treat each bullet as li, and ignore the subheadings (they are not list items). But we might lose the subheading info. However we could incorporate them as part of the first li? Eg "Project Coordination: Serve as the on-site point of contact..." but that changes wording. Better to keep subheadings as plain text outside list? But then they'd not be in a list; but they are headings within responsibilities. The instruction only says use
- for any list of duties/requirements/benefits. Use