Project Director - Michels Infrastructure Solutions, Inc.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings allowed. Travel not in list, so we should not create a Travel heading. Instead we could fold travel info into a short
maybe under Overview or Requirements. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Travel is not minor metadata; it's a requirement. Could be placed under Requirements or Qualifications. Probably under Requirements (What It Takes) we can include travel ability. So we will not create a Travel heading. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "AA/EOE/M/W/Vet/Disability https://www.michels.us/website-user-privacy-policy/" which is EEO boilerplate; remove. Also remove duplicated lines: there may be duplicates like "Why Michels Infrastructure Solutions, Inc.?" and "Why You?" etc. Keep them. We need to preserve all substantive information. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections: About Michels Infrastructure Solutions (maybe "About the role"? Actually "About Michels Infrastructure Solutions" is a section about company. Could be "About the role"? Not exactly. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. Let's see:
- About Michels Infrastructure Solutions: could be "About the role"? Actually "About the role" is generic description of role. But we have "Position Overview". That could be "About the role". We'll use "About the role" heading for Position Overview.
- Key Responsibilities: heading "Responsibilities".
- What You'll Do: maybe also responsibilities; but it's a list of duties. Could combine with Responsibilities? But we should not duplicate. The posting has both "Key Responsibilities" and "What You'll Do". They are similar but we need to preserve all info; we can combine them under Responsibilities as a single list, but we must not lose any detail. We'll merge bullet points.
- Why Michels Infrastructure Solutions, Inc.?: could be "Benefits"? Actually that's about company culture/why work there. Could be "Skills"? Not exactly. Could be "About the role"? Not. There's no exact heading for that; but we could treat as "About the role" maybe? But we already used that. Could create a "Skills" heading? Not appropriate. The instruction says prefer a few substantive sections over many thin ones. We could incorporate that info into "About the role" or maybe a separate "Why Michels" section not in allowed headings; but we must only use allowed headings. If we create a heading not in list, it's against instruction? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have info for:
- About the role: Position Overview (executive leadership, etc.)
- Responsibilities: Key Responsibilities + What You'll Do (combined)
- Requirements: What It Takes (education/experience) maybe also travel ability.
- Qualifications: maybe overlapping with Requirements; but we can treat Requirements as education/experience, Qualifications as specific skills/experience? However we have a lot of skill details in What It Takes (proficiency with tools, strong financial, etc.). Could split: Requirements = education + years experience; Qualifications = specific experience and skills; Skills = technical proficiencies.
But we must not create thin sections. Let's think: The posting includes:
- Education: Bachelor's degree in ... and 10+ years experience.
- Demonstrated experience leading large-scale mission-critical...
- Proven success managing projects with significant financial responsibility...
- Strong client-facing experience...
- Experience managing Project Managers, Construction Managers, Project Controls teams, field leadership personnel, and multidisciplinary project organizations.
- Strong understanding of project execution, project controls, project finance, procurement, scheduling, contract management, risk management, and commercial strategy.
- Experience overseeing self-perform construction operations including civil, utility, structural concrete, power, telecommunications, and mission-critical infrastructure scopes.
- Experience supporting business development efforts, proposal development, strategic pursuits, and executive project reviews.
- Proficiency with Procore, Autodesk Construction Cloud, Primavera P6, Microsoft Project, Power BI, or similar project execution and reporting platforms.
- Strong financial, organizational, analytical, negotiation, leadership, presentation, and communication skills.
- Ability to make sound decisions in fast-paced environments while balancing operational, financial, and customer priorities.
- Valid driver's license with an acceptable driving record.
- Ability to travel approximately 75% and support long-term onsite project assignments throughout North America as required.
Thus we can categorize:
- Requirements: Education + years experience + valid driver's license + travel ability.
- Qualifications: Demonstrated experience leading large-scale..., proven success managing..., strong client-facing experience..., experience managing teams..., strong understanding..., experience overseeing self-perform..., experience supporting business development...
- Skills: Proficiency with software..., strong financial, organizational, analytical, negotiation, leadership, presentation, communication skills, ability to make sound decisions.
But we need to avoid thin sections. Could combine Qualifications and Skills into one "Qualifications" section. But we have both headings allowed; we could use Qualifications for experience and Skills for technical proficiencies. That seems reasonable.
Benefits: Comprehensive Benefits Package list.
Pay: Not mentioned; we should not create Pay section.
Schedule: Not mentioned besides travel; but we could treat travel as Schedule? Not exactly. The instruction says include a section ONLY when posting has real, specific content for it. Since schedule not mentioned, we omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
Now we need to format.
We'll start with About the role
then
with Position Overview content.
Position Overview text: "As a Project Director, you will provide executive leadership for large-scale hyperscale data center and mission-critical infrastructure projects from project pursuit through final turnover. You will be accountable for project safety, client satisfaction, commercial performance, operational execution, staffing strategy, and overall business results across one or multiple major projects.This role serves as the senior leader responsible for aligning project teams, field operations, clients, subcontractors, suppliers, and executive stakeholders around successful project outcomes. You will oversee Project Managers, Construction Managers, Project Controls personnel, and field leadership while ensuring projects are delivered safely, profitably, and in accordance with client expectations.Success requires exceptional leadership skills, executive-level communication abilities, strong financial acumen, and proven experience managing large, complex infrastructure programs."
We need to preserve all info; we can combine into a paragraph.
Next Responsibilities:
Responsibilities
then with list items from Key Responsibilities and What You'll Do.
Let's extract bullet points:
Key Responsibilities:
- Provide executive oversight for hyperscale data center and mission-critical infrastructure projects from preconstruction through closeout.
- Establish project execution strategies that support safety, quality, schedule, financial, and client satisfaction objectives.
- Lead Project Managers, Construction Managers, Project Controls teams, and field leadership personnel throughout all phases of project delivery.
- Develop and maintain executive-level relationships with clients, developers, design partners, subcontractors, and key stakeholders.
- Drive project profitability through effective commercial management, contract administration, forecasting, risk management, and change management.
- Support strategic growth initiatives, project pursuits, proposal development efforts, and customer engagement activities.
What You'll Do:
- Oversee the successful delivery of large-scale hyperscale data center and mission-critical infrastructure programs.
- Serve as the senior client-facing representative and executive sponsor for assigned projects.
- Lead project teams responsible for site development, mass grading, wet utilities, dry utilities, fiber infrastructure, ground improvement, structural concrete, power infrastructure, and commissioning activities.
- Direct project execution strategies, staffing models, procurement planning, risk mitigation efforts, and operational priorities.
- Monitor project financial performance, forecasts, contract compliance, cash flow, schedule performance, and resource utilization.
- Review and approve project budgets, execution plans, staffing plans, procurement strategies, and major project decisions.
- Support contract negotiations, dispute resolution, change order management, and commercial strategy development.
- Facilitate executive project reviews, client meetings, operational reviews, and project performance assessments.
- Work closely with preconstruction, estimating, procurement, safety, quality, commissioning, project controls, and operations teams to ensure successful project outcomes.
- Identify business risks and opportunities while implementing strategies that improve operational performance and client satisfaction.
- Mentor and develop future project leadership while fostering a culture of accountability, safety, collaboration, and operational excellence.
We need to ensure no duplicates. Some overlap: "Provide executive oversight..." similar to "Oversee the successful delivery..." but we keep both as they are not identical; but we could combine to avoid redundancy. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we combine, we might lose nuance. Safer to keep both but maybe some are duplicates. Let's see if any are exact duplicates: Not exact. We'll keep all.
We'll create - for each.
Next Requirements:
Requirements
then with:
- Bachelor's degree in Construction Management, Engineering, Civil Engineering, Business, Project Management, or a related field and 10+ years of progressive project leadership experience, or an equivalent combination of education and experience.
- Valid driver's license with an acceptable driving record.
- Ability to travel approximately 75% and support long-term onsite project assignments throughout North America as required.
Next Qualifications: Qualifications
then with:
- Demonstrated experience leading large-scale mission-critical, hyperscale data center, EPC, industrial, power, utility, heavy civil, or complex infrastructure projects.
- Proven success managing projects with significant financial responsibility, complex stakeholder groups, and aggressive schedules.
- Strong client-facing experience with demonstrated ability to develop and maintain executive-level customer relationships.
- Experience managing Project Managers, Construction Managers, Project Controls teams, field leadership personnel, and multidisciplinary project organizations.
- Strong understanding of project execution, project controls, project finance, procurement, scheduling, contract management, risk management, and commercial strategy.
- Experience overseeing self-perform construction operations including civil, utility, structural concrete, power, telecommunications, and mission-critical infrastructure
for prose. We need to decide sections: About Michels Infrastructure Solutions (maybe "About the role"? Actually "About Michels Infrastructure Solutions" is a section about company. Could be "About the role"? Not exactly. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. Let's see: - About Michels Infrastructure Solutions: could be "About the role"? Actually "About the role" is generic description of role. But we have "Position Overview". That could be "About the role". We'll use "About the role" heading for Position Overview. - Key Responsibilities: heading "Responsibilities". - What You'll Do: maybe also responsibilities; but it's a list of duties. Could combine with Responsibilities? But we should not duplicate. The posting has both "Key Responsibilities" and "What You'll Do". They are similar but we need to preserve all info; we can combine them under Responsibilities as a single list, but we must not lose any detail. We'll merge bullet points. - Why Michels Infrastructure Solutions, Inc.?: could be "Benefits"? Actually that's about company culture/why work there. Could be "Skills"? Not exactly. Could be "About the role"? Not. There's no exact heading for that; but we could treat as "About the role" maybe? But we already used that. Could create a "Skills" heading? Not appropriate. The instruction says prefer a few substantive sections over many thin ones. We could incorporate that info into "About the role" or maybe a separate "Why Michels" section not in allowed headings; but we must only use allowed headings. If we create a heading not in list, it's against instruction? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have info for:
- About the role: Position Overview (executive leadership, etc.)
- Responsibilities: Key Responsibilities + What You'll Do (combined)
- Requirements: What It Takes (education/experience) maybe also travel ability.
- Qualifications: maybe overlapping with Requirements; but we can treat Requirements as education/experience, Qualifications as specific skills/experience? However we have a lot of skill details in What It Takes (proficiency with tools, strong financial, etc.). Could split: Requirements = education + years experience; Qualifications = specific experience and skills; Skills = technical proficiencies.
But we must not create thin sections. Let's think: The posting includes:
- Education: Bachelor's degree in ... and 10+ years experience.
- Demonstrated experience leading large-scale mission-critical...
- Proven success managing projects with significant financial responsibility...
- Strong client-facing experience...
- Experience managing Project Managers, Construction Managers, Project Controls teams, field leadership personnel, and multidisciplinary project organizations.
- Strong understanding of project execution, project controls, project finance, procurement, scheduling, contract management, risk management, and commercial strategy.
- Experience overseeing self-perform construction operations including civil, utility, structural concrete, power, telecommunications, and mission-critical infrastructure scopes.
- Experience supporting business development efforts, proposal development, strategic pursuits, and executive project reviews.
- Proficiency with Procore, Autodesk Construction Cloud, Primavera P6, Microsoft Project, Power BI, or similar project execution and reporting platforms.
- Strong financial, organizational, analytical, negotiation, leadership, presentation, and communication skills.
- Ability to make sound decisions in fast-paced environments while balancing operational, financial, and customer priorities.
- Valid driver's license with an acceptable driving record.
- Ability to travel approximately 75% and support long-term onsite project assignments throughout North America as required.
Thus we can categorize:
- Requirements: Education + years experience + valid driver's license + travel ability.
- Qualifications: Demonstrated experience leading large-scale..., proven success managing..., strong client-facing experience..., experience managing teams..., strong understanding..., experience overseeing self-perform..., experience supporting business development...
- Skills: Proficiency with software..., strong financial, organizational, analytical, negotiation, leadership, presentation, communication skills, ability to make sound decisions.
But we need to avoid thin sections. Could combine Qualifications and Skills into one "Qualifications" section. But we have both headings allowed; we could use Qualifications for experience and Skills for technical proficiencies. That seems reasonable.
Benefits: Comprehensive Benefits Package list.
Pay: Not mentioned; we should not create Pay section.
Schedule: Not mentioned besides travel; but we could treat travel as Schedule? Not exactly. The instruction says include a section ONLY when posting has real, specific content for it. Since schedule not mentioned, we omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
Now we need to format.
We'll start with About the role
then
About the role
thenwith Position Overview content. Position Overview text: "As a Project Director, you will provide executive leadership for large-scale hyperscale data center and mission-critical infrastructure projects from project pursuit through final turnover. You will be accountable for project safety, client satisfaction, commercial performance, operational execution, staffing strategy, and overall business results across one or multiple major projects.This role serves as the senior leader responsible for aligning project teams, field operations, clients, subcontractors, suppliers, and executive stakeholders around successful project outcomes. You will oversee Project Managers, Construction Managers, Project Controls personnel, and field leadership while ensuring projects are delivered safely, profitably, and in accordance with client expectations.Success requires exceptional leadership skills, executive-level communication abilities, strong financial acumen, and proven experience managing large, complex infrastructure programs." We need to preserve all info; we can combine into a paragraph. Next Responsibilities:
Responsibilities
then- with list items from Key Responsibilities and What You'll Do.
Let's extract bullet points:
Key Responsibilities:
- Provide executive oversight for hyperscale data center and mission-critical infrastructure projects from preconstruction through closeout.
- Establish project execution strategies that support safety, quality, schedule, financial, and client satisfaction objectives.
- Lead Project Managers, Construction Managers, Project Controls teams, and field leadership personnel throughout all phases of project delivery.
- Develop and maintain executive-level relationships with clients, developers, design partners, subcontractors, and key stakeholders.
- Drive project profitability through effective commercial management, contract administration, forecasting, risk management, and change management.
- Support strategic growth initiatives, project pursuits, proposal development efforts, and customer engagement activities.
What You'll Do:
- Oversee the successful delivery of large-scale hyperscale data center and mission-critical infrastructure programs.
- Serve as the senior client-facing representative and executive sponsor for assigned projects.
- Lead project teams responsible for site development, mass grading, wet utilities, dry utilities, fiber infrastructure, ground improvement, structural concrete, power infrastructure, and commissioning activities.
- Direct project execution strategies, staffing models, procurement planning, risk mitigation efforts, and operational priorities.
- Monitor project financial performance, forecasts, contract compliance, cash flow, schedule performance, and resource utilization.
- Review and approve project budgets, execution plans, staffing plans, procurement strategies, and major project decisions.
- Support contract negotiations, dispute resolution, change order management, and commercial strategy development.
- Facilitate executive project reviews, client meetings, operational reviews, and project performance assessments.
- Work closely with preconstruction, estimating, procurement, safety, quality, commissioning, project controls, and operations teams to ensure successful project outcomes.
- Identify business risks and opportunities while implementing strategies that improve operational performance and client satisfaction.
- Mentor and develop future project leadership while fostering a culture of accountability, safety, collaboration, and operational excellence.
We need to ensure no duplicates. Some overlap: "Provide executive oversight..." similar to "Oversee the successful delivery..." but we keep both as they are not identical; but we could combine to avoid redundancy. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we combine, we might lose nuance. Safer to keep both but maybe some are duplicates. Let's see if any are exact duplicates: Not exact. We'll keep all.
We'll create
- for each.
Next Requirements:
Requirements
then- with:
- Bachelor's degree in Construction Management, Engineering, Civil Engineering, Business, Project Management, or a related field and 10+ years of progressive project leadership experience, or an equivalent combination of education and experience.
- Valid driver's license with an acceptable driving record.
- Ability to travel approximately 75% and support long-term onsite project assignments throughout North America as required.
Next Qualifications:
Qualifications
then- with:
- Demonstrated experience leading large-scale mission-critical, hyperscale data center, EPC, industrial, power, utility, heavy civil, or complex infrastructure projects.
- Proven success managing projects with significant financial responsibility, complex stakeholder groups, and aggressive schedules.
- Strong client-facing experience with demonstrated ability to develop and maintain executive-level customer relationships.
- Experience managing Project Managers, Construction Managers, Project Controls teams, field leadership personnel, and multidisciplinary project organizations.
- Strong understanding of project execution, project controls, project finance, procurement, scheduling, contract management, risk management, and commercial strategy.
- Experience overseeing self-perform construction operations including civil, utility, structural concrete, power, telecommunications, and mission-critical infrastructure