2026_9 - REI - Sr Change Readiness and Training Specialist
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The list includes many possible headings; we should only include sections where there is real specific content. We must not repeat job title as heading. Also we must not put Job ID etc. We must remove boilerplate like EEO etc. Also we must not include sections with placeholder text like "[Insert ...]" because those are not real content. So we should omit Engagement Details, Compensation and Benefits because they contain placeholders. Also "About Guidacent’s Culture" is real content, we can include maybe as "Culture". But headings list includes "Benefits, Pay, Schedule". Since we have no actual compensation/benefits details, we should not create those sections. Also we should not create Schedule section. We should include sections: About the role (maybe Position Overview), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications?), maybe Skills? But we have "What Success Looks Like" could be a section but not in list; we could still include as a heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those as examples, but we can also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. We can also include other headings if needed but better to stick to those. So we need to map content:
- About the role: Position Overview paragraph.
- Responsibilities: Key Responsibilities (multiple bullet points).
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: maybe we could include some skills from Required Qualifications? But we already have Requirements. Could combine? But better to have Skills separate if we have specific skill list. The posting includes many skills within qualifications. Could create Skills section summarizing skills like communication, project management, etc. However we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to pull out skill statements from the text. That could be okay as long as we don't lose info. But we could also keep them within Requirements and Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Required and Preferred into Qualifications? But they gave separate headings Requirements and Qualifications. We could use Requirements for Required Qualifications, Qualifications for Preferred Qualifications. That seems fine.
We also have "What Success Looks Like" which is not in the list but could be a section; but we could incorporate into About the role or Responsibilities? It's more about outcomes. Could be its own section but not in the list; maybe we should not create a heading not listed? The instruction says 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 to be safe, we could create a section called "Success Metrics" or similar but not listed. Might be okay. However they said "Prefer a few substantive sections over many thin ones." So maybe we can omit What Success Looks Like and integrate its content into About the role or Responsibilities. But we must preserve ALL substantive information; we can't discard it. So we need to include it somewhere. Could add a section "What Success Looks Like" as a heading, even if not in the list, but it's still a heading. The instruction didn't forbid other headings, just gave examples. So we can include it.
Similarly "Engagement Details" and "Compensation and Benefits" are placeholders, we should omit them entirely because they have no real content. "About Guidacent’s Culture" is real content; we could make a section "Culture". That's not in the list but okay.
Thus final HTML will have sections:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. We can also include other headings if needed but better to stick to those. So we need to map content:
- About the role: Position Overview paragraph.
- Responsibilities: Key Responsibilities (multiple bullet points).
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: maybe we could include some skills from Required Qualifications? But we already have Requirements. Could combine? But better to have Skills separate if we have specific skill list. The posting includes many skills within qualifications. Could create Skills section summarizing skills like communication, project management, etc. However we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to pull out skill statements from the text. That could be okay as long as we don't lose info. But we could also keep them within Requirements and Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Required and Preferred into Qualifications? But they gave separate headings Requirements and Qualifications. We could use Requirements for Required Qualifications, Qualifications for Preferred Qualifications. That seems fine.
We also have "What Success Looks Like" which is not in the list but could be a section; but we could incorporate into About the role or Responsibilities? It's more about outcomes. Could be its own section but not in the list; maybe we should not create a heading not listed? The instruction says 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 to be safe, we could create a section called "Success Metrics" or similar but not listed. Might be okay. However they said "Prefer a few substantive sections over many thin ones." So maybe we can omit What Success Looks Like and integrate its content into About the role or Responsibilities. But we must preserve ALL substantive information; we can't discard it. So we need to include it somewhere. Could add a section "What Success Looks Like" as a heading, even if not in the list, but it's still a heading. The instruction didn't forbid other headings, just gave examples. So we can include it.
Similarly "Engagement Details" and "Compensation and Benefits" are placeholders, we should omit them entirely because they have no real content. "About Guidacent’s Culture" is real content; we could make a section "Culture". That's not in the list but okay.
Thus final HTML will have sections:
About the role
About the role
... (Position Overview paragraph)
Responsibilities
- ... each bullet from Key Responsibilities
Requirements
- ... each bullet from Required Qualifications
Qualifications
- ... each bullet from Preferred Qualifications
What Success Looks Like
... paragraph(s) from that section
Culture
... paragraph from About Guidacent’s Culture (excluding EEO boilerplate)
We must ensure we don't include any boilerplate like equal opportunity employer etc. The "About Guidacent’s Culture" paragraph includes: "Guidacent values consultants who are collaborative, accountable, thoughtful, and committed to delivering practical results. We look for professionals who are comfortable working through ambiguity, willing to challenge assumptions constructively, and able to build strong relationships across business and technology teams." Then after that there is "Guidacent is an equal opportunity employer..." which we must remove. So we only keep the first two sentences. Now we need to extract the exact text from the posting. Let's copy relevant parts. Position Overview: "Position Overview The Senior Change Readiness and Training Specialist will assess how planned initiatives affect employees and stakeholders, identify organizational readiness needs, and develop the change management, communication, and training strategies required to support successful adoption. This role will collaborate with business leaders, project sponsors, project managers, business analysts, training professionals, technology teams, and other stakeholders. The ideal candidate is an experienced change practitioner who can move comfortably between strategy and execution, communicate effectively across all levels of an organization, and advocate for the people affected by business and technology change." We need to preserve that as prose in a. Ensure we keep the sentences exactly. Key Responsibilities: It's a list with headings inside? The text: "Key Responsibilities Change Readiness and Adoption Lead change readiness activities for large-scale business and technology initiatives.Conduct stakeholder analyses, change impact assessments, and organizational readiness assessments.Identify changes to roles, responsibilities, workflows, behaviors, capabilities, and ways of working.Partner with leaders and stakeholders to identify adoption risks, resistance points, and barriers to change.Develop practical mitigation strategies that improve organizational readiness and user adoption.Monitor adoption following implementation and recommend additional interventions when adoption goals are not being met.Help project teams evaluate organizational readiness as part of major implementation and go-live decisions.Serve as an advocate for employees and other users throughout technology and process implementations. Change Strategy and Stakeholder Engagement Develop and execute change management strategies aligned with program objectives and stakeholder needs.Build stakeholder engagement plans that create awareness, understanding, acceptance, and adoption.Advise leaders and project teams on change management practices and readiness considerations.Facilitate discussions with executives, managers, subject matter experts, and impacted teams.Coach business leaders and project team members on their roles in leading and reinforcing change.Promote consistent change management practices, standards, and tools across initiatives. Communications Create and execute communication plans for complex business and technology changes.Draft clear, audience-specific messages that explain what is changing, why it is changing, how employees will be affected, and what actions they need to take.Recommend the appropriate sequencing, timing, and delivery channels for communications.Develop executive communications, presentations, FAQs, job aids, newsletters, email campaigns, and digital content.Coordinate communication reviews and approvals with project sponsors and business stakeholders. Training and Enablement Assess training needs based on stakeholder groups, business impacts, process changes, and technology changes.Design and develop training strategies, curricula, course materials, facilitator guides, job aids, and supporting resources.Develop and deliver instructor-led, virtual, and self-paced learning experiences.Coordinate training schedules, audiences, objectives, logistics, and deliverables.Facilitate training sessions and other learning or readiness activities for employees, managers, and project stakeholders.Create engaging digital learning content, which may include e-learning modules, system simulations, instructional videos, surveys, and interactive sites.Evaluate training effectiveness and modify enablement approaches based on feedback, readiness indicators, and adoption results. Measurement and Reporting Define meaningful change readiness, communication, training, and adoption metrics.Develop dashboards, status reports, and other tools to communicate readiness, adoption, risks, and performance.Provide regular updates and actionable recommendations to project leaders and executive stakeholders.Gather and synthesize information from multiple sources to support sound decisions.Capture lessons learned and contribute to the continuous improvement of change management and training practices." We need to split into list items. Each sentence seems to be a responsibility. We'll create