Senior Application Security Engineer
Shutterfly · Minneapolis, MN · 1 mo ago
On-siteInformation Technology$128k–$181k/yrFull-time
We need to produce HTML fragment with sections: About the role? The posting includes description. We need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We have description: At Shutterfly... This is an exciting time... This is role description. Could be "About the role". Then responsibilities: list of duties (What You'll Do Here). Then required qualifications: list. Preferred qualifications: maybe under Qualifications or Skills. Benefits: mention bonus incentive, health benefits, 401K, other perks. Pay: salary ranges listed. Schedule: remote possibility? It says "This opportunity can be remote, but candidates must reside in a state...". That's schedule/location info. Could be under Schedule or maybe not needed. We'll include Schedule if we have info: remote eligible, must reside in certain states.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, diversity statement, application instructions, etc. Also remove "Learn more about our commitment..." etc. Also remove "Supporting a diverse and inclusive workforce..." maybe keep? It's EEO boilerplate; should remove. Also remove "This position will accept applications..." etc.
We must preserve all substantive info. So keep description, responsibilities bullet list, required qualifications bullet list, preferred qualifications bullet list, benefits bullet list, pay table, schedule info.
We must not invent or summarize away detail. Use
- for any list of duties/requirements/benefits. Use
for prose. We need sections: About the role (prose), Responsibilities (list), Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe list of skills like programming language, Burp Suite, etc), Benefits, Pay, Schedule. We must avoid empty sections. Let's extract content. About the role: first paragraph(s) before "What You'll Do Here". That includes: "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." We can put that as
About the role
...
Responsibilities: under "What You'll Do Here" then bullet list items each starting with bold headings? The text includes headings like 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:. Each followed by description. We need to turn each into - items. Should we keep the heading bold? We can just include the text as is inside
- . Ensure we preserve all detail.
Let's extract each bullet:
- 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.
Now Required Qualifications: list after "Required Qualifications". Items:
- 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.
Preferred Qualifications: list after "Preferred Qualifications". Items:
- 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.
Now Benefits: The text: "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/."
We can make a list: bonus incentive, health benefits, 401K program, other employee perks. Also maybe mention link? We could include as prose? But rule: use
- for any list of benefits. So we can list those items. The link maybe as prose? Could include as
More details ...
. But that's not a list; it's prose. We'll keep as. Pay: The salary ranges: list per location. We need to present as maybe a table? But rule only allows
- for lists,
for prose, headings. We could present as
- each location range. That's acceptable.
Schedule: remote eligibility and state restrictions. Could be prose: "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." Also maybe mention ongoing basis until filled? That's application instruction; we should remove. So schedule section: remote work eligibility.
We must not include boilerplate like diversity statement, EEO, etc. Also remove "Learn more about our commitment to Diversity, Equity, and Inclusion on our Career Site." Remove that.
Also remove "Supporting a diverse and inclusive workforce is important..." etc.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ... ...
Required Qualifications
- ... ...
Preferred Qualifications
- ... ...
Skills
Maybe we could combine some skills from qualifications? But we already have qualifications sections. The instruction says use sections like Skills if posting has real specific content. We have skills like proficiency in programming language, Burp Suite, etc. Those are already in qualifications. Could create a Skills section extracting those: Proficient in one modern programming language (preferably Java) and able to review code in most major languages; Advanced user of Burp Suite Pro; bonus if you have created custom extensions in Java or Python or have used or modified existing extensions; Strong command-line and scripting skills (bash, zsh, Python) on Linux and Mac; etc. But to avoid duplication, we could keep qualifications as is and not create Skills. However the instruction says we can include sections only when posting has real specific content. We already have Required Qualifications and Preferred Qualifications; that's enough. Skills could be omitted to avoid thin sections. We'll omit Skills. Benefits:Benefits
- Bonus incentive
- Health benefits
- 401K program
- Other employee perks
More details about our company benefits can be found at shutterflyinc.com/benefits.
But rule: usefor prose. The link could be inside
. That's fine. Pay:
- each location range. That's acceptable.
Schedule: remote eligibility and state restrictions. Could be prose: "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." Also maybe mention ongoing basis until filled? That's application instruction; we should remove. So schedule section: remote work eligibility.
We must not include boilerplate like diversity statement, EEO, etc. Also remove "Learn more about our commitment to Diversity, Equity, and Inclusion on our Career Site." Remove that.
Also remove "Supporting a diverse and inclusive workforce is important..." etc.
Now produce HTML fragment.
Structure:
- for lists,
- for any list of benefits. So we can list those items. The link maybe as prose? Could include as