Development Project Manager (Data Center Construction OFCI)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience", "not specified", etc. So we need to parse the posting.
The posting includes:
- Who We Are: description (multiple paragraphs). This could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have:
- Who We Are: company description. Could be "About the role"? Not exactly. But maybe we treat as "About the role" (though it's about company). However instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings? It says use for section headings (e.g. ...). Likely we should use those headings when applicable. So we need sections: About the role (maybe company overview), Responsibilities (What You Will Do), Requirements (What You Will Need To Be Successful), Qualifications (maybe same as Requirements?), Skills (Other Key Skills), Benefits (The Perks), Pay (none), Schedule (none). We should not create Pay or Schedule sections if not present.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO statements, legal, accommodation request, etc. Also remove duplicated lines: "Who We Are:" appears twice; we need to combine? Probably just keep once.
We need to output only HTML fragment.
Let's extract substantive content:
Company description (Who We Are): multiple paragraphs. We'll combine into a
maybe multiple
s.
Then "Who You Are And The Impact You Will Have:" heading then description of role: "The Development Project Manager (Data Center Construction OFCI) is primarily responsible for leading and managing the design, preconstruction and construction activities on a given project(s). The Project Manager will interact on a daily basis with Facilities, Contractors, Designers, Engineers, Commissioning Agents, Vendors, and Data Center Operations staff and should have both written and oral communication skills commensurate with this level of regular communication."
That's a prose description; we could put under About the role? Actually that's more role summary. Could be part of About the role.
Then "What You Will Do:" list of responsibilities (many bullet-like sentences). We need to turn each into
- inside
. They are separated by line breaks? The text is a long paragraph with sentences separated by spaces? Actually they are separated by line breaks? In the source they appear as separate sentences but not bullet. We'll treat each sentence as a duty. We need to preserve all detail; we can split by periods? But better to keep each line as separate - as they appear. However we need to avoid losing detail. We'll extract each responsibility as separate item.
List:
- Manage multiple projects on a campus(es) and maintain updated budgets, schedules, and status reports for each
- Create and communicate updates on development program & project status on a monthly basis suitable for executive level reviews.
- Effectively present information in a manner to support efficient decision making
- Work with QTS stakeholders, design, and construction teams to create a master development program for site(s), including a complete campus design solution and capital budget.
- Manage entitlement and permitting needs for each assigned site project(s)
- Implement and manage multi-phased site development plans to achieve time, budget, and quality standards in a predictable fashion.
- Continuously update a campus master plan to provide predictable statistics in a dynamic environment
- Write scopes of work for design, construction, commissioning services & participate in procurement and project cost estimates
- Evaluate and level pricing proposals for design, construction, and commissioning services
- Work closely with strategic procurement team on equipment procurement and delivery process
- Ensure appropriate submittals are coordinated with site stakeholders
- Monitor & create project budget / cost-to-date against overall project budget.
- Establish project schedules and manage teams to on-time completion
- Review and approve monthly pay applications from the contractors
- Review change order requests from contractors and negotiate pricing
- Establish site construction security procedures in conjunction with site security team
- Develop plans for product deployment and review / communicate plans with QTS staff involved
- Collaborate with Sales Engineers and Product teams to aid in custom deal solutioning for prospective clients within the applicable schedule and budget for an assigned location.
- Establish and maintain relationships serving as liaison with key QTS stakeholders
- Represent QTS Interests as leader in OAC meetings
- Create & build relationships that enhance QTS’s ability to be a leader in creating the World’s Most Valuable Data Center Real Estate
- Aid in due diligence efforts for potential new sites on an as-needed basis
- Work with the internal development team to enhance project management processes and protocols
That's many.
Then "What You Will Need To Be Successful (basic Qualifications):" list:
- Bachelor’s degree in Science or Engineering or equivalent professional experience
- Five or more years of professional experience in commercial construction practices and procedures, including management of Lump Sum, Construction Management @ Risk, and Design Build project delivery methods from conceptual development through procurement to close out
- Experience with Microsoft Office suite, specifically PowerPoint for use in communicating program updates to executive level, and Excel to create and maintain site program & individual project budgets
- Be able to travel as needed for the business
Then "Other Key Skills:" list:
- MBA, Masters in Engineering, Management, or related field desirable
- Experience with delivery of mission critical data center facilities
- Extensive experience with management of MEP trades
Then "The Perks (and these are just a few!):" list:
- Q-Rest Sabbatical
- Employee Stock Purchase Plan
- QTS scholarship for dependents
- Eagle Club Award Trip Eligibility
- Paid Volunteer and Floating days
- Tuition Assistance, Parental Leave and Military Leave Assistance
We need to output sections: About the role (maybe combine Who We Are and role summary), Responsibilities (the What You Will Do list), Requirements (basic Qualifications), Qualifications (maybe same as Requirements? but we could treat Requirements as basic qualifications, Qualifications as other key skills? Actually they said headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have:
- About the role: company overview + role summary.
- Responsibilities: What You Will Do list.
- Requirements: basic qualifications list.
- Qualifications: maybe other key skills? Or we could treat Qualifications as other key skills (MBA etc). But they also have Skills heading. Could treat Skills as other key skills? Actually they have both Qualifications and Skills. Might map: Qualifications = basic qualifications, Skills = other key skills. Or vice versa. Let's decide: Requirements = basic qualifications (must have). Qualifications = other key skills (desirable). Skills = maybe also other key skills? But we have only one set of "Other Key Skills". Could treat that as Skills. Then we might not need Qualifications separate. But we need to follow instruction: include a section ONLY when posting has real specific content. So we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits. We could omit Qualifications if we treat Requirements as qualifications. But they listed both Requirements and Qualifications as possible headings; we can choose to use Requirements for basic qualifications and Skills for other key skills. That seems logical.
Thus:
About the role
... company description + role summary ...
Responsibilities
- ... each responsibility ...
Requirements
- ... basic qualifications ...
Skills
- ... other key skills ...
Benefits
- ... perks ...
We should not include Pay or Schedule as not present.
We need to remove boilerplate: EEO statements, legal, accommodation request, etc. Also remove duplicated "Who We Are:" lines. Also remove "We conform to all the laws..." etc.
Now craft HTML.
We need to preserve all substantive information: ensure we don't lose any detail from company description, role summary, responsibilities, requirements, skills, benefits.
Let's write company description paragraphs:
Original:
"Who We Are: As a global leader in digital infrastructure, QTS designs, builds and operates advanced data centers that support strategic AI, cloud and digital transformation initiatives. We are driven by a mission to connect the world for good and our people make it possible. Every single day, the creativity, dedication and genuine care for our communities are what push us forward and make this a truly special place to be. Who We Are: It's pretty exciting to find yourself standing in a pivotal moment in time. It’s even more exciting to be out front leading it. At QTS, our world-class data centers are supporting our customers’ most strategic growth initiatives, positioning us at the forefront of today’s dynamic digital transformation. As AI and cloud drive the demand for increased speed, capacity and capability, QTS has emerged as the global digital infrastructure leader, committed to connecting the world for good. Driven by purpose and fueled by a spirit of innovation, QTS designs, builds and operates some of the world’s most advanced, forward-thinking data centers. QTS is a portfolio company of Blackstone. QTS is Powered by People. People who play a vital role in our company’s culture, innovation and growth. People who are committed to contributing to the communities where we operate and work. People who are knowledgeable, resourceful and mission driven. Together, we do great things."
We can combine into a few paragraphs. Remove duplicated "Who We Are:" phrase. We'll produce maybe two elements.
First paragraph: "As a global leader in digital infrastructure, QTS designs, builds and operates advanced data centers that support strategic AI, cloud and digital transformation initiatives. We are driven by a mission to connect the world for good and our people make it possible. Every single day, the creativity, dedication and genuine care for our communities are what push us forward and make this a truly special place to be."
Second paragraph: "It's pretty exciting to find yourself standing in a pivotal moment in time. It’s even more exciting to be out front leading it. At QTS, our world-class data centers are supporting our customers’ most strategic growth initiatives, positioning us at the forefront of today’s dynamic digital transformation. As AI and cloud drive the demand for increased speed, capacity and capability, QTS has emerged as the global digital infrastructure leader, committed to connecting the world for good. Driven by purpose and fueled by a spirit of innovation, QTS designs, builds and operates some of the world’s most advanced, forward-thinking data centers. QTS is a portfolio company of Blackstone. QTS is Powered by People. People who play a vital role in our company’s culture, innovation and growth. People who are committed to contributing to the communities where we operate and work. People who are knowledgeable, resourceful and mission driven. Together, we do great things."
Then role summary: "The Development Project Manager (Data Center Construction OFCI) is primarily responsible for leading and managing the design, preconstruction and construction activities on a given project(s). The Project Manager will interact on a daily basis with Facilities, Contractors, Designers, Engineers, Commissioning Agents, Vendors, and Data Center Operations staff and should have both written and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience", "not specified", etc. So we need to parse the posting. The posting includes: - Who We Are: description (multiple paragraphs). This could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - Who We Are: company description. Could be "About the role"? Not exactly. But maybe we treat as "About the role" (though it's about company). However instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings? It says use for section headings (e.g. ...). Likely we should use those headings when applicable. So we need sections: About the role (maybe company overview), Responsibilities (What You Will Do), Requirements (What You Will Need To Be Successful), Qualifications (maybe same as Requirements?), Skills (Other Key Skills), Benefits (The Perks), Pay (none), Schedule (none). We should not create Pay or Schedule sections if not present.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO statements, legal, accommodation request, etc. Also remove duplicated lines: "Who We Are:" appears twice; we need to combine? Probably just keep once.
We need to output only HTML fragment.
Let's extract substantive content:
Company description (Who We Are): multiple paragraphs. We'll combine into a
maybe multiple
s. Then "Who You Are And The Impact You Will Have:" heading then description of role: "The Development Project Manager (Data Center Construction OFCI) is primarily responsible for leading and managing the design, preconstruction and construction activities on a given project(s). The Project Manager will interact on a daily basis with Facilities, Contractors, Designers, Engineers, Commissioning Agents, Vendors, and Data Center Operations staff and should have both written and oral communication skills commensurate with this level of regular communication." That's a prose description; we could put under About the role? Actually that's more role summary. Could be part of About the role. Then "What You Will Do:" list of responsibilities (many bullet-like sentences). We need to turn each into
- . They are separated by line breaks? The text is a long paragraph with sentences separated by spaces? Actually they are separated by line breaks? In the source they appear as separate sentences but not bullet. We'll treat each sentence as a duty. We need to preserve all detail; we can split by periods? But better to keep each line as separate
- as they appear. However we need to avoid losing detail. We'll extract each responsibility as separate item.
List:
- Manage multiple projects on a campus(es) and maintain updated budgets, schedules, and status reports for each
- Create and communicate updates on development program & project status on a monthly basis suitable for executive level reviews.
- Effectively present information in a manner to support efficient decision making
- Work with QTS stakeholders, design, and construction teams to create a master development program for site(s), including a complete campus design solution and capital budget.
- Manage entitlement and permitting needs for each assigned site project(s)
- Implement and manage multi-phased site development plans to achieve time, budget, and quality standards in a predictable fashion.
- Continuously update a campus master plan to provide predictable statistics in a dynamic environment
- Write scopes of work for design, construction, commissioning services & participate in procurement and project cost estimates
- Evaluate and level pricing proposals for design, construction, and commissioning services
- Work closely with strategic procurement team on equipment procurement and delivery process
- Ensure appropriate submittals are coordinated with site stakeholders
- Monitor & create project budget / cost-to-date against overall project budget.
- Establish project schedules and manage teams to on-time completion
- Review and approve monthly pay applications from the contractors
- Review change order requests from contractors and negotiate pricing
- Establish site construction security procedures in conjunction with site security team
- Develop plans for product deployment and review / communicate plans with QTS staff involved
- Collaborate with Sales Engineers and Product teams to aid in custom deal solutioning for prospective clients within the applicable schedule and budget for an assigned location.
- Establish and maintain relationships serving as liaison with key QTS stakeholders
- Represent QTS Interests as leader in OAC meetings
- Create & build relationships that enhance QTS’s ability to be a leader in creating the World’s Most Valuable Data Center Real Estate
- Aid in due diligence efforts for potential new sites on an as-needed basis
- Work with the internal development team to enhance project management processes and protocols
That's many.
Then "What You Will Need To Be Successful (basic Qualifications):" list:
- Bachelor’s degree in Science or Engineering or equivalent professional experience
- Five or more years of professional experience in commercial construction practices and procedures, including management of Lump Sum, Construction Management @ Risk, and Design Build project delivery methods from conceptual development through procurement to close out
- Experience with Microsoft Office suite, specifically PowerPoint for use in communicating program updates to executive level, and Excel to create and maintain site program & individual project budgets
- Be able to travel as needed for the business
Then "Other Key Skills:" list:
- MBA, Masters in Engineering, Management, or related field desirable
- Experience with delivery of mission critical data center facilities
- Extensive experience with management of MEP trades
Then "The Perks (and these are just a few!):" list:
- Q-Rest Sabbatical
- Employee Stock Purchase Plan
- QTS scholarship for dependents
- Eagle Club Award Trip Eligibility
- Paid Volunteer and Floating days
- Tuition Assistance, Parental Leave and Military Leave Assistance
We need to output sections: About the role (maybe combine Who We Are and role summary), Responsibilities (the What You Will Do list), Requirements (basic Qualifications), Qualifications (maybe same as Requirements? but we could treat Requirements as basic qualifications, Qualifications as other key skills? Actually they said headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have:
- About the role: company overview + role summary.
- Responsibilities: What You Will Do list.
- Requirements: basic qualifications list.
- Qualifications: maybe other key skills? Or we could treat Qualifications as other key skills (MBA etc). But they also have Skills heading. Could treat Skills as other key skills? Actually they have both Qualifications and Skills. Might map: Qualifications = basic qualifications, Skills = other key skills. Or vice versa. Let's decide: Requirements = basic qualifications (must have). Qualifications = other key skills (desirable). Skills = maybe also other key skills? But we have only one set of "Other Key Skills". Could treat that as Skills. Then we might not need Qualifications separate. But we need to follow instruction: include a section ONLY when posting has real specific content. So we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits. We could omit Qualifications if we treat Requirements as qualifications. But they listed both Requirements and Qualifications as possible headings; we can choose to use Requirements for basic qualifications and Skills for other key skills. That seems logical.
Thus:
About the role
... company description + role summary ...
Responsibilities
- ... each responsibility ...
Requirements
- ... basic qualifications ...
Skills
- ... other key skills ...
Benefits
- ... perks ...
elements. First paragraph: "As a global leader in digital infrastructure, QTS designs, builds and operates advanced data centers that support strategic AI, cloud and digital transformation initiatives. We are driven by a mission to connect the world for good and our people make it possible. Every single day, the creativity, dedication and genuine care for our communities are what push us forward and make this a truly special place to be." Second paragraph: "It's pretty exciting to find yourself standing in a pivotal moment in time. It’s even more exciting to be out front leading it. At QTS, our world-class data centers are supporting our customers’ most strategic growth initiatives, positioning us at the forefront of today’s dynamic digital transformation. As AI and cloud drive the demand for increased speed, capacity and capability, QTS has emerged as the global digital infrastructure leader, committed to connecting the world for good. Driven by purpose and fueled by a spirit of innovation, QTS designs, builds and operates some of the world’s most advanced, forward-thinking data centers. QTS is a portfolio company of Blackstone. QTS is Powered by People. People who play a vital role in our company’s culture, innovation and growth. People who are committed to contributing to the communities where we operate and work. People who are knowledgeable, resourceful and mission driven. Together, we do great things." Then role summary: "The Development Project Manager (Data Center Construction OFCI) is primarily responsible for leading and managing the design, preconstruction and construction activities on a given project(s). The Project Manager will interact on a daily basis with Facilities, Contractors, Designers, Engineers, Commissioning Agents, Vendors, and Data Center Operations staff and should have both written and