Project Manager - Data Center Construction
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "PeopleFirst Benefits" heading? It's a heading but we can treat as Benefits section. We need to include only sections with real content.
We need to extract content:
Intro: "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 We are seeking a Project Manager - Data Center Construction to join our growing Data Center Innovations division in Pasco, WA. In this role, you will develop strategies, goals, and objectives for projects to ensure delivery of the project safely, on time and on budget with high client satisfaction."
That's prose for About the role.
Then responsibilities: list under "Key responsibilities include:" then subheadings: Project Management, Project Controls, Team Management, Other duties as assigned. Under each there are bullet-like sentences separated by periods. We need to convert to
- . Probably each sentence is a duty. We'll need to split them.
Let's extract each duty:
Project Management:
- Identify required resources and develop project plans, schedules, and scopes of work to achieve project goals.
- Serve as the primary contact for project engineering staff during construction and transition activities between project phases.
- Communicate with the General Contractor, Architect, Engineer, Owner, and other stakeholders to support project execution.
- Define project responsibilities for management, engineering, and field staff, and coach team members to ensure accountability.
- Assist the business development team in responding to requests for proposal and bid processes.
- Assess site safety, implement actions to prevent injury, and ensure safety compliance for all on-site personnel.
Project Controls:
- Assumes financial responsibility for project including accurate, timely and relevant reporting to stakeholders.
- Facilitates invoice payments from clients and to subcontractors.
- Reviews and approves subcontractor billing.
- Prepares client and subcontractor change orders.
- Monitors, controls and reports on the financial performance of projects.
- Drafts subcontracts and purchase agreements.
- Monitors and proofs change issue log.
- Document Control associated with Design Drawings, Permits, RFI’s, Submittals, etc.
- Prepares or supervises the preparation of Submittals, Operation & Maintenance Manuals, Expediting Reports, Change Order Log, RFI log, Correspondence Log, etc.
- Assesses any potential job cost impacts, submits, negotiates and tracks all change orders requests.
- Prepares or supervises the preparation of Job Start and Project Closeout materials.
- Reviews contracts, drawings, specifications and other resources to answer questions in a timely manner.
- Evaluates bid estimates, develops cost codes, establishes definitive budgets, develops manpower plan with Superintendents, and monitors field labor progress.
- Takes responsibility for the development and implementation of a comprehensive construction execution plan, including Safety and Quality Assurance.
- Delivers accurate and timely data to support project forecasts.
Team Management:
- Coaches and mentors project team members.
- Develops project staffing plans to include labor, subcontractors, etc.
- Acts as steward of McKinstry culture; communicate and influence policies and procedures.
- Establishes, leads and documents assigned meetings.
- Define individual project responsibilities and accountabilities.
- Other duties as assigned.
We could combine all responsibilities into one list, but better to keep subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require subheadings inside. So we can have a single Responsibilities section with a - list of all duties. That's fine.
Now requirements/qualifications/skills: "What You Need To Succeed At McKinstry" includes:
- Proficiency in all Senior Construction Project Engineer responsibilities.
- BA/BS in Construction Management, Mechanical Engineering, Electrical Engineering, Architecture, Facilities Management, or comparable degree required.
- Completion of OSHA 30 Class is required.
- 5-7 years of experience in project engineering or construction is required.
- Experience working for a General Contractor.
- Experience on large data center projects is required.
- Professional Engineer (PE), Certified Project Manager (CPM), LEED, DBIA professional designations preferred.
- Basic estimating skills required.
- Registered Communications Distribution Designer (RCDD), CPM professional designation is preferred.
- Demonstrates an understanding of accounting and financial management preferred
We can separate into Requirements (required) and Skills (preferred). But we can also combine into Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could have a single "Requirements and Qualifications" section with both required and preferred items. But we need to use
for section headings like Requirements, Qualifications, Skills. We could have Requirements (required) and Skills (preferred). That's two sections. That's okay.
But we must not create sections with filler like "not specified". All content is present.
Now Benefits: "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 need to list benefits as - . Also note "Competitive pay" is mentioned but we also have Pay range later. We'll keep Competitive pay as a benefit item.
Pay: "The pay range for this position is $93,600 - $147,060 per year; however, base pay offered may vary depending on job-related knowledge, skills, and experience. Base pay information is based on market location. 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."
We need a Pay section with that prose.
Schedule: not mentioned, so omit.
Now we must remove boilerplate: EEO statement, drug-free workplace, confidentiality, immigration, work authorization, etc. Also remove "See benefit plan documents for complete details." maybe keep? It's part of benefits but could be considered boilerplate? It's a reference; we could keep but it's not substantive detail. Might be okay to keep but it's not a benefit. Safer to omit? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "See benefit plan documents for complete details." is not exactly legal boilerplate but it's a reference. I'd keep it as part of benefits? It's not a benefit itself. Might be considered filler. I'd omit it.
Also remove "People come first at McKinstry, and we go beyond the basic benefits with:" maybe keep as intro sentence before list.
We need to preserve all substantive information. So we should keep the sentences describing benefits.
Let's craft HTML.
Structure:
About the role
... (intro paragraph)
Responsibilities
- ...
...
Requirements
- Proficiency in all Senior Construction Project Engineer responsibilities.
- BA/BS in Construction Management, Mechanical Engineering, Electrical Engineering, Architecture, Facilities Management, or comparable degree required.
- Completion of OSHA 30 Class is required.
- 5-7 years of experience in project engineering or construction is required.
- Experience working for a General Contractor.
- Experience on large data center projects is required.
- Basic estimating skills required.
Skills
- Professional Engineer (PE), Certified Project Manager (CPM), LEED, DBIA professional designations preferred.
- Registered Communications Distribution Designer (RCDD), CPM professional designation is preferred.
- Demonstrates an understanding of accounting and financial management preferred.
Benefits
- 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
- 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
Pay
The pay range for this position is $93,600 - $147,060 per year; however, base pay offered may vary depending on job-related knowledge, skills, and experience. Base pay information is based on market location. 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.
Check for any duplicated lines: we have not repeated.
Check for any boilerplate left: we removed EEO etc.
Check for any "PeopleFirst Benefits" heading removed; we used Benefits.
Check for any mention of "See benefit plan documents for complete details." removed.
Check for any mention of "People come first at McKinstry, and we go beyond the basic benefits with:" we kept as intro? Actually we omitted that sentence; we could include it as a before the list. But we already have a list; we could keep that sentence as prose. The instruction: preserve ALL substantive information. That sentence is substantive? It's a description. Might be good to include as a
before the
. Let's add a before the list: "People come first at McKinstry, and we go beyond the basic benefits with:" then the list.
Similarly for benefits basics: "When it comes to the basics, we have you covered:" could be a
before the list. But we already have list items that include those basics. Could
for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "PeopleFirst Benefits" heading? It's a heading but we can treat as Benefits section. We need to include only sections with real content. We need to extract content: Intro: "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 We are seeking a Project Manager - Data Center Construction to join our growing Data Center Innovations division in Pasco, WA. In this role, you will develop strategies, goals, and objectives for projects to ensure delivery of the project safely, on time and on budget with high client satisfaction." That's prose for About the role. Then responsibilities: list under "Key responsibilities include:" then subheadings: Project Management, Project Controls, Team Management, Other duties as assigned. Under each there are bullet-like sentences separated by periods. We need to convert to
- . Probably each sentence is a duty. We'll need to split them.
Let's extract each duty:
Project Management:
- Identify required resources and develop project plans, schedules, and scopes of work to achieve project goals.
- Serve as the primary contact for project engineering staff during construction and transition activities between project phases.
- Communicate with the General Contractor, Architect, Engineer, Owner, and other stakeholders to support project execution.
- Define project responsibilities for management, engineering, and field staff, and coach team members to ensure accountability.
- Assist the business development team in responding to requests for proposal and bid processes.
- Assess site safety, implement actions to prevent injury, and ensure safety compliance for all on-site personnel.
Project Controls:
- Assumes financial responsibility for project including accurate, timely and relevant reporting to stakeholders.
- Facilitates invoice payments from clients and to subcontractors.
- Reviews and approves subcontractor billing.
- Prepares client and subcontractor change orders.
- Monitors, controls and reports on the financial performance of projects.
- Drafts subcontracts and purchase agreements.
- Monitors and proofs change issue log.
- Document Control associated with Design Drawings, Permits, RFI’s, Submittals, etc.
- Prepares or supervises the preparation of Submittals, Operation & Maintenance Manuals, Expediting Reports, Change Order Log, RFI log, Correspondence Log, etc.
- Assesses any potential job cost impacts, submits, negotiates and tracks all change orders requests.
- Prepares or supervises the preparation of Job Start and Project Closeout materials.
- Reviews contracts, drawings, specifications and other resources to answer questions in a timely manner.
- Evaluates bid estimates, develops cost codes, establishes definitive budgets, develops manpower plan with Superintendents, and monitors field labor progress.
- Takes responsibility for the development and implementation of a comprehensive construction execution plan, including Safety and Quality Assurance.
- Delivers accurate and timely data to support project forecasts.
Team Management:
- Coaches and mentors project team members.
- Develops project staffing plans to include labor, subcontractors, etc.
- Acts as steward of McKinstry culture; communicate and influence policies and procedures.
- Establishes, leads and documents assigned meetings.
- Define individual project responsibilities and accountabilities.
- Other duties as assigned.
We could combine all responsibilities into one list, but better to keep subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require subheadings inside. So we can have a single Responsibilities section with a
- list of all duties. That's fine.
Now requirements/qualifications/skills: "What You Need To Succeed At McKinstry" includes:
- Proficiency in all Senior Construction Project Engineer responsibilities.
- BA/BS in Construction Management, Mechanical Engineering, Electrical Engineering, Architecture, Facilities Management, or comparable degree required.
- Completion of OSHA 30 Class is required.
- 5-7 years of experience in project engineering or construction is required.
- Experience working for a General Contractor.
- Experience on large data center projects is required.
- Professional Engineer (PE), Certified Project Manager (CPM), LEED, DBIA professional designations preferred.
- Basic estimating skills required.
- Registered Communications Distribution Designer (RCDD), CPM professional designation is preferred.
- Demonstrates an understanding of accounting and financial management preferred
We can separate into Requirements (required) and Skills (preferred). But we can also combine into Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could have a single "Requirements and Qualifications" section with both required and preferred items. But we need to use
for section headings like Requirements, Qualifications, Skills. We could have Requirements (required) and Skills (preferred). That's two sections. That's okay. But we must not create sections with filler like "not specified". All content is present. Now Benefits: "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 need to list benefits as
- . Also note "Competitive pay" is mentioned but we also have Pay range later. We'll keep Competitive pay as a benefit item.
Pay: "The pay range for this position is $93,600 - $147,060 per year; however, base pay offered may vary depending on job-related knowledge, skills, and experience. Base pay information is based on market location. 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."
We need a Pay section with that prose.
Schedule: not mentioned, so omit.
Now we must remove boilerplate: EEO statement, drug-free workplace, confidentiality, immigration, work authorization, etc. Also remove "See benefit plan documents for complete details." maybe keep? It's part of benefits but could be considered boilerplate? It's a reference; we could keep but it's not substantive detail. Might be okay to keep but it's not a benefit. Safer to omit? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "See benefit plan documents for complete details." is not exactly legal boilerplate but it's a reference. I'd keep it as part of benefits? It's not a benefit itself. Might be considered filler. I'd omit it.
Also remove "People come first at McKinstry, and we go beyond the basic benefits with:" maybe keep as intro sentence before list.
We need to preserve all substantive information. So we should keep the sentences describing benefits.
Let's craft HTML.
Structure:
About the role
... (intro paragraph)
Responsibilities
- ... ...
Requirements
- Proficiency in all Senior Construction Project Engineer responsibilities.
- BA/BS in Construction Management, Mechanical Engineering, Electrical Engineering, Architecture, Facilities Management, or comparable degree required.
- Completion of OSHA 30 Class is required.
- 5-7 years of experience in project engineering or construction is required.
- Experience working for a General Contractor.
- Experience on large data center projects is required.
- Basic estimating skills required.
Skills
- Professional Engineer (PE), Certified Project Manager (CPM), LEED, DBIA professional designations preferred.
- Registered Communications Distribution Designer (RCDD), CPM professional designation is preferred.
- Demonstrates an understanding of accounting and financial management preferred.
Benefits
- 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
- 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
Pay
The pay range for this position is $93,600 - $147,060 per year; however, base pay offered may vary depending on job-related knowledge, skills, and experience. Base pay information is based on market location. 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.
Check for any duplicated lines: we have not repeated. Check for any boilerplate left: we removed EEO etc. Check for any "PeopleFirst Benefits" heading removed; we used Benefits. Check for any mention of "See benefit plan documents for complete details." removed. Check for any mention of "People come first at McKinstry, and we go beyond the basic benefits with:" we kept as intro? Actually we omitted that sentence; we could include it as abefore the list. But we already have a list; we could keep that sentence as prose. The instruction: preserve ALL substantive information. That sentence is substantive? It's a description. Might be good to include as a
before the
- . Let's add a
before the list: "People come first at McKinstry, and we go beyond the basic benefits with:" then the list. Similarly for benefits basics: "When it comes to the basics, we have you covered:" could be a
before the list. But we already have list items that include those basics. Could
- . Also note "Competitive pay" is mentioned but we also have Pay range later. We'll keep Competitive pay as a benefit item.
Pay: "The pay range for this position is $93,600 - $147,060 per year; however, base pay offered may vary depending on job-related knowledge, skills, and experience. Base pay information is based on market location. 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."
We need a Pay section with that prose.
Schedule: not mentioned, so omit.
Now we must remove boilerplate: EEO statement, drug-free workplace, confidentiality, immigration, work authorization, etc. Also remove "See benefit plan documents for complete details." maybe keep? It's part of benefits but could be considered boilerplate? It's a reference; we could keep but it's not substantive detail. Might be okay to keep but it's not a benefit. Safer to omit? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "See benefit plan documents for complete details." is not exactly legal boilerplate but it's a reference. I'd keep it as part of benefits? It's not a benefit itself. Might be considered filler. I'd omit it.
Also remove "People come first at McKinstry, and we go beyond the basic benefits with:" maybe keep as intro sentence before list.
We need to preserve all substantive information. So we should keep the sentences describing benefits.
Let's craft HTML.
Structure:
- list of all duties. That's fine.
Now requirements/qualifications/skills: "What You Need To Succeed At McKinstry" includes:
- Proficiency in all Senior Construction Project Engineer responsibilities.
- BA/BS in Construction Management, Mechanical Engineering, Electrical Engineering, Architecture, Facilities Management, or comparable degree required.
- Completion of OSHA 30 Class is required.
- 5-7 years of experience in project engineering or construction is required.
- Experience working for a General Contractor.
- Experience on large data center projects is required.
- Professional Engineer (PE), Certified Project Manager (CPM), LEED, DBIA professional designations preferred.
- Basic estimating skills required.
- Registered Communications Distribution Designer (RCDD), CPM professional designation is preferred.
- Demonstrates an understanding of accounting and financial management preferred
We can separate into Requirements (required) and Skills (preferred). But we can also combine into Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could have a single "Requirements and Qualifications" section with both required and preferred items. But we need to use