Director, Program Management Office

We need to output HTML fragment with sections: About the role? Actually the posting includes "About You", "A Day In The Life", "Necessary Qualifications", "What We Can Offer You". Also there is some extra fluff about ARCO etc. We must remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to preserve all substantive information. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. We must not repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We need to preserve all substantive information: The posting includes: - About You: description of role, responsibilities, etc. - A Day In The Life: bullet list of duties (actually sentences separated by periods but we can treat as list). - Necessary Qualifications: list of qualifications. - What We Can Offer You: list of benefits. Also there is some extra content about ARCO, mission, etc. That might be considered boilerplate? It's not exactly legal/EEO but it's company description. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ARCO description might be considered not boilerplate but maybe it's fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The ARCO description includes details about the company, its values, growth, etc. Is that substantive? Possibly yes, but it's not directly about the job. The instruction says remove boilerplate, but not necessarily company overview. However typical job postings include "About Us" which might be considered boilerplate but could be kept. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company description. So we might keep it as a section? But we only have headings for specific categories: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. 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 says use those for those categories. It also says "Prefer a few substantive sections over many thin ones." So we could combine some. We need to decide what sections to include: About the role (maybe from "About You" and "A Day In The Life" combined?), Responsibilities (maybe from A Day In The Life), Requirements (maybe from Necessary Qualifications), Benefits (from What We Can Offer You). Could also include Skills (maybe from qualifications). But we need to avoid thin sections. We could structure:

  About the role

  ... (summary of role)

  Responsibilities

  • ...

  Qualifications

  • ...

  Benefits

  • ...
  We must not include Pay or Schedule sections because not specified. We need to preserve all substantive information: So we need to extract the responsibilities list from "A Day In The Life". That paragraph contains many sentences; we can turn each sentence into a list item. Similarly, qualifications list from "Necessary Qualifications": each bullet-like sentence. Benefits list from "What We Can Offer You": each benefit. Also we might include a short paragraph about the company (ARCO) maybe as part of About the role? Or we could add a separate section like "About the company" but not in allowed headings. 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 we should prefer those. However we could incorporate company description into About the role paragraph. We must remove legal/EOO etc at the end: "ARCO does not accept unsolicited resumes..." and "LEGAL DISCLAIMER EOE, including disability/vets". Those are boilerplate; remove. Also remove duplicated lines: I don't see duplicates. Now craft the HTML. We need to ensure we don't include any markdown fences. Let's extract text. About You paragraph: "We are seeking a strategic and results-driven Director of Program Management within our Technology team to lead and evolve our IT Project Management Office, driving enterprise-wide execution excellence across the technology portfolio. This leader will be responsible for establishing and advancing PMO governance, portfolio management practices, and delivery standards to ensure alignment between technology initiatives and business strategy. As a key member of the Technology Leadership Team, the Director of PMO will oversee a team of Project Managers, define project prioritization frameworks, optimize resource planning, and serve as the executive owner of project execution and delivery performance. This role requires a forward-thinking leader with strong operational rigor, executive presence, a demonstrated capability of managing organizational change management and the ability to influence cross-functional stakeholders in a dynamic and fast-paced environment." We can keep that as prose. A Day In The Life sentences (split by periods): "Lead, mentor, and scale a team of Project Managers, fostering a culture of accountability, strategic thinking, and continuous improvement." "Establish and mature enterprise PMO governance, standards, tools, and methodologies (Agile, Waterfall, and hybrid models) to ensure consistency and delivery excellence." "Establish and own the demand-to-project lifecycle process, including demand intake, qualification, portfolio prioritization, and capacity planning, partnering with Product Owners to ensure visibility, accountability, and timely progression of initiatives from request through execution." "Oversee the successful execution of large, complex, cross-functional technology programs from ideation through implementation and value realization." "Develop and manage portfolio-level reporting, KPIs, financial tracking, and health metrics; provide regular executive updates to senior leadership and the CIO." "Drive enterprise risk management practices within the project portfolio, ensuring proactive mitigation and effective issue escalation." "Partner closely with business leaders, technology teams, and external vendors to ensure transparency, alignment, and successful delivery outcomes." "Champion organizational change management and adoption strategies to maximize the impact of new systems, tools, and processes." "Optimize resource allocation and financial stewardship across the technology portfolio to drive efficiency and return on investment." "Continuously assess and improve PMO processes, leveraging data and industry best practices to elevate delivery maturity." We'll make each a

  . Necessary Qualifications sentences: "Bachelor’s degree in Business, Information Technology, Engineering, or a related field required; PMP, PgMP, or equivalent certification strongly preferred." "12+ years of progressive experience in IT project and program management, including 5+ years of leadership experience." "Proven experience building, transforming, or leading an enterprise PMO." "Strong expertise in technology delivery, including software development, infrastructure, SaaS implementations, digital transformation initiatives, and enterprise systems." "Demonstrated experience managing complex portfolios with significant budget oversight." "Exceptional leadership and team development skills, with the ability to influence at the executive level." "Proficiency with project management and portfolio tools (e.g., Microsoft Project, Smartsheet, Jira, Confluence, ServiceNow, portfolio management platforms)." "Strong financial acumen and experience managing capital and operating budgets." "Excellent communication, facilitation, and stakeholder engagement skills." "Experience managing third-party vendors and external delivery partners." "Familiarity with Agile frameworks, DevOps practices, ITIL service management principles, and change management frameworks preferred." Make each a

  . What We Can Offer You sentences: "We are dedicated to the well-being of our associates and are proud to be consistently recognized as a Best Place to Work." "Our compensation and benefits package not only supports our associates and their families but benefits local communities and communities around the world." "Industry-leading performance-based bonus program" "Employee Stock Ownership Plan (ESOP)" "Traditional and Roth 401k" "Tuition reimbursement for associates" "Scholarship for associates’ children up to $28,000 per child" "1-month paid sabbatical after every five years of employment, plus $5,000 for travel" "1-week paid volunteer leave each year" "100% charitable match" "Medical, dental, and vision insurance coverage" "100% paid 12-week maternity leave" Some of these are fragments; we can keep as list items. Now we need to decide about the introductory sentences about compensation and benefits package etc. Could be prose before list. We'll put a

  for the first two sentences, then

  for the list. Now we need to ensure we don't include any boilerplate like "At ARCO, our first core value is to treat people fairly..." etc. That's after benefits. That is company description/values; maybe we could keep as a short paragraph under About the role? But it's not directly about the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's more like company culture. Might be considered substantive? It's not about the job but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. If we remove it, we are summarizing away detail (the company's values). So we should keep it. But where to put? Could add a section "About the company" but not in allowed headings. However we could incorporate into About the role paragraph as extra sentences. Let's see that paragraph: "At ARCO, our first core value is to treat people fairly and do the right thing. We are proud to be a drug-free workplace and an equal opportunity employer, and all qualified applicants will receive consideration for employment. From recruiting, training, and hiring practices to selecting our subcontractors, we understand that the diversity of all those involved in the construction process enhances our ability to deliver the best solutions to our customers. We hire the best and the brightest from across the country – constructing a team of experts in architecture, design, engineering, project management, and business services. MAKE YOUR MOVE We are proud to be one of the fastest-growing, privately-owned companies in America, celebrating over 30 years of experience as design-build experts. We have completed over 7,500 design-build projects nationwide. We ranked #9 on ENR’s Design-Build Firms list and #34 on ENR's Top 400 Contractors list of 2026. Most importantly, our clients like us, trust us, and want to do business with us. We are looking for people with the same enthusiasm, passion, and respect for the hard work that brought us to where we are today. Are you a person who can make a difference at ARCO? If the answer is “Yes!” we look forward to meeting you." This includes a call to action and some marketing. The instruction says remove application instructions. This includes "Are you a person who can make a difference at ARCO? If the answer is “Yes!” we look forward to meeting you." That's somewhat application encouragement; could be considered application instruction? It's not exactly instructions to apply, but it's a call to action. Might be considered boilerplate? The instruction says remove application instructions. This is more like a motivational