Senior Application Security Engineer

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 with real content. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, diversity statement, application instructions, etc. Keep substantive info. We need to parse the posting. First paragraph: "At Shutterfly, we make life’s experiences unforgettable..." That's about company mission. Could be "About the role" or maybe "About Shutterfly". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and then paragraph describing role. Then "What You'll Do Here" with bullet list of duties. That's Responsibilities. Then "Required Qualifications" heading. Then "Preferred Qualifications" heading. Then compensation/pay info: "The compensation package for this role is based on multiple factors..." plus base pay ranges per location. That's Pay section. Then benefits: "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 ..." That's Benefits. Schedule: Not mentioned explicitly; maybe remote possibility: "This opportunity can be remote, but candidates must reside in a state in which Shutterfly is registered to do business." That's location/remote info, could be Schedule? Not exactly schedule. Could be "Work Arrangement" but not in allowed headings. Since schedule not specified, we should not create Schedule section. Skills: Could be derived from qualifications but we have Required and Preferred sections; maybe we can combine into Qualifications and Skills? The instruction says we can use Skills heading if there is real specific content. We have list of required qualifications (degree, experience, etc.) and preferred qualifications (certifications, etc.). Could treat Required as Qualifications, Preferred as Skills? But better to follow typical: Required Qualifications and Preferred Qualifications as separate sections? The allowed headings include Qualifications and Skills. We could put Required Qualifications under

Qualifications

and Preferred under

Skills

. Or we could have both under Qualifications and Skills. Let's decide: Use Qualifications for required (degree, experience). Use Skills for preferred (certifications, etc.). That seems reasonable. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points under Responsibilities, Required Qualifications, Preferred Qualifications, Pay, Benefits. We must not include boilerplate like diversity statement, EEO, etc. Also remove "Supporting a diverse and inclusive workforce..." paragraph. Also remove "Learn more about our commitment..." etc. Also remove "This position will accept applications on an ongoing basis until filled." and "#SFLYTechnology". Also remove "More details about our company benefits can be found at https://shutterflyinc.com/benefits/"? That's part of benefits; we can keep mention but maybe it's okay as it's substantive? It's a link to benefits details; we can keep as part of Benefits paragraph. We must not include navigation, legal, EEO, etc. Now produce 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

• 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.
• 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.
• 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.
• 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.
• Identify, triage, and drive remediation of application vulnerabilities through manual testing and exploitation, escalating systemic issues to the appropriate engineering teams.
• Lead threat modeling exercises and perform risk assessments for new and existing applications, using offensive insight to prioritize the risks that matter most.
• Collaborate with incident response and Blue Team partners to investigate application-related security incidents, applying offensive expertise to scope, reproduce, and understand attacker activity.
• Help define and reinforce secure development practices, including code reviews and integration of security checks into the CI/CD pipeline.
• Perform and lead security reviews of critical PRs and code changes, and review code in most major languages.
• Partner with engineering and architecture teams to advise on secure systems and applications design, ensuring security is built in from the ground up.
• 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.
• 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.
• Work closely with product, engineering, DevOps, defensive security, and compliance teams to align security with business goals.
• 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.
• Make effective use of the existing security tooling stack (e.g., SAST, SCA, DAST, IAST) to support offensive and defensive work.

Then Qualifications (required):

Qualifications

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

Then Skills (preferred):

Skills

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

Then Pay:

Pay

The compensation package for this role is based on multiple factors, such as job level, responsibilities, location, and candidate experience. The base pay ranges included below are specific to the locations listed, and may not be applicable to other locations.

• 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]
• Hawaii: [$120,250-144,750]

This position may be eligible for a bonus incentive, health benefits, a 401K program, and other employee perks.

Then Benefits:

Benefits

More details about our company benefits can be found at https://shutterflyinc.com/benefits/.

We should not include schedule. Check for any leftover boilerplate: The diversity statement removed. The "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." This is location/remote info; could be considered under Benefits? Not exactly. Could be a separate section like "Work Arrangement" but not allowed. Since we don't have a heading for location, we could incorporate into Benefits or Pay? Probably better to add a short paragraph under Benefits or maybe under About the role? But the instruction: only include sections when posting has real, specific content for it. This is specific content about remote eligibility. There's no heading for it; we could incorporate into Benefits as a note? But Benefits heading is for benefits; remote eligibility is not a benefit. Could create a section "Location" but not allowed headings. The allowed headings list does not include Location. So we must either drop it or incorporate into an existing section where it fits loosely. Perhaps