We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes "What We Offer" with benefits: Health Insurance including Medical, Dental and Vision, 401k, Paid Time off, Parental and Caregiver Leave, Flexible Work Schedule. Also mentions "Experience will be the determining factor for position level and compensation." No explicit pay figure. So we should not create Pay section because no specific pay. Schedule: mentions "Hybrid either in Mequon or Milwaukee, WI." Also later: "Rockwell Automation’s hybrid policy aligns that employees are expected to work at a Rockwell location at least Mondays, Tuesdays, and Thursdays unless they have a business obligation out of the office." That's schedule info. So we can include Schedule section.
Benefits: we have health insurance, 401k, PTO, parental leave, flexible work schedule. So Benefits section.
Qualifications: The posting has "The Essentials - You Will Have" and "The Preferred - You Might Also Have". Those are qualifications/requirements. We need to separate maybe Requirements and Qualifications? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills. We need to decide what content goes where.
We have "Job Description" paragraph describing role. That could be About the role.
Primary Responsibilities list: that is Responsibilities.
The Essentials (Bachelor's degree or equivalent, legal auth to work US, ability to travel up to 20%) are Requirements.
The Preferred list: many items could be Qualifications or Skills. We could split: Qualifications (education, experience) and Skills (specific competencies). But we can also combine into Qualifications. However we need to avoid thin sections. Let's create sections: About the role (intro paragraph), Responsibilities (list), Requirements (Essentials), Qualifications (Preferred), Benefits (What We Offer), Schedule (Hybrid policy). Skills maybe not needed if we put skills in Qualifications. But we could create Skills section for things like "Strong knowledge of project management best practices and methodologies", "Experience working with global teams", etc. However many of those are in Preferred. Might be better to have Qualifications for education/experience and Skills for competencies. Let's parse Preferred list:
- Typically requires a minimum of 5 years management experience.
- Bachelor's Degree in Business, Engineering, Operations Management, Project Management, or related field.
- Minimum 15 years of professional experience in project management, program management, PMO leadership, product development, or business operations.
- Minimum 8 years of people leadership experience, including experience leading managers.
- Experience managing PMO Managers, Project Managers, Program Managers, or similar professional organizations.
- Strong knowledge of project management best practices and methodologies.
- Experience working with global teams and within a matrixed organization.
- Experience presenting to executive leadership and facilitating strategic decision-making.
- Master of Business Administration (MBA) or relevant advanced degree.
- Demonstrated experience working in Agile and SAFe environments, particularly organizations where Agile and traditional project management methodologies coexist.
- SAFe certifications such as SAFe Scrum Master, Release Train Engineer (RTE), SAFe Agilist (SA), or Lean Portfolio Management (LPM).
- Experience with New Product Introduction (NPI), Common Product Development (CPD), or other structured product development processes.
- Experience leading complex product development programs from concept through commercialization.
- Experience leading PMO organizations within engineering, technology, or product development environments.
- Experience leading organizational transformation, integration, or change management initiatives.
- Experience working in a large global company with responsibility for both direct and indirect reports.
We could categorize: Education: Bachelor's degree in specific fields, MBA. Experience: years of experience, people leadership, managing PMO managers, etc. Skills: knowledge of methodologies, Agile/SAFe, certifications, global teams, matrix, presenting to execs, NPI/CPD, leading complex product development, leading PMO orgs, transformation/change management, large global company.
But we can keep it simple: Qualifications section includes all Preferred items as a list. That may be okay; it's not too thin. However we already have Requirements section for Essentials. Then Qualifications for Preferred. That seems fine.
We also need About the role: The initial paragraph about Rockwell Automation and the job description summary: "As the Senior Manager, PMO, you will lead a team..." That's basically the role description. We'll put that in About the role.
Responsibilities: The list under Primary Responsibilities (multiple sentences). We'll convert each sentence to
.
We must not repeat job title as heading. So no heading for Senior Manager, PMO.
We must not include Job ID etc. Not present.
We must remove boilerplate: The EEO statement, accommodation contact, etc. Also remove duplicated lines. Also remove "To learn more about our benefits package, please visit at www.raquickfind.com." That's maybe part of benefits but it's a link; we can keep benefits but maybe drop the link as it's not substantive? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is not substantive? It's a reference; could be considered boilerplate. Safer to drop it.
Also remove "This position is part of a job family. Experience will be the determining factor for position level and compensation." That's substantive? It mentions compensation determination but no specific pay; we already decided not to add Pay section. This sentence could be placed maybe in About the role or Qualifications? It's about compensation determination; but we have no Pay section. Could we include it in About the role? It's not about role but about compensation. Might be considered boilerplate? It's not EEO. It's about job family. Might be okay to keep as a short paragraph under About the role or Qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." We could incorporate that sentence into About the role as a note. But it's not about role. Maybe better to put it in Qualifications as a note about experience determining level/compensation. But we already have Qualifications list; adding a sentence there is fine.
Also remove "At Rockwell Automation we are dedicated to building a diverse, inclusive and authentic workplace, so if you're excited about this role but your experience doesn't align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right person for this or other roles. We are an Equal Opportunity Employer including disability and veterans. If you are an individual with a disability and you need assistance or a reasonable accommodation during the application process, please contact our services team at +1 (844) 404-7247." That's EEO boilerplate; must remove.
Also remove "Rockwell Automation’s hybrid policy aligns that employees are expected to work at a Rockwell location at least Mondays, Tuesdays, and Thursdays unless they have a business obligation out of the office." That's schedule info; we keep.
Now craft HTML.
Structure:
About the role
Rockwell Automation is a global technology leader focused on helping the world’s manufacturers be more productive, sustainable, and agile. With more than 28,000 employees who make the world better every day, we know we have something special. Behind our customers - amazing companies that help feed the world, provide life-saving medicine on a global scale, and focus on clean water and green mobility - our people are energized problem solvers that take pride in how the work we do changes the world for the better. We welcome all makers, forward thinkers, and problem solvers who are looking for a place to do their best work. And if that’s you we would love to have you join us! As the Senior Manager, PMO, you will lead a team of PMO Managers, Project Managers, and Project Coordinators responsible for delivering strategic product development and business initiatives across the Power & Motion Business (PMB). You will provide leadership and oversight for project execution, resource planning, governance, and continuous improvement while ensuring alignment between business priorities and execution. You will partner with Engineering, Product Management, Business Operations, Quality, Manufacturing, Supply Chain, and Finance leaders to drive execution excellence, develop project management capabilities, and provide transparency into organizational performance. Your success will be measured by your ability to strengthen accountability, increase ownership, improve execution discipline, and develop a high-performing PMO organization. You will report to Director PMO, Business Operations, & HPO. You will work Hybrid either in Mequon or Milwaukee, WI.
But note we already have Schedule section later; we might not need to repeat hybrid location in About the role. However the instruction: preserve ALL substantive information. If we move hybrid location to Schedule section, we should not duplicate. But we can keep it in About the role and also mention in Schedule? That would duplicate. Better to keep location in About the role and schedule details in Schedule section. The About the role currently includes "You will work Hybrid either in Mequon or Milwaukee, WI." That's location. The Schedule section will detail expectations (Mondays, Tuesdays, Thursdays). So we keep both.
Now Responsibilities:
Responsibilities
- Lead, develop, and coach PMO Manager and Project Managers, while fostering a culture of accountability, ownership, and execution excellence.
- Provide expert guidance and thought leadership to establish PMO policies, procedures, governance processes, delivery frameworks, and project management methodologies.
- Proactively report overall status, progress, issues, risks, resource constraints, and dependencies across major programs and initiatives.
- Partner with business and engineering leadership to align priorities, resources, and execution plans with strategic objectives.
- Lead resource planning activities to ensure effective utilization of project management resources and alignment to business needs and budgets.
- Champion Agile, Hybrid SAFe, and traditional project management practices, ensuring teams apply the appropriate methodology based on project and business needs.
- Develop organizational capabilities, talent strategies, succession plans, and career development pathways for project management professionals.
- Independently identify, manage, and mitigate program and organizational risks, resulting in proactive contingency planning.
- Prepare and lead executive reviews and governance forums.
- Present project, organizational, and strategic business updates to senior executives and leadership teams.
- Build strong relationships and collaborative partnerships across Engineering, Product Management, Operations, Quality, Manufacturing, Supply Chain, and functional organizations.
- Drive consistency and discipline across project management processes, governance, risk management, and reporting to improve organizational execution maturity.
- Operate effectively across multiple time zones and global teams.
Now Requirements (Essentials):
Requirements
- Bachelor's Degree or Equivalent Years of Relevant Work Experience.
- Legal authorization to work in the US is required. We will not sponsor individuals for employment visas, now or in the future, for this job opening.
- Ability to travel up to 20%.
Now Qualifications (Preferred):
Qualifications
- Typically requires a minimum of 5 years management experience.
- Bachelor's Degree in Business, Engineering, Operations Management, Project Management, or related field.
- Minimum 15 years of professional experience in project management, program management, PMO leadership, product development, or business operations.
- Minimum 8 years of people leadership experience, including experience leading managers.
- Experience managing PMO Managers, Project Managers, Program Managers, or similar professional organizations.