Senior Director, Security Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First part: company description (Iterable is AI customer engagement platform...). That's about the company, maybe "About the role"? Actually "How you’ll make a difference" is description of role. Could treat as "About the role". We'll include that as prose. Then "What You’ll Do" list of responsibilities. That's responsibilities. Then "What We’re Looking For" list of requirements/qualifications. Then "Success in the First 12 Months" maybe could be considered as expectations, but not a standard heading; we could incorporate into Responsibilities or maybe a separate section like "Objectives". But only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "What We’re Looking For" to Requirements (or Qualifications). Could split into Requirements and Qualifications but we need to avoid thin sections. Probably combine into Requirements. "Success in the First 12 Months" could be part of Responsibilities or maybe a separate "Objectives" but not allowed; we could incorporate into Responsibilities as additional bullet points. "Perks & Benefits:" list of benefits. That's Benefits section. "US base salary range..." that's Pay. Schedule not mentioned; we should not include Schedule. Also need to include maybe "About the role" includes company overview and role impact. We must not repeat job title as heading. No Job ID. We must remove boilerplate: recruitment disclaimer, EEO, etc. Also remove "Learn more about our story..." etc? That's company description; we can keep as part of About the role. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as given? We can keep them as list items. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's craft:

About the role

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! How you’ll make a difference: 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.

Then responsibilities:

Responsibilities

• Define and execute a multi-year Security Engineering strategy aligned to business priorities, customer trust, and risk appetite.
• Set a focused portfolio of priorities with clear owners, sequencing, milestones, and measurable outcomes.
• Lead and develop managers and senior technical leaders across multiple security functions.
• Establish operating mechanisms that improve accountability, execution visibility, and delivery predictability.
• Address missed commitments, unresolved blockers, and priority conflicts directly.
• Build an AI-forward roadmap for security engineering, automation, operations, and decision support.
• Mature application security, cloud and platform security, detection and response, vulnerability management, and incident readiness.
• Lead post-incident improvement and resilience programs that address systemic risk.
• Partner with Engineering, Product, IT, GRC, Legal, Finance, and Customer-facing teams to enable secure business outcomes.
• Own organizational planning, budget, vendor strategy, headcount planning, and investment tradeoffs.
• Advise executives and Board partners on security posture, material risks, priorities, and investments.

Then Requirements/Qualifications: combine. We have "What We’re Looking For" list: - 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. Also "Success in the First 12 Months" list: - Establish a clear strategy, operating model, roadmap, and measurement framework. - Align security functions around a focused set of business and risk priorities. - Launch an AI-forward security roadmap that improves leverage and automation. - Improve accountability, delivery predictability, and visibility into portfolio execution. - Strengthen leadership capacity through manager development and succession planning. These could be considered as expectations but we could incorporate into Responsibilities or maybe a separate section like "Objectives". Since not allowed, we could add them to Responsibilities as additional bullets (makes sense). But we already have responsibilities list; we could add these as part of responsibilities (makes sense). However we must not duplicate content; we can add them as additional bullets under Responsibilities. Alternatively we could create a separate section "Expectations" but not allowed. So we add to Responsibilities. Thus responsibilities list will be longer. Now Benefits: list from "Perks & Benefits:": - 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 as list items. Pay: US base salary range $220,000 - $300,000. Also note that individual pay determined by location etc. We'll include that as prose. Schedule: not present, omit. Now ensure we removed boilerplate: recruitment disclaimer, EEO, etc. Also removed "Iterable Values Model" maybe we could incorporate values into About the role? It's a list of values; could be included as prose. But we might keep it as part of About the role? The values are listed after "Iterable Values Model". Could be considered part of company culture; we could keep as prose. However it's a list; we could incorporate as a paragraph. But we must not invent or summarize away detail; we need to preserve all substantive information. The values list: Run As One, Be An Owner, Transparency, Growth Mindset with descriptions. We should keep that. Thus About the role paragraph may become long; we can include values as a separate paragraph after company description. We'll keep About the role as multiple paragraphs? The instruction: use

for prose. Could have multiple

elements. We'll structure:

About the role

Iterable is the AI customer engagement platform ...

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 ...

How you’ll make a difference: Customers trust Iterable with sensitive information. Security Engineering protects that trust ...

But we need to preserve all details; we can split into multiple paragraphs. Now Responsibilities will include the earlier list plus the success in first 12 months items. Let's list all responsibilities bullets: From "What You’ll Do": - Define and execute a multi-year Security Engineering strategy aligned to business priorities, customer trust, and risk appetite. - Set a focused portfolio of priorities with clear owners, sequencing, milestones, and measurable outcomes. - Lead and develop managers and senior technical leaders across multiple security functions. - Establish operating mechanisms that improve accountability, execution visibility, and delivery predictability. - Address missed commitments, unresolved blockers, and priority conflicts directly. - Build an AI-forward roadmap for security engineering, automation, operations, and decision support. - Mature application security, cloud and platform security, detection and response, vulnerability management, and incident readiness. - Lead post-incident improvement and resilience programs that address systemic risk. - Partner with Engineering, Product, IT, GRC, Legal, Finance, and Customer-facing teams to enable secure business outcomes. - Own organizational planning, budget, vendor strategy, headcount planning, and investment tradeoffs. - Advise executives and Board partners on security posture, material risks, priorities, and investments. From "Success in the First 12 Months": - Establish a clear strategy, operating model, roadmap, and measurement framework. - Align security functions around a focused set of business and risk priorities. - Launch an AI-forward security roadmap that improves leverage and automation. - Improve accountability, delivery predictability, and visibility into portfolio execution. - Strengthen leadership capacity through manager development and succession planning. We could combine similar items but we must preserve all detail; we can keep duplicates if they appear similar but not identical. However "Define and execute a multi-year Security Engineering strategy..." vs "Establish a clear strategy, operating model, roadmap, and measurement framework." They are similar but not identical; we keep both. Now Requirements/Qualifications: list from "What We’re Looking For". Also maybe include "Iterable Values Model"? Not needed. We'll create a section

Requirements

with ul list. Now Benefits:

Benefits

with ul list. Pay:

Pay

with p containing salary range and note. Now ensure we didn't include any boilerplate like "Recruitment Disclaimer", "Equal Employment Opportunity", etc. Let's craft final HTML. Check for any stray text: we must not include markdown code fences. Now produce