Director, Talent Development

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about community, benefits, etc. That's like "About the role" or maybe "About the company". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. The posting includes: community, benefits, balance, opportunity, recognition. That's more like company culture/benefits. Could be "About the role" or "About the company". But we have a separate Benefits section: they list minimum 50% childcare discount, immediate access to benefits, innovative health programs, 401(k) company match, flexible schedules, no nights/weekends, ability to bring children to work, paid time off, ongoing training, tuition reimbursement, credential assistance, Master Teacher Program. Those are benefits. So we should have a Benefits section with those items as list. Responsibilities: list of key responsibilities bullet points. Requirements/Qualifications: Minimum Qualifications and Preferred Qualifications. Could combine into Requirements? The instruction says use headings like Requirements, Qualifications, Skills. We need to decide. Probably "Requirements" for minimum qualifications, "Preferred Qualifications" maybe as part of Qualifications? But we can have "Qualifications" heading and include both minimum and preferred? However they said prefer a few substantive sections over many thin ones. Could have "Requirements" (minimum) and "Preferred Qualifications" maybe as part of same section? But we could have "Qualifications" with subheadings? Not allowed; only headings

. Could have two sections: "Requirements" (minimum) and "Preferred Qualifications". That's okay. Skills: Knowledge, Skills and Abilities section. We also have a paragraph about community etc. Could be "About the role" or "About the company". Since they said do NOT repeat the job title as a heading. The job title is Director of Talent Development. So we can have an "About the role" section describing the role and the community etc. That paragraph includes: "Join a strong community where all we do is care-for the children and families we serve every day, as well as for our dedicated team members. Our people are our best asset. We listen and we know what you're looking for: You want benefits... You want balance... You want opportunity... You want recognition." That's basically describing the role and company culture. So we can put that as About the role. We must remove boilerplate: EEO statement, etc. Remove that. We must not include Pay or Schedule sections unless explicitly stated. They mention flexible schedules, no nights or weekends, ability to bring children to work, paid time off. That's schedule info. Should we create a Schedule section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state schedule info: flexible schedules, no nights or weekends, ability to bring children to work, paid time off. So we can include a Schedule section. However they also said prefer a few substantive sections over many thin ones. Could combine schedule info into Benefits? But schedule is separate concept. Might be okay to have Schedule section. But we also have Benefits section already with many items. Could we merge schedule into Benefits? The instruction says use Benefits heading for benefits. Schedule heading for schedule. Since they explicitly mention schedule details, we can create Schedule section. Pay: not mentioned, so omit. Now we need to preserve all substantive information. Let's extract. About the role paragraph: "Join a strong community where all we do is care-for the children and families we serve every day, as well as for our dedicated team members. Our people are our best asset. We listen and we know what you're looking for: You want benefits. We support you with a minimum 50% childcare discount, immediate access to benefits, innovative health programs, 401(k) company match, and much more. You want balance. We offer flexible schedules that work for you, no nights or weekends, the ability to bring your children to work with you, and paid time off. You want opportunity. We invest in your future with ongoing training, tuition reimbursement, credential assistance, and our unique Master Teacher Program. You want recognition. We provide a positive, fun workplace where employees are appreciated." We should not repeat the benefits list again in Benefits section? But we need to preserve all info. The About the role paragraph already includes some benefits. If we also list them in Benefits section, we would be duplicating. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but we should avoid unnecessary duplication? It didn't say to avoid duplication. However typical approach is to not repeat same info in multiple sections. But we could keep the About the role paragraph as is, and then Benefits section could list the same items? That would be duplication. Better to keep the About the role paragraph as a summary, and then Benefits section list the specific benefits. But the About the role paragraph already lists many benefits; we could keep it and not duplicate. However we need to ensure we don't lose any detail: the About the role paragraph includes: minimum 50% childcare discount, immediate access to benefits, innovative health programs, 401(k) company match, flexible schedules, no nights/weekends, ability to bring children to work, paid time off, ongoing training, tuition reimbursement, credential assistance, Master Teacher Program. Those are all benefits. If we put them in Benefits section as list, we would be repeating. But maybe we can keep About the role paragraph as a narrative and then Benefits section list the same items but that's duplication. The instruction didn't forbid duplication, but "Prefer a few substantive sections over many thin ones." Duplication would create thin sections? Not exactly. Might be okay but better to avoid redundancy. We could keep About the role paragraph as a brief overview without listing specifics, but the paragraph includes specifics. If we remove specifics from About the role, we would lose detail. So we need to keep them somewhere. Perhaps we keep About the role paragraph as is, and then we do not create a separate Benefits section (since benefits already covered). But the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have specific content for benefits, but we already covered it in About the role. However we could still create a Benefits section and list them, but that would duplicate. I'd choose to not duplicate and keep About the role paragraph containing the benefits details, and omit a separate Benefits section. However the instruction says "Prefer a few substantive sections over many thin ones." Having About the role with benefits details is fine. But we might still want a Benefits section to follow the expected format. The example headings include Benefits. The posting definitely has benefits content. So likely they expect a Benefits section. The About the role paragraph could be more generic about community, not listing benefits. But the paragraph includes benefits. Could we split: About the role paragraph: "Join a strong community where all we do is care-for the children and families we serve every day, as well as for our dedicated team members. Our people are our best asset. We listen and we know what you're looking for." Then we could move the specific benefit statements to Benefits section. That would preserve all info without duplication. Let's do that: About the role: first two sentences about community and people. Then Benefits section list the specific benefits. Thus we need to parse the paragraph into two parts: generic community statement and the benefit statements. Original: "Join a strong community where all we do is care-for the children and families we serve every day, as well as for our dedicated team members. Our people are our best asset. We listen and we know what you're looking for: You want benefits. We support you with a minimum 50% childcare discount, immediate access to benefits, innovative health programs, 401(k) company match, and much more. You want balance. We offer flexible schedules that work for you, no nights or weekends, the ability to bring your children to work with you, and paid time off. You want opportunity. We invest in your future with ongoing training, tuition reimbursement, credential assistance, and our unique Master Teacher Program. You want recognition. We provide a positive, fun workplace where employees are appreciated." We can keep About the role as: "Join a strong community where all we do is care-for the children and families we serve every day, as well as for our dedicated team members. Our people are our best asset. We listen and we know what you're looking for." Then Benefits section list: minimum 50% childcare discount, immediate access to benefits, innovative health programs, 401(k) company match, flexible schedules that work for you, no nights or weekends, ability to bring your children to work with you, paid time off, ongoing training, tuition reimbursement, credential assistance, unique Master Teacher Program, positive fun workplace where employees are appreciated (recognition). Actually recognition is also a benefit? Could be part of Benefits or separate. But we can include recognition as a benefit. Now Responsibilities: list bullet points from "Key Responsibilities:" and "Other duties as assigned." We'll include the bullet points. Minimum Qualifications: list. Preferred Qualifications: list. Knowledge, Skills and Abilities: list. We need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include any markdown code fences. Let's craft. Sections:

  About the role

  Join a strong community where all we do is care-for the children and families we serve every day, as well as for our dedicated team members. Our people are our best asset. We listen and we know what you're looking for.

  Benefits

  • Minimum 50% childcare discount
  • Immediate access to benefits
  • Innovative health programs
  • 401(k) company match
  • Flexible schedules that work for you
  • No nights or weekends
  • Ability to bring your children to work with you
  • Paid time off
  • Ongoing training
  • Tuition reimbursement
  • Credential assistance
  • Unique Master Teacher Program
  • Positive, fun workplace where employees are appreciated

  Responsibilities

  • Own the enterprise-wide talent development strategy and align programs with business goals, workforce planning, and organizational growth.
  • Partner with senior leaders and HR business partners to identify capability gaps and develop scalable solutions that address business and workforce needs.
  • Set the strategy and lead the design of foundational training, role-readiness frameworks, learning journeys, onboarding, and new-manager development programs.
  • Identify and implement AI-powered tools and automated workflows that improve content creation, learning personalization, skills assessment, reporting, and program delivery.
  • Champion responsible experimentation and adoption of emerging learning technologies based on organizational fit, value, and return on investment.
  • Build, lead, coach, and develop a high-performing talent development team while managing priorities, budgets, learning platforms, and vendor relationships.
  • Define and monitor measures of program effectiveness, engagement, promotion, retention, time-to-proficiency, and return on investment; use insights to continuously improve programs.
  • Advise executive leadership on talent development needs, outcomes, and innovative solutions that strengthen organizational capability.
  • Other duties as assigned.

  Minimum Qualifications

  • Eight or more years of progressive experience in talent development, organizational development, or learning and development is required.
  • Three or more years of experience leading people is required.
  • Hands-on experience or strong working knowledge of AI tools and platforms applied to learning and development or talent functions is required.
  • Proven ability to influence senior stakeholders and serve as a strategic partner to executive