Product Security Engineer II

About the InfoSec & IT Team

The Application Security team helps Affirm build and launch products that earn customer trust, meet compliance obligations, and reduce business risk. We partner closely with product, engineering, infrastructure, risk, compliance, and other teams to identify security risks early, recommend pragmatic mitigations, and help teams find safe paths to launch.

We are looking for an early-career Application Security Engineer who is curious, collaborative, and comfortable working with code. You will help assess application risks, support vulnerability management efforts, partner with engineering teams on secure design decisions, and contribute lightweight tooling, automation, and code-informed analysis that helps AppSec scale across Affirm.

This role is a great fit for someone who has hands-on software or security experience, enjoys reading and reasoning about code, is actively developing offensive security skills, and wants to apply those skills in a product-minded, risk-based way.

What You'll Do

• Partner with product and engineering teams to identify application security risks and help frame them as clear business risks, launch options, and recommended next steps.

• Read application code, configuration, pull requests, logs, and documentation to understand how systems work and where security risks may exist.

• Contribute small code changes, scripts, detections, tests, secure defaults, or automation that improve AppSec workflows and reduce recurring issues.

• Work in GitHub to review code changes, understand engineering context, participate in pull request discussions, track remediation work, and collaborate with engineers.

• Help evaluate vulnerabilities from internal testing, bug bounty reports, security tooling, penetration tests, and other sources; partner with teams to prioritize and remediate issues based on real-world risk.

• Contribute to vulnerability management workflows, including triage, validation, severity assessment, remediation guidance, tracking, and reporting.

• Translate recurring security findings into repeatable mechanisms such as secure coding guidance, checklists, paved paths, lightweight automation, detection logic, reusable review patterns, or developer-facing documentation.

• Work with engineers to understand system designs, data flows, trust boundaries, authentication and authorization models, code paths, and potential abuse cases.

• Communicate security issues clearly to both technical and non-technical audiences, including the risk, tradeoffs, recommended mitigations, and residual risk.

• Build strong relationships across Affirm teams and influence security outcomes without relying on formal authority.

• Help connect AppSec work to customer trust, regulatory/compliance expectations, operational resilience, and business outcomes.

• Continue developing hands-on offensive, defensive, and software engineering skills through practical work, labs, tooling, research, certifications, or contributions to internal security programs.

What We Look For

• 4+ years of experience in application security, software engineering, security engineering, vulnerability management, penetration testing, security operations, or equivalent practical experience.

• Foundational programming ability in one or more languages such as Python, JavaScript/TypeScript, Kotlin, or similar.

• Comfort reading, navigating, and reasoning about code, even in unfamiliar codebases.

• Experience using Git and GitHub or similar version-control workflows, including branches, commits, pull requests, code review, issues, or project tracking.

• Some hands-on experience building, testing, breaking, or securing software. This could include professional experience, internships, security labs, CTFs, bug bounty work, open-source contributions, personal projects, automation scripts, internal tools, or coursework.

• Ability to write clear, maintainable scripts or small programs to solve practical problems, automate manual workflows, analyze data, validate findings, or improve security processes.

• Foundational understanding of common web, API, mobile, cloud, and application security risks, such as OWASP Top 10 issues, authentication and authorization flaws, injection, insecure design, secrets exposure, dependency risks, and data protection concerns.

• Interest in offensive security, such as studying for or completing security certifications, practicing web/API testing, learning exploit development fundamentals, using tools like Burp Suite, or participating in labs and capture-the-flag environments.

• Exposure to vulnerability management concepts, including triage, severity assessment, remediation tracking, false-positive analysis, compensating controls, and risk-based prioritization.

• Ability to reason about risk and tradeoffs, not just identify issues. You can explain what could go wrong, how likely it is, what impact it may have, and what options exist to reduce risk.

• Strong product and engineering empathy. You seek to understand launch goals, technical constraints, user impact, and business priorities before recommending a path forward.

• Clear written and verbal communication skills, including the ability to explain security findings in practical, actionable terms.

• A collaborative mindset and comfort working across product, engineering, compliance, risk, infrastructure, and security teams.

• Curiosity, humility, and a growth mindset. You proactively seek feedback, ask good questions, and continue building your technical depth.

• Secure-by-design judgment, including the ability to spot patterns, recommend simple controls, and balance launch velocity with meaningful risk reduction.

• Highlight any open‑source security tools or scripts you have built in your résumé; concrete artifacts show you can deliver automation.
• Prepare to discuss a recent vulnerability you triaged: describe the finding, risk assessment, and how you guided remediation.
• Brush up on GitHub pull‑request review etiquette; interviewers may ask you to walk through a mock code review.
• Showcase familiarity with at least one programming language mentioned (Python, TypeScript, Kotlin) by sharing relevant code samples or projects.
• Emphasize soft‑skill examples where you translated technical risk to non‑technical stakeholders, as communication is a key part of the role.
• Research Affirm’s credit‑product ecosystem so you can speak to how security impacts user trust in buy‑now‑pay‑later services.
• When negotiating, leverage typical remote‑work benefits (home‑office stipend, flexible PTO) even if salary numbers aren’t disclosed.