Associate Director, Application Security
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- "About The Role Grade Level (for internal use): 12" - This is minor metadata, could be folded into a short
or dropped
- "The Team" - This is descriptive prose about the team
- "Responsibilities And Impact" - This is a list of responsibilities
- "What We're Looking For" - This has "Basic Required Qualifications" (list) and "Additional Preferred Qualifications" (list)
- "Compensation/Benefits Information (This section is only applicable to US candidates)" - This has salary range info
- "What's In It For You?" - This has mission, values, benefits description
- "Global Hiring And Opportunity At S&P Global" - This is boilerplate EEO/equal opportunity stuff
- "Recruitment Fraud Alert" - Boilerplate
- "Equal Opportunity Employer" - Boilerplate
- "US Candidates Only: Know Your Rights..." - Boilerplate
- "Job ID: 332051 Posted On: 2026-10-20 Location: Dallas, Texas, United States" - Minor metadata
I need to structure this into sections with real content:
1. About the role (could include team description and grade level)
2. Responsibilities (the list under "Responsibilities And Impact")
3. Requirements/Qualifications (both basic required and preferred)
4. Pay (the compensation info)
5. Benefits (the benefits description)
I should not include the EEO, fraud alert, job ID, posted date, location as separate sections - those are boilerplate/metadata.
Let me create the HTML:
- Start with a
for the grade level and team description maybe
- Then
About the role
with team description
- Responsibilities
with - for each bullet
-
Requirements
with subsections for required and preferred? Or just one list? The rules say use for section headings like Requirements, Qualifications. I could do Requirements
then maybe for required vs preferred? But the rule says use for section headings. I'll keep it simple: Requirements
with two lists: required and preferred, maybe with
labels.
-
Pay
with the salary range
- Benefits
with the benefits description
I need to preserve all substantive information. The benefits section has a list of benefit categories. I'll use - for those.
The "What's In It For You?" includes mission, values, benefits. I'll include mission and values as prose, benefits as list.
The "Global Hiring And Opportunity" is boilerplate EEO, so remove.
The "Recruitment Fraud Alert" and "Equal Opportunity Employer" are boilerplate, remove.
The "US Candidates Only: Know Your Rights" is boilerplate, remove.
Job ID, posted date, location: minor metadata, fold into a short
at the end or drop. I'll drop them as they are not substantive.
Now, let's write the HTML.
I'll structure:
Grade Level: 12 (internal use)
About the role
The SGA Application Security team operates as a strategic security partner, combining Application Security, DevSecOps, Exposure Management, and AI Security capabilities to proactively reduce risk while enabling enterprise innovation. Our collaborative, fast-paced culture emphasizes automation-first approaches, developer partnership, and continuous learning in emerging technologies. As a senior leader, you'll drive enterprise-wide security transformation initiatives, guide AI-powered security innovations, and lead a global team focused on solving complex challenges that impact business growth and cyber resilience.
Responsibilities
- Lead execution of the enterprise Application Security strategy and roadmap, driving secure SDLC transformation, platform maturity, and measurable risk reduction across global engineering teams
- Own and oversee comprehensive application security testing capabilities including SAST, SCA, DAST, API security, threat modeling, and penetration testing while establishing enterprise standards and governance frameworks
- Drive strategic adoption and operational effectiveness of enterprise AppSec and ASPM platforms, providing executive-ready reporting on coverage, vulnerability trends, and remediation performance
- Lead software supply chain security initiatives covering dependency governance, artifact curation, provenance validation, and trusted build practices while managing incident response for zero-day exposures
- Build, mentor, and develop a high-performing global team while managing strategic vendor relationships and driving cross-functional transformation with technology, product, and business leaders
- Provide leadership in adopting generative AI and agentic technologies within Application Security, establishing governance for custom AI-enabled tools, agents, and automations while ensuring appropriate security and oversight
Requirements
Basic Required Qualifications
- Demonstrated leadership of enterprise Application Security, DevSecOps, or Product Security programs in complex environments with proven track record of driving transformation
- Deep knowledge of application testing methodologies, threat modeling, secure architecture, CI/CD security, cloud-native security, and software supply chain risk management
- Experience defining enterprise standards, operating models, remediation governance, exception processes, and establishing measurable KPIs and KRIs
- Strong stakeholder management and executive communication skills with ability to translate technical risk into business impact and strategic decisions
- Experience leading teams, mentoring technical professionals, managing vendor relationships, and driving cross-functional initiatives across global organizations
- Executive-level communication and presentation capabilities
- Strategic thinking with ability to balance technical depth and business priorities
- Strong leadership and team development skills with global mindset
- Proven ability to influence and drive change across complex organizational structures
Additional Preferred Qualifications
- Demonstrated knowledge of generative AI, large language models, AI-assisted software development, and practical application of AI technologies to cybersecurity and DevSecOps use cases
- Strong understanding of Model Context Protocol (MCP), AI agents, agentic architectures, tool calling, retrieval-augmented generation, AI security risks, and governance frameworks for AI integration
- Experience with multi-cloud security architectures and controls across platforms such as AWS, Azure, and GCP with understanding of cloud-native delivery environments
- Proven track record in vendor management, contract negotiation, platform roadmap development, and strategic technology partnerships in enterprise security environments
Pay
Anticipated base salary range: $130,000 to $160,000 (US candidates). Final base salary based on geographic location, experience level, skill set, training, licenses, and certifications.
Benefits
Our Mission: Advancing Essential Intelligence. Our People: We're more than 35,000 strong worldwide—so we're able to understand nuances while having a broad perspective. Our team is driven by curiosity and a shared belief that Essential Intelligence can help build a more prosperous future for us all. From finding new ways to measure sustainability to analyzing energy transition across the supply chain to building workflow solutions that make it easy to tap into insight and apply it. We are changing the way people see things and empowering them to make an impact on the world we live in. We're committed to a more equitable future and to helping our customers find new, sustainable ways of doing business. Join us and help create the critical insights that truly make a difference.
Our Values: Integrity, Discovery, Partnership. Throughout our history, the world's leading organizations have relied on us for the Essential Intelligence they need to make confident decisions about the road ahead. We start with a foundation of integrity in all we do, bring a spirit of discovery to our work, and collaborate in close partnership with each other and our customers to achieve shared goals.
We take care of you, so you can take care of business. We care about our people. That's why we provide everything you—and your career—need to thrive at S&P Global.
- Health & Wellness: Health care coverage designed for the mind and body.
- Flexible Downtime: Generous time off helps keep you energized for your time on.
- Continuous Learning: Access a wealth of resources to grow your career and learn valuable new skills.
- Invest in Your Future: Secure your financial future through competitive pay, retirement planning, a continuing education program with a company-matched student loan contribution, and financial wellness programs.
- Family Friendly Perks: It's not just about you. S&P Global has perks for your partners and little ones, too, with some best-in class benefits for families.
- Beyond the Basics: From retail discounts to referral incentive awards—small perks can make a big difference.
For more information on benefits by country visit: https://spgbenefits.com/benefit-summaries
That seems comprehensive. I used for subsections under Requirements. The rules say use for section headings, but didn't forbid for subsections. However, to be safe, maybe I should keep only and use
for labels. But the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other heading levels. But to be safe, I'll use for main sections and maybe
for subsections. However, the example includes "Qualifications" as a section heading. I have "Requirements" as a section heading, and within it "Basic Required Qualifications" and "Additional Preferred Qualifications". I could make them separate sections: "Required Qualifications" and "Preferred Qualifications". That might be better.
Let me restructure:
Required Qualifications
...
Preferred Qualifications
...
But the original has "What We're Looking For" with two subsections. I'll follow the content.
Also, the "About the role" section includes the team description. The grade level is minor metadata; I'll include it in a
before the sections or within About the role.
I'll output the HTML fragment without any wrapping tags.
Now, ensure no markdown code fences. Just plain HTML.
Let
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - "About The Role Grade Level (for internal use): 12" - This is minor metadata, could be folded into a short
or dropped - "The Team" - This is descriptive prose about the team - "Responsibilities And Impact" - This is a list of responsibilities - "What We're Looking For" - This has "Basic Required Qualifications" (list) and "Additional Preferred Qualifications" (list) - "Compensation/Benefits Information (This section is only applicable to US candidates)" - This has salary range info - "What's In It For You?" - This has mission, values, benefits description - "Global Hiring And Opportunity At S&P Global" - This is boilerplate EEO/equal opportunity stuff - "Recruitment Fraud Alert" - Boilerplate - "Equal Opportunity Employer" - Boilerplate - "US Candidates Only: Know Your Rights..." - Boilerplate - "Job ID: 332051 Posted On: 2026-10-20 Location: Dallas, Texas, United States" - Minor metadata I need to structure this into sections with real content: 1. About the role (could include team description and grade level) 2. Responsibilities (the list under "Responsibilities And Impact") 3. Requirements/Qualifications (both basic required and preferred) 4. Pay (the compensation info) 5. Benefits (the benefits description) I should not include the EEO, fraud alert, job ID, posted date, location as separate sections - those are boilerplate/metadata. Let me create the HTML: - Start with a
for the grade level and team description maybe - Then
About the role
with team description -Responsibilities
with- for each bullet
-
Requirements
with subsections for required and preferred? Or just one list? The rules say usefor section headings like Requirements, Qualifications. I could do
Requirements
then maybefor required vs preferred? But the rule says use
for section headings. I'll keep it simple:
Requirements
with two lists: required and preferred, maybe withlabels. -
Pay
with the salary range -Benefits
with the benefits description I need to preserve all substantive information. The benefits section has a list of benefit categories. I'll use- for those.
The "What's In It For You?" includes mission, values, benefits. I'll include mission and values as prose, benefits as list.
The "Global Hiring And Opportunity" is boilerplate EEO, so remove.
The "Recruitment Fraud Alert" and "Equal Opportunity Employer" are boilerplate, remove.
The "US Candidates Only: Know Your Rights" is boilerplate, remove.
Job ID, posted date, location: minor metadata, fold into a short
at the end or drop. I'll drop them as they are not substantive. Now, let's write the HTML. I'll structure:
Grade Level: 12 (internal use)
About the role
The SGA Application Security team operates as a strategic security partner, combining Application Security, DevSecOps, Exposure Management, and AI Security capabilities to proactively reduce risk while enabling enterprise innovation. Our collaborative, fast-paced culture emphasizes automation-first approaches, developer partnership, and continuous learning in emerging technologies. As a senior leader, you'll drive enterprise-wide security transformation initiatives, guide AI-powered security innovations, and lead a global team focused on solving complex challenges that impact business growth and cyber resilience.
Responsibilities
- Lead execution of the enterprise Application Security strategy and roadmap, driving secure SDLC transformation, platform maturity, and measurable risk reduction across global engineering teams
- Own and oversee comprehensive application security testing capabilities including SAST, SCA, DAST, API security, threat modeling, and penetration testing while establishing enterprise standards and governance frameworks
- Drive strategic adoption and operational effectiveness of enterprise AppSec and ASPM platforms, providing executive-ready reporting on coverage, vulnerability trends, and remediation performance
- Lead software supply chain security initiatives covering dependency governance, artifact curation, provenance validation, and trusted build practices while managing incident response for zero-day exposures
- Build, mentor, and develop a high-performing global team while managing strategic vendor relationships and driving cross-functional transformation with technology, product, and business leaders
- Provide leadership in adopting generative AI and agentic technologies within Application Security, establishing governance for custom AI-enabled tools, agents, and automations while ensuring appropriate security and oversight
Requirements
Basic Required Qualifications
- Demonstrated leadership of enterprise Application Security, DevSecOps, or Product Security programs in complex environments with proven track record of driving transformation
- Deep knowledge of application testing methodologies, threat modeling, secure architecture, CI/CD security, cloud-native security, and software supply chain risk management
- Experience defining enterprise standards, operating models, remediation governance, exception processes, and establishing measurable KPIs and KRIs
- Strong stakeholder management and executive communication skills with ability to translate technical risk into business impact and strategic decisions
- Experience leading teams, mentoring technical professionals, managing vendor relationships, and driving cross-functional initiatives across global organizations
- Executive-level communication and presentation capabilities
- Strategic thinking with ability to balance technical depth and business priorities
- Strong leadership and team development skills with global mindset
- Proven ability to influence and drive change across complex organizational structures
Additional Preferred Qualifications
- Demonstrated knowledge of generative AI, large language models, AI-assisted software development, and practical application of AI technologies to cybersecurity and DevSecOps use cases
- Strong understanding of Model Context Protocol (MCP), AI agents, agentic architectures, tool calling, retrieval-augmented generation, AI security risks, and governance frameworks for AI integration
- Experience with multi-cloud security architectures and controls across platforms such as AWS, Azure, and GCP with understanding of cloud-native delivery environments
- Proven track record in vendor management, contract negotiation, platform roadmap development, and strategic technology partnerships in enterprise security environments
Pay
Anticipated base salary range: $130,000 to $160,000 (US candidates). Final base salary based on geographic location, experience level, skill set, training, licenses, and certifications.
Benefits
Our Mission: Advancing Essential Intelligence. Our People: We're more than 35,000 strong worldwide—so we're able to understand nuances while having a broad perspective. Our team is driven by curiosity and a shared belief that Essential Intelligence can help build a more prosperous future for us all. From finding new ways to measure sustainability to analyzing energy transition across the supply chain to building workflow solutions that make it easy to tap into insight and apply it. We are changing the way people see things and empowering them to make an impact on the world we live in. We're committed to a more equitable future and to helping our customers find new, sustainable ways of doing business. Join us and help create the critical insights that truly make a difference.
Our Values: Integrity, Discovery, Partnership. Throughout our history, the world's leading organizations have relied on us for the Essential Intelligence they need to make confident decisions about the road ahead. We start with a foundation of integrity in all we do, bring a spirit of discovery to our work, and collaborate in close partnership with each other and our customers to achieve shared goals.
We take care of you, so you can take care of business. We care about our people. That's why we provide everything you—and your career—need to thrive at S&P Global.
- Health & Wellness: Health care coverage designed for the mind and body.
- Flexible Downtime: Generous time off helps keep you energized for your time on.
- Continuous Learning: Access a wealth of resources to grow your career and learn valuable new skills.
- Invest in Your Future: Secure your financial future through competitive pay, retirement planning, a continuing education program with a company-matched student loan contribution, and financial wellness programs.
- Family Friendly Perks: It's not just about you. S&P Global has perks for your partners and little ones, too, with some best-in class benefits for families.
- Beyond the Basics: From retail discounts to referral incentive awards—small perks can make a big difference.
For more information on benefits by country visit: https://spgbenefits.com/benefit-summaries
That seems comprehensive. I usedfor subsections under Requirements. The rules say use
for section headings, but didn't forbid
for subsections. However, to be safe, maybe I should keep only
and use
for labels. But the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other heading levels. But to be safe, I'll use
for main sections and maybe
for subsections. However, the example includes "Qualifications" as a section heading. I have "Requirements" as a section heading, and within it "Basic Required Qualifications" and "Additional Preferred Qualifications". I could make them separate
sections: "Required Qualifications" and "Preferred Qualifications". That might be better. Let me restructure:
Required Qualifications
- ...
Preferred Qualifications
- ...
before the sections or within About the role. I'll output the HTML fragment without any wrapping tags. Now, ensure no markdown code fences. Just plain HTML. Let
- for those.
The "What's In It For You?" includes mission, values, benefits. I'll include mission and values as prose, benefits as list.
The "Global Hiring And Opportunity" is boilerplate EEO, so remove.
The "Recruitment Fraud Alert" and "Equal Opportunity Employer" are boilerplate, remove.
The "US Candidates Only: Know Your Rights" is boilerplate, remove.
Job ID, posted date, location: minor metadata, fold into a short