Principal, AI Security

We need to output HTML fragment with sections: About the role? The posting includes intro about Itron, then Role Summary, Duties & Responsibilities, Required Skills & Experience, Preferred Skills & Experience, Benefits Info, Travel, Salary, etc. We must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We should not repeat job title as heading. No Job ID. We must include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to output only HTML fragment, no /, no markdown fences. We need to decide sections: - About the role: could contain Role Summary paragraph. - Responsibilities: Duties & Responsibilities list. - Requirements: Required Skills & Experience (maybe also Preferred? but we can combine? The instruction says prefer few substantive sections over many thin ones. Could combine Required and Preferred into Skills? But they have separate headings: Skills, Requirements, Qualifications. We need to decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: Role Summary (About the role). Duties & Responsibilities (Responsibilities). Required Skills & Experience (Requirements? maybe Qualifications?). Preferred Skills & Experience (Skills?). Benefits Info (Benefits). Travel (maybe Schedule? but Travel is less than 25% - could be Schedule? Actually Schedule could be work schedule/hybrid. Travel is separate but not requested. We have Pay: base salary range $96,000-165,000 annually, bonus program. Schedule: hybrid work schedule mentioned. We need to include Pay and Schedule sections only if posting actually states them. Yes, salary range given, hybrid work schedule given. Travel: less than 25% - not requested heading, we could fold into a short p maybe under About? But instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Travel is minor metadata; we could include in a paragraph under About the role or maybe under Benefits? Probably better to include in a short p under About the role or maybe under Benefits? But we have Benefits section already. Travel is not benefits. Could include in a short p under About the role. We must not include boilerplate like EEO, accommodation, etc. Remove those lines. We need to preserve all substantive info: that includes the description of Itron, role summary, duties, required skills, preferred skills, benefits, salary, bonus, hybrid work schedule, travel less than 25%. We must not invent or summarize away detail: we need to keep specifics like "Define and lead Itron's enterprise AI security strategy, architecture, policies, standards, reference architectures, and multi-year roadmap." etc. We need to keep them as list items. We need to use

• for any list of duties/requirements/benefits. Thus:

  About the role

  Itron is innovating new ways for utilities and cities to manage energy and water... (the intro paragraph up to "Join us." maybe also the paragraph about Itron being global leader etc). Actually the intro includes multiple paragraphs: "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us. Itron, Inc. (NASDAQ: ITRI) is a global leader...". We need to preserve all substantive info. So we can combine into a paragraph(s). Use

  for prose. Then after that we have Role Summary paragraph: "The Principal, AI Security Architecture & Engineering serves as Itron's senior technical authority for AI security....". That could be part of About the role or separate? Probably About the role includes role summary. We'll include that as part of About the role. Then Responsibilities: list each duty as

• . Then Requirements: maybe combine Required Skills & Experience as list? But they are not a simple list; they are sentences. Could still be
  • each bullet? The content is paragraph with multiple sentences separated by periods. Could break into bullet points? The instruction: Use
    • for any list of duties/requirements/benefits. The posting has "Required Skills & Experience" with multiple sentences each starting with a number? Actually it's: "7+ years of experience in cybersecurity, security architecture, cloud security, identity and access management, application security, product security, or a related technical discipline. 2+ years of experience working with AI-enabled systems, machine learning environments, automation platforms, advanced analytics solutions, or generative AI technologies. Demonstrated hands-on experience securing or building agentic systems, AI orchestration platforms, non-human identity solutions, model integrations, retrieval pipelines, and automated workflows. Experience implementing security controls for cloud platforms, APIs, identity services, secrets management, data protection, logging, monitoring, and third-party integrations. Proven experience conducting threat modeling, architecture reviews, security assessments, control validations, and cyber risk evaluations. Strong understanding of authentication, authorization, least privilege, secure software design principles, and modern security architectures. Ability to analyze complex AI and cybersecurity risks and communicate practical recommendations to both technical and business leaders. Exceptional written, verbal, facilitation, and stakeholder-management skills. Demonstrated ability to operate effectively across diverse teams while driving accountability, collaboration, and execution in a fast-changing technology environment. Bachelor's degree in Computer Science, Cybersecurity, Information Systems, Engineering, or a related field, or equivalent combination of education and experience." Thus we can treat each line as a
    • . Similarly Preferred Skills & Experience: each line as
    • . Benefits: "This position also includes a competitive benefit package including; financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program, hybrid work schedule, and more!" That's a sentence; we could make a
      • but it's a list within sentence. Could break into items: financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program, hybrid work schedule, and more. We'll make
        • each. Pay: base salary range $96,000-165,000 annually, eligible for annual bonus program. We'll put in

          . Schedule: hybrid work schedule mentioned already in benefits; but we could also have a Schedule section stating hybrid work schedule (flexible remote/office). Since it's already in benefits, maybe we don't need separate Schedule. But we need to include Schedule section only if posting has real specific content for it. The posting mentions hybrid work schedule in benefits; we could still have a Schedule section that says "Hybrid work schedule (flexible remote/office)". However that would duplicate content. The instruction: Prefer a few substantive sections over many thin ones. So maybe we omit Schedule section and keep hybrid work schedule under Benefits. But the instruction says we must use headings for Benefits, Pay, Schedule if posting actually states them. It does state hybrid work schedule, so we could include Schedule. However we already have hybrid work schedule in Benefits; we could still include Schedule with that detail. It's not duplicating if we mention it only there. But we already mentioned hybrid work schedule in Benefits; we could keep it there and not repeat. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we put Schedule heading, we need specific content. We have hybrid work schedule; we could put that as content. But we already used hybrid work schedule in Benefits; we could still mention it again but that would be duplication. The instruction didn't forbid duplication across sections, but we should avoid unnecessary duplication. Better to keep hybrid work schedule under Benefits and not have a separate Schedule section. However the instruction says we must use headings for Benefits, Pay, Schedule if posting actually states them. It does state hybrid work schedule, so we need a Schedule section. But we could put Schedule content as "Hybrid work schedule (flexible remote/office)" and keep Benefits without hybrid work schedule? But Benefits also includes hybrid work schedule as part of list; we could keep it there and also in Schedule? Might be okay but could be seen as duplication. The instruction didn't explicitly forbid duplication, but we should aim for few substantive sections. Having both Benefits and Schedule with overlapping content may be thin. Perhaps we can treat hybrid work schedule as part of Benefits and not create Schedule section, because the instruction says "Prefer a few substantive sections over many thin ones." So we can omit Schedule if we consider it thin. However the instruction also says "include a section ONLY when the posting has real, specific content for it". It does have real content (hybrid work schedule). So we could include Schedule but we need to ensure it's not thin. We could make Schedule section contain more detail: maybe mention hybrid work schedule plus travel less than 25%? Travel is not schedule but could be included. However Travel is not a heading we have. We could incorporate travel into Schedule? Not ideal. Given the instruction to prefer few sections, I'd omit Schedule and keep hybrid work schedule under Benefits. The instruction says we must use headings for Benefits, Pay, Schedule if posting actually states them. It's ambiguous whether we must include all three if they exist. The phrase: "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not a requirement to include all. Then later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we include a section only if there is real specific content. So we can include Benefits and Pay, and optionally Schedule if we think hybrid work schedule is specific content. It is specific. So we should include Schedule. To avoid duplication, we could move hybrid work schedule from Benefits to Schedule, and keep Benefits without that item. But Benefits also includes financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program, and more. We can keep those. Then Schedule section will have hybrid work schedule. That avoids duplication. Thus: Benefits: financial, social, health and wellbeing programs, paid vacation, 401k matching, employee stock purchase program, and more. Schedule: Hybrid work schedule (flexible remote/office). Pay: Base salary range $96,000–$165,000 annually; eligible for annual bonus program. Travel less than 25%: we could fold into a short p under About the role or maybe under Schedule? But we have no Travel heading. We'll add a short p under About the role after the intro: "Travel: Less than 25% on average." Or we could include in a paragraph under About the role. Now we need to strip boilerplate: EEO, accommodation, equal opportunity, etc. Also remove lines like "Itron is committed to building an inclusive and diverse workforce..." and "If you are excited about this role but your past experiences don't perfectly align..." and "Itron is proud to be an Equal Opportunity Employer." and accommodation contact. Also remove "Itron is transforming how the world manages energy, water and city services..." at the end (that's boilerplate). Also remove "Join us as we create a more resourceful world: www.itron.com". Also remove "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us." Actually that is part of the intro; we might keep it as it's substantive about company mission. It's not boilerplate? It's marketing but still part of posting. We'll keep. We