Senior IT Project Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph: "Join our growing team and discover why Summit Utilities, Inc. continues to earn national and regional recognition as an employer of choice. Our recognitions include Best Places to Work in Maine (2019–2025); Best Places to Work in Arkansas (2020, 2023, 2025); Best Places to Work in Oklahoma (2022–2025); Best Places to Work in Missouri (2023 and 2026); Best Places to Work in Colorado (2025); Forbes America’s Best Small Employers (2023); and, most recently, Proud and Purposeful Employer (2026). Summit is a growing natural gas utility providing safe, reliable, and clean burning natural gas service to homes and businesses in Arkansas, Colorado, Maine, Missouri, Oklahoma, and Texas. Being part of the Summit team means embracing excellence and innovation, committing to safety each and every day, and doing all that we can to serve each other, our customers, and the communities where we live. We aim to bring warmth and energy to everything we do. We have an exciting opportunity for a Senior IT Project Manager (SGL19). This hybrid position can be based in one of our Arkansas or Oklahoma offices, or remotely in Texas." That's about the role/company. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" heading for that intro. Then "POSITION SUMMARY" paragraph: "The Senior IT Project Manager plays a pivotal part in delivering mission-critical projects for Summit’s enterprise applications and integrated systems. This role proactively leads diverse, cross-functional teams across IT, business functions, and third parties and manages all aspects of the project lifecycle from initiation through closure. The position ensures projects meet stakeholder expectations for quality, scope, schedule, and budget; drives continuous process improvement and organizational change; engages executive leadership and team leads to define and communicate key metrics aligned with Summit’s business objectives; and ensures projects remain consistent with the overall IT strategy." That could be part of responsibilities or summary. Could be under "Responsibilities" heading. Then "PRIMARY DUTIES AND RESPONSIBILITIES" bullet list (actually sentences). We'll need to convert to

• . The list items are each sentence starting with a verb. We'll extract each. List: - Lead end-to-end project management activities—including planning, execution, monitoring, and closure for medium- to large-sized software application projects such as ERP implementations, system integrations, data migrations, and custom development. - Manage project scope, schedule, resources, quality, risks, issues, communication, budgets, and stakeholder expectations. - Coordinate diverse, cross-functional teams across IT, business functions, vendors, consultants, contractors, multiple locations, time zones, and offshore resource. - Apply project management best practices, methodologies, and standards such as PMBOK, Agile, and Scrum. - Develop and execute IT cutover plans for project go-lives and align them with dependent business cutover activities. - Prepare project charters, plans, schedules, status reports, change requests, lessons learned, and other required documentation. - Provide leadership, guidance, and direction to project team members and stakeholders; monitor performance, quality, and deliverables. - Track, report, escalate, and resolve project risks and issues, report project status and progress to senior management and sponsors. - Assist project teams in defining scope, goals, requirements, approach, and deliverables that support business objectives. - Partner with business leads and business analysts on requirements gathering, user acceptance testing, and cutover planning. - Work with business leaders and the Training team on change management planning and communications. - Coordinate with Business and IT Leads to deliver smaller-scope system enhancements and resolve system issues through the Jira ticketing process. - Review project management procedures, identify improvement opportunities, and work with PMO leadership to implement changes. That's responsibilities. Then "EDUCATION AND WORK EXPERIENCE" paragraph: "Bachelor’s degree or advanced degree in Computer Science, Information Systems, Business Administration, or a related field. Ten or more years of proven experience managing medium- to large-sized software application projects, preferably in the utilities industry and involving ERP, CRM, CIS, or field service systems. Project Management Professional (PMP), Certified ScrumMaster (CSM), Professional Scrum Master (PSM), or related certification strongly preferred. Experience with ERP and/or CRM systems, including sales and service processing, customer relationship management, content management, financial management/accounting, manufacturing, and inventory control systems. Experience with project management and workflow tools such as Jira, Smartsheet, Microsoft Project Online, or Asana. Working knowledge of Power BI, Tableau, or similar data analytics tools and proficiency with process-mapping tools such as Microsoft Visio or Lucidchart. Utility industry experience and SAP experience preferred." We can treat as "Qualifications" or "Requirements". The instruction includes Requirements and Qualifications headings. We need to decide which to use. Usually Requirements = education/experience; Qualifications = certifications, skills. But we can combine. However we must not create thin sections. We could have "Requirements" for education/experience, and "Qualifications" for certifications and preferred experience. Or we could have a single "Requirements" covering all. But we need to follow instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications if content exists. We have education and work experience (requirements). Then we have certifications (PMP etc) strongly preferred, experience with ERP/CRM, tools, etc. Those could be qualifications. Then "KNOWLEDGE, SKILLS, ABILITIES" list: we can put under "Skills" heading. List items: - Ability to establish and manage effective relationships with business leaders, key subject matter experts, and technical team members in a matrixed organization. - Strong presentation, facilitation, negotiation, and conflict-resolution skills at all organizational levels, including the ability to bridge functional and technical resources. - Ability to work in a fast-paced environment while managing multiple projects and priorities in a dynamic, rapidly evolving organization. - Knowledge of computer system capabilities, business processes, and workflows. - Strong problem-solving, analytical, and decision-making skills, with the ability to deliver results under pressure. - Proficient knowledge of user acceptance testing methodologies and documentation. - Knowledge of requirements-gathering techniques, technical specifications, process mapping, system testing, and deployment. - Ability to work independently and remotely with minimal supervision and adapt to shifting priorities and requirements. - Excellent organizational and time-management skills. - Strong Microsoft Word, Excel, and PowerPoint skills. Then after that: "The above statements are intended to describe the general nature and level of work being performed by employees assigned to this classification. They are not intended to be construed as an exhaustive list of all responsibilities, duties and/or skills required of all personnel so classified." That's boilerplate; we should remove. Then: "Summit offers competitive pay and medical/dental/vision and other benefits that provide flexibility, choice, and support to our employees when they need it most. We understand that home and family are essential pieces of your life, and our benefits are designed to support you both at work and at home." That's benefits and pay mention. It mentions competitive pay and benefits. We need to include Benefits and Pay sections only if posting actually states them. It does state competitive pay and benefits (medical/dental/vision and other benefits). So we can create Benefits section with that description. Pay section: we only have "competitive pay" but no specific numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive pay, but is that enough? It says "competitive pay". That's a statement about pay, albeit not specific. The instruction says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive pay" is somewhat vague but not exactly placeholder like those examples. It's a real statement. I'd say we can include Pay section with that sentence. However we need to avoid filler. "competitive pay" is not a placeholder like "commensurate with experience". It's a real statement. So we can include Pay. Similarly Benefits: we have description. Schedule: not mentioned. The posting says hybrid position can be based in Arkansas or Oklahoma offices, or remotely in Texas. That's location, not schedule. No schedule info (full-time, part-time, hours). So we should not create Schedule section. Now we need to remove boilerplate: EEO statement, etc. Also remove "Summit Utilities, Inc. is an Equal Opportunity Employer..." etc. Also remove "The above statements..." etc. Also remove any duplicated lines. Now produce HTML fragment with headings

  and content. Structure:

  About the role

  Join our growing team and discover why Summit Utilities, Inc. continues to earn national and regional recognition as an employer of choice. Our recognitions include Best Places to Work in Maine (2019–2025); Best Places to Work in Arkansas (2020, 2023, 2025); Best Places to Work in Oklahoma (2022–2025); Best Places to Work in Missouri (2023 and 2026); Best Places to Work in Colorado (2025); Forbes America’s Best Small Employers (2023); and, most recently, Proud and Purposeful Employer (2026). Summit is a growing natural gas utility providing safe, reliable, and clean burning natural gas service to homes and businesses in Arkansas, Colorado, Maine, Missouri, Oklahoma, and Texas. Being part of the Summit team means embracing excellence and innovation, committing to safety each and every day, and doing all that we can to serve each other, our customers, and the communities where we live. We aim to bring warmth and energy to everything we do. We have an exciting opportunity for a Senior IT Project Manager (SGL19). This hybrid position can be based in one of our Arkansas or Oklahoma offices, or remotely in Texas.

  Position Summary

  maybe we can incorporate into Responsibilities. But we have a separate POSITION SUMMARY paragraph. Could be part of Responsibilities or we could make a separate section "Position Summary". However the instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list Position Summary. But we can still include if we think it's substantive. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they also say "Prefer a few substantive sections over many thin ones." So we could merge the Position Summary into Responsibilities or About the role. Probably better to include under Responsibilities heading, as it describes the role's purpose. We'll combine. Thus under Responsibilities we can include the position summary paragraph plus the list of duties. But we need to avoid duplication. We'll put the summary as a

  then the

  . Now Requirements: education and work experience. Qualifications: certifications, preferred experience, tools, etc. Skills: knowledge, skills, abilities list. Benefits: description. Pay: description. Now ensure we don't include