Endpoint Security Product Lead

We need to output HTML fragment with sections: About the role? Actually we have sections: "Who We Are Looking For", "Why this role is important to us", "What you will be responsible for", "What we value", "Education & Preferred Qualifications", "Additional Requirements", "Work Requirement", "Salary Range", "Benefits", "About State Street". Also maybe "About the role" not present. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not put Job ID as heading. We must include a section only when posting has real, specific content for it. So we need to map content to appropriate headings. We have content: - "Who We Are Looking For": description of role, reporting line, leading team, define strategy, etc. Could be "About the role" or maybe "Responsibilities"? Actually "Who We Are Looking For" is more about the role description. Could map to "About the role". Use

About the role

then

with that content. - "Why this role is important to us": could be "About the team" or maybe not a standard heading. Could be omitted? But we need to include only when real content. Could map to "About the team"? Not in list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should try to fit into those. "Why this role is important to us" could be part of About the role. Could combine. - "What you will be responsible for": that's Responsibilities. Use

Responsibilities

then

• each bullet. - "What we value": that's Skills? Actually "What we value These skills will help you succeed in this role" list of skills. Could map to

  Skills

  then
  . - "Education & Preferred Qualifications": that's Qualifications. Use

  Qualifications

  then maybe
  for bullet points? It includes Bachelor's degree, 8+ years, etc. Could be
  . - "Additional Requirements": could be Requirements? Actually we have Requirements heading. Could map Additional Requirements to Requirements. Use

  Requirements

  then
  . - "Work Requirement": that's Schedule? Actually Work Requirement includes hybrid work model, ability to collaborate global teams, standard business hours with flexibility. That's about schedule/work arrangement. Could map to

  Schedule

  then

  or

  . We'll use

  . - "Salary Range": that's Pay. Use

  Pay

  then

  with salary range and note. - Benefits: we have benefits paragraph after salary range. Use

  Benefits

  then
  maybe list each benefit. - "About State Street": could be About the company? Not in list. Could be omitted or maybe we could put under About the role? But it's separate. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The list of headings is just examples; we can use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we could also use other headings if needed? Probably better to stick to those. "About State Street" could be considered "About the role"? Not exactly. Could be omitted? But it's substantive info about company. Might be okay to include as a section with heading "About the company"? Not in list. Might be considered boilerplate? It's about the company, not boilerplate. Could include as

  About State Street

  but that's not in the list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed. We'll include About State Street. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO statement, Job Application Disclosure, Job ID, etc. Also remove "About State Street" maybe not boilerplate. Keep it. We need to preserve all substantive information. Let's extract content. **Who We Are Looking For**: "We are looking for a VP, Endpoint Product Security Lead reporting into the Defensive Engineering leadership team within Global Cyber Security (GCS). This role will lead the Endpoint Product Security team and define the strategy, roadmap, and maturity of enterprise endpoint security capabilities. The role will build a shared and embedded product model with GTS Endpoint Platform leaders, aligning Cyber Security requirements with GTS platform priorities to deliver shared security outcomes across the enterprise." **Why this role is important to us**: "The team you will be joining is part of Defensive Engineering within Global Cyber Security, a function that is critical to the company’s cybersecurity strategy. Endpoints remain a significant attack surface for unauthorized software, malicious content, credential theft, and other cyber threats. This role will lead the team responsible for advancing endpoint security maturity through proactive controls, strong product management, measurable outcomes, and close partnership with GTS." We could combine with Who We Are Looking For under About the role. **What you will be responsible for**: List of responsibilities (bulleted). Let's extract each bullet: - Lead, develop, and manage a team of endpoint product security professionals, setting clear priorities, expectations, and accountability. - Define and drive the enterprise endpoint security strategy, product roadmap, and maturity plan. - Build a shared product operating model with GTS Endpoint Platform leaders that aligns priorities, roadmaps, ownership, and success measures. - Treat the GTS Endpoint Platform organization as a key customer and partner, ensuring security capabilities are practical, scalable, and embedded within endpoint platform services. - Establish shared outcomes and metrics across GCS and GTS for endpoint security coverage, policy enforcement, control effectiveness, exceptions, and risk reduction. - Drive the adoption and maturity of capabilities such as application control, browser security, endpoint hardening, attack surface reduction, and endpoint resilience. - Establish endpoint security requirements, configuration standards, policy baselines, and secure-by-design practices. - Assess control coverage and effectiveness, identify security gaps, and prioritize improvements based on threat, risk, and business impact. - Lead security product evaluations, proof-of-concepts, vendor assessments, and platform lifecycle planning. - Collaborate with the Cyber Defense Center to improve endpoint telemetry, visibility, investigation, and incident response capabilities. - Partner with Infrastructure, Desktop Engineering, Server, Cloud, and other technology teams to embed security throughout the endpoint lifecycle. - Maintain product documentation, control evidence, and supporting materials for risk, audit, and regulatory requirements. - Serve as the product owner and senior subject matter expert for enterprise endpoint security capabilities. **What we value** (skills): List: - Proven experience leading and developing technical or cybersecurity teams. - Strong experience with enterprise endpoint security technologies, controls, and architectures. - Experience building effective partnerships and shared product models across Cyber Security and Technology organizations. - Ability to align security requirements with platform engineering priorities and operational needs. - Experience developing security product strategies, roadmaps, technical standards, and maturity plans. - Strong understanding of endpoint threats and preventative controls across workstations, servers, browsers, and virtual environments. - Experience with application control, browser security, endpoint hardening, attack surface reduction, and endpoint resilience. - Knowledge of frameworks and practices such as NIST CSF, CIS Controls, CIS Benchmarks, MITRE ATT&CK, and Zero Trust. - Experience defining meaningful metrics, measuring control effectiveness, and driving remediation of security gaps. - Strong leadership, product management, communication, and stakeholder-management skills. **Education & Preferred Qualifications**: - Bachelor’s degree in Computer Science, Information Security, Engineering, or a related field, or equivalent practical experience. - 8+ years of experience in cybersecurity, endpoint security, security engineering, security architecture, or security product management. - 3+ years of experience leading technical or cybersecurity teams. - Experience implementing or maturing enterprise security platforms and controls at scale. - Experience working in financial services or another highly regulated industry preferred. - Relevant certifications such as CISSP, CCSP, GIAC, or equivalent preferred. **Additional Requirements**: - Experience driving security control adoption across large and complex endpoint environments. - Experience managing product roadmaps, vendor relationships, and security platform lifecycles. - Ability to translate threats, control gaps, and regulatory requirements into actionable product priorities. - Ability to influence and drive shared outcomes across GCS, GTS, Infrastructure, Cloud, Risk, and Engineering organizations. - Strong focus on team development, collaboration, accountability, and continuous improvement. **Work Requirement**: - Hybrid work model in accordance with company policy. - Ability to collaborate effectively with global teams across multiple time zones. - Standard business hours with flexibility to support critical security incidents, deployments, and initiatives when required. **Salary Range**: - $120,000 - $202,500 Annual - The range quoted above applies to the role in the primary location specified. If the candidate would ultimately work outside of the primary location above, the applicable range could differ. **Benefits**: - Employees are eligible to participate in State Street’s comprehensive benefits program, which includes: our retirement savings plan (401K) with company match; insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages; paid-time off including vacation, sick leave, short term disability, and family care responsibilities; access to our Employee Assistance Program; incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans); and, eligibility for certain tax advantaged savings plans. - For a full overview, visit https://hrportal.ehr.com/statestreet/Home. **About State Street**: - Across the globe, institutional investors rely on us to help them manage risk, respond to challenges, and drive performance and profitability. We keep our clients at the heart of everything we do, and smart, engaged employees are essential to our continued success. We are committed to fostering an environment where every employee feels valued and empowered to reach their full potential. As an essential partner in our shared success, you’ll benefit from inclusive development opportunities, flexible work-life support, paid volunteer days, and vibrant employee networks that keep you connected to what matters most. Join us in shaping the future. We need to output HTML fragment only, no markdown fences. We'll structure:

  About the role

  ... combined Who We Are Looking For and Why this role is important to us ...

  Responsibilities

  • ... each bullet ...

  Skills

  • ... each skill ...

  Qualifications

  • ... each edu/pref qual ...

  Requirements

  • ... each additional requirement ...

  Schedule

  ... work requirement bullets maybe as

  but we can keep

  with sentences.

  Pay

  ... salary range text ...

  Benefits

  • ... each benefit item? Could be a single paragraph but we can split into list items for clarity.

  About State Street

  ... about state street paragraph ...

  We must not include boilerplate like EEO, Job ID, etc. Check for duplicated lines: none. Now craft HTML. Be careful to escape any HTML special