Change Management Lead

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 that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, application instructions, duplicated lines, cookie/navigation etc. Must preserve all substantive info. We need to parse the posting. Key parts: - Intro about Johnson & Johnson mission etc. Could be considered "About the role" or maybe "About the company". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have "About the role" heading with description of role and company context. - Role Summary: includes duration-based Change Management Lead position with anticipated end date on or around 2029. That's substantive. - Key Responsibilities: bullet list. - Required Skills & Expertise: bullet list. - Preferred Qualifications: bullet list. - Key performance indicators (KPIs): bullet list. - Primary Stakeholders: bullet list. - Pay: "The anticipated base pay range for this position is : $87,000.00 - $150,650.00". So we need a Pay section with that. - Benefits: Not mentioned explicitly. No benefits details. So we should not create Benefits section. - Schedule: Not mentioned. So no Schedule. - Qualifications: Could combine Required Skills & Expertise and Preferred Qualifications? The instruction says separate sections: Requirements, Qualifications, Skills. We need to decide mapping. Usually "Requirements" could be required skills/expertise. "Qualifications" could be preferred qualifications. "Skills" could be maybe a summary of skills? But we have both required and preferred. We could put Required Skills & Expertise under

Requirements

. Preferred Qualifications under

Qualifications

. Skills maybe not needed separately; but we could also put a Skills section if we have skill list. However we already have required skills; maybe we can put Skills as a separate section summarizing key skills? But instruction: Prefer a few substantive sections over many thin ones. So we might combine Required Skills & Expertise and Preferred Qualifications into one "Requirements" section? But they said use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must use all; we include only those with real content. So we could have About the role, Responsibilities, Requirements (combining required and preferred), Pay. Possibly also Skills if we want to separate required vs preferred? But we can keep it simple: About the role, Responsibilities, Requirements (including required and preferred), Pay. But we also have KPIs and Primary Stakeholders. Those could be part of Responsibilities or maybe a separate section like "Key Performance Indicators" not in list. Since not in allowed headings, we might incorporate them into Responsibilities or Requirements? The instruction says use headings for sections like those listed; but we could also add other headings if needed? It 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. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add other headings if they have content, but better to stick to given examples to be safe. However KPIs and Stakeholders are substantive; we could fold them into Responsibilities or Requirements. For instance, under Responsibilities we could add bullet points about KPI tracking and stakeholder engagement already covered. The KPIs list is about measuring effectiveness; could be part of Responsibilities (drive adoption, track metrics). The Primary Stakeholders list could be part of Responsibilities (stakeholder engagement). So we can incorporate. Thus sections: - About the role: includes company mission, role summary, duration, location? Locations: Raritan, New Jersey, United States of America, São José dos Campos, São Paulo, Brazil, São Paulo, Brazil (duplicate). We should preserve location info but not repeat duplicates. Could list unique locations: Raritan, New Jersey, USA; São José dos Campos, São Paulo, Brazil; São Paulo, Brazil (actually São Paulo appears twice; maybe one is São José dos Campos, São Paulo, Brazil and another São Paulo, Brazil (city). We'll keep both as separate: São José dos Campos, São Paulo, Brazil; São Paulo, Brazil. Could combine as "Raritan, New Jersey, USA; São José dos Campos, São Paulo, Brazil; São Paulo, Brazil". We'll include in About the role. - Responsibilities: bullet list of key responsibilities (change strategy & planning, stakeholder engagement & communications, adoption & impact realization, content development & enablement, cross-functional collaboration & governance). We'll include those. - Requirements: combine Required Skills & Expertise and Preferred Qualifications. Could split into two sub-sections? But we can just list bullet points under Requirements, maybe separate required vs preferred with headings inside? But we cannot add extra headings? Could use inside

but better to keep simple: list required skills bullet points, then maybe a note "Preferred qualifications:" then bullet points. That's still within same section. - Pay:

Pay

with paragraph containing the pay range. We must not include boilerplate like EEO, legal, application instructions, duplicated lines, cookie/navigation etc. Also remove repeated mission statements that appear twice. We'll keep one copy. We must not invent or summarize away detail. Must preserve all substantive information. So we need to ensure we don't lose any specifics like "duration-based Change Management Lead position with an anticipated end date on or around 2029." Also "Define and lead the change management strategy aligned to program objectives and transformation milestones." etc. We need to ensure we keep all bullet points from Responsibilities, Required Skills & Expertise, Preferred Qualifications, KPIs, Primary Stakeholders (if we fold them). But we must not lose any specifics. If we fold KPIs and Stakeholders into Responsibilities, we need to ensure we include those details. Let's extract details: From posting: **Role Summary** - Johnson & Johnson MedTech is recruiting for a duration-based Change Management Lead position with an anticipated end date on or around 2029. - We are seeking a Change Management Lead (Manager) to define and execute the change strategy for a MedTech Supply Chain (MTSC) transformation program. - This role will drive stakeholder engagement, communications, and adoption planning across high-visibility workstreams. - The successful candidate will create structured change plans, develop multi‑modal content, and partner with program and functional leaders to embed and sustain new ways of working. **Key Responsibilities** (with subheadings) - Change strategy & planning - Define and lead the change management strategy aligned to program objectives and transformation milestones. - Develop comprehensive change plans, including stakeholder engagement, communications, training, and adoption approaches. - Identify and assess change impacts, risks, and stakeholder needs across functions; recommend mitigation strategies. - Stakeholder engagement & communications - Design and execute stakeholder engagement strategies for MTSC leadership, budget owners, workstream DRIs, and key BU stakeholders. - Lead development of consistent leadership messaging, cascade materials, FAQs, and regular updates to ensure alignment of messaging across PMO, workstreams, and leadership. - Build relationships and influence across a matrixed environment to secure sponsorship and active participation. - Adoption & impact realization - Drive adoption of new processes, tools, and ways of working across MTSC workstreams. - Define, track, and report adoption and behavior-change metrics to measure effectiveness of change initiatives. - Identify resistance points and implement mitigation plans to ensure sustained behavior change. - Content development & enablement - Create scalable, multi-modal content (presentations, playbooks, training aids, FAQs) to support change execution. - Equip leaders and managers with materials and coaching to effectively cascade change through the organization. - Continuously iterate content and engagement approaches based on feedback and outcomes. - Cross-functional collaboration & governance - Partner with PMO, project leadership, Finance, Operations, and PM/Analytics to align change activities with program deliverables and reporting cadences. - Participate in governance forums to surface change risks, readiness, and mitigation plans. - Support readiness checks and pre-/post-implementation assessments to validate adoption and sustainment. **Required Skills & Expertise** - Strong experience in change management within large-scale transformation programs, ideally in supply chain, operations, or medtech/healthcare. - Proven ability to design and deliver stakeholder engagement strategies that drive adoption and organizational alignment. - Excellent communication and storytelling skills across multiple organizational levels (leadership, managers, individual contributors). - Experience developing structured change plans, communications, training materials, and adoption measurement approaches. - Ability to navigate complex, matrixed environments and influence without formal authority. - Strong project management skills, with attention to detail and the ability to operate under tight timelines. **Preferred Qualifications** - 5+ years of relevant change management, organizational development, or transformation experience; manager level experience preferred. - Certification in change management (e.g., Prosci) or equivalent practical experience. - Familiarity with adoption metrics, readiness assessments, and stakeholder sentiment measurement. - Experience with communications and collaboration platforms (e.g., MS Teams, SharePoint, learning platforms) and content design tools (PowerPoint, simple LMS authoring). - Bachelor’s degree in Business, Organizational Development, Communications, or related field; advanced degree a plus. **Key performance indicators (KPIs)** - Clarity and buy-in for the change management approach. - Effectiveness of communications (reach, clarity, engagement). - Adoption rates for new processes and tools; measurable behavior change. - Stakeholder alignment and sentiment (sponsor and manager engagement). - Timeliness and quality of readiness assessments and adoption reporting. **Primary Stakeholders** - Program leadership and sponsor - PMO leadership and program management teams - Finance / Program Finance Lead - Workstream DRIs and Operations partners - IT / Data Engineering and Analytics teams - Business unit leaders and commercial stakeholders **Pay** - The anticipated base pay range for this position is : $87,000.00 - $150,650.00 Also location: All Job Posting Locations: Raritan, New Jersey, United States of America, São José dos Campos, São Paulo, Brazil, São Paulo, Brazil We need to include location in About the role. Also we have repeated mission statements; we should include only once. Now craft HTML. Structure:

About the role

At Johnson & Johnson, we believe health is everything... (mission statement). Role summary: duration-based Change Management Lead position with anticipated end date on or around 2029... Locations: Raritan, New Jersey, USA; São José dos Campos, São Paulo, Brazil; São Paulo, Brazil.

But we need to preserve all substantive info: mission statement, role summary, maybe also mention that it's Johnson & Johnson MedTech, a member of Johnson & Johnson's Family of Companies. Also mention that we are seeking a Change Management Lead (Manager) to define and execute change strategy for MedTech Supply Chain transformation program. Also mention that role will drive stakeholder engagement, communications, adoption planning across high-visibility workstreams. Also mention that successful candidate will create structured change plans, develop multi-modal content, partner with program and functional leaders to embed and sustain new ways of working. We'll combine. Then Responsibilities:

Responsibilities

• ... each bullet as
• maybe grouping sub-bullets? Could keep each bullet as separate
• . For sub-bullets under