Learning and Development_Program Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info. We need to parse the job description. Key parts: - Job description: "The Program Manager, ONWARD Connected, is responsible for the end-to-end management and execution of assigned ONWARD Connected programs. This role serves as one of the operational owners for programs, driving planning, coordination, participant experience, communications, logistics, reporting, and continuous improvement from initial planning through program close. The Program Manager works closely with the ONWARD Connected Lead, subject matter experts, facilitators, Learning Operations, Learning Communications, Learning Impact, Connected Capabilities Leads, Learning& Performance Business Partners, HR Business Partners, and external vendors to translate program objectives into well-executed, high-quality learning experiences. This role requires strong project and program management skills, sound judgment, attention to detail, and the ability to independently manage multiple programs, stakeholders, timelines, and priorities. The Program Manager proactively identifies risks and opportunities, resolves issues, and ensures programs are delivered effectively, consistently, and with a strong participant experience." That's about the role (overview). Could be "About the role" section. Then "Key Responsibilities" with sub-sections: Program Planning & End-to-End Management, Nominations & Participant Management, Participant Experience & Communications, Digital & On-Demand Program Management, Program Operations & Logistics, Data, Reporting & Continuous Improvement, Systems, Documentation & Governance. Each has bullet-like paragraphs (some sentences). We need to turn them into

  • for any list of duties/requirements/benefits. So each bullet point can be a
  • . The subheadings could be maybe

    ? But only allowed headings are

    for section headings. We could treat each major responsibility as a

    ? But the instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the role, Responsibilities, etc. Within Responsibilities we can have

    • items. We should not create extra headings for sub-sections unless they are separate sections like "Program Planning & End-to-End Management". But those are not in the allowed list; we could still include them as

      ? The instruction says use

      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)." Likely they expect only those section headings. However we can still use

      for each major responsibility if we consider them sections. But better to follow instruction: Use

      for section headings (like About the role, Responsibilities, etc). So we will have sections: About the role, Responsibilities, Requirements (maybe Key Capabilities), Skills (maybe overlapping), Benefits, Pay, Schedule. We need to extract Requirements/Qualifications/Skills from "Key Capabilities". That list includes program & project management, ownership & accountability, stakeholder management, communication, organization & execution, problem solving & judgment, continuous improvement, learning program operations. Those are capabilities/skills. Could be placed under Requirements or Skills. We'll decide: Use "Requirements" for required experience/skills, and "Skills" maybe not needed if overlapping. But we need to avoid thin sections. We'll combine capabilities into either Requirements or Skills. Since they are capabilities, maybe "Requirements". We'll put them as

      • . Benefits: Not mentioned explicitly. There's mention of salary range $50,000-$95,000. That's Pay. Also schedule: "Omnicom’s policy requires employees to work in the office for a minimum of three days a week, unless additional in-office days are directed by their agency or manager. Our objective is to increase this requirement over time, and many of our agencies as well as Omnicom’s corporate group already require five days of in-office attendance." That's schedule info (in-office requirement). So we can have Pay and Schedule sections. Benefits: Not mentioned besides maybe generic statements about inclusive teams etc. Not specific benefits like health, retirement. So we should not create Benefits section if no specific content. We also need to include any other substantive info like "Omnicom is committed to hiring and developing exceptional talent..." that's fluff; could be omitted as boilerplate? It's not a legal EEO but it's a value statement. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The value statement about inclusive teams maybe not boilerplate but could be considered fluff. However it's substantive about culture. Might keep as part of About the role? But we already have About the role overview. Could add a paragraph about company commitment. But to be safe, we can include it in About the role as prose. We must not repeat job title as heading. So no heading "Program Manager, ONWARD Connected". We'll just have sections. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities bullet points. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

        About the role

        ... overview paragraph(s) ...

        Responsibilities

        • Program Planning & End-to-End Management: ... (the whole paragraph)
        ... etc for each responsibility subsection. etc. But each responsibility subsection has multiple sentences; we could keep as one
        • containing the whole block. That's okay. We need to ensure we don't lose any detail. Let's extract each responsibility block text. From the posting: **Program Planning & End-to-End Management** "Own the end-to-end planning and execution of assigned ONWARD Connected programs, partnering with the Connected Lead and key stakeholders to establish program timelines, cadence, target audiences, milestones, and delivery plans.Develop and manage annual program schedules, ensuring all critical milestones—including marketing, nominations, preparation, delivery, evaluation, and follow-up—are clearly defined and proactively managed.Drive cross-functional coordination with SMEs, facilitators, vendors, Learning Operations, and other partners to ensure programs are fully planned and delivery-ready.Identify dependencies, risks, and potential conflicts across programs and proactively develop solutions to keep programs on track.Partner with Learning Operations to align program schedules and requirements with other learning offerings across the Omnicom network.Serve as the central point of accountability for program readiness, ensuring key activities, deliverables, and stakeholder commitments are completed on time." **Nominations & Participant Management** "Own and manage the nomination and enrollment process for assigned programs, including participant criteria, timelines, processes, and stakeholder communications.Partner with the appropriate Connected Capability Learning Business Partner (LPBP) and other stakeholders to design and execute nomination processes that align with program objectives.Develop and maintain participant pools, including candidate lists, waitlists, and alumni populations, ensuring accurate and timely participant information.Monitor participation across programs and proactively address gaps, changes, or issues that may affect program composition or delivery.Ensure participant selection and enrollment processes support appropriate diversity and cross-network representation where applicable." **Participant Experience & Communications** "Own the participant experience from initial nomination through program completion, serving as the primary point of contact and ensuring participants have the information and support needed at every stage.Develop and manage all participant-facing communications, including:Calendar invitationsWelcome and program informationPre-work, logistics, and remindersSession updates, changes, and FAQsPost-program follow-up and resourcesEstablish and maintain communication plans, templates, and timelines to ensure consistent and timely participant engagement.Partner with Learning Communications to leverage communication tools, automation, and scalable processes that improve the participant experience and operational efficiency.Monitor program-specific inboxes and communication channels, proactively addressing participant questions and concerns and escalating issues when appropriate.Identify opportunities to improve participant communications and the overall program experience based on feedback, participation data, and recurring questions or issues." **Digital & On-Demand Program Management** "Own the operational management of programs with on-demand or digital components, ensuring participants have appropriate access to required learning experiences and resources.Partner with Learning Operations to assign programs to participants through the LMS and ensure accurate enrollment and tracking.Monitor enrollment, progress, and completion data and proactively follow up with participants who are at risk of not completing required components.Ensure all program information in the LMS—including descriptions, dates, links, prerequisites, and other requirements—is accurate, current, and aligned with the program experience.Identify and resolve issues affecting the digital participant experience in partnership with Learning Operations and other relevant stakeholders." **Program Operations & Logistics** "Own all operational aspects of program delivery, ensuring programs are fully prepared and executed according to established plans.Manage virtual program logistics, including platform setup, breakout rooms, recordings, technology testing, and other delivery requirements.Manage in-person program logistics, including rooms, audiovisual requirements, materials, and other onsite needs.Coordinate the development, preparation, and distribution of program materials—including agendas, participant guides, facilitator guides, workbooks, and slide decks—in collaboration with Connected Lead, SMEs, and facilitators.Maintain accurate participant rosters and attendance records and ensure required information is provided to Learning Operations for LMS and reporting purposes.Ensure attendance and other program records required for compliance, reporting, and governance are accurate and maintained appropriately.Proactively identify operational risks or gaps and drive resolution to ensure a seamless program experience." **Data, Reporting & Continuous Improvement** "Partner with Learning Impact to establish evaluation approaches that generate meaningful feedback and insights for each program.Own the deployment, tracking, and completion of program evaluations, including surveys and pulse checks.Analyze participant, completion, attendance, and evaluation data to identify trends, opportunities, and potential issues.Translate data and feedback into concise, actionable insights and recommendations for Connected Lead, SMEs, and key stakeholders, including Connected Capabilities Leads, LPBPs, and HRBPs.Monitor program performance and proactively identify trends such as low attendance, participant drop-off, completion challenges, experience gaps, and areas of strong engagement.Use insights and stakeholder feedback to recommend and implement improvements to program design, operations, communications, and participant experience.Maintain appropriate reporting and documentation to support ongoing program visibility and decision-making." **Systems, Documentation & Governance** "Own the accuracy and integrity of centralized program records and ensure information is current, accessible, and appropriately maintained.Manage and maintain:Full program calendarParticipant lists and alumni recordsProgram artifacts, including agendas, presentations, communication templates, surveys, reports, and supporting materialsEnsure appropriate version control across curricula, program materials, and other key program assets.Support and uphold applicable data privacy, compliance, and governance requirements related to participant communications and data handling.Develop and maintain program documentation, including FAQs, troubleshooting guides, standard operating procedures, and “how we run” documentation.Build and maintain a strong program knowledge base that enables consistency, scalability, and effective onboarding of new team members.Identify opportunities to improve program processes, documentation, systems, and governance to increase efficiency and scalability across ONWARD Connected." Now Key Capabilities (skills): "Program & Project Management: Demonstrated ability to independently manage complex programs from planning through execution, evaluation, and close.Ownership &