Program Change Manager - Autonomous Vehicle Roadside Assistance (Chandler, AZ)

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "How We Partner To Protect You", DEI, EEO, Req Id, Posted At, etc. Also remove "Application Window" maybe? It's not a required heading; but we can include as a paragraph maybe? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can drop those lines. Also "Application Window" maybe minor metadata; we could drop or put in a

. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Application Window is not exactly application instructions but maybe considered metadata; we can drop or keep as a short p. Safer to drop. We need sections: About the role (maybe from Job Description overview). Responsibilities (Key Responsibilities). Requirements (maybe Education, Experience, Frameworks, Tools Knowledge). Qualifications (maybe Preferred Certifications). Skills (Core Competencies). Benefits (Benefits). Pay (Salary Range). Schedule (maybe not present; there is no schedule info, so we should NOT create Schedule section). Also we have "Job Type: Full-Time" maybe could be considered schedule? But schedule is about hours/shift; not given. So we omit Schedule. We must not repeat job title as heading. The page already shows it, so we don't add heading for job title. We need to preserve all substantive information. Let's extract. From "About TaskUs": description of company. That's about the company, not necessarily "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" likely corresponds to the job description overview (Position Overview). We'll put that under About the role. We also have "Job Description: Job Title: Change Management Program Manager Location: [Phoenix, AZ / Remote / Hybrid] Department: Operations Reports To: Director of Operations Job Type: Full-Time Position Overview". We'll incorporate location, department, reports to, job type maybe as a short paragraph under About the role or maybe as metadata. Since we should not create headings for those, we can embed them in a paragraph. We need to preserve location, department, reports to, job type. So we can include a paragraph: "Location: Phoenix, AZ / Remote / Hybrid. Department: Operations. Reports To: Director of Operations. Job Type: Full-Time." Now "Position Overview" text: "We are seeking an experienced Change Management Program Manager to lead and execute strategic change initiatives across the organization. In this role, you will design and implement end-to-end change management strategies, minimize resistance, and maximize employee adoption for major enterprise transformations. You will work closely with executive sponsors, cross-functional project leads, and department heads to align people, processes, and technology-ensuring business readiness and long-term sustainment of change." That's the overview. Now Responsibilities: list under Key Responsibilities with bullet points. We need to convert each bullet into

. The headings under Key Responsibilities: Change Strategy & Framework Development, Program Execution & Alignment, Stakeholder Management & Sponsorship, Communications & Training Oversight. Each has sub-bullets. We'll need to flatten? Probably we can keep each main heading as a

with its description, or we could nest

. The instruction: Use
• for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep simple: each main bullet as
• containing the description (including sub-bullets as sentences). Could also make sub-bullets as separate
• under a nested
  . Safer to keep flat but include all details. Let's extract each: Change Strategy & Framework Development: - Develop structured, scalable change management strategies using industry-standard frameworks (e.g., Prosci ADKAR, Kotter). - Conduct comprehensive Change Impact Assessments, stakeholder analyses, and organizational readiness assessments. - Establish change metrics and KPIs to measure adoption, proficiency, and business impact. Program Execution & Alignment: - Integrate change management plans into broader PMO and Agile project delivery schedules. - Oversee communications, training, and leadership alignment streams across concurrent project phases. - Define and manage risk mitigation strategies for change resistance, fatigue, and operational disruption. Stakeholder Management & Sponsorship: - Partner with C-suite and senior leaders to coach them in their roles as effective change sponsors. - Establish and lead cross-functional Change Champion Networks to drive ground-level advocacy and engagement. - Resolve escalated change-related risks, conflicts, and roadblocks across business units. Communications & Training Oversight: - Partner with Corporate Communications to craft targeted, transparent multi-channel messaging strategies. - Collaborate with L&D teams to identify capability gaps and design end-user training programs. - Monitor feedback channels, conduct pulse surveys, and iterate delivery methods based on user sentiment. Now Requirements: maybe combine Education, Experience, Frameworks, Project Mgmt, Tools Knowledge. The heading "Qualifications & Experience:" includes Education, Experience, Frameworks, Project Mgmt, Tools Knowledge, Preferred Certifications. We could split into Requirements (Education, Experience, Frameworks, Project Mgmt, Tools Knowledge) and Qualifications (Preferred Certifications) and Skills (Core Competencies). But the instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map. Requirements: likely the mandatory qualifications: Education, Experience, Frameworks, Project Mgmt, Tools Knowledge. Qualifications: maybe Preferred Certifications. Skills: Core Competencies. Let's extract. Education: Bachelor's degree in Business Administration, Organizational Psychology, Communications, or related field (Master's preferred). Experience: 5+ years of dedicated Change Management experience, with at least 2-3 years leading large-scale enterprise transformation programs. Frameworks: Deep expertise in change methodologies (Prosci ADKAR, Kotter, Bridges Transition Model). Project Mgmt: Hands-on experience working alongside PMO structures in both Waterfall and Agile/Scrum environments. Tools Knowledge: Proficiency with project tracking tools (Jira, Asana, MS Project) and change analytics/survey tools. Preferred Certifications: CCMP (Certified Change Management Professional), Prosci Certified Change Practitioner, PMP (Project Management Professional) or Agile/Scrum Certification (e.g., CSM, SAFe). Core Competencies: Strategic Influence, Empathy & Active Listening, Data-Driven Analysis, Agility & Resilience (with descriptions). Now Benefits: "We offer a comprehensive benefits package including medical, dental, and vision insurance; 401(k) with company match; and paid time off including vacation, sick leave, and holidays." Pay: Salary Range: $117,000.00 - $175,000.00 per year. Also Pay Transparency Statement details; we should preserve that as part of Pay section? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The Pay Transparency Statement is specific content about pay. So we should include it under Pay section. Schedule: Not present, so omit. Now we need to output only HTML fragment. Use

  for each section heading. Use

  for prose. Use

  • for lists. We need to ensure we don't repeat job title as heading. Not needed. We need to preserve all substantive info. Let's craft. Structure:

    About the role

    Location: Phoenix, AZ / Remote / Hybrid. Department: Operations. Reports To: Director of Operations. Job Type: Full-Time.

    We are seeking an experienced Change Management Program Manager to lead and execute strategic change initiatives across the organization. In this role, you will design and implement end-to-end change management strategies, minimize resistance, and maximize employee adoption for major enterprise transformations. You will work closely with executive sponsors, cross-functional project leads, and department heads to align people, processes, and technology-ensuring business readiness and long-term sustainment of change.

    Responsibilities

    • Change Strategy & Framework Development: Develop structured, scalable change management strategies using industry-standard frameworks (e.g., Prosci ADKAR, Kotter). Conduct comprehensive Change Impact Assessments, stakeholder analyses, and organizational readiness assessments. Establish change metrics and KPIs to measure adoption, proficiency, and business impact.
    • Program Execution & Alignment: Integrate change management plans into broader PMO and Agile project delivery schedules. Oversee communications, training, and leadership alignment streams across concurrent project phases. Define and manage risk mitigation strategies for change resistance, fatigue, and operational disruption.
    • Stakeholder Management & Sponsorship: Partner with C-suite and senior leaders to coach them in their roles as effective change sponsors. Establish and lead cross-functional Change Champion Networks to drive ground-level advocacy and engagement. Resolve escalated change-related risks, conflicts, and roadblocks across business units.
    • Communications & Training Oversight: Partner with Corporate Communications to craft targeted, transparent multi-channel messaging strategies. Collaborate with L&D teams to identify capability gaps and design end-user training programs. Monitor feedback channels, conduct pulse surveys, and iterate delivery methods based on user sentiment.

    Requirements

    • Education: Bachelor's degree in Business Administration, Organizational Psychology, Communications, or related field (Master's preferred).
    • Experience: 5+ years of dedicated Change Management experience, with at least 2-3 years leading large-scale enterprise transformation programs.
    • Frameworks: Deep expertise in change methodologies (Prosci ADKAR, Kotter, Bridges Transition Model).
    • Project Mgmt: Hands-on experience working alongside PMO structures in both Waterfall and Agile/Scrum environments.
    • Tools Knowledge: Proficiency with project tracking tools (Jira, Asana, MS Project) and change analytics/survey tools.

    Qualifications

    • Preferred Certifications: CCMP (Certified Change Management Professional), Prosci Certified Change Practitioner, PMP (Project Management Professional) or Agile/Scrum Certification (e.g., CSM, SAFe).

    Skills

    • Strategic Influence: Ability to build credibility and influence stakeholders at all levels without direct authority.
    • Empathy & Active Listening: Deep understanding of psychological drivers, resistance patterns, and team dynamics.
    • Data-Driven Analysis: Ability to translate user adoption data into actionable program shifts.
    • Agility & Resilience: Comfortable managing ambiguity and navigating shifting priorities in dynamic environments.

    Benefits

    We offer a comprehensive benefits package including medical, dental, and vision insurance; 401(k) with company match; and paid time off including vacation, sick leave, and holidays.

    Pay

    Salary Range: $117,000.00 - $175,000.00 per year.

    Pay Transparency Statement: The base salary range represents the low and high end of the anticipated salary range for this position across our US locations. The "pay scale" provided is a good faith estimate of the range the employer reasonably expects to pay for the position at the time of hire.