Senior Lead, Leadership Experience Partner

We need to output HTML fragment with headings

for sections: 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: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove privacy statement, EEOC statement, ADA disclaimer, sourcing model, etc. We need to preserve all substantive information: job description paragraphs, about the role, what you will be doing (list of duties), required qualifications, preferred qualifications, maybe benefits? The posting mentions "Competitive salary and benefits" under "A Career At FIS Is More Than Just a Job." It says "Competitive salary and benefits". That's a statement about benefits and pay but not specific details. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Competitive salary and benefits" but no specifics. Is that enough? The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive salary and benefits" is vague but it's a statement. It's not a specific number or detail. Might be considered filler? It's not a specific detail; it's generic. Likely we should not create Benefits or Pay sections because they lack specifics. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Benefits, Pay, Schedule. Thus sections: About the role (we have a paragraph), Responsibilities (list of duties), Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications?), Skills (maybe we can combine required and preferred? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe we can extract skills from required/preferred: facilitation, presentation, communication, stakeholder management, etc). But we must not invent or summarize away detail. We can list skills as bullet points derived from the text. That's permissible as long as we don't invent. We can extract explicit skill mentions: "Strong facilitation, presentation and communication skills", "Proven ability to manage multiple priorities while maintaining high standards of quality, consistency and operational excellence", "Strong consulting, facilitation and stakeholder management skills with the ability to influence senior leaders without direct authority", "Experience enabling facilitators, instructors or subject matter experts to effectively deliver learning programs", "Experience with virtual learning technologies, blended learning environments, learner engagement platforms, and AI technology and platforms". Also certification preferences. We need to ensure we don't duplicate content. We can put required qualifications under Requirements heading, preferred qualifications under Qualifications heading, and skills under Skills heading (maybe overlapping). But we must not repeat same info in multiple sections? The instruction doesn't forbid repetition but says preserve ALL substantive information; we can repeat if needed but better to avoid duplication. However we need to include all info; we could put required qualifications in Requirements, preferred in Qualifications, and skills in Skills (maybe summarizing skill-related statements). But some skill statements appear also in required qualifications; we could still include them there and not duplicate in Skills, but then we might miss some skill details if we omit them. Better to include skill details under Skills heading, and keep required qualifications focusing on education/experience, etc. Let's parse. Required qualifications bullet points (from text): - Bachelor's degree in Human Resources, Organizational Development, Learning and Development, Business, Education or a related field, or equivalent combination of education and experience - 12+ years of experience in leadership development, talent development, organizational effectiveness, or executive education, with direct ownership over designing and delivering leadership development solutions including a focus specifically on Director, VP, or executive level positions - Demonstrated ability to partner with business leaders to design, adapt and deliver impactful learning experiences and leadership journeys (beyond programs or workshops), that influence leader capabilities and support long-term adoption of behavior shifts and new ways of working - Experience enabling facilitators, instructors or subject matter experts to effectively deliver learning programs and development initiatives - Strong facilitation, presentation and communication skills, including the ability to engage diverse audiences, adapt to group dynamics and build credibility with stakeholders - Proven ability to manage multiple priorities while maintaining high standards of quality, consistency and operational excellence - Proven success creating end-to-end leadership journeys that drive measurable behavior change and business outcomes - Strong consulting, facilitation and stakeholder management skills with the ability to influence senior leaders without direct authority Preferred qualifications: - Advanced experience delivering enterprise-wide leadership development or talent development programs in a large, matrixed, global organization - Certification in leadership assessment tools, facilitation, coaching, adult learning, organizational development or related disciplines. (e.g~ Hogan, organizational development certifications, Gallup, MBTI, DISC, Birkman, ICF Coaching Certification, etc) - Experience with virtual learning technologies, blended learning environments, learner engagement platforms, and AI technology and platforms Now responsibilities list (What You Will Be Doing): - Deliver high-quality leadership and capability-building programs that create engaging and impactful learning experiences for diverse audiences - Build the end-to-end experience that leaders will undergo to build capability, including metrics of success that indicate behavior change and ROI - Facilitate instructor-led, virtual and blended learning experiences while adapting content, pacing and delivery approaches to meet participant needs - Partner with business leaders and subject matter experts to translate business priorities and real-world challenges into relevant learning experiences - Reinforce leadership behaviors and skill application through coaching moments, guided practice, experiential learning activities and real-world scenarios - Gather participant feedback, learning insights and field signals to continuously improve program quality, relevance and learner outcomes - Deliver a train-the-trainer model that equips subject matter experts and instructors to consistently deliver high-quality learning experiences - Collaborate with internal experts and facilitators to coordinate specialized content and support scalable program delivery models - Apply delivery standards, playbooks, templates and best practices to ensure consistent, repeatable and high-quality program execution - Manage program delivery operations, participant engagement activities, feedback processes and learning continuity across multiple initiatives - Serve as a trusted advisor to stakeholders by providing insights and recommendations that strengthen learning effectiveness and business impact - As a Senior Lead, Leadership Experience Partner, lead the end-to-end curation and delivery of enterprise development programs that build capability, reinforce key behaviors and support organizational growth Note the last bullet repeats some of earlier but okay. Now About The Role paragraph: "As a Senior Lead, Leadership Experience Partner, you will lead the delivery of enterprise leadership and professional development experiences that help employees build critical skills and achieve business goals. You will serve as a strategic delivery partner, translating business priorities into engaging, practical learning experiences that drive measurable behavior change and skill application. Working closely with leaders, facilitators and subject matter experts, you will ensure learning programs are relevant, scalable and consistently delivered with excellence. This role combines facilitation expertise, operational rigor and continuous improvement to create meaningful learner experiences across the organization." We also have earlier generic description about FIS but that's boilerplate? It's about company mission; could be considered substantive? It's not specific to role. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The introductory paragraph about FIS mission might be considered generic but not explicitly listed as boilerplate. However it's not specific to the role; but it's part of job description. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it if it's substantive. However the instruction also says "Prefer a few substantive sections over many thin ones." The mission paragraph could be part of About the role? But we already have About the role section; we could include that mission paragraph as part of About the role? The About the role heading currently has the paragraph describing the role. The earlier paragraph about FIS innovators etc could be considered a general company overview; we could either include it under About the role as introductory context or drop it as boilerplate? It's not explicitly listed as boilerplate to remove, but it's generic marketing fluff. Might be considered not substantive for the role. However the instruction says preserve ALL substantive information; if we consider it not substantive (just fluff), we could drop it. Safer to keep it? The instruction about "Prefer a few substantive sections over many thin ones" suggests we should not create sections with little content. The mission paragraph is not a section; it's just a paragraph. We could include it as a

before the headings? The instruction says output only HTML fragment; we can include paragraphs outside headings. It didn't say we must wrap everything in headings. So we could include a

with that mission summary, then headings for About the role, Responsibilities, Requirements, Qualifications, Skills. That would preserve all info. But we need to avoid repeating job title as heading. Already not. We must not include Pay/Benefits/Schedule sections because no specifics. Now we need to format lists: Use

• for any list of duties/requirements/benefits. So responsibilities list as
  . Required qualifications as
  . Preferred qualifications as
  . Skills list as
  . Also maybe we could combine required and preferred qualifications under Requirements and Qualifications headings respectively. Now we need to ensure we don't include duplicated lines. There's some duplication: The responsibilities list includes a bullet about "As a Senior Lead, Leadership Experience Partner, lead the end-to-end curation and delivery..." which is similar to About the role paragraph. Might be considered duplicate but it's still substantive; we could keep it. Now we need to strip out boilerplate: Privacy Statement, EEOC Statement, ADA Disclaimer, Sourcing Model, etc. Also remove lines like "Position Type Full time Type Of Hire Experienced (relevant combo of work and education)" - that's metadata; we should drop it per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can drop that line entirely. Also drop "A Career At FIS Is More Than Just a Job. It’s The Chance To Shape The Future Of Fintech. At FIS, We Offer You A voice in the future of fintechAlways-on learning and developmentCollaborative work environmentOpportunities to give backCompetitive salary and benefits" - This includes "Competitive salary and benefits" which we decided not to create a section for; but we could keep this as a

  maybe? It's somewhat generic but includes mention of benefits. However it's also somewhat boilerplate marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's more of a benefits blurb. Since we are not making a Benefits section, we could keep it as a

  under maybe a general section? But we have no heading for it. Could we include it as a paragraph before sections? It's not duplicated. It's substantive? It mentions benefits but not specific. Might be considered filler. Safer to drop it? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary and benefits". That's a statement about benefits and pay, albeit vague. But we are not making a section; we could still keep the sentence as a paragraph. However the instruction also says "Prefer a few substantive sections over many thin ones." If we keep that sentence as a paragraph, it's thin. Might be better to drop it to avoid thin content. I'd drop it. Thus final HTML: start with a

  containing the FIS mission paragraph? Actually we have the mission paragraph: "Every day at FIS, innovators, problem-solvers