Manager - PMO Team - Hybrid

We need to output HTML fragment with sections: About the role? The posting includes intro about company culture, then role description. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if there is real specific content. We have content: About the role: description of PMO Manager role. Could be under "About the role". Responsibilities: list of duties under "Project Management Office (PMO) Leadership Responsibilities". Requirements: maybe "Training, Education, And Experience". Qualifications: maybe certifications. Skills: "Technical Skills". Benefits: mention of benefits: "Arbella employees are eligible for exceptional benefit and wellness programs including medical, dental, vision, 401k plan, career development, flexible schedules and much more!" Also earlier bullet list of perks: On-site gym, nurse, cafeterias, shuttle, tuition assistance, volunteer opportunities, training, mentorship, etc. So we have benefits content. Pay: salary range given: $140,000 - $160,000. Schedule: Not explicitly mentioned; maybe flexible schedules mentioned under benefits but not schedule specifics. No explicit schedule. So we should not create Schedule section. We need to avoid boilerplate like EEO etc. Not present. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to avoid repeating job title as heading. Not needed. We need to not put Job ID etc. We need to output only HTML fragment. Let's structure:

  About the role

  At Arbella, we’re focused on people... (the intro about company culture) ... As the Arbella Manager for the PMO, you will lead the Project Management Office (PMO) function, driving enterprise-wide project governance, delivery excellence, and operational transparency across the project portfolio. This leadership role is responsible for establishing and evolving PMO standards, enabling successful execution of strategic initiatives, and ensuring consistent, high-quality delivery within a fast-paced, technology-driven environment. The PMO Manager will oversee portfolio governance, project delivery methodologies, resource planning for the Project Managers, and reporting practices including and not limited to project budgets, project schedule and status while partnering closely with business and technology leaders to align initiatives with organizational priorities and business value. This role also provides leadership, coaching, and operational direction to 5 project managers and governance activities to strengthen delivery capabilities and organizational effectiveness.

  But we need to ensure we keep all substantive info: The intro about company culture is part of posting; we should include it. It's not a list, so

  . Then Responsibilities: we have a list under "Project Management Office (PMO) Leadership Responsibilities". We'll make

  Responsibilities

  then
  • each bullet. List items: - Lead and manage the Project Management Office (PMO), establishing governance frameworks, delivery standards, methodologies, and reporting practices across the organization. - Oversee portfolio governance, project intake, prioritization, and cross-functional alignment to ensure strategic execution of enterprise initiatives. - Provide leadership and direction to project managers, including mentoring, coaching, performance management, and professional development. - Drive organizational consistency and accountability through effective project lifecycle management from initiation through delivery. - Monitor project health, including project performance metrics, budgets, risks, issues, dependencies, and resource utilization. - Partner with executive leadership and business stakeholders to align project investments with business strategy, operational goals, and value delivery. - Lead resource management, capacity planning, and project pipeline visibility to optimize organizational delivery effectiveness. - Identify opportunities for continuous improvement in project management processes, governance, and delivery practices. - Foster a culture of collaboration, transparency, accountability, and delivery excellence across teams. Also there is "Success Metrics" section; could be considered part of responsibilities or maybe separate? It lists metrics. Could be included under Responsibilities as additional bullet points? But they are success metrics, not duties. Could be separate section? The instruction: include a section only when posting has real specific content. We could treat Success Metrics as part of Responsibilities or maybe as its own section "Success Metrics". But we only have predefined headings list; we could add a custom heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; not add others. So we should map Success Metrics into Responsibilities or maybe Requirements? Probably Responsibilities. Thus we can add bullet points for success metrics under Responsibilities as well. Success Metrics bullets: - Drives execution-focused project delivery while maintaining alignment with business goals and strategic priorities. - Consistently improves delivery effectiveness, governance maturity, and operational efficiency across the portfolio. - Successfully delivers against internal and external stakeholder expectations. - Builds strong partnerships across IT, business functions, and enterprise leadership. - Effectively manages team performance, resource allocation, and organizational priorities. - Demonstrates confident, professional, and transparent communication at all organizational levels. - Provides accurate, balanced, and actionable performance feedback and development guidance to team members. - Leads by example through strong leadership presence, accountability, and collaboration. - Demonstrates effective and diplomatic verbal and written communication skills. - Maintains awareness of evolving project management, governance, and quality assurance best practices, introducing innovative approaches where appropriate. Now Requirements: we have "Training, Education, And Experience" section. Also maybe "Technical Skills" is separate. So Requirements could be education and experience. Thus

    Requirements

    with list: - Bachelor’s degree required. - Minimum of 5–8 years of project management experience, including 3+ years leading a PMO and Project Managers, project teams, or delivery organizations. - Strong facilitation, presentation, influencing, relationship management, and organizational leadership skills. - PMP, PMI-ACP, ScrumMaster, or related certifications preferred. But note that "Strong facilitation..." could be considered Skills. However we have a separate Skills section for technical skills. The instruction says use sections as appropriate. We could put those under Requirements or Qualifications. Let's treat them as Requirements (experience/skills). But we also have a Qualifications section maybe for certifications? The posting mentions certifications preferred. Could be under Qualifications. We need to decide mapping: The posting has "Training, Education, And Experience" and then "Technical Skills". So we can map: - Requirements: Education and experience (Bachelor's degree, 5-8 years experience, 3+ years leading PMO, etc.) - Qualifications: Certifications preferred (PMP, etc.) maybe also strong facilitation etc. But we can also put facilitation under Skills? Actually facilitation is a soft skill. Could be under Skills? But we have Technical Skills for technical. Might be better to have a Qualifications section for certifications and maybe soft skills. But the instruction says prefer a few substantive sections over many thin ones. So we might combine some. Let's think: We have About the role, Responsibilities, Requirements (education/experience), Skills (technical), Benefits, Pay. We can put certifications under Requirements or Qualifications. Since we have a Qualifications heading in the list, we could use it for certifications. But we also have strong facilitation etc. Could be under Skills? But they are not technical. However we could still put them under Skills as a broader sense. But the instruction says use headings e.g. Skills; doesn't restrict to technical only. So we can put all skill-related items under Skills. Thus:

    Skills

    • Strong facilitation, presentation, influencing, relationship management, and organizational leadership skills.
    • Strong experience with project and portfolio management tools (e.g., MS Project, Jira, SmartSheet).
    • Deep understanding of Agile, Waterfall, and Hybrid delivery methodologies.
    • Experience with data visualization and reporting tools (e.g. Power BI, Tableau) to support portfolio reporting and KPI tracking.
    • Familiarity with compliance, risk management, and audit processes preferred.
    Then Requirements: education and experience.

    Requirements

    • Bachelor’s degree required.
    • Minimum of 5–8 years of project management experience, including 3+ years leading a PMO and Project Managers, project teams, or delivery organizations.
    Qualifications: certifications preferred.

    Qualifications

    • PMP, PMI-ACP, ScrumMaster, or related certifications preferred.
    Now Benefits: we have list of perks and benefits. We need to include all substantive info: On-site gym and fitness classes and one-on-one personal training; On-site nurse, nutritional counseling, and mental health resources; Full-service cafeterias; Free shuttle service to Quincy Adams T Station; Tuition assistance programs; Opportunities to get involved: Arbella Activities Committee, Diversity and Inclusion Council, and more; A company committed to community: volunteer opportunities, employee-led community efforts, and the Arbella Insurance Foundation; Robust training, mentorship, and professional/personal development programs; Colleagues who genuinely care about each other; Arbella is committed to building a workplace that’s diverse, inclusive, and equitable for everyone... Also mention: Arbella employees are eligible for exceptional benefit and wellness programs including medical, dental, vision, 401k plan, career development, flexible schedules and much more! We should capture all. We'll make a
    with each bullet. Potential bullets: - On-site gym and fitness classes, plus one-on-one personal training - On-site nurse, nutritional counseling, and mental health resources - Full-service cafeterias - Free shuttle service to Quincy Adams T Station - Tuition assistance programs - Opportunities to get involved: Arbella Activities Committee, Diversity and Inclusion Council, and more - Volunteer opportunities, employee-led community efforts, and the Arbella Insurance Foundation (company committed to community) - Robust training, mentorship, and professional/personal development programs - Colleagues who genuinely care about each other - Commitment to a diverse, inclusive, and equitable workplace where all are valued and empowered to reach full potential - Exceptional benefit and wellness programs including medical, dental, vision, 401k plan, career development, flexible schedules, and more We should avoid fluff like "It’s no wonder our employees have voted Arbella one of the Boston Business Journal’s “Best Places to Work” every year since 2009!" That's substantive? It's a statement about recognition. Could be included in About the role? Might be considered boilerplate? It's not navigation/legal; it's a fact about awards. Could be included in About the role paragraph. We'll keep it. Pay: we have salary range.

    Pay

    Our current reasonable and good faith estimate of the annual salary wage range for this position is approximately $140,000 - $160,000 based on a variety of factors including, but not limited to, relevant skills and experience, educational background and certifications, performance and qualifications, market demand for the role and other organizational needs. Please note: The advertised pay range is not a guarantee or promise of a specific wage.

    We should not include the "Please note" maybe it's boilerplate but it's part of the pay disclosure; we keep it. Schedule: Not present, so omit. Now ensure we didn't repeat job title as heading. Not. Now output only HTML fragment. Let's craft final HTML. We need to ensure proper nesting. We'll start with

    About the role

    then

    ...

    Then

    Responsibilities

    ...
    Then

    Requirements