PMO Project Manager (Data Center Construction)

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the job posting. First, we need to decide which sections are present. The posting includes: - Who We Are (company description) – not a section heading we need; we can ignore or maybe treat as About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should map content to these headings as appropriate. We need to avoid repeating job title as heading (the page already shows it). So we don't output a heading for the job title. We need to include sections only when posting has real, specific content. Let's extract content: About the role: Could be description of role: "The Project Management Office (PMO) Project Manager (Data Center Construction) is the PMO's embedded project management partner to the Pre-Construction and Construction functions..." That's description of role. So we can put that under

About the role

with paragraphs. Responsibilities: The "What You’ll Do" bullet list. That's responsibilities. Requirements: Could be "What We’re Looking For" list of experience etc. That's requirements. Qualifications: Might be similar to requirements; but we can treat "What We’re Looking For" as Qualifications? Actually they said "Qualifications" as a possible heading. We have both Requirements and Qualifications; we need to decide which content goes where. The posting includes "What We’re Looking For" which includes experience, knowledge, abilities, skills, certification. That could be both Requirements and Qualifications. We could split: Requirements: experience, knowledge, ability to take ambiguous initiatives, facilitate cross-functional teams, stakeholder-management, problem-solving, experience with Jira, communication skills. Qualifications: PMP or equivalent certification preferred. Or we could combine. But we need to avoid thin sections. Perhaps better to have one section "Requirements" containing all that, and skip Qualifications if not enough distinct content. However we have "Skills" heading possible; we could put skills there. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those with real content. We could include About the role, Responsibilities, Requirements, Benefits. Possibly Skills if we have distinct skills list. The "What We’re Looking For" includes skills like stakeholder-management, problem-solving, communication, etc. Could be Skills. But we also have experience requirements. Might be better to have Requirements (experience) and Skills (specific skills). Let's see. We have "What We Offer (US)" which includes benefits: Competitive base salary and discretionary bonus, Flexible Time Off, Company paid Holidays, Company paid sick leave, Company-paid health and protective benefits, 3% 401(k) company contribution, Generous paid Parental Leave, Free virtual coaching and counseling sessions through Ginger, Opportunities to learn about the Crypto industry, Free daily snacks in-office, Smart, entrepreneurial, and fun colleagues, Employee Resource Groups. Also note "Benefits may vary depending on location." So we have Benefits section. Pay: The posting mentions "Competitive base salary and discretionary bonus" but not specific numbers. That's pay info. However instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive base salary and discretionary bonus, which is pay info. So we can include Pay section with that sentence. However we also have Benefits section that includes many items; we could combine Pay and Benefits? But they are separate headings. The instruction says prefer a few substantive sections over many thin ones. If we split Pay and Benefits, we might have two thin sections. But we have substantive content for both: Pay: competitive base salary and discretionary bonus. Benefits: list of items. Could be okay. Schedule: Not mentioned. So we omit Schedule. We also need to include metadata like Job ID etc? Not needed; we drop. We need to remove boilerplate: EEO etc. Remove that. We need to preserve all substantive information; do not invent or summarize away detail. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus: - About the role: prose paragraphs (maybe multiple). We'll put the description in

  . - Responsibilities: list of duties from "What You’ll Do". We'll make

  • each bullet. - Requirements: list from "What We’re Looking For" maybe split into experience and skills? But we can make a single list. - Skills: maybe we could separate but risk thin. Let's see if we can make a substantive Skills section: The posting includes "Strong ability to take ambiguous or complex initiatives and create structured execution plans." etc. Those are skills. But they are also in Requirements. Might be duplication. Better to follow typical structure: About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. We need to ensure we don't create empty sections. Let's extract precise text. About the role: The paragraph starting "The Project Management Office (PMO) Project Manager (Data Center Construction) is the PMO's embedded project management partner to the Pre-Construction and Construction functions." Continue until "...while allowing technical leaders to remain focused on their areas of expertise." That's the description. We need to preserve all substantive information; we can split into multiple paragraphs if needed but it's okay as one. Responsibilities: The bullet list under "What You’ll Do". Let's capture each bullet: - Partner closely with Pre-Construction and Construction leadership to understand priorities, upcoming work, constraints, and cross-functional needs. - Translate complex initiatives into clearly defined workstreams, tasks, milestones, owners, dependencies, and decision points. - Establish and maintain visibility into current and upcoming work through the PMO project management systems and reporting processes. - Identify dependencies between Pre-Construction / Construction and Site Development, Operations, Technology, EHS, Procurement, Finance, Legal, and other functions. - Facilitate the cross-functional meetings required to move work forward, with clear objectives, ownership, decisions, action items, and follow-through. - Connect department heads and functional stakeholders when work has broader organizational impacts or requires decisions across teams. - Identify risks, stalled work, unclear ownership, resource constraints, or competing priorities and drive the appropriate conversations toward resolution. - Escalate material risks and decisions to department leadership, the Head of PMO, or business leadership when appropriate. - Partner with department leadership on prioritization and sequencing when multiple initiatives compete for resources or have interdependent timelines. - Support capacity and resourcing discussions by providing visibility into upcoming work, workload, dependencies, and potential constraints. - Ensure required Procurement, Finance, Legal, and other support-function processes are incorporated into project plans and initiated at the appropriate time. - Improve communication between Pre-Construction / Construction and other departments by ensuring relevant information reaches the appropriate stakeholders and other embedded PMO PMs. - Provide objective facilitation when priorities, ownership, timelines, or expectations conflict across departments. - Track execution against agreed business priorities and provide leadership with clear visibility into progress, risks, decisions, and blockers. - Partner with the Head of PMO and other embedded PMO PMs to consistently apply PMO standards, tools, processes, and reporting practices. That's many bullets. Requirements: The bullet list under "What We’re Looking For". Let's capture: - 5+ years of experience in project management, program management, construction, infrastructure, engineering, development, or a related environment. - Experience coordinating complex initiatives involving multiple departments, technical teams, and business stakeholders. - Working knowledge of pre-construction and construction processes sufficient to understand dependencies, sequencing, terminology, and business impacts. - Strong ability to take ambiguous or complex initiatives and create structured execution plans. - Demonstrated ability to facilitate cross-functional teams and create accountability without direct authority. - Strong stakeholder-management skills and ability to communicate effectively with technical teams, functional leaders, and executives. - Strong problem-solving skills with an ability to identify organizational gaps, dependencies, and risks before they affect execution. - Experience with project/work management platforms such as Jira and related collaboration and documentation tools. - Strong written and verbal communication and executive reporting skills. - PMP or equivalent certification preferred. We could treat the last as qualification but we can include in Requirements. Benefits: Under "What We Offer (US)". List: - Competitive base salary and discretionary bonus - Flexible Time Off (i.e. unlimited paid vacation days) - Company paid Holidays (11) - Company paid sick leave - Company-paid health and protective benefits for employees, partners, and other dependents - 3% 401(k) company contribution - Generous paid Parental Leave - Free virtual coaching and counseling sessions through Ginger - Opportunities to learn about the Crypto industry - Free daily snacks in-office - Smart, entrepreneurial, and fun colleagues - Employee Resource Groups - Benefits may vary depending on location. We need to decide if we separate Pay and Benefits. The first item "Competitive base salary and discretionary bonus" is pay. The rest are benefits. We could make Pay section with that sentence, Benefits section with the rest. However the instruction says prefer a few substantive sections over many thin ones. Pay section would be just one sentence; might be thin. But we could combine Pay and Benefits into a single Benefits section that includes pay as first bullet. However the headings list includes Benefits and Pay separate; we could choose to only include Benefits and not Pay, as pay is part of benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay, but we could still include it under Benefits. However they said "Prefer a few substantive sections over many thin ones." So maybe we combine into Benefits and omit Pay heading. That seems reasonable. Thus sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we don't include Schedule or Pay. Now we need to output only HTML fragment, no /, no markdown. We'll output:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Benefits

    • ...
    ...
    Make sure to preserve all substantive information. Do not omit any bullet. Check for any duplicated lines: none. We need to remove boilerplate: EEO etc. Already omitted. Check that we didn't include job title heading. Now craft the HTML. We need to be careful with escaping any HTML special characters like &, <, >. The text includes parentheses, commas, etc. No need to escape unless we have < or >. There's no HTML tags inside. The phrase "i.e." includes periods; fine. We need to ensure we don't accidentally include stray characters. Let's construct. About the role paragraph: Combine the two paragraphs? Actually there is a paragraph describing role and then a paragraph about "The role gives department leadership a partner..." We'll combine into one

    maybe with two sentences. Better to keep as one

    containing both sentences. Text: "The Project Management Office (PMO) Project Manager (Data Center Construction) is the PMO's embedded project management partner to the Pre-Construction and Construction functions. This is not a traditional construction PM role responsible for replacing the technical ownership of the Pre-Construction or Construction teams. Department leaders and subject matter experts retain ownership and accountability for their work. Instead, the PM provides the cross-functional coordination, structure, visibility, and accountability required to move complex initiatives forward across departmental boundaries. Pre-construction and construction activities inherently depend on multiple teams - including Site Development, Operations, Technology, EHS, Finance, Proc