AI Software Engineering Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - Intro paragraph: "What if your next software development leadership role helped shape how AI enables R&D teams to build the future - while supporting a mission that matters. Accelerating responsible AI adoption across software and firmware teams that help safeguard the world’s most vital resources..." This is about the role. Could be "About the role". - Then description of Veralto mission, etc. Might be part of About the role. - "We offer:" list: Bonus/incentive pay, flexible remote-friendly work environment, paid holidays, permissive PTO, ongoing investment in career via training, on-the-job development, coaching. - Then "Reporting to the CTO, AI & Software, the AI Software Engineering Lead will be the first hire dedicated to accelerating how Veralto Water Quality software and firmware teams use AI to build better, faster, and smarter." This is about role. - Then description of responsibilities: "You will operate like a technical SWAT-team leader..." etc. That's responsibilities. - Then "What You'll Do" bullet list: embed directly with teams, coach developers, create playbooks, support Kaizens, evaluate tools, build proofs of concept, measure impact, lead through influence. - Then "What You'll Bring (Requirements):" bullet list: principal-level depth, hands-on experience applying AI dev tools, ability to understand code bases, credibility with developers, strong communication and change leadership. - Then "You would stand out if you also bring (Preferred Requirements):" bullet list: experience across software and embedded/firmware, IoT solutions, leading DevOps, change management, familiarity with water quality markets, understanding AI governance. - Then later: "This is a rare opportunity..." maybe part of About. - Then compensation: "The compensation range for this role is $180,000-$200,000 CAD per year. This job is also eligible for bonus pay." Also mention benefits: "We offer a comprehensive package of benefits including paid time off, and medical/dental/vision insurance to eligible employees." - Also earlier "We offer:" list includes bonus/incentive pay, flexible remote-friendly work environment, paid holidays, permissive PTO, ongoing investment in career. - Also location: "This position is remote-friendly, with preferred locations in Vancouver, B.C. or Loveland, CO. Travel is expected to collaborate with Water Quality teams across North America, with potential international collaboration as needed." That's Schedule? Actually location and travel. Could be under "Schedule" maybe not. There's no explicit schedule like full-time, part-time. Could omit Schedule section if not specific. The instruction: include a section ONLY when posting has real, specific content for it. So we need to see if there is schedule info: Not explicit about hours, full-time, etc. So we may omit Schedule. - Benefits: we have content: bonus/incentive pay, flexible remote-friendly work environment, paid holidays, permissive PTO, ongoing investment in career via training, on-the-job development, coaching, plus medical/dental/vision insurance. So we can create Benefits section. - Pay: we have compensation range and bonus eligibility. So Pay section. - About the role: we have introductory paragraphs describing mission, impact, etc. - Responsibilities: we have "What You'll Do" list. - Requirements: we have "What You'll Bring (Requirements):" list. - Qualifications: maybe same as Requirements? But we have also "Preferred Requirements". Could treat Requirements as required qualifications, and Qualifications as preferred? But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include. We have content for Requirements (required). We have content for Preferred Requirements (could go under Qualifications or Skills). We also have skills listed: hands-on experience applying AI dev tools, ability to understand code bases, credibility, strong communication, change leadership. Those are skills. Could put under Skills. But we must not create thin sections. Prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But headings are predefined; we can choose to include only those with substantive content. We could include Requirements (required) and Qualifications (preferred) as separate if both have substantive content. They do. Skills: we could extract skill bullets from requirements and preferred. But that may be thin. Might be better to not include Skills if we already have Requirements and Qualifications covering skills. However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; we include only those with real content. Thus we can have:

About the role

with paragraphs describing mission, impact, Veralto, Water Quality segment, etc.

Responsibilities

with

• list of What You'll Do items.

  Requirements

  with
  • list of What You'll Bring (Requirements).

    Qualifications

    with
    • list of You would stand out if you also bring (Preferred Requirements).

      Benefits

      with
      • list of We offer: bonus/incentive pay, flexible remote-friendly work environment, paid holidays, permissive PTO, ongoing investment in career via dedicated training, on-the-job development, coaching, plus medical/dental/vision insurance.

        Pay

        with

        containing compensation range and bonus eligibility. We should not include Schedule as no specific schedule info. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: unsolicited assistance, diversity statement, etc. Also remove legal disclaimer about pay, etc. Also remove "Note: No amount of pay is considered to be wages..." etc. Also remove "This position is for a new role within our team." etc. Also remove "At Veralto, we value diversity..." etc. Also remove "Unsolicited Assistance" paragraph. Also remove "We do not accept unsolicited assistance..." etc. Also remove "With annual sales of $5 billion..." etc. Also remove "Veralto’s Water Quality companies—..." etc. Also remove "Veralto is headquartered in Waltham, MA..." etc. Also remove "The below range reflects..." etc. Actually we need to keep compensation range but we can discard the surrounding legal text about range may be modified etc. Keep the core: "The compensation range for this role is $180,000-$200,000 CAD per year. This job is also eligible for bonus pay." Also we can keep "We offer a comprehensive package of benefits including paid time off, and medical/dental/vision insurance to eligible employees." but we already have benefits list. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep details like "remote-friendly, with preferred locations in Vancouver, B.C. or Loveland, CO. Travel is expected to collaborate with Water Quality teams across North America, with potential international collaboration as needed." That's location/travel info. Where to put? Could be under About the role or maybe under Benefits? Not exactly benefit. Could be under About the role as part of role description. Or we could create a separate section "Location & Travel" but not in allowed headings. So we incorporate into About the role. Also we have "Reporting to the CTO, AI & Software, the AI Software Engineering Lead will be the first hire dedicated to accelerating how Veralto Water Quality software and firmware teams use AI to build better, faster, and smarter." That's about role. Also we have "This is not a narrow coding role or a slide-deck strategy role — it is a hands-on, high-influence opportunity to embed with engineering teams, understand real code bases, coach developers, prove what is possible, and help scale AI-enabled development practices across multiple operating companies." That's responsibilities. We need to ensure we don't lose any substantive bullet points. Let's extract all substantive content: Intro: "What if your next software development leadership role helped shape how AI enables R&D teams to build the future - while supporting a mission that matters. Accelerating responsible AI adoption across software and firmware teams that help safeguard the world’s most vital resourcesMoving beyond AI theory to build practical tools, proofs of concept, and better engineering workflows that developers can use every daySolving varied, high-impact technical challenges with the autonomy of a strategic individual contributor, the grit of a hands on leader, and the influence of a cross-company catalyst" That's a bit run-on but we keep. Then mission paragraph: "At Veralto, our unifying purpose of Safeguarding the World’s Most Vital Resources™ is more than words: it’s a proven path towards positive change, improvement for our planet, and development for yourself. As part of Veralto’s Water Quality segment, the work you’ll do will contribute to a safer world and a more sustainable future. In partnership with our Water Quality companies, you’ll help ensure that 3.4 billion people—over 40% of the world’s population—have safe drinking water every day. And when you join Veralto’s vibrant global network of 13 operating companies and 17,000 associates, you join a unique culture and work environment where purpose meets possibility: where the work you do has an everyday impact on the resources and essentials we all rely on, and where you’ll have boundless opportunities to deepen your skillset, pursue your ambitions, and grow your career." Then "We offer:" list: Bonus/incentive pay, A flexible, remote-friendly work environment, Paid holidays and a permissive paid time off policy emphasizing flexibility and trust, Ongoing investment in your career through dedicated training, on-the-job development, and coaching. Then "Reporting to the CTO, AI & Software, the AI Software Engineering Lead will be the first hire dedicated to accelerating how Veralto Water Quality software and firmware teams use AI to build better, faster, and smarter. This is not a narrow coding role or a slide-deck strategy role — it is a hands-on, high-influence opportunity to embed with engineering teams, understand real code bases, coach developers, prove what is possible, and help scale AI-enabled development practices across multiple operating companies. You will operate like a technical SWAT-team leader: jumping into the highest-value opportunities, learning the development environment quickly, helping teams apply AI-assisted engineering in practical ways, measuring the impact, and then carrying those lessons to the next challenge. Along the way, you will help modernize legacy environments, support AI-focused Kaizens, build tangible proofs of concept, and influence experienced developers through credibility, curiosity, and hands-on technical depth. This position is remote-friendly, with preferred locations in Vancouver, B.C. or Loveland, CO. Travel is expected to collaborate with Water Quality teams across North America, with potential international collaboration as needed." Then "What You'll Do" bullet list: - Embed directly with software and firmware teams to identify practical AI use cases, improve workflows, and accelerate adoption - Coach developers on AI-assisted coding, testing, documentation, refactoring, debugging, and legacy code modernization - Create practical playbooks, prompt libraries, reusable patterns, and engineering standards that make AI adoption easier to scale - Support focused AI and software Kaizens, hackathon-style working sessions, and technical workshops that turn ideas into usable solutions - Evaluate and champion emerging AI development tools, coding agents, RAG approaches, agentic workflows, and other technologies that improve engineering productivity - Build tangible proofs of concept that demonstrate how AI can improve engineering delivery and potentially unlock customer-facing innovation - Measure impact through adoption, productivity, quality, DORA metrics, and other practical indicators of engineering improvement - Lead through influence across multiple Water