Program Manager

We need to output HTML fragment with sections: About the role (summary), Responsibilities, Requirements (maybe Required Qualifications), Skills? The posting includes "Must Haves", "Key Responsibilities", "Governance, Tracking, and Follow-Through", "Risk, Issue, and Dependency Management", "Reporting and Leadership Visibility", "Tools, Documentation, and Operational Excellence". Also "Required Qualifications", "Preferred Qualifications". Also "How will contractor performance be measured?" maybe not needed? It's a detail but could be part of Responsibilities? It's about measurement; maybe we can include as a separate section? The instruction: include a section ONLY when posting has real, specific content for it. We have content for Responsibilities (multiple bullet-like paragraphs). We have Required Qualifications. We have Preferred Qualifications. We have Skills? Not explicit separate list but could be under Required Qualifications (proficiency with M365). We could have a Skills section if we extract. But better to keep sections: About the role (summary), Responsibilities, Required Qualifications, Preferred Qualifications. Also maybe "Tools, Documentation, and Operational Excellence" could be part of Responsibilities. The instruction: Prefer a few substantive sections over many thin ones. So we can combine similar items. We need to use

for section headings. Use

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

  for prose. We must not repeat job title. No Job ID. Remove boilerplate. So we need to extract substantive content. Let's parse the posting: - About Ascendion (company description) - we can ignore? It's not part of role specifics; but maybe we can include as About the company? Not required. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include About the role (summary). The company description maybe not needed; but we could include as a brief intro? It says "About Ascendion" then later "About the Role". The instruction: do NOT repeat the job title as a heading (the page already shows it). It doesn't forbid including company description, but we should focus on role. Probably we can include a short paragraph about the company under About the role? But better to follow headings: About the role (summary). Then Responsibilities (list). Then Requirements (maybe Required Qualifications). Then Preferred Qualifications (maybe as a separate section). Could also include Skills under Requirements. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. Let's extract the summary: Under "About the Role" there is a paragraph: "Summary: This Program/Project Manager will support the Lease Construction and Fitout Program. This role will support the Lease Delivery, Construction & Integration, Execution Operational Planning (EOP) team. The EOP team supports the project based execution teams on programs and initiatives to develop tools, runbooks, trainings, templates and sources of truths. This role is focused on operationalizing strategy into action through disciplined program and project management. The Program Manager will manage multiple concurrent workstreams, coordinate across cross-functional stakeholders, establish accountability, maintain visibility to progress and risk, and ensure commitments are followed through to completion. The successful candidate will be a proactive and highly organized program/project manager who is comfortable operating in a dynamic environment with multiple priorities. The individual must be able to investigate unfamiliar topics, identify the right stakeholders and information sources, develop an informed path forward, and know when to independently proceed versus when alignment or escalation is appropriate. Administrative and coordination activities are expected as part of the role to serve the broader objective of effective program governance, execution, accountability, and follow-through." That's the summary. Now Responsibilities: The posting has sections: "Key Responsibilities Program and Initiative Execution", then bullet-like sentences. Then "Governance, Tracking, and Follow-Through", then "Risk, Issue, and Dependency Management", then "Reporting and Leadership Visibility", then "Tools, Documentation, and Operational Excellence". Also later there is a paragraph "A typical day will involve..." which seems like more responsibilities. We need to capture all responsibilities as list items. Let's extract each bullet: From "Key Responsibilities Program and Initiative Execution": - Drive assigned programs, initiatives, and workstreams from planning through execution, implementation, and closeout. - Translate objectives into clear plans, milestones, owners, dependencies, deliverables, and target dates. - Manage multiple concurrent initiatives and recurring responsibilities while maintaining appropriate prioritization and visibility. - Establish clear accountability and proactively follow up with owners to ensure commitments and deliverables progress as planned. - Identify gaps, dependencies, or potential barriers early and take appropriate action to maintain progress. - Independently investigate questions or ambiguous requirements, gather relevant information, engage appropriate subject matter experts, and develop informed recommendations or proposed next steps. - Support regional and global initiatives, continuous improvement efforts, process standardization, training, and other EOP priorities. From "Governance, Tracking, and Follow-Through": - Maintain appropriate program and initiative governance to provide clear visibility into status, milestones, dependencies, risks, actions, and decisions. - Maintain program artifacts such as initiative trackers, action logs, schedules, documentation, status materials, meeting outputs, and supporting resources. - Ensure actions have clearly identified owners and target dates and remain engaged until commitments are completed or appropriately escalated. - Support EOP Rhythm of Business activities, including recurring program reviews, stakeholder forums, trainings, workshops, and other governance activities. - Support consistent adoption and maintenance of EOP processes, templates, tools, and documentation. - Administrative and coordination activities are expected as part of the role but should serve the broader objective of effective program governance, execution, accountability, and follow-through. From "Risk, Issue, and Dependency Management": - Proactively identify risks, issues, dependencies, and blockers that could affect program objectives or delivery. - Manage routine program risks and blockers by establishing appropriate ownership, next steps, and follow-up. - Surface material risks or decisions requiring leadership involvement in a timely manner, with sufficient context to support informed decision-making. - Maintain visibility to open issues and ensure they are tracked through resolution, mitigation, acceptance, or appropriate escalation. From "Reporting and Leadership Visibility": - Prepare clear, concise, and leadership-ready program reporting. - Consolidate information across workstreams into meaningful updates covering progress, milestones, accomplishments, risks/blockers, decisions needed, and upcoming actions. - Provide accurate and timely status information rather than relying solely on individual stakeholder updates. - Maintain sufficient supporting information and program artifacts to enable effective leadership review and decision-making. From "Tools, Documentation, and Operational Excellence": - Effectively use M 365 business productivity tools, including Excel, PowerPoint, SharePoint, Teams, and Outlook. - Learn and effectively use applicable internal tools, trackers, dashboards, SharePoint Lists, Power Apps, repositories, and reporting resources. - Support tools such as Tools for Success and other EOP resources as part of program execution and governance. - Identify opportunities to simplify, standardize, or improve existing processes and ways of working. - Support documentation maintenance, lessons learned, best-practice sharing, and continuous improvement activities. Then later "A typical day will involve driving the operational execution of multiple EOP programs and initiatives, participating in and facilitating a high volume of meetings and working sessions, coordinating across stakeholders, maintaining program governance, and ensuring decisions and commitments translate into action. Own the day-to-day operational management of the DCBM AMERS Tools for Success Power App, maintaining it as a reliable source of truth for key resources such as templates, checklists, reports, playbooks, and supporting guidance. Manage resource updates, access needs, requests, and stakeholder feedback. Drive assigned programs and initiatives from planning through execution, translating leadership strategy and direction into organized work plans, milestones, actions, and deliverables. Own program and initiative governance by maintaining trackers, monitoring progress, following up with accountable owners, identifying gaps, and ensuring commitments are driven to completion. Participate in and support a high volume of meetings, working sessions, and program forums across EOP and cross\-functional stakeholder groups. Effectively balance meeting commitments with ongoing program management and execution responsibilities. Produce timely, high-quality, and accurate meeting notes within 24 hours of assigned meetings. Synthesize discussions into clear documentation of key decisions, action items, owners, target dates, risks, dependencies, and unresolved topics. Manage the operational rhythm of key meetings and working sessions, including agenda development, stakeholder coordination, facilitation, documentation of decisions and actions, and post-meeting follow-through. Drive accountability following meetings and program reviews by translating discussions into clear actions and tracking commitments through completion or appropriate escalation. Provide Zlear program visibility through structured reporting that summarizes progress, accomplishments, upcoming milestones, risks, dependencies, blockers, and decisions needed for EOP leadership. Proactively identify and manage program risks, issues, and dependencies, resolving routine blockers where possible and escalating items requiring leadership guidance or decisions. Develop high-quality program documentation and communications, including process documentation, runbooks, templates, checklists, status reports, presentations, training materials, and formal communications. Partner with the Senior Program Manager to operationalize EOP priorities while independently driving assigned workstreams and maintaining appropriate leadership visibility. Coordinate with cross-functional partners and subject matter experts to gather inputs, resolve dependencies, advance deliverables, and drive actions to closure. Identify opportunities to improve how work is executed, including simplifying processes, strengthening governance, improving documentation, and increasing consistency across EOP programs and initiatives." These are also responsibilities; many overlap with earlier lists but we should include them to preserve all substantive info. However we must avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication but we should keep all. However duplication may be okay but could be considered redundant. Better to combine unique items, but we risk losing some detail if we deduplicate. Safer to include all items as they appear, even if some repeat. But we can group them under Responsibilities as a single

  with all items. Now Required Qualifications: - 5+ years of relevant program and/or project management experience. - Experience supporting data center, construction, infrastructure, engineering, integration, or complex capital-project environments. - Knowledge of construction, integration (fiber, telecom, network, equipment, systems and infrastructure) Data center and construction experience is required because they can accelerate understanding of the operating environment; however, deep technical expertise is not required. - Strong program/project management fundamentals, ownership, judgment, communication, and follow-through are critical to success. - Strong proficiency with M 365 tools, including Excel, PowerPoint, SharePoint, Teams, and Outlook. - Ability and willingness to quickly learn new business processes, tools, systems, and organizational structures. Preferred Qualifications: - Experience working within a matrixed organization involving multiple functions, stakeholders, and competing priorities. - Experience supporting process improvement, standardization, operational excellence, change management, or governance initiatives. - Experience coordinating trainings, workshops, program forums, or other cross-functional working sessions. - Experience preparing concise program reporting and executive-level status materials. Also there is "How will contractor performance be measured?" which could be a separate section but not required headings list includes maybe not. Could be part of Responsibilities? It's about measurement; we could include as a separate section "Performance Measurement". But the instruction only lists certain headings; we can add others if needed but better to stick to given headings. However we could include it under Responsibilities as a bullet? It's not a duty but a metric. Might be okay to omit? The instruction says preserve ALL substantive information; we should not omit. So we need to include that info somewhere. Could add a section "Performance Measurement" with

  Performance Measurement

  and list. But the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It says "include a section ONLY when the posting has real, specific content for it". So we can add a section for Performance Measurement if we want. However they might expect only those headings. Safer to