VDC Project Manager
Comfort Systems USA · Grand Rapids, MI · 1 mo ago
Project ManagementFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro: "Amteck, a nationally recognized Top 50 Electrical Design-Build Contractor, is redefining what it means to deliver excellence in electrical construction. With decades of experience and a reputation built on a people-first culture, safety, integrity, innovation, and customer satisfaction, we’re proud to be at the forefront of the industry. Our team is expanding, and we are now seeking a Virtual Design & Construction (VDC) Project Manager to drive excellence across a range of electrical design-build projects."
That's about the role.
- "The VDC Project Manager leads the planning, execution, and oversight of Virtual Design and Construction (VDC) initiatives across construction projects. This position is eligible to be fully remote or to be based out of our Lexington, KY headquarters or our Greenville, SC office."
That's location/remote info.
- "Key Responsibilities" then bullet list (but not using
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro: "Amteck, a nationally recognized Top 50 Electrical Design-Build Contractor, is redefining what it means to deliver excellence in electrical construction. With decades of experience and a reputation built on a people-first culture, safety, integrity, innovation, and customer satisfaction, we’re proud to be at the forefront of the industry. Our team is expanding, and we are now seeking a Virtual Design & Construction (VDC) Project Manager to drive excellence across a range of electrical design-build projects."
That's about the role.
- "The VDC Project Manager leads the planning, execution, and oversight of Virtual Design and Construction (VDC) initiatives across construction projects. This position is eligible to be fully remote or to be based out of our Lexington, KY headquarters or our Greenville, SC office."
That's location/remote info.
- "Key Responsibilities" then bullet list (but not using tags in source). We need to extract responsibilities.
List:
- Project Planning & Execution: Develop project-specific BIM execution plans, including Level of Detail (LOD) specifications, and BIM standards
- Project Schedule and BIM Hours Management: Review construction schedules periodically to make sure priorities are clear for BIM Team and time is being used effectively. Work closely with PMs/APMs and Work Package Coordinators
- Design and Construction Drawings Review: Review new drawings releases to assist in capturing changes that might affect the BIM efforts, helping to mitigate errors and rework in the field
- Communication and Collaboration: Maintaining relationships with stakeholders, facilitating communication, and ensuring project requirements are met
- Quality Assurance: Ensuring the accuracy and quality of 3D models and other VDC deliverables using tools like Navisworks, Liquid Cloud and Open Space
- Process Improvement: Helping in the implementation of best practices and developing project-specific VDC strategies
- VDC Management: Ensuring VDC workflows and standards are being applied effectively. Responsible for keeping Trello Blue Board up to date
- Installation Drawings Review and Management: Assisting in the review of installation drawings to ensure they meet Company standards and project requirements and submit them for approval
- Technology Implementation: Asist in evaluating and implementing new VDC technologies and workflows to improve project efficiency and productivity
- Model Setup: Assisting in setting up models for new projects
- "Skills & Qualifications" then list:
Understanding of BIM/VDC principles and workflows.
Experience in project planning and scheduling
Ability to effectively communicate with various stakeholders and facilitate collaboration
Ability to lead and mentor teams, enforce safety protocols, and foster a positive working environment
Knowledge of relevant industry standards and regulations
Excellent time management skills
Ability to work independently and as part of a team
Experience using 3D installation tracking software like Open Space and Assemble
Nice to have: proficiency with various software programs including Trello, Revit, Navisworks, Bluebeam, and Microsoft Office
- Then "Ready to build what’s next? Apply with us today!" (application instruction, remove)
- Then company history: "In 1977 Amteck was founded in Central Kentucky with the belief that growth only comes by listening and responding to both clients and employees. Four decades later, Amteck has grown from a small electrical contracting firm to a national leader in the design/build support electrical contracting industry. Amteck specializes in facility growth expansion initiatives of companies that operate in the manufacturing, industrial, process, food, and beverage, hospitality, healthcare, distribution facilities, and commercial and institutional sectors. The number one goal is the Safety of our Employees and maintaining our culture and core values: THE AMTECK WAY – SAFETY, QUALITY, & CUSTOMER SATISFACTION."
That's about the company, could be "About the company" but we only have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company info under About the role? Or maybe we can create an "About the company" but not allowed headings list. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should stick to those? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings. So we need to map content to those sections.
We have:
- About the role: intro paragraph(s) describing role and maybe location/remote eligibility.
- Responsibilities: list of responsibilities.
- Requirements: maybe the "Skills & Qualifications" list (but that includes skills and qualifications). Could split into Requirements and Qualifications and Skills? But we have separate headings for Requirements, Qualifications, Skills. We need to decide what goes where.
The posting has "Skills & Qualifications" heading with bullet list. Could treat that as Skills and Qualifications combined. But we have separate headings; we could put the list under Skills and maybe Qualifications empty? But we must not create empty sections. So we need to decide: maybe we treat the list as Skills, and Qualifications could be omitted if no distinct qualifications. However there are items like "Understanding of BIM/VDC principles and workflows." that's more knowledge/skill. "Experience in project planning and scheduling" is experience (qualification). "Ability to effectively communicate..." skill. "Ability to lead and mentor teams..." skill/leadership. "Knowledge of relevant industry standards and regulations" knowledge. "Excellent time management skills" skill. "Ability to work independently and as part of a team" skill. "Experience using 3D installation tracking software like Open Space and Assemble" experience/skill. "Nice to have: proficiency with various software programs including Trello, Revit, Navisworks, Bluebeam, and Microsoft Office" nice-to-have skill.
Thus we could put all under Skills (or Qualifications). But we have both headings available; we could split: Requirements could be the mandatory items (understanding, experience, ability to communicate, ability to lead, knowledge, time management, ability to work independently/team, experience with software). Qualifications could be the nice-to-have? Or maybe Requirements = mandatory, Qualifications = nice-to-have. Skills = maybe overlapping. But we need to avoid filler.
Better: Use Requirements for mandatory items, Qualifications for nice-to-have, Skills maybe not needed. But we have to include only sections with real content. Could do:
- About the role
- Responsibilities
- Requirements
- Qualifications
- Skills (maybe we can omit if we put all in Requirements/Qualifications). But we have both Requirements and Qualifications; we could put mandatory in Requirements, nice-to-have in Qualifications, and maybe Skills omitted.
But the instruction says use those headings as examples; we could also add other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those.
Thus we need to map content:
About the role: intro + location/remote.
Responsibilities: list.
Requirements: mandatory skills/experience.
Qualifications: nice-to-have.
Skills: maybe we could omit or combine with Requirements? But we need to avoid empty sections. Could we put Skills as a subsection of Requirements? Not needed.
Alternatively, we could put all skill-related items under Skills, and Requirements could be something like "Eligibility: fully remote or based in Lexington, KY or Greenville, SC". But that's location, not requirement.
Better: Use Requirements for the bullet list under Skills & Qualifications (mandatory). Use Qualifications for the nice-to-have. Omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications.
Check if any Benefits, Pay, Schedule mentioned: none. So we omit those.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit any detail.
We need to include location/remote eligibility in About the role.
We need to include the company history? That's substantive but not under any of the allowed headings. Could we put it under About the role as well? That would be about the company, not role. But we could include it as part of About the role? Might be stretching but we need to preserve all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include company history somewhere. If we don't have a heading for it, we could include it as a paragraph under About the role (maybe as a second paragraph). That would still preserve it. It's not invented; it's just placed under a heading that may not be perfect but allowed.
Alternatively, we could add a heading "About the company" but not in the list; risk of violating 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 an exhaustive list. So we could add other headings if needed. But to be safe, we could add About the company heading. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those.
Thus we place company history under About the role as a second paragraph.
Now we need to format lists with - . For responsibilities and requirements/qualifications.
We need to ensure we don't repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We already removed "Ready to build what’s next? Apply with us today!" and maybe the "Apply with us today!" line.
Also remove duplicated lines? Not seeing duplicates.
Now produce HTML fragment.
Structure:
About the role
Amteck, a nationally recognized Top 50 Electrical Design-Build Contractor, is redefining what it means to deliver excellence in electrical construction. With decades of experience and a reputation built on a people-first culture, safety, integrity, innovation, and customer satisfaction, we’re proud to be at the forefront of the industry. Our team is expanding, and we are now seeking a Virtual Design & Construction (VDC) Project Manager to drive excellence across a range of electrical design-build projects. The VDC Project Manager leads the planning, execution, and oversight of Virtual Design and Construction (VDC) initiatives across construction projects. This position is eligible to be fully remote or to be based out of our Lexington, KY headquarters or our Greenville, SC office.
In 1977 Amteck was founded in Central Kentucky with the belief that growth only comes by listening and responding to both clients and employees. Four decades later, Amteck has grown from a small electrical contracting firm to a national leader in the design/build support electrical contracting industry. Amteck specializes in facility growth expansion initiatives of companies that operate in the manufacturing, industrial, process, food, and beverage, hospitality, healthcare, distribution facilities, and commercial and institutional sectors. The number one goal is the Safety of our Employees and maintaining our culture and core values: THE AMTECK WAY – SAFETY, QUALITY, & CUSTOMER SATISFACTION.
Responsibilities
- Project Planning & Execution: Develop project-specific BIM execution plans, including Level of Detail (LOD) specifications, and BIM standards
- Project Schedule and BIM
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should stick to those? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should only use those headings. So we need to map content to those sections.
We have:
- About the role: intro paragraph(s) describing role and maybe location/remote eligibility.
- Responsibilities: list of responsibilities.
- Requirements: maybe the "Skills & Qualifications" list (but that includes skills and qualifications). Could split into Requirements and Qualifications and Skills? But we have separate headings for Requirements, Qualifications, Skills. We need to decide what goes where.
The posting has "Skills & Qualifications" heading with bullet list. Could treat that as Skills and Qualifications combined. But we have separate headings; we could put the list under Skills and maybe Qualifications empty? But we must not create empty sections. So we need to decide: maybe we treat the list as Skills, and Qualifications could be omitted if no distinct qualifications. However there are items like "Understanding of BIM/VDC principles and workflows." that's more knowledge/skill. "Experience in project planning and scheduling" is experience (qualification). "Ability to effectively communicate..." skill. "Ability to lead and mentor teams..." skill/leadership. "Knowledge of relevant industry standards and regulations" knowledge. "Excellent time management skills" skill. "Ability to work independently and as part of a team" skill. "Experience using 3D installation tracking software like Open Space and Assemble" experience/skill. "Nice to have: proficiency with various software programs including Trello, Revit, Navisworks, Bluebeam, and Microsoft Office" nice-to-have skill.
Thus we could put all under Skills (or Qualifications). But we have both headings available; we could split: Requirements could be the mandatory items (understanding, experience, ability to communicate, ability to lead, knowledge, time management, ability to work independently/team, experience with software). Qualifications could be the nice-to-have? Or maybe Requirements = mandatory, Qualifications = nice-to-have. Skills = maybe overlapping. But we need to avoid filler.
Better: Use Requirements for mandatory items, Qualifications for nice-to-have, Skills maybe not needed. But we have to include only sections with real content. Could do:
- About the role
- Responsibilities
- Requirements
- Qualifications
- Skills (maybe we can omit if we put all in Requirements/Qualifications). But we have both Requirements and Qualifications; we could put mandatory in Requirements, nice-to-have in Qualifications, and maybe Skills omitted.
But the instruction says use those headings as examples; we could also add other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those.
Thus we need to map content:
About the role: intro + location/remote.
Responsibilities: list.
Requirements: mandatory skills/experience.
Qualifications: nice-to-have.
Skills: maybe we could omit or combine with Requirements? But we need to avoid empty sections. Could we put Skills as a subsection of Requirements? Not needed.
Alternatively, we could put all skill-related items under Skills, and Requirements could be something like "Eligibility: fully remote or based in Lexington, KY or Greenville, SC". But that's location, not requirement.
Better: Use Requirements for the bullet list under Skills & Qualifications (mandatory). Use Qualifications for the nice-to-have. Omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications.
Check if any Benefits, Pay, Schedule mentioned: none. So we omit those.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit any detail.
We need to include location/remote eligibility in About the role.
We need to include the company history? That's substantive but not under any of the allowed headings. Could we put it under About the role as well? That would be about the company, not role. But we could include it as part of About the role? Might be stretching but we need to preserve all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include company history somewhere. If we don't have a heading for it, we could include it as a paragraph under About the role (maybe as a second paragraph). That would still preserve it. It's not invented; it's just placed under a heading that may not be perfect but allowed.
Alternatively, we could add a heading "About the company" but not in the list; risk of violating 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 an exhaustive list. So we could add other headings if needed. But to be safe, we could add About the company heading. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those.
Thus we place company history under About the role as a second paragraph.
Now we need to format lists with - . For responsibilities and requirements/qualifications.
We need to ensure we don't repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We already removed "Ready to build what’s next? Apply with us today!" and maybe the "Apply with us today!" line.
Also remove duplicated lines? Not seeing duplicates.
Now produce HTML fragment.
Structure:
About the role
Amteck, a nationally recognized Top 50 Electrical Design-Build Contractor, is redefining what it means to deliver excellence in electrical construction. With decades of experience and a reputation built on a people-first culture, safety, integrity, innovation, and customer satisfaction, we’re proud to be at the forefront of the industry. Our team is expanding, and we are now seeking a Virtual Design & Construction (VDC) Project Manager to drive excellence across a range of electrical design-build projects. The VDC Project Manager leads the planning, execution, and oversight of Virtual Design and Construction (VDC) initiatives across construction projects. This position is eligible to be fully remote or to be based out of our Lexington, KY headquarters or our Greenville, SC office.
In 1977 Amteck was founded in Central Kentucky with the belief that growth only comes by listening and responding to both clients and employees. Four decades later, Amteck has grown from a small electrical contracting firm to a national leader in the design/build support electrical contracting industry. Amteck specializes in facility growth expansion initiatives of companies that operate in the manufacturing, industrial, process, food, and beverage, hospitality, healthcare, distribution facilities, and commercial and institutional sectors. The number one goal is the Safety of our Employees and maintaining our culture and core values: THE AMTECK WAY – SAFETY, QUALITY, & CUSTOMER SATISFACTION.
Responsibilities
- Project Planning & Execution: Develop project-specific BIM execution plans, including Level of Detail (LOD) specifications, and BIM standards
- Project Schedule and BIM
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those.
Thus we need to map content:
About the role: intro + location/remote.
Responsibilities: list.
Requirements: mandatory skills/experience.
Qualifications: nice-to-have.
Skills: maybe we could omit or combine with Requirements? But we need to avoid empty sections. Could we put Skills as a subsection of Requirements? Not needed.
Alternatively, we could put all skill-related items under Skills, and Requirements could be something like "Eligibility: fully remote or based in Lexington, KY or Greenville, SC". But that's location, not requirement.
Better: Use Requirements for the bullet list under Skills & Qualifications (mandatory). Use Qualifications for the nice-to-have. Omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications.
Check if any Benefits, Pay, Schedule mentioned: none. So we omit those.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit any detail.
We need to include location/remote eligibility in About the role.
We need to include the company history? That's substantive but not under any of the allowed headings. Could we put it under About the role as well? That would be about the company, not role. But we could include it as part of About the role? Might be stretching but we need to preserve all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include company history somewhere. If we don't have a heading for it, we could include it as a paragraph under About the role (maybe as a second paragraph). That would still preserve it. It's not invented; it's just placed under a heading that may not be perfect but allowed.
Alternatively, we could add a heading "About the company" but not in the list; risk of violating 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 an exhaustive list. So we could add other headings if needed. But to be safe, we could add About the company heading. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those.
Thus we place company history under About the role as a second paragraph.
Now we need to format lists with - . For responsibilities and requirements/qualifications.
We need to ensure we don't repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We already removed "Ready to build what’s next? Apply with us today!" and maybe the "Apply with us today!" line.
Also remove duplicated lines? Not seeing duplicates.
Now produce HTML fragment.
Structure:
About the role
Amteck, a nationally recognized Top 50 Electrical Design-Build Contractor, is redefining what it means to deliver excellence in electrical construction. With decades of experience and a reputation built on a people-first culture, safety, integrity, innovation, and customer satisfaction, we’re proud to be at the forefront of the industry. Our team is expanding, and we are now seeking a Virtual Design & Construction (VDC) Project Manager to drive excellence across a range of electrical design-build projects. The VDC Project Manager leads the planning, execution, and oversight of Virtual Design and Construction (VDC) initiatives across construction projects. This position is eligible to be fully remote or to be based out of our Lexington, KY headquarters or our Greenville, SC office.
In 1977 Amteck was founded in Central Kentucky with the belief that growth only comes by listening and responding to both clients and employees. Four decades later, Amteck has grown from a small electrical contracting firm to a national leader in the design/build support electrical contracting industry. Amteck specializes in facility growth expansion initiatives of companies that operate in the manufacturing, industrial, process, food, and beverage, hospitality, healthcare, distribution facilities, and commercial and institutional sectors. The number one goal is the Safety of our Employees and maintaining our culture and core values: THE AMTECK WAY – SAFETY, QUALITY, & CUSTOMER SATISFACTION.
Responsibilities
- Project Planning & Execution: Develop project-specific BIM execution plans, including Level of Detail (LOD) specifications, and BIM standards
- Project Schedule and BIM
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those.
Thus we place company history under About the role as a second paragraph.
Now we need to format lists with - . For responsibilities and requirements/qualifications.
We need to ensure we don't repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We already removed "Ready to build what’s next? Apply with us today!" and maybe the "Apply with us today!" line.
Also remove duplicated lines? Not seeing duplicates.
Now produce HTML fragment.
Structure:
About the role
Amteck, a nationally recognized Top 50 Electrical Design-Build Contractor, is redefining what it means to deliver excellence in electrical construction. With decades of experience and a reputation built on a people-first culture, safety, integrity, innovation, and customer satisfaction, we’re proud to be at the forefront of the industry. Our team is expanding, and we are now seeking a Virtual Design & Construction (VDC) Project Manager to drive excellence across a range of electrical design-build projects. The VDC Project Manager leads the planning, execution, and oversight of Virtual Design and Construction (VDC) initiatives across construction projects. This position is eligible to be fully remote or to be based out of our Lexington, KY headquarters or our Greenville, SC office.
In 1977 Amteck was founded in Central Kentucky with the belief that growth only comes by listening and responding to both clients and employees. Four decades later, Amteck has grown from a small electrical contracting firm to a national leader in the design/build support electrical contracting industry. Amteck specializes in facility growth expansion initiatives of companies that operate in the manufacturing, industrial, process, food, and beverage, hospitality, healthcare, distribution facilities, and commercial and institutional sectors. The number one goal is the Safety of our Employees and maintaining our culture and core values: THE AMTECK WAY – SAFETY, QUALITY, & CUSTOMER SATISFACTION.
Responsibilities
- Project Planning & Execution: Develop project-specific BIM execution plans, including Level of Detail (LOD) specifications, and BIM standards
- Project Schedule and BIM
About the role
Amteck, a nationally recognized Top 50 Electrical Design-Build Contractor, is redefining what it means to deliver excellence in electrical construction. With decades of experience and a reputation built on a people-first culture, safety, integrity, innovation, and customer satisfaction, we’re proud to be at the forefront of the industry. Our team is expanding, and we are now seeking a Virtual Design & Construction (VDC) Project Manager to drive excellence across a range of electrical design-build projects. The VDC Project Manager leads the planning, execution, and oversight of Virtual Design and Construction (VDC) initiatives across construction projects. This position is eligible to be fully remote or to be based out of our Lexington, KY headquarters or our Greenville, SC office.
In 1977 Amteck was founded in Central Kentucky with the belief that growth only comes by listening and responding to both clients and employees. Four decades later, Amteck has grown from a small electrical contracting firm to a national leader in the design/build support electrical contracting industry. Amteck specializes in facility growth expansion initiatives of companies that operate in the manufacturing, industrial, process, food, and beverage, hospitality, healthcare, distribution facilities, and commercial and institutional sectors. The number one goal is the Safety of our Employees and maintaining our culture and core values: THE AMTECK WAY – SAFETY, QUALITY, & CUSTOMER SATISFACTION.
Responsibilities
- Project Planning & Execution: Develop project-specific BIM execution plans, including Level of Detail (LOD) specifications, and BIM standards
- Project Schedule and BIM