Document Controls Engineer - Michels Infrastructure Solutions, Inc.
for headings etc. Must include sections only when posting has real specific content. We need to parse the job posting.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each section heading.
We must not repeat job title as heading. No Job ID etc.
We must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We must include sections only when posting has real specific content.
Let's extract content:
Job title: Document Controls Engineer (but we don't repeat as heading).
Location: Project-Based (maybe location line). Travel: Approximately 75% Travel Required.
We need to decide sections.
We have "About Michels Infrastructure Solutions" - that's about company, not role. Could be "About the role"? Actually "About Michels Infrastructure Solutions" is about company. 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" which describes role. Could be "About the role". We'll put that under About the role
with paragraphs.
We have "Key Responsibilities" and then "What You'll Do" which are responsibilities. So we can combine into Responsibilities section with - .
We have "What You'll Do" bullet list (actually sentences). We'll treat as list items.
We have "Why Michels Infrastructure Solutions, Inc.?" which is about company benefits/culture. Could be part of Benefits? But we have separate Benefits section later. The "Why Michels..." includes things like training investment, etc. Might be considered Benefits or "Why you?".
We have "Comprehensive Benefits Package" list.
We have "Why You?" which is about candidate traits; could be part of Qualifications or Skills? Might be considered "Qualifications"? But we have separate "What It Takes" which lists requirements: education, experience, etc. That's Requirements/Qualifications.
We have "What It Takes" which includes education, experience, etc. That's Requirements/Qualifications.
We have "Ability to travel approximately 75%..." which is Schedule/Travel. So we can put under Schedule section.
We have Pay: not mentioned. So we should NOT include Pay section because no specific content.
We have Benefits: we have list.
We have Skills: maybe we can extract from "What It Takes" like proficiency with Microsoft Office Suite and document management platforms etc. Could be Skills section.
But we need to avoid thin sections. Prefer few substantive sections.
We could combine Requirements and Qualifications into one section? But headings are predefined; we must use those exact headings if we include them. We can choose to include only those sections that have substantive content.
Let's list possible sections:
- About the role: from Position Overview paragraph(s). Good.
- Responsibilities: from Key Responsibilities and What You'll Do.
- Requirements: from What It Takes (education, experience, etc.) plus maybe travel ability? Travel could be Schedule.
- Qualifications: maybe overlapping with Requirements; but we could decide to include only Requirements and not Qualifications to avoid duplication. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using both Requirements and Qualifications if content distinct. But we should avoid thin sections. We could put education/experience under Requirements, and skills/technical proficiencies under Skills. Qualifications could be left out if not distinct.
- Skills: proficiency with MS Office, document management platforms, analytical, organizational, communication, problem-solving, ability to work with teams, etc.
- Benefits: Comprehensive Benefits Package list.
- Schedule: travel approx 75% etc.
- Pay: not present, omit.
We must ensure we don't include placeholder text like "commensurate with experience". Not present.
Now we need to preserve all substantive information. Let's extract details.
First, About the role: from Position Overview paragraph(s):
"As a Document Controls Engineer, you will be responsible for managing project documentation, workflows, and information systems supporting large-scale hyperscale data center and mission-critical infrastructure projects. You will ensure project records are organized, accurate, accessible, and maintained in accordance with contractual requirements, quality standards, and project procedures.
This role serves as a critical link between project management, engineering, procurement, quality, commissioning, field operations, customers, and subcontractors. You will support document control processes throughout the project lifecycle, ensuring information is captured, distributed, tracked, and archived effectively.
Success requires strong organizational capabilities, attention to detail, technical proficiency, and the ability to manage multiple priorities in a fast-paced project environment."
We'll put that as
maybe multiple paragraphs.
Responsibilities: combine Key Responsibilities and What You'll Do.
Key Responsibilities bullet list (actually sentences separated by periods). Let's list them:
- Manage project document control systems, procedures, workflows, and reporting processes.
- Coordinate the review, distribution, tracking, and retention of project documentation throughout the project lifecycle.
- Maintain engineering drawings, specifications, requests for information (RFIs), submittals, transmittals, correspondence, meeting minutes, and project records.
- Support project teams by ensuring timely access to accurate and current project information.
- Monitor document workflows to ensure compliance with project requirements, quality standards, and customer expectations.
- Support commissioning, turnover, and closeout activities through the organization and delivery of project documentation packages.
What You'll Do list:
- Manage document control activities supporting hyperscale data centers and mission-critical infrastructure projects.
- Coordinate document workflows between project management, engineering, procurement, quality, commissioning, owners, subcontractors, and vendors.
- Track RFIs, submittals, drawings, specifications, change documentation, and project correspondence.
- Maintain revision control and ensure project teams are working from current and approved project documents.
- Support project reporting activities and develop documentation status reports, logs, and metrics.
- Assist with commissioning documentation, turnover packages, O&M manuals, as-built documentation, and project closeout deliverables.
- Ensure project records are maintained in accordance with contractual requirements, company standards, and customer expectations.
- Support implementation and continuous improvement of document management processes and systems.
We can combine into a single list, maybe deduplicate similar items but we must preserve all substantive info; we can keep both but might be duplicate. Safer to keep both as separate list items; but we could combine to avoid duplication but still preserve info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we combine and remove duplicates, we might be summarizing away detail? Duplicates are same info repeated; removing duplicates is not losing info, just not repeating. That's acceptable. We'll produce a list with unique items.
Let's create list items:
- Manage project document control systems, procedures, workflows, and reporting processes.
- Coordinate the review, distribution, tracking, and retention of project documentation throughout the project lifecycle.
- Maintain engineering drawings, specifications, requests for information (RFIs), submittals, transmittals, correspondence, meeting minutes, and project records.
- Support project teams by ensuring timely access to accurate and current project information.
- Monitor document workflows to ensure compliance with project requirements, quality standards, and customer expectations.
- Support commissioning, turnover, and closeout activities through the organization and delivery of project documentation packages.
- Manage document control activities supporting hyperscale data centers and mission-critical infrastructure projects. (similar to first but maybe redundant)
- Coordinate document workflows between project management, engineering, procurement, quality, commissioning, owners, subcontractors, and vendors.
- Track RFIs, submittals, drawings, specifications, change documentation, and project correspondence.
- Maintain revision control and ensure project teams are working from current and approved project documents.
- Support project reporting activities and develop documentation status reports, logs, and metrics.
- Assist with commissioning documentation, turnover packages, O&M manuals, as-built documentation, and project closeout deliverables.
- Ensure project records are maintained in accordance with contractual requirements, company standards, and customer expectations.
- Support implementation and continuous improvement of document management processes and systems.
We can keep all; it's fine.
Requirements: from What It Takes:
"Bachelor's degree in Construction Management, Engineering, Project Controls, Business Administration, Information Management, or a related discipline and 3+ years of document control, project controls, engineering, construction administration, or related experience, or an equivalent combination of education and experience.
Experience supporting large construction, EPC, mission-critical, data center, power, industrial, or infrastructure projects.
Experience managing engineering drawings, specifications, RFIs, submittals, transmittals, meeting minutes, contract documents, and project records.
Understanding of project execution processes, engineering workflows, procurement activities, commissioning requirements, and project closeout procedures.
Experience maintaining document control systems and records management processes throughout the project lifecycle.
Proficiency with Microsoft Office Suite and document management platforms such as Autodesk Construction Cloud, Procore, Aconex, SharePoint, Unifier, InEight, Prolog, or similar systems.
Ability to organize large volumes of documentation while maintaining accuracy and meeting deadlines.
Strong analytical, organizational, communication, and problem-solving skills.
Ability to work effectively with project teams, customers, subcontractors, vendors, and engineering partners.
Experience supporting commissioning documentation, turnover packages, and as-built documentation is preferred.
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 need to separate travel into Schedule maybe. But travel is also a requirement. We'll put travel under Schedule section.
Thus Requirements will include everything except travel ability.
We'll list as
- .
Skills: Could be proficiency with MS Office, document management platforms, analytical, organizational, communication, problem-solving, ability to work with teams, etc. But many of those are already in Requirements. To avoid duplication, we could treat Skills as the technical proficiencies: MS Office, document management platforms (Autodesk Construction Cloud, Procore, Aconex, SharePoint, Unifier, InEight, Prolog, etc.), ability to organize large volumes, etc. But we risk duplication. However instruction says prefer few substantive sections over many thin ones. Maybe we can combine Requirements and Qualifications and Skills into one section? But headings are prescribed; we can still include only those we need. Perhaps we can include Requirements and Benefits and Schedule only, and put other info under Responsibilities and About the role. The "What It Takes" includes education/experience etc. That's definitely Requirements. We'll put that under Requirements.
Skills could be omitted if we feel it's thin. But we have specific technical proficiencies that could be considered Skills. However they are already in Requirements list. To avoid duplication, we could move those to Requirements and not have Skills section. That's okay.
Qualifications: Could be omitted.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
Check if Benefits section has real specific content: Yes, list of benefits.
Schedule: travel approx 75% etc.
Now we need to ensure we don't include boilerplate like "AA/EOE/M/W/Vet/Disability" and privacy policy link. Remove.
Also remove "Why Michels Infrastructure Solutions, Inc.?" and "Why You?" sections as they are not required headings; but we could incorporate some of that content into Benefits or About the role? The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Why Michels..." is not boilerplate but it's promotional; but we are not required to include it under any heading. Since we only output sections for headings we choose, we can omit that content entirely? But we must preserve ALL substantive information. If we omit that content, we are losing substantive info. However we could incorporate some of that into Benefits or About the role? The "Why Michel
About the role
with paragraphs. We have "Key Responsibilities" and then "What You'll Do" which are responsibilities. So we can combine into Responsibilities section with- .
We have "What You'll Do" bullet list (actually sentences). We'll treat as list items.
We have "Why Michels Infrastructure Solutions, Inc.?" which is about company benefits/culture. Could be part of Benefits? But we have separate Benefits section later. The "Why Michels..." includes things like training investment, etc. Might be considered Benefits or "Why you?".
We have "Comprehensive Benefits Package" list.
We have "Why You?" which is about candidate traits; could be part of Qualifications or Skills? Might be considered "Qualifications"? But we have separate "What It Takes" which lists requirements: education, experience, etc. That's Requirements/Qualifications.
We have "What It Takes" which includes education, experience, etc. That's Requirements/Qualifications.
We have "Ability to travel approximately 75%..." which is Schedule/Travel. So we can put under Schedule section.
We have Pay: not mentioned. So we should NOT include Pay section because no specific content.
We have Benefits: we have list.
We have Skills: maybe we can extract from "What It Takes" like proficiency with Microsoft Office Suite and document management platforms etc. Could be Skills section.
But we need to avoid thin sections. Prefer few substantive sections.
We could combine Requirements and Qualifications into one section? But headings are predefined; we must use those exact headings if we include them. We can choose to include only those sections that have substantive content.
Let's list possible sections:
- About the role: from Position Overview paragraph(s). Good.
- Responsibilities: from Key Responsibilities and What You'll Do.
- Requirements: from What It Takes (education, experience, etc.) plus maybe travel ability? Travel could be Schedule.
- Qualifications: maybe overlapping with Requirements; but we could decide to include only Requirements and not Qualifications to avoid duplication. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using both Requirements and Qualifications if content distinct. But we should avoid thin sections. We could put education/experience under Requirements, and skills/technical proficiencies under Skills. Qualifications could be left out if not distinct.
- Skills: proficiency with MS Office, document management platforms, analytical, organizational, communication, problem-solving, ability to work with teams, etc.
- Benefits: Comprehensive Benefits Package list.
- Schedule: travel approx 75% etc.
- Pay: not present, omit.
We must ensure we don't include placeholder text like "commensurate with experience". Not present.
Now we need to preserve all substantive information. Let's extract details.
First, About the role: from Position Overview paragraph(s):
"As a Document Controls Engineer, you will be responsible for managing project documentation, workflows, and information systems supporting large-scale hyperscale data center and mission-critical infrastructure projects. You will ensure project records are organized, accurate, accessible, and maintained in accordance with contractual requirements, quality standards, and project procedures.
This role serves as a critical link between project management, engineering, procurement, quality, commissioning, field operations, customers, and subcontractors. You will support document control processes throughout the project lifecycle, ensuring information is captured, distributed, tracked, and archived effectively.
Success requires strong organizational capabilities, attention to detail, technical proficiency, and the ability to manage multiple priorities in a fast-paced project environment."
We'll put that as
maybe multiple paragraphs. Responsibilities: combine Key Responsibilities and What You'll Do. Key Responsibilities bullet list (actually sentences separated by periods). Let's list them: - Manage project document control systems, procedures, workflows, and reporting processes. - Coordinate the review, distribution, tracking, and retention of project documentation throughout the project lifecycle. - Maintain engineering drawings, specifications, requests for information (RFIs), submittals, transmittals, correspondence, meeting minutes, and project records. - Support project teams by ensuring timely access to accurate and current project information. - Monitor document workflows to ensure compliance with project requirements, quality standards, and customer expectations. - Support commissioning, turnover, and closeout activities through the organization and delivery of project documentation packages. What You'll Do list: - Manage document control activities supporting hyperscale data centers and mission-critical infrastructure projects. - Coordinate document workflows between project management, engineering, procurement, quality, commissioning, owners, subcontractors, and vendors. - Track RFIs, submittals, drawings, specifications, change documentation, and project correspondence. - Maintain revision control and ensure project teams are working from current and approved project documents. - Support project reporting activities and develop documentation status reports, logs, and metrics. - Assist with commissioning documentation, turnover packages, O&M manuals, as-built documentation, and project closeout deliverables. - Ensure project records are maintained in accordance with contractual requirements, company standards, and customer expectations. - Support implementation and continuous improvement of document management processes and systems. We can combine into a single list, maybe deduplicate similar items but we must preserve all substantive info; we can keep both but might be duplicate. Safer to keep both as separate list items; but we could combine to avoid duplication but still preserve info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we combine and remove duplicates, we might be summarizing away detail? Duplicates are same info repeated; removing duplicates is not losing info, just not repeating. That's acceptable. We'll produce a list with unique items. Let's create list items: - Manage project document control systems, procedures, workflows, and reporting processes. - Coordinate the review, distribution, tracking, and retention of project documentation throughout the project lifecycle. - Maintain engineering drawings, specifications, requests for information (RFIs), submittals, transmittals, correspondence, meeting minutes, and project records. - Support project teams by ensuring timely access to accurate and current project information. - Monitor document workflows to ensure compliance with project requirements, quality standards, and customer expectations. - Support commissioning, turnover, and closeout activities through the organization and delivery of project documentation packages. - Manage document control activities supporting hyperscale data centers and mission-critical infrastructure projects. (similar to first but maybe redundant) - Coordinate document workflows between project management, engineering, procurement, quality, commissioning, owners, subcontractors, and vendors. - Track RFIs, submittals, drawings, specifications, change documentation, and project correspondence. - Maintain revision control and ensure project teams are working from current and approved project documents. - Support project reporting activities and develop documentation status reports, logs, and metrics. - Assist with commissioning documentation, turnover packages, O&M manuals, as-built documentation, and project closeout deliverables. - Ensure project records are maintained in accordance with contractual requirements, company standards, and customer expectations. - Support implementation and continuous improvement of document management processes and systems. We can keep all; it's fine. Requirements: from What It Takes: "Bachelor's degree in Construction Management, Engineering, Project Controls, Business Administration, Information Management, or a related discipline and 3+ years of document control, project controls, engineering, construction administration, or related experience, or an equivalent combination of education and experience. Experience supporting large construction, EPC, mission-critical, data center, power, industrial, or infrastructure projects. Experience managing engineering drawings, specifications, RFIs, submittals, transmittals, meeting minutes, contract documents, and project records. Understanding of project execution processes, engineering workflows, procurement activities, commissioning requirements, and project closeout procedures. Experience maintaining document control systems and records management processes throughout the project lifecycle. Proficiency with Microsoft Office Suite and document management platforms such as Autodesk Construction Cloud, Procore, Aconex, SharePoint, Unifier, InEight, Prolog, or similar systems. Ability to organize large volumes of documentation while maintaining accuracy and meeting deadlines. Strong analytical, organizational, communication, and problem-solving skills. Ability to work effectively with project teams, customers, subcontractors, vendors, and engineering partners. Experience supporting commissioning documentation, turnover packages, and as-built documentation is preferred. 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 need to separate travel into Schedule maybe. But travel is also a requirement. We'll put travel under Schedule section. Thus Requirements will include everything except travel ability. We'll list as
- . Skills: Could be proficiency with MS Office, document management platforms, analytical, organizational, communication, problem-solving, ability to work with teams, etc. But many of those are already in Requirements. To avoid duplication, we could treat Skills as the technical proficiencies: MS Office, document management platforms (Autodesk Construction Cloud, Procore, Aconex, SharePoint, Unifier, InEight, Prolog, etc.), ability to organize large volumes, etc. But we risk duplication. However instruction says prefer few substantive sections over many thin ones. Maybe we can combine Requirements and Qualifications and Skills into one section? But headings are prescribed; we can still include only those we need. Perhaps we can include Requirements and Benefits and Schedule only, and put other info under Responsibilities and About the role. The "What It Takes" includes education/experience etc. That's definitely Requirements. We'll put that under Requirements. Skills could be omitted if we feel it's thin. But we have specific technical proficiencies that could be considered Skills. However they are already in Requirements list. To avoid duplication, we could move those to Requirements and not have Skills section. That's okay. Qualifications: Could be omitted. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Check if Benefits section has real specific content: Yes, list of benefits. Schedule: travel approx 75% etc. Now we need to ensure we don't include boilerplate like "AA/EOE/M/W/Vet/Disability" and privacy policy link. Remove. Also remove "Why Michels Infrastructure Solutions, Inc.?" and "Why You?" sections as they are not required headings; but we could incorporate some of that content into Benefits or About the role? The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Why Michels..." is not boilerplate but it's promotional; but we are not required to include it under any heading. Since we only output sections for headings we choose, we can omit that content entirely? But we must preserve ALL substantive information. If we omit that content, we are losing substantive info. However we could incorporate some of that into Benefits or About the role? The "Why Michel