Associate, Enterprise Change Management

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. We need to parse the posting. Key sections: - About the role: The intro paragraphs describing Genesys, the role, vision, etc. Likely we can put that under About the role. - Responsibilities: The "What You’ll Do" bullet list. - Requirements: The "What You’ll Bring" bullet list (experience, etc.) - Qualifications: Might be overlapping with Requirements; but we can treat Requirements as qualifications. However we need to decide: The posting has "What You’ll Bring" which includes experience, skills, etc. Could map to Requirements and Skills. But we need to follow instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if there is real specific content. We have content for: - About the role: yes. - Responsibilities: yes (What You’ll Do list). - Requirements: maybe we can put the experience and qualifications under Requirements. - Skills: maybe separate skills like communication, organizational, AI curiosity, etc. But we could combine. - Benefits: yes (Benefits list). - Pay: yes (Compensation range). - Schedule: maybe not explicit; they mention flexible work schedules and work from home opportunities under Benefits. No explicit schedule like full-time, etc. So we should not create Schedule section unless posting actually states it. It does not give schedule specifics, only flexible work schedules mentioned under Benefits. So we omit Schedule. - Qualifications: Could be separate from Requirements? The posting includes "What You’ll Bring" which includes experience, familiarity, etc. That could be considered Qualifications. But we already have Requirements. To avoid duplication, we could treat Requirements as the experience/qualifications, and Skills as the specific skillset (communication, writing, organizational, relationship building, data feedback, AI curiosity, growth mindset). However the posting lumps them together. We need to decide how to split. Better: Use Requirements for the experience and qualifications (2+ years experience, familiarity with methodologies, supporting change activities, etc.). Use Skills for the abilities (strong communication and writing skills, ability to translate complex info, experience developing communications, strong organizational skills, ability to build relationships, experience gathering feedback, curiosity about AI, growth mindset). That seems reasonable. Qualifications: maybe we could omit if we already covered. But we need to include only if real specific content. Could we put Qualifications as same as Requirements? Might be redundant. Safer to include Requirements and Skills, omit Qualifications. But the instruction says we can include sections only when posting has real specific content for it. It doesn't require us to include all possible headings. So we can omit Qualifications if we think it's not distinct. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Now we need to format: - Use

for each section heading. - Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO, navigation, etc. Must remove duplicated lines. We need to extract the prose for About the role: The initial paragraphs up to "What You’ll Do". Let's capture: "Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve operational efficiency and build stronger customer relationships. Help build, support and operate technology used by more than 8,000 organizations in over 100 countries – moving AI from possibility to production in real-world enterprise environments every day. Department & Team: Enterprise Change Management Reports to: Clare Robinson Location: Remote / Virtual (US-Based) Associate, Enterprise Change Management Let’s be honest—traditional change management isn’t enough anymore. AI is changing how work gets done. People and AI are working together in new ways. Technology is moving faster, customer expectations keep evolving, and businesses need to be able to adapt just as quickly. At Genesys, we think that creates an exciting opportunity to rethink change. We’re building the next evolution of change—moving beyond managing change one project at a time to creating a connected approach that helps our people and our business continuously adapt and thrive. That means creating great change experiences for employees, helping leaders confidently lead their teams through change, using AI and data to better understand what people need, and staying focused on whether our work is actually delivering the outcomes we set out to achieve. We call this the Genesys Way of Change—our modern approach to making transformation happen. It’s human-centered, intelligent, connected, and always evolving. We’re not interested in simply applying yesterday’s change playbooks to tomorrow’s challenges. We want to learn, experiment, use new technology, and find better ways to help people and the business adapt faster and turn change into meaningful results. As an Associate, Enterprise Change Management, you’ll help bring this vision to life. Working alongside our Enterprise Change Management team and partners across Genesys, you’ll help create and deliver change experiences that enable our people to understand what’s changing, adapt quickly, and thrive in new ways of working. You’ll help us understand how change is landing, turn data and feedback into insights, experiment with AI and new approaches, and build the tools and practices that will shape how change happens across Genesys. If you’re curious about people, excited by how AI is changing the workplace, and want to learn how transformation really happens inside a global company, this is an opportunity to help us build what comes next." We need to exclude the "Department & Team: Enterprise Change Management Reports to: Clare Robinson Location: Remote / Virtual (US-Based) Associate, Enterprise Change Management" maybe considered metadata; but it's substantive? It's about role location etc. Could be considered part of About the role. However instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. This is metadata like department, reports to, location. We could keep it as a short paragraph. It's not a heading. So we can include it in About the role paragraph. Thus About the role paragraph will include all that prose. Now Responsibilities: The bullet list under "What You’ll Do". Let's capture each bullet: - Support design/development of change experiences and execute change activities for assigned initiatives or workstreams, coordinating milestones, dependencies, risks, and deliverables to support successful adoption - Develop communications, learning materials, engagement activities, presentations, toolkits, change champion networks, and other tactics and activities that help employees understand and adopt new ways of working - Use AI-enabled tools to increase personal productivity, streamline routine change activities, improve content development, and experiment with more effective ways of delivering change - Partner with business stakeholders and project teams to keep change deliverables aligned with broader initiative priorities - Track readiness, employee experience, engagement, adoption, and other relevant metrics to understand change progress, surface insights, and capture lessons learned - Share ideas, feedback, and lessons learned that improve team practices and contribute to the continued evolution of the Genesys Way of Change We need to preserve exactly. Now Requirements: The bullet list under "What You’ll Bring" but we need to separate experience/qualifications vs skills. Let's list the bullets: - 2+ years of experience in organizational change management, employee communications, or learning and enablement. - Familiarity with established organizational change methodologies, tools, and practices - Experience supporting or delivering change activities for business, technology, organizational, or enterprise initiatives - Strong communication and writing skills, with the ability to translate complex information into clear and engaging content for different audiences - Experience developing communications, learning materials, presentations, engagement activities, or enablement experiences that support adoption and behavior change - Strong organizational skills, with experience managing project plans, milestones, deliverables, and competing priorities - Demonstrated ability to build productive relationships and communicate clearly and credibly with immediate stakeholders and project team members - Experience gathering feedback and using qualitative or quantitative data to understand readiness, employee experience, engagement, or adoption - Curiosity about AI and emerging technology, with the ability and willingness to use AI-enabled tools to improve personal productivity and the quality of change delivery - Growth mindset and continuous learning orientation, with an interest in developing deeper expertise in enterprise change management We need to split: Requirements (experience, familiarity, experience supporting change, experience developing communications? Actually that's skill). Let's decide: Requirements: the experience-based items: - 2+ years of experience in organizational change management, employee communications, or learning and enablement. - Familiarity with established organizational change methodologies, tools, and practices - Experience supporting or delivering change activities for business, technology, organizational, or enterprise initiatives - Experience developing communications, learning materials, presentations, engagement activities, or enablement experiences that support adoption and behavior change - Experience gathering feedback and using qualitative or quantitative data to understand readiness, employee experience, engagement, or adoption Skills: the skill-based items: - Strong communication and writing skills, with the ability to translate complex information into clear and engaging content for different audiences - Strong organizational skills, with experience managing project plans, milestones, deliverables, and competing priorities - Demonstrated ability to build productive relationships and communicate clearly and credibly with immediate stakeholders and project team members - Curiosity about AI and emerging technology, with the ability and willingness to use AI-enabled tools to improve personal productivity and the quality of change delivery - Growth mindset and continuous learning orientation, with an interest in developing deeper expertise in enterprise change management That seems reasonable. Now Benefits: list from "Benefits:" section: - Medical, Dental, and Vision Insurance. - Telehealth coverage - Flexible work schedules and work from home opportunities - Development and career growth opportunities - Open Time Off in addition to 10 paid holidays - 401(k) matching program - Adoption Assistance - Fertility treatments Also there is a line "Click here to view a summary overview of our Benefits." That's a link/instruction; we should remove as it's navigation/application instruction? It's a link to benefits summary; could be considered boilerplate? It's not substantive benefit detail; it's a link. We should drop it. Also there is a paragraph "Working at Genesys AI at enterprise scale – ..." that's more about company culture; could be considered part of Benefits? Actually it's more about culture and perks. Might be considered additional benefits but not listed as benefits. The instruction: include Benefits section only when posting has real specific content for it. The posting does have a Benefits list; we should include that. The extra culture paragraph could be considered part of About the role or maybe a separate section like "About Genesys". But we don't have a heading for that. We could incorporate into About the role? It's after Benefits. It's more about company culture; could be considered part of About the role or maybe we could add a section "About Genesys" but not in allowed headings. So we might drop it as it's not under allowed headings and not required. However it's substantive info about culture; but we have no heading for it. The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings; we should not create other headings. So we should either fold that content into About the role or Benefits? It's about culture, not benefits. Could fold into About the role as additional description. That would preserve info. Thus we will add that paragraph to About the role after the initial description. Now Pay: The compensation range: "$86,300.