Senior Application Security Engineer

We need to output HTML fragment with sections: About the role? The posting includes description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, not invent. Remove boilerplate like EEO, etc. We need to include Pay section because posting includes base pay ranges per location. Also Benefits: mentions bonus incentive, health benefits, 401K, other perks, link. So Benefits section. Schedule? Not mentioned. So no Schedule. Skills? Could be derived from qualifications but maybe we can have a Skills section summarizing required/preferred? But we must not invent. Could list required qualifications as list under Requirements or Qualifications. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We need About the role (intro). Responsibilities (list of duties). Requirements (maybe required qualifications). Qualifications (maybe preferred?). But we must not duplicate. Could combine Required Qualifications under Requirements, Preferred under Qualifications. Skills maybe not needed if covered. But we can include Skills if there is explicit skill list: e.g., "Proficient in one modern programming language (preferably Java) and able to review code in most major languages." etc. Could be under Skills. However we must not create sections with filler. We have content for each. Let's extract: About the role: first paragraph describing Shutterfly and role overview. Responsibilities: bullet list of duties under "What You'll Do Here": Red Team Operations, Purple Team Collaboration, AI-Driven Offensive Security, Bug Bounty Program Management, Vulnerability Management, Threat Modeling & Risk Assessment, Incident Response, Secure SDLC, Code Review, Security Architecture & Design, Subject Matter Expertise, Mentorship & Leadership, Cross-Functional Collaboration, Continuous Improvement, Security Tooling. Requirements: Required Qualifications bullet list. Qualifications: Preferred Qualifications bullet list. Skills: maybe we can extract specific skills: proficiency in Burp Suite Pro, programming language, command-line scripting, etc. But those are already in qualifications. Could still have Skills section summarizing technical skills: Burp Suite Pro, AI/LLM tools, programming languages, scripting, etc. But to avoid duplication, maybe we omit Skills and put those under Requirements/Qualifications. However instruction says we can use those headings; not required to use all. We'll include only sections with substantive content: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO, diversity statement, application instructions, etc. Remove lines about supporting diverse workforce, learn more about commitment, etc. Also remove "This position may be eligible for a bonus incentive, health benefits, a 401K program, and other employee perks. More details about our company benefits can be found at https://shutterflyinc.com/benefits." That's benefits info; we keep but maybe summarize as bullet list. Pay: include base pay ranges per location. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep the exact pay ranges and location lists. Also benefits details: bonus incentive, health benefits, 401K program, other employee perks, link. Keep that. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove lines about "Supporting a diverse and inclusive workforce is important..." and "Learn more about our commitment...". Also remove "This opportunity can be remote, but candidates must reside in a state in which Shutterfly is registered to do business. This includes all US states except District of Columbia, North Dakota, Mississippi, Rhode Island, Vermont, and Wyoming." That's substantive? It's about eligibility; maybe keep as part of About the role? It's location eligibility. Could be considered part of role details. Not explicitly listed as a section but we could include under About the role as a sentence. It's substantive. Keep it. Also remove "This position will accept applications on an ongoing basis until filled. #SFLYTechnology". That's application instruction/boilerplate; remove. Now craft HTML. Structure:

About the role

At Shutterfly, we make life’s experiences unforgettable. We believe there is extraordinary power in the self‑expression. That’s why our family of brands helps customers create products and capture moments that reflect who they uniquely are. This is an exciting time for Shutterfly, and we are looking for a Senior Application Security Engineer (Offensive / Red Team) to join our team. In this role you will help shape an evolving offensive security practice, leading Red Team engagements against Shutterfly's critical applications while partnering closely with our Blue Team throughout each engagement to produce Purple Team outcomes — stronger detections, faster response, and measurably improved defenses. We're looking for someone who is as passionate about uncovering and exploiting a vulnerability as they are about working alongside defenders to make sure it can be detected, contained, and remediated. Just as important, you'll partner with developers and engineering teams to educate them on how to prevent and avoid vulnerabilities in the first place, and guide them on how to fix issues once identified. Your focus will be on building an offensive security capability that strengthens the entire security program, with collaboration between offense, defense, and engineering at its core.

Then Responsibilities:

Responsibilities

• Red Team Operations: Plan and lead offensive engagements against Shutterfly's applications and supporting infrastructure using established offensive and testing techniques — manual web penetration testing, exploitation, fuzzing, and adversary emulation supported by industry-standard offensive tooling — and coordinate with third-party testers when engagements call for it.
• Purple Team Collaboration: Work hand-in-hand with the Blue Team throughout every engagement. Share tactics, techniques, and procedures in real time, validate and improve detection and alerting coverage, run collaborative exercises, and convert offensive findings into concrete defensive improvements.
• AI-Driven Offensive Security: Augment conventional offensive techniques with AI and LLM-based tooling to accelerate and extend offensive and testing work — reconnaissance, payload and test-case generation, code and configuration review, and exploitation. Maintain a working understanding of how threat actors are weaponizing AI, and fold that knowledge into engagements and defensive recommendations to keep pace with a rapidly changing threat landscape.
• Bug Bounty Program Management: Manage the bug bounty program end to end — triage, impact assessment, risk scoring (CVSS), locating vulnerable code, providing mitigation guidance, thorough re-testing, and refining program policy and scope as needed.
• Vulnerability Management: Identify, triage, and drive remediation of application vulnerabilities through manual testing and exploitation, escalating systemic issues to the appropriate engineering teams.
• Threat Modeling & Risk Assessment: Lead threat modeling exercises and perform risk assessments for new and existing applications, using offensive insight to prioritize the risks that matter most.
• Incident Response: Collaborate with incident response and Blue Team partners to investigate application-related security incidents, applying offensive expertise to scope, reproduce, and understand attacker activity.
• Secure SDLC: Help define and reinforce secure development practices, including code reviews and integration of security checks into the CI/CD pipeline.
• Code Review: Perform and lead security reviews of critical PRs and code changes, and review code in most major languages.
• Security Architecture & Design: Partner with engineering and architecture teams to advise on secure systems and applications design, ensuring security is built in from the ground up.
• Subject Matter Expertise: Serve as a top technical resource to engineers across the organization. Help them reproduce vulnerabilities, understand impact, document issues, and validate the effectiveness of fixes.
• Mentorship & Leadership: Mentor junior security engineers and developers on offensive techniques, secure coding practices, and security principles. Build relationships with stakeholders and business leaders across the organization.
• Cross-Functional Collaboration: Work closely with product, engineering, DevOps, defensive security, and compliance teams to align security with business goals.
• Continuous Improvement: Maintain up-to-date knowledge of relevant offensive techniques, threats, mitigations, security best practices, and the evolving role of AI in both offensive operations and adversary activity.
• Security Tooling: Make effective use of the existing security tooling stack (e.g., SAST, SCA, DAST, IAST) to support offensive and defensive work.

Requirements:

Requirements

• Bachelor's degree in computer science, cybersecurity, or a related technical field, or comparable hands-on experience in lieu of a degree.
• Demonstrated experience leading or performing offensive security work, such as web application penetration testing or Red Team engagements, with hands-on proficiency in conventional offensive and testing techniques and industry-standard offensive tooling.
• Hands-on experience using AI/LLM tools for offensive security or testing, with an understanding of how threat actors are leveraging AI in a rapidly evolving threat landscape.
• Proficient in one modern programming language (preferably Java) and able to review code in most major languages.
• Strong analytical and problem-solving abilities with a risk-based security approach.
• Advanced user of Burp Suite Pro; bonus if you have created custom extensions in Java or Python or have used or modified existing extensions.
• Excellent communication and collaboration skills, with the ability to work across offensive and defensive teams, IT, engineering, and business stakeholders.

Qualifications (Preferred):

Qualifications

• Experience running Purple Team exercises or otherwise collaborating directly with defensive/Blue Team functions to improve detection and response.
• Full stack web development experience within an active security program.
• Experience managing a bug bounty program.
• A security certification that demonstrates proficiency in offensive security, network/web/mobile/AD assessments, secure coding, and professional report creation (for example: OSCP, OSEP, CRTO, OSWA, OSWE, GWAPT, GWEB).
• Submitted reports to bug bounty programs or VDPs, and you've found a CVE along the way.
• Strong command-line and scripting skills (bash, zsh, Python) on Linux and Mac.
• Enjoy attending security conferences and occasionally participate in CTFs.
• Spend time on cyber security training platforms (HackTheBox, TryHackMe).
• Have worked with engineering teams to develop secure code libraries.
• Capable of rapidly learning and integrating emerging tools and platforms with minimal supervision.

Benefits:

Benefits

• Eligible for a bonus incentive.
• Health benefits.
• 401K program.
• Other employee perks.
• Details available at shutterflyinc.com/benefits.

Pay:

Pay

• California: [$128,000‑181,250]
• Connecticut and New York: [$128,000‑165,750]
• Colorado, Illinois, Minnesota and Washington: [$128,000‑153,000]
• Nevada: [$120,250‑165,750]
• Maryland and New Jersey: [$138,250‑165,750]
• Hawai