Senior Director, Security Engineering

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to parse the posting. The posting includes: - Intro about Iterable (company description) – maybe "About the role"? Actually "About the role" would be description of role. The text includes "How you’ll make a difference:" and then description of role. That could be "About the role". Also "What You’ll Do" list of responsibilities. - "What We’re Looking For" list of requirements/qualifications/skills. - "Success in the First 12 Months" maybe could be part of responsibilities or qualifications? Not a standard heading; we could treat as part of responsibilities or maybe "Expectations". But we only have allowed headings; we could put that under Responsibilities or maybe under a separate section like "Expectations" but not allowed. So we should incorporate into Responsibilities or maybe Qualifications. - "Iterable Values Model" maybe not needed. - "Perks & Benefits:" list. - "The US base salary range for this position at the start of employment is $220,000 - $300,000." plus explanation. That's Pay. - No explicit Schedule info. So we should not create Schedule section. - Benefits: we have list of perks & benefits. - Skills: maybe we can extract from "What We’re Looking For": technical grounding etc. Could be Skills section. - Qualifications: maybe years of experience etc. We need to avoid boilerplate: remove EEO, recruitment disclaimer, etc. Also remove navigation, cookie, legal, etc. The posting includes a lot of boilerplate at end: Recruitment Disclaimer, EEO statement, etc. Must remove. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can format into HTML. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. The job title is "Senior Director, Security Engineering". Not to be used as heading. We must not put Job ID/requisition numbers as headings – none present. We must only include sections when posting has real specific content. Thus sections likely: About the role (from "How you’ll make a difference:" paragraph), Responsibilities (from "What You’ll Do" bullet list), Requirements (maybe from "What We’re Looking For" list of experience/skills), Qualifications (maybe overlapping), Skills (maybe technical grounding), Benefits (from "Perks & Benefits:" list), Pay (salary range). Possibly also "Success in the First 12 Months" could be part of Responsibilities or maybe a separate section like "Expectations" but not allowed; we could incorporate into Responsibilities as additional prose. We must not create sections with filler like "commensurate with experience". Not present. We need to decide how to split the "What We’re Looking For" list into Requirements, Qualifications, Skills. The list includes: - 12+ years of experience in security engineering or a related technical security discipline. - 7+ years leading security organizations, including managers and senior technical leaders. - Experience setting strategy and delivering outcomes across multiple security functions. - Strong technical grounding in application security, cloud security, detection and response, automation, and vulnerability management. - Experience leading complex incidents, post-incident remediation, and resilience improvements. - Experience managing budgets, vendors, organizational design, and strategic investments. - A track record of developing talent, creating focus, addressing missed delivery, and leading through ambiguity and change. - Exceptional executive communication, judgment, influence, and written communication skills. We could treat first two as Requirements (years of experience). The rest as Qualifications or Skills. But we need to avoid duplication. Perhaps: - Requirements: years of experience (12+ years, 7+ years leading). - Qualifications: experience setting strategy, leading incidents, managing budgets, developing talent, executive communication. - Skills: technical grounding in specific areas. But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to decide what goes where. Let's extract substantive content: About the role: The paragraph starting "How you’ll make a difference:" and maybe the preceding paragraph about Security Engineering protects trust etc. Actually the "How you’ll make a difference:" section includes a description: "Customers trust Iterable with sensitive information. Security Engineering protects that trust by partnering across the company to build secure products, infrastructure, and systems. We embed security architecture into how Engineering develops and launches features, using automation to scale protection, resilience, and assurance. Reporting to the CISO, the Senior Director, Security Engineering owns the strategy, organization, and execution of Iterable’s technical security portfolio, including Product Security, Platform Security, Application Security, Detection and Response, vulnerability management, automation, and incident readiness. This leader will help build an AI-forward Security organization by using AI to improve security technology, team leverage, decision-making, and operational scale. The role requires strong organizational leadership: creating focus, setting clear priorities, establishing accountability, and turning strong talent into predictable delivery." That seems like a good About the role description. Responsibilities: The bullet list under "What You’ll Do". Each line starts with a verb. We'll put each as

  . Requirements: The years of experience items: "12+ years of experience in security engineering or a related technical security discipline." and "7+ years leading security organizations, including managers and senior technical leaders." Qualifications: maybe the rest of the "What We’re Looking For" items that are not pure skills: "Experience setting strategy and delivering outcomes across multiple security functions.", "Experience leading complex incidents, post-incident remediation, and resilience improvements.", "Experience managing budgets, vendors, organizational design, and strategic investments.", "A track record of developing talent, creating focus, addressing missed delivery, and leading through ambiguity and change.", "Exceptional executive communication, judgment, influence, and written communication skills." Skills: "Strong technical grounding in application security, cloud security, detection and response, automation, and vulnerability management." Benefits: The list under "Perks & Benefits:" includes: - Competitive salaries, meaningful equity, & 401(k) plan - Medical, dental, vision, & life insurance - Community Impact Days (additional paid holidays) - Fertility & Adoption Assistance - Paid Sabbatical - Flexible PTO - Monthly Employee Wellness allowance - Monthly Professional Development allowance - Pre-tax commuter benefits - Complete laptop workstation We need to keep each as list items. Pay: The US base salary range paragraph: "The US base salary range for this position at the start of employment is $220,000 - $300,000. Within this range, individual pay is determined by specific US work location, as well as additional factors, including job-related skills, experience, relevant education or training, and internal equity considerations. Please note that the range listed above reflects only base salary. The total compensation package includes variable pay (where applicable), equity, plus a range of benefits, including medical, dental, vision, and financial. In addition, we offer perks such as generous stipends for health & fitness and learning & development, among others." We should keep that as prose under Pay heading. Schedule: No info, so omit. We also need to remove boilerplate: The intro about Iterable (first paragraph) maybe not needed for About the role? Actually the first paragraph is company overview; could be considered "About the company" but not a requested heading. We could either omit it or include it under About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive but not part of role. However we have no heading for company overview. Could we include it as a paragraph before sections? The instruction says output ONLY the HTML fragment, no /. It didn't forbid extra paragraphs not under headings. But they said use

  for section headings,

  • for any list,

    for prose. So we can have prose paragraphs not under a heading? Probably okay but better to fit into sections. The company overview could be placed under About the role as an introductory paragraph? But About the role should be about the role, not company. However we could treat the first paragraph as "About the company" but not a permitted heading. Might be safer to include it as a paragraph before any heading, as it's substantive. The instruction didn't forbid extra prose outside headings. It said use

    for section headings,

    • for any list,

      for prose. So we can have

      anywhere. Thus we can output:

      Iterable is the AI customer engagement platform, built for enterprise scale, loved by teams, and trusted by global brands like Redfin, SeatGeek, Priceline, Calm, and Box. Our platform empowers organizations to activate customer data from any source, design seamless cross-channel experiences, and optimize engagement with Nova Intelligence, the AI layer of our platform, all with enterprise-grade security and compliance. Today, nearly 1,200 brands across 50+ countries rely on Iterable to drive growth, deepen customer relationships, and deliver joyful customer experiences. Our success is powered by extraordinary people who bring our core values to life every day: Be an Owner, Growth Mindset, Run as One, and Transparency. And the market has noticed: G2 recognizes Iterable as a Leader globally, spanning the Americas, EMEA, APAC, ANZ, and Latin America, with category leadership in Personalization, Marketing Automation, Push Notifications, and Mobile Marketing, and a 4.5/5-star rating from hundreds of users. Gartner named Iterable a Challenger in the Gartner Magic Quadrant for Multichannel Marketing in both 2024 and 2025. We’ve also earned TrustRadius Top Rated honors in 2024 and 2025, were named a TrustRadius Buyer’s Choice for 2026, and were featured in Snowflake’s Modern Marketing Data Stack 2026. With a global presence that includes offices in San Francisco, Denver, London, Sydney, and Lisbon, plus remote employees worldwide, we are committed to building a diverse and inclusive workplace. We welcome candidates from all backgrounds and encourage you to apply. Learn more about our story and mission on our Culture and About Us pages. Let’s shape the future of customer engagement together!

      Then

      About the role

      with the paragraph from "How you’ll make a difference:" (maybe we keep that as prose). Then

      Responsibilities

      with
      of the What You’ll Do bullets. Then

      Requirements

      with
      of the two experience items. Then

      Qualifications

      with
      of the remaining items (strategy, incidents, budgets, talent development, executive communication). Then

      Skills

      with
      of the technical grounding item (maybe just one item). Could be a
      • Strong technical grounding in application security, cloud security, detection and response, automation, and vulnerability management.
      Then

      Benefits

      with
      of the perks list. Then

      Pay

      with

      of the salary range paragraph. We must ensure we don't include any boilerplate like EEO, recruitment disclaimer, etc. Also remove the "Iterable Values Model" section (maybe not needed). Also remove the "Success in the First 12 Months" section? That is substantive; we could incorporate into Responsibilities or maybe as a separate section like "Expectations" but not allowed. Could add as