Project Controls Specialist - Michels Infrastructure Solutions, Inc.
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Key sections:
- About Michels Infrastructure Solutions (maybe "About the role"? Actually "About Michels Infrastructure Solutions" is about company. Could map to "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Position Overview (description) could be "About the role".
- Key Responsibilities (list) -> Responsibilities.
- What You'll Do (list) also responsibilities; could combine.
- Why Michels Infrastructure Solutions, Inc.? (benefits/ company selling points) maybe not a standard heading; could be part of Benefits? But they have separate Benefits section later.
- Comprehensive Benefits Package (list) -> Benefits.
- Why You? (personal traits) maybe Skills? Could be Qualifications? Might be "Skills".
- What It Takes (requirements) -> Requirements/Qualifications/Skills.
- Travel info etc maybe Schedule? Travel 75% maybe schedule? Not exactly schedule but travel requirement. Could be Schedule? The instruction says include Schedule only if posting actually states them. It does state travel approximately 75% and ability to travel. That's not a schedule like shift times. Might be considered Schedule? Probably not; better to omit Schedule if not explicit work hours. Pay: not mentioned. So omit Pay and Schedule.
We need to include sections only if real specific content.
Thus we will have:
About the role
with paragraph(s) from Position Overview and maybe About Michels Infrastructure Solutions? Actually About the role should describe the role. We'll combine Position Overview paragraph.
Responsibilities
with - from Key Responsibilities and What You'll Do (maybe combine). Ensure not duplicate.
Requirements
with education/experience etc from What It Takes.
Skills
maybe from What It Takes includes skills like analytical, Excel, etc. Could also include "Why You?" traits. But we need to avoid duplication. Perhaps we put skills under Skills heading: list of skills like Advanced proficiency with Microsoft Excel, experience with Power BI, Primavera P6, etc, strong analytical, organizational, communication, problem-solving, time-management skills, ability to work with teams, commitment to safety, valid driver's license, ability to travel 75%.
But travel maybe not skill. Could be under Requirements.
We need to decide mapping.
Better: Use Requirements for education/experience, Qualifications for specific qualifications? But we only have headings list; we can choose to use Requirements and Skills. Qualifications maybe similar to Requirements. To keep few sections, we can use Requirements and Skills.
Thus:
- About the role: paragraph(s) describing role.
- Responsibilities: list.
- Requirements: education/experience + maybe travel requirement? Travel is not a requirement but a condition; could be placed under Requirements as "Ability to travel approximately 75%".
- Skills: list of technical and soft skills.
Benefits: list from Comprehensive Benefits Package.
We must not include Pay or Schedule.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details like specific tools list, etc.
Let's extract details.
From posting:
About Michels Infrastructure Solutions (company description) maybe not needed for role but could be part of About the role? Might be considered boilerplate? It's substantive about company but not role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. Where to put? Could be under About the role? Or maybe a separate section like "About the company" but not allowed headings. We could incorporate into About the role paragraph as context. That's okay.
Thus About the role paragraph will include: description of role, plus description of Michels Infrastructure Solutions (the company) maybe.
Let's craft:
About the role: "As a Project Controls Specialist, you will support project controls functions across large-scale hyperscale data center and mission-critical infrastructure projects. Working closely with Project Managers, Project Controls Managers, field leadership, accounting, procurement, and executive stakeholders, you will assist in developing forecasts, tracking project costs, monitoring budgets, maintaining reporting systems, and supporting project performance analysis. This role serves as a key resource for project teams by providing accurate project data, maintaining reporting consistency, identifying performance trends, and helping ensure projects remain aligned with financial and operational objectives. Michels Infrastructure Solutions (MIS) brings together the full capabilities of the Michels Family of Companies under a Super General Contractor (Super GC) model, providing mission-critical owners and developers with a single point of accountability for every phase of project execution. By combining self-performed specialty design, construction, and commissioning services, MIS delivers large-scale, multidisciplinary projects with greater control over safety, quality, schedule, and cost. MIS specializes in the delivery of hyperscale data centers and mission-critical facilities, leveraging expertise across mass grading and site development, wet and dry utilities, fiber and telecommunications infrastructure, ground improvement, deep foundations, structural concrete, power infrastructure, and commissioning."
That seems to capture.
Now Responsibilities: combine Key Responsibilities and What You'll Do.
Key Responsibilities bullet list:
- Support project controls activities including forecasting, budgeting, cost tracking, reporting, and project performance analysis.
- Assist with maintaining project budgets, cost reports, cash flow forecasts, and project dashboards.
- Monitor project costs, commitments, labor performance, procurement activities, and productivity trends.
- Support monthly forecasting cycles and project reporting processes.
- Assist in identifying budget variances, schedule impacts, risks, and performance trends.
- Help maintain project controls systems, tools, procedures, and reporting standards.
What You'll Do bullet list:
- Support project controls efforts across hyperscale data center and mission-critical infrastructure projects.
- Analyze project costs, commitments, forecasts, labor productivity, procurement status, and project financial performance.
- Develop and maintain project reports, dashboards, KPI metrics, and forecasting tools.
- Assist project teams with budget management, change tracking, cash flow forecasting, and project reporting.
- Support project reviews, forecasting meetings, operational reviews, and executive reporting activities.
- Collaborate with accounting, procurement, project management, field operations, and scheduling teams to maintain accurate project information.
- Track project trends and identify opportunities for improvement in project performance and reporting.
- Support project startup, execution, commissioning, turnover, and closeout reporting requirements.
- Assist with implementation and continuous improvement of project controls processes and systems.
We need to ensure no duplication; some overlap but we can keep both as they are distinct but similar. It's okay to keep both; we just need to preserve all substantive info. Duplication is okay if it's in original; but we could combine to avoid redundancy but must not lose info. Safer to keep both but maybe combine similar points? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we combine and lose nuance, might be summarizing. Better to keep both lists as is, even if some overlap. We'll output a single with all items from both lists, preserving each.
Now Requirements: from What It Takes.
Paragraph: "Bachelor's degree in Construction Management, Engineering, Finance, Accounting, Business, Project Management, Economics, or a related discipline and 2+ years of project controls, project management, cost controls, scheduling, finance, accounting, construction, engineering, or related experience, or an equivalent combination of education and experience. Experience supporting construction, mission-critical, data center, EPC, utility, industrial, power, or infrastructure projects is preferred. Understanding of budgeting, forecasting, cost management, project reporting, procurement tracking, and project performance measurement. Experience supporting project financial analysis, cost reporting, forecasting, cash flow analysis, or operational reporting is preferred. Ability to analyze project costs, commitments, productivity trends, procurement status, and financial performance data. Advanced proficiency with Microsoft Excel and Microsoft Office Suite. Experience with Power BI, Primavera P6, Microsoft Project, Procore, Autodesk Construction Cloud, InEight, Oracle Primavera, SAP, Oracle, or similar project controls platforms is preferred. Strong analytical, organizational, communication, problem-solving, and time-management skills. Ability to work effectively with project teams, field personnel, accounting, procurement, scheduling, and executive leadership. Commitment to safety, quality, accountability, and continuous learning. 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. Travel may include extended durations based on project assignments and business needs."
We'll put that in a maybe? But it's long; could be
. The instruction: use
for prose. So we can put that as a paragraph.
Now Skills: maybe we can extract from Why You? and other skill-like statements.
Why You? bullet list (actually sentences):
- You like to surround yourself with dedicated, value-driven people.
- You relish new challenges and evolving technology.
- You cringe when you hear: “Because that's the way we've always done it.”
- You enjoy analyzing information and identifying trends that improve business performance.
- You thrive in environments where organization, planning, and accountability drive success.
- You are motivated by ownership, continuous improvement, and helping teams achieve successful project outcomes.
- You want your work to directly impact the delivery of world-class infrastructure projects.
These are more personal traits/ motivations; could be considered Skills or Qualifications. We'll put them under Skills as bullet list.
Also we have some skill statements already in Requirements (strong analytical, etc). To avoid duplication, we could keep them in Requirements and not duplicate in Skills. But we need to preserve all info; if we omit them from Skills, they are still present in Requirements. That's fine.
Thus Skills heading will contain the Why You? list.
Now Benefits: Comprehensive Benefits Package list:
- Health Insurance
- Dental Insurance
- Life Insurance
- Flexible Spending Accounts (FSA)
- Health Savings Account (HSA)
- Short-Term Disability Insurance
- Long-Term Disability Insurance
- 401(k) Retirement Plan
- Legal Plan
- Identity Theft Protection and Monitoring Plan
- Benefits may vary based on position and location.
We'll put as
- .
Now we must not include Pay or Schedule sections.
Now produce HTML fragment: only the elements, no or . We'll output:
About the role
...
Responsibilities
- ...
...
Requirements
...
Skills
- ...
...
Benefits
- ...
...
Make sure to preserve line breaks? Not needed.
Now craft the content precisely.
About the role paragraph: combine earlier.
Let's write:
As a Project Controls Specialist, you will support project controls functions across large-scale hyperscale data center and mission-critical infrastructure projects. Working closely with Project Managers, Project Controls Managers, field leadership, accounting, procurement, and executive stakeholders, you will assist in developing forecasts, tracking project costs, monitoring budgets, maintaining reporting systems, and supporting project performance analysis. This role serves as a key resource for project teams by providing accurate project data, maintaining reporting consistency, identifying performance trends, and helping ensure projects remain aligned with financial and operational objectives. Michels Infrastructure Solutions (MIS) brings together the full capabilities of the Michels Family of Companies under a Super General Contractor (Super GC) model, providing mission-critical owners and developers with a single point of accountability for every phase of project execution. By combining self-performed specialty design, construction, and commissioning services, MIS delivers large-scale, multidisciplinary projects with greater control over safety, quality, schedule, and cost. MIS specializes in the delivery of hyperscale data
Requirements
with education/experience etc from What It Takes.Skills
maybe from What It Takes includes skills like analytical, Excel, etc. Could also include "Why You?" traits. But we need to avoid duplication. Perhaps we put skills under Skills heading: list of skills like Advanced proficiency with Microsoft Excel, experience with Power BI, Primavera P6, etc, strong analytical, organizational, communication, problem-solving, time-management skills, ability to work with teams, commitment to safety, valid driver's license, ability to travel 75%. But travel maybe not skill. Could be under Requirements. We need to decide mapping. Better: Use Requirements for education/experience, Qualifications for specific qualifications? But we only have headings list; we can choose to use Requirements and Skills. Qualifications maybe similar to Requirements. To keep few sections, we can use Requirements and Skills. Thus: - About the role: paragraph(s) describing role. - Responsibilities: list. - Requirements: education/experience + maybe travel requirement? Travel is not a requirement but a condition; could be placed under Requirements as "Ability to travel approximately 75%". - Skills: list of technical and soft skills. Benefits: list from Comprehensive Benefits Package. We must not include Pay or Schedule. Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details like specific tools list, etc. Let's extract details. From posting: About Michels Infrastructure Solutions (company description) maybe not needed for role but could be part of About the role? Might be considered boilerplate? It's substantive about company but not role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. Where to put? Could be under About the role? Or maybe a separate section like "About the company" but not allowed headings. We could incorporate into About the role paragraph as context. That's okay. Thus About the role paragraph will include: description of role, plus description of Michels Infrastructure Solutions (the company) maybe. Let's craft: About the role: "As a Project Controls Specialist, you will support project controls functions across large-scale hyperscale data center and mission-critical infrastructure projects. Working closely with Project Managers, Project Controls Managers, field leadership, accounting, procurement, and executive stakeholders, you will assist in developing forecasts, tracking project costs, monitoring budgets, maintaining reporting systems, and supporting project performance analysis. This role serves as a key resource for project teams by providing accurate project data, maintaining reporting consistency, identifying performance trends, and helping ensure projects remain aligned with financial and operational objectives. Michels Infrastructure Solutions (MIS) brings together the full capabilities of the Michels Family of Companies under a Super General Contractor (Super GC) model, providing mission-critical owners and developers with a single point of accountability for every phase of project execution. By combining self-performed specialty design, construction, and commissioning services, MIS delivers large-scale, multidisciplinary projects with greater control over safety, quality, schedule, and cost. MIS specializes in the delivery of hyperscale data centers and mission-critical facilities, leveraging expertise across mass grading and site development, wet and dry utilities, fiber and telecommunications infrastructure, ground improvement, deep foundations, structural concrete, power infrastructure, and commissioning." That seems to capture. Now Responsibilities: combine Key Responsibilities and What You'll Do. Key Responsibilities bullet list: - Support project controls activities including forecasting, budgeting, cost tracking, reporting, and project performance analysis. - Assist with maintaining project budgets, cost reports, cash flow forecasts, and project dashboards. - Monitor project costs, commitments, labor performance, procurement activities, and productivity trends. - Support monthly forecasting cycles and project reporting processes. - Assist in identifying budget variances, schedule impacts, risks, and performance trends. - Help maintain project controls systems, tools, procedures, and reporting standards. What You'll Do bullet list: - Support project controls efforts across hyperscale data center and mission-critical infrastructure projects. - Analyze project costs, commitments, forecasts, labor productivity, procurement status, and project financial performance. - Develop and maintain project reports, dashboards, KPI metrics, and forecasting tools. - Assist project teams with budget management, change tracking, cash flow forecasting, and project reporting. - Support project reviews, forecasting meetings, operational reviews, and executive reporting activities. - Collaborate with accounting, procurement, project management, field operations, and scheduling teams to maintain accurate project information. - Track project trends and identify opportunities for improvement in project performance and reporting. - Support project startup, execution, commissioning, turnover, and closeout reporting requirements. - Assist with implementation and continuous improvement of project controls processes and systems. We need to ensure no duplication; some overlap but we can keep both as they are distinct but similar. It's okay to keep both; we just need to preserve all substantive info. Duplication is okay if it's in original; but we could combine to avoid redundancy but must not lose info. Safer to keep both but maybe combine similar points? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we combine and lose nuance, might be summarizing. Better to keep both lists as is, even if some overlap. We'll output a single- with all items from both lists, preserving each.
Now Requirements: from What It Takes.
Paragraph: "Bachelor's degree in Construction Management, Engineering, Finance, Accounting, Business, Project Management, Economics, or a related discipline and 2+ years of project controls, project management, cost controls, scheduling, finance, accounting, construction, engineering, or related experience, or an equivalent combination of education and experience. Experience supporting construction, mission-critical, data center, EPC, utility, industrial, power, or infrastructure projects is preferred. Understanding of budgeting, forecasting, cost management, project reporting, procurement tracking, and project performance measurement. Experience supporting project financial analysis, cost reporting, forecasting, cash flow analysis, or operational reporting is preferred. Ability to analyze project costs, commitments, productivity trends, procurement status, and financial performance data. Advanced proficiency with Microsoft Excel and Microsoft Office Suite. Experience with Power BI, Primavera P6, Microsoft Project, Procore, Autodesk Construction Cloud, InEight, Oracle Primavera, SAP, Oracle, or similar project controls platforms is preferred. Strong analytical, organizational, communication, problem-solving, and time-management skills. Ability to work effectively with project teams, field personnel, accounting, procurement, scheduling, and executive leadership. Commitment to safety, quality, accountability, and continuous learning. 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. Travel may include extended durations based on project assignments and business needs."
We'll put that in a
- .
Now we must not include Pay or Schedule sections.
Now produce HTML fragment: only the elements, no or . We'll output:
About the role
...
Responsibilities
- ... ...
Requirements
...
Skills
- ... ...
Benefits
- ... ...
As a Project Controls Specialist, you will support project controls functions across large-scale hyperscale data center and mission-critical infrastructure projects. Working closely with Project Managers, Project Controls Managers, field leadership, accounting, procurement, and executive stakeholders, you will assist in developing forecasts, tracking project costs, monitoring budgets, maintaining reporting systems, and supporting project performance analysis. This role serves as a key resource for project teams by providing accurate project data, maintaining reporting consistency, identifying performance trends, and helping ensure projects remain aligned with financial and operational objectives. Michels Infrastructure Solutions (MIS) brings together the full capabilities of the Michels Family of Companies under a Super General Contractor (Super GC) model, providing mission-critical owners and developers with a single point of accountability for every phase of project execution. By combining self-performed specialty design, construction, and commissioning services, MIS delivers large-scale, multidisciplinary projects with greater control over safety, quality, schedule, and cost. MIS specializes in the delivery of hyperscale data
maybe? But it's long; could be
. The instruction: use
for prose. So we can put that as a paragraph. Now Skills: maybe we can extract from Why You? and other skill-like statements. Why You? bullet list (actually sentences): - You like to surround yourself with dedicated, value-driven people. - You relish new challenges and evolving technology. - You cringe when you hear: “Because that's the way we've always done it.” - You enjoy analyzing information and identifying trends that improve business performance. - You thrive in environments where organization, planning, and accountability drive success. - You are motivated by ownership, continuous improvement, and helping teams achieve successful project outcomes. - You want your work to directly impact the delivery of world-class infrastructure projects. These are more personal traits/ motivations; could be considered Skills or Qualifications. We'll put them under Skills as bullet list. Also we have some skill statements already in Requirements (strong analytical, etc). To avoid duplication, we could keep them in Requirements and not duplicate in Skills. But we need to preserve all info; if we omit them from Skills, they are still present in Requirements. That's fine. Thus Skills heading will contain the Why You? list. Now Benefits: Comprehensive Benefits Package list: - Health Insurance - Dental Insurance - Life Insurance - Flexible Spending Accounts (FSA) - Health Savings Account (HSA) - Short-Term Disability Insurance - Long-Term Disability Insurance - 401(k) Retirement Plan - Legal Plan - Identity Theft Protection and Monitoring Plan - Benefits may vary based on position and location. We'll put as