Director of Learning & Development

We need to output HTML fragment with sections: About the role? Actually the posting includes "The Opportunity" description, responsibilities, qualifications, benefits, etc. We must not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We need to parse the posting: - Intro about company: could be "About the role"? Actually "About the role" is generic; we could use "About the role" heading for description of opportunity? The posting includes "The Opportunity" describing role. Could map to "About the role". Or we could use "About the role" heading and put that paragraph. - Responsibilities: there is a list under "Key Responsibilities". Use

Responsibilities

with

• . - Requirements/Qualifications: there is "What You Bring To The Table" (experience, skills) and "What Will Make You Stand Out?" (education, certifications, etc). Could combine into Requirements or Qualifications. We need to decide: maybe "Qualifications" heading for required experience and skills; "Skills" heading for standout? But we should avoid thin sections. Could combine into one "Qualifications" section covering both required and preferred. However we need to preserve all substantive info. - Benefits: there is "Beyond the Paycheck" then list: Competitive Salary (but says commensurate with experience, performance-based bonuses), Purpose-Driven Work Environment, Flexible Dress Code, People-Focused Culture, Tools for Success, Health and Wellness, Retirement Planning, Life Insurance. Also mention "Competitive Salary : Compensation commensurate with your experience, with the opportunity to earn performance-based bonuses". Since we should not create Pay section unless posting actually states them. It does mention compensation commensurate with experience and performance-based bonuses. That is somewhat vague but still specific? It says "Competitive Salary : Compensation commensurate with your experience, with the opportunity to earn performance-based bonuses". That's not a specific number but it's still mention of pay. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should NOT create a Pay section if the content is just "commensurate with experience". The posting says "Competitive Salary : Compensation commensurate with your experience, with the opportunity to earn performance-based bonuses." That's basically "commensurate with experience" plus bonus mention. That's likely considered filler. So we should avoid a Pay section. However we could include that info under Benefits? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits section is allowed if there are benefits. There are benefits listed: health, dental, vision, 401k match, life insurance, etc. So we can have Benefits section. - Schedule: not mentioned, so no Schedule section. - Skills: maybe we could have a Skills section for standout qualifications? But we could incorporate into Qualifications. We need to avoid boilerplate like EEO, E-Verify, etc. Remove those lines. We need to preserve all substantive information: company intro, opportunity description, responsibilities, qualifications (experience, skills, education, certifications, experience in fire protection, etc), benefits (health, dental, vision, 401k match, life insurance, flexible dress code, people-focused culture, tools for success, purpose-driven work environment, competitive salary mention? maybe we can include salary info under Benefits? But it's not a benefit per se; but we could include under "Compensation" but that's Pay. Since we shouldn't create Pay section due to vague statement, maybe we can include that sentence in the Benefits section as part of "Competitive Salary" but that might be considered Pay. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid mentioning compensation within Benefits section; but it's safer to not create a Pay section. We could include the compensation sentence under a "Compensation" paragraph inside Benefits? Might be considered a Pay section though. Safer to omit the compensation sentence entirely? But we must preserve ALL substantive information. The compensation sentence is substantive: "Competitive Salary : Compensation commensurate with your experience, with the opportunity to earn performance-based bonuses." It's somewhat vague but still substantive. We need to include it somewhere. Perhaps we can include it under a "Compensation" heading? But that would be a Pay section, which we should avoid if it's just "commensurate with experience". The instruction 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. So if we create a Pay heading and put that sentence, it's a heading followed by filler text (commensurate with experience). That's disallowed. So we cannot create a Pay section. We could embed that sentence inside another section, like Benefits or About the role, but that might be odd. However the instruction only forbids creating a Pay section; it does not forbid mentioning compensation elsewhere. So we can include that sentence in the Benefits section as a note about compensation. That might be acceptable. Similarly, "Flexible Dress Code" is a benefit; we can include under Benefits. Thus sections: - About the role (or maybe "About the role" heading) containing the company intro and opportunity description? The company intro is about Encore; but "About the role" could be the opportunity description. We could split: maybe "About the role" heading for the opportunity description; and we could have a separate "About Encore" but not required. Since we only need headings from list, we can use "About the role" for the opportunity description. The company intro could be placed before any heading as a

  (since no heading). That's allowed: we can have introductory paragraph(s) before first heading. Thus output:

  At Encore Fire Protection, we are proud to be the East Coast's largest full-service fire protection company, serving over 90,000 customers from Maine to Louisiana . Our team of more than 2,400 dedicated employees provides customized fire protection solutions that protect lives and property every day . Our goal is to deliver a unique experience to those who depend on us to make their lives safer and easier. We are passionate about growing with purpose, driving real innovation, and creating a winning culture built on teamwork, success, and an unwavering commitment to safety. Our mission? To be the best fire protection company the industry has ever seen.

  About the role

  The Director of Learning and Development is Encore's first dedicated hire in shaping how our people grow and will be integral in building that function from the ground up . This is a unique opportunity for a hands-on training leader to shape how our organization develops talent – from technicians out in the field to our corporate staff across all levels. You 'll own everything from conceptualization and curriculum design to hands on facilitation – working closely with leadership to identify skill gaps and build programs that support individual growth as well as company - wide performance. This role combines designing scalable training programs and establishing the systems, tools, and cadences that let L&D operate as a durable function rather than a one-off initiative. The ideal candidate will have a point of view on how Encore should develop talent, partner with leaders across the business to identify real skill and performance gaps and translate those gaps into training that people actually use . You will partner closely with department heads and field leadership, using instructional design and facilitation skills to build buy-in for a function that doesn't yet exist.

  Responsibilities

  • Design & implement Encore’s first formal learning & development strategy, aligned with business goals and growth plans
  • Build scalable training programs from scratch, inclusive of onboarding, technical/trade skills, leadership development, compliance, and soft skills
  • Develop and deliver training content (both in person and virtually), and coach others to help facilitate as we scale the Learning & Development function
  • Expand the Docebo LMS ecosystem, integrating additional learning tools and content platforms as needed to build a scalable training infrastructure across all locations
  • Establish training metrics to evaluate programs, continuously improving program content and delivery and driving measurable outcomes
  • Develop career pathing & advancement frameworks to support internal mobility and employee retention
  • Partner with business leaders to identify skill gaps and align learning initiatives
  • Lead with operational excellence , managing complex projects and timelines with discipline and foresight, ensuring flawless delivery and continuous improvement

  Qualifications

  • 8+ years of progressive experience within a Human Resources function, including a minimum of 5 years dedicated specifically to Learning & Development
  • Proven ability to both design and facilitate training programs -- this is not a strategy only role
  • A scrappy, entrepreneurial builder’s mindset with a strong bias for action
  • Skilled in crafting comprehensive blended learning solutions across diverse delivery methods; including in-person, virtual, and self-paced
  • Excellent communication and relationship building skills, comfortable engaging with employees at every level, from technicians to executives

  Skills

  • Bachelor's Degree in Human Resources , Business Administration, Organizational Psychology, Communications or relevant fields.
  • Additional certifications such as SHRM-SCP, SPHR, CPTD or CPTM nice to have, but not required
  • Experience working across diverse audiences (field/trade employees and office staff) is a strong plus
  • Experience in fire protection, construction, field services, or another decentralized, trade-based industry
  • You’ve built an L&D function from scratch, without the assistance of a team or existing infrastructure
  • Familiarity with AI-enhanced learning tools

  Benefits

  • Competitive Salary : Compensation commensurate with your experience, with the opportunity to earn performance-based bonuses.
  • Purpose-Driven Work Environment : We believe in working smarter, not harder. You’ll be part of a culture that values results, and we empower our team to focus on impactful work.
  • Flexible Dress Code : Upon joining, you’ll receive branded Encore swag, and we believe in dressing for the objective , not the occasion. Most days, you can enjoy a casual work environment, but we’ll dress up when the situation calls for it.
  • People-Focused Culture : We know our greatest strength is our people. That’s why we’ve built a culture that encourages experimentation, learning, and improving together. You’ll have the space to share your ideas and help shape a company that is constantly growing.
  • Tools for Success: Access to leading-edge web-based productivity tools.
  • Health and Wellness : Comprehensive medical, dental, and vision coverage through Blue Cross to keep you and your family healthy.
  • Retirement Planning : Participation in our Fidelity 401(k) plan with a company match, helping you save for your future.
  • Life Insurance : Company-paid life insurance policy of $50,000 to give you peace of mind.
  We must ensure we didn't include boilerplate like EEO, E-Verify, etc. We removed those lines. Check for any repeated lines: we removed duplicated lines. Check for any filler placeholder text: Benefits includes "Competitive Salary : Commensurate with your experience". That's still filler but it's inside Benefits section, not a Pay section. The instruction only forbids creating Pay/Schedule/Benefits sections unless posting actually states them. Benefits section is allowed because there are real benefits