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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove equal opportunity etc. Also remove recruitment disclaimer? That's likely boilerplate/legal; we should remove. Also remove equal opportunity statement. Also remove "Learn more about our story..." etc. Also remove "Iterable Values Model" maybe part of values but could be considered part of About the role? Might be considered part of company description; we can include under About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: The description of role: "How you’ll make a difference: Customers trust Iterable with sensitive information. Security Engineering protects that trust..." plus "Reporting to the CISO, the Senior Director, Security Engineering owns the strategy..." etc. Also "What You’ll Do" list. Thus we can put About the role containing the narrative description (maybe combine the "How you’ll make a difference" and "What You’ll Do"). - Responsibilities: Could be the bullet list under "What You’ll Do". That's responsibilities. - Requirements: The list under "What We’re Looking For". That's requirements. - Qualifications: Might be overlapping with requirements; but we could treat "What We’re Looking For" as Requirements, and maybe Qualifications could be something else like "Success in the First 12 Months"? That could be Qualifications? Or maybe we treat "Success in the First 12 Months" as Qualifications or Expectations. The instruction says include a section only when posting has real specific content for it. We have content for Success in the First 12 Months (list). Could be considered "Qualifications" or maybe "Expectations". But we have predefined headings list; we can use Qualifications for that. - Skills: Could be extracted from requirements list (technical grounding etc). But we might not need separate Skills if we already have Requirements. However we could still include Skills if there is explicit skill list. The posting mentions "Strong technical grounding in application security, cloud security, detection and response, automation, and vulnerability management." That's skill. Also "Experience leading complex incidents..." etc. Might be covered under Requirements. To avoid duplication, we could put Skills as a separate section listing those specific skills. But we must not invent or summarize away detail; we can extract. - Benefits: The posting includes "Perks & Benefits:" list with many items. Also mentions "Competitive salaries, meaningful equity, & 401(k) plan" etc. So we have Benefits section. - Pay: The posting includes "The US base salary range for this position at the start of employment is $220,000 - $300,000." plus note about total compensation. So we have Pay. - Schedule: Not mentioned. No info about schedule (remote, hybrid, etc). There's mention of global presence, remote employees worldwide, but not explicit schedule. Should we include Schedule? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule not stated, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't repeat content unnecessarily. We'll extract substantive info. Let's parse the posting: Company description at start: "Iterable is the AI customer engagement platform..." etc. That's generic company overview; could be part of About the role? Usually About the role includes role description, not company overview. But we could include a brief company overview under About the role? The instruction: do not repeat job title as heading; we can include company overview as part of About the role? Might be okay. However we should preserve all substantive information; we can include that as a paragraph under About the role before responsibilities. But we also have "How you’ll make a difference:" paragraph. That's role impact. We also have "What You’ll Do:" list. Thus About the role could contain company overview + How you’ll make a difference paragraph. Responsibilities: the bullet list under What You’ll Do. Requirements: the list under What We’re Looking For (the 12+ years etc). That's requirements. Qualifications: maybe "Success in the First 12 Months" list. Skills: maybe extract specific skill items: "Strong technical grounding in application security, cloud security, detection and response, automation, and vulnerability management." Also "Experience leading complex incidents, post-incident remediation, and resilience improvements." Also "Experience managing budgets, vendors, organizational design, and strategic investments." Also "A track record of developing talent, creating focus, addressing missed delivery, and leading through ambiguity and change." Also "Exceptional executive communication, judgment, influence, and written communication skills." Those could be skills. But we already have many of those in Requirements list. To avoid duplication, we could treat Requirements as the bullet list of experience/years etc, and Skills as the specific technical and soft skills. However the bullet list under What We’re Looking For includes both experience and skills. Might be better to split: Requirements = the experience/years bullets (12+ years, 7+ years leading, Experience setting strategy, etc). Skills = technical grounding etc. But the bullet list includes all. Let's examine: "What We’re Looking For 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 the first three as Requirements (experience, leadership, strategy). The rest as Skills. But the instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Skills into one section called Requirements (or Qualifications). But we have separate headings allowed; we need to decide. We have also Qualifications (Success in first 12 months). That's distinct. Thus we could have: - About the role (company overview + impact) - Responsibilities (What You’ll Do) - Requirements (the experience/leadership/strategy bullets) - Skills (technical grounding, incident experience, budget/vendor, talent development, communication) - Qualifications (Success in first 12 months) - Benefits (Perks & Benefits list) - Pay (salary range) We must not include Schedule. Now we need to format using

for each section heading, then content:

for prose,

• for lists. We must not include any markdown code fences. Just raw HTML. We must remove boilerplate: navigation, legal, EEO, scam warning, recruitment disclaimer, equal opportunity, etc. Also remove "Learn more about our story..." etc. Also remove "Iterable Values Model" maybe part of values but could be considered part of About the role? It's a list of values with explanations. Could be considered part of company culture; but we might keep it under About the role as it's substantive? However it's not directly about the role; it's company values. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep the values if they are substantive. But they are under "Iterable Values Model". That's a section describing values. Could be considered part of About the role or maybe a separate section? But we only have predefined headings; we could include it under About the role as a paragraph. However the values list is not directly about the role but it's still substantive info about the company. We'll include it as a paragraph under About the role after the impact paragraph. We must also remove "Perks & Benefits:" heading but we will create our own Benefits section with

  Benefits

  and list. We must also remove "The US base salary range..." but we will create Pay section. Now let's craft content. About the role: Paragraph 1: Company overview: "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." Paragraph 2: Impact: "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." Paragraph 3: Values (maybe): "Iterable’s current values while building a high-performing organization that delivers meaningful security outcomes: Run As One: Anchor work in shared company outcomes, clarify the end state, and commit to decisions. Be An Owner: Own outcomes, address problems directly, and use company resources wisely. Transparency: Share early, communicate clearly, own mistakes, and challenge directly with empathy. Growth Mindset: Challenge the status quo, learn quickly, and continuously raise the bar." We could combine values into a
  list? But they are sentences with colons. Could keep as

  with line breaks? Better to use

  • for each value. However the instruction: Use
    • for any list of duties/requirements/benefits. Values could be considered a list; we can use
      . That's fine. Now Responsibilities: The bullet list under "What You’ll Do". Let's extract each line: - 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