Jobs › Stripe

Security Engineer

Stripe · Remote · 8611 Security Analytics

Posted Sep 25, 2026 · We last checked this listing on Oct 6, 2026

Apply at Stripe

Likely interview questions for this role

Written from this job description, not a generic list. Each one notes what the interviewer is really checking.

About your past

Tell me about a defense you built that attackers got around. What did you learn about how they adapted?

What they are checking: Whether they expect adversaries to respond and design for the second move, not just the first.

Tell me about a time you worked with Fraud or Risk partners who wanted a stricter control than the product team would accept. How did it land?

What they are checking: Whether they can broker a decision between teams with different goals using data rather than rank.

Tell me about a time you were wrong about what an attacker was doing. How did you find out?

What they are checking: Whether they hold their hypotheses loosely and let the data correct them before the damage grows.

What would you do

A new abuse vector shows up on a Friday and attackers are already using it. Walk me through how you'd get a safeguard prototyped and live before it scales.

What they are checking: Whether they can move fast under pressure without shipping a control that breaks things for real users.

You've built a control that works, and now it needs to move to a product team that didn't ask for it. How do you hand it off so it survives?

What they are checking: Whether they can transfer ownership cleanly with docs, alerts and buy-in, so the incubated work doesn't rot.

How do you decide when a quick prototype is good enough to run in production versus when it needs more hardening?

What they are checking: Whether they can judge the risk of a rough control against the cost of leaving a hole open.

About the work

How do you use real attacker telemetry to decide what a control should actually block?

What they are checking: Whether they design defenses from observed behavior rather than guessing at what attackers might do.

Every control you ship costs some legitimate users a little friction. How do you measure that trade-off between blocking abuse and protecting conversion?

What they are checking: Whether they can run a fair experiment and put numbers on both the fraud stopped and the good users lost.

How would you build a regression suite so a threat you blocked once can't quietly come back six months later?

What they are checking: Whether they think about permanence and automated checks instead of one-time fixes that decay.

Say card testing spikes against a checkout endpoint. What signals would you look at first, and what's the quickest control you could put in place?

What they are checking: Whether they know practical abuse patterns in payments and can pick a fast, low-risk first response.

Practice this interview out loud.

Offer builds a real interview for this exact role at Stripe from your resume and this job description, asks the questions one at a time, and tells you what landed. The first one is free.

Practice this out loud

The full job description

As published by Stripe.

Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone’s reach while doing the most important work of your career. About the team Abuse Control Engineering (ACE) is Stripe’s rapid-response technical defense and control incubator. When urgent abuse vectors emerge, ACE bridges the gap using real attacker telemetry to prototype, test, and deploy software safeguards before vulnerabilities can be exploited at scale. We partner closely with Fraud, Risk and Product Engineering to run rigorous experiments, balancing aggressive risk mitigation against legitimate user conversion. Operating as both a strike team and an incubator, ACE builds automated regression suites in partnership with Abuse Research to permanently block threat recurrence and seamlessly transfers mature controls to long-term product owners across Stripe. What you’ll do As an Abuse Control Engineer on the Abuse Control Engineering (ACE) team, you will design, prototype, and incubate technical defenses that safeguard Stripe’s financial ecosystem against complex, cross-cutting abuse vectors.   Where emerging threat patterns identify Stripe product weaknesses, ACE steps in to rapidly build and experiment with technical safeguards. Driven by empirical evidence and Stripe’s FT3 (Fraud Taxonomy 3.0) framework, you will translate threat intelligence into hard technical control requirements (e.g., API rate-limiting, step-up challenges, parameter validation, pre-debit holds).  You will carefully balance security and product velocity, running experiments to evaluate risk reduction against user conversion impact. Managing controls through a strict incubation lifecycle, you will build automated regression suites to prevent recurrence and partner with native product teams to hand off mature, long-term defenses.   Responsibilities • Rapid Control Prototyping: Design, prototype, and deploy technical controls across API, protocol, and product boundaries to immediately close high-impact abuse vectors.  Evidence-Based Technical Requirements: Translate empirical attacker evidence and FT3 threat research Abuse Research, Fraud and Security into precise technical abuse requirements and control specifications.  • Control Co-Design: Collaborate closely with teams across Stripe to co-design resilient, secure controls across payment, onboarding, identity, and Connect surfaces.    • Risk Experimentation: Run rigorous experiments and A/B tests to measure risk reduction against legitimate user conversion impact, optimizing controls to minimize friction while neutralizing threats.   • Regression Testing: Build comprehensive regression testing suites and automated attack simulations with Abuse Research to ensure mitigated abuse vectors do not recur.  • Stakeholder Management: Execute ACE’s incubation model by defining handoff criteria, operational documentation, and target dates to transfer successful controls to product teams. Who you are We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement. Minimum requirements • 3+ years of experience in Security Engineering, Software Engineering, Application Security, or Anti-Abuse Engineering in a high-scale production environment. • B.S. or M.S. in Computer Science, Cybersecurity, Software Engineering, or a related technical field, or equivalent practical experience. • Strong software development background with expert proficiency in Python, Go, Java, or similar production languages, alongside expert SQL skills for analyzing system telemetry. • Hands-on engineering experience building API-level safeguards, rate-limiting frameworks, authentication/authorization checks, or input validation controls. • Demonstrated experience with automated testing frameworks, including writing unit, integration, and regression tests for critical backend software. • Strong cross-functional collaboration and communication skills, with a track record of partnering across security, product, and platform teams to drive technical outcomes. Preferred qualifications • Proven track record of designing and executing A/B tests, evaluating control efficacy, and balancing security safeguards against user conversion friction. • Deep expertise in threat modeling, secure system architecture, and modern application security design principles. • Familiarity with established threat frameworks (e.g., FT3, MITRE ATT&CK) and applying adversary kill chain analysis to build resilient defenses. • Strong domain knowledge of financial fraud vectors, threat actor TTPs, and attacker infrastructure (e.g., Account Takeover, Card Testing, Credential Stuffing). • Hands-on experience with large-scale data processing platforms (e.g., Databricks, Trino, PySpark) to monitor and measure control performance across distributed systems. • Demonstrated capability in incubating software features, establishing clear operational handoff criteria, and seamlessly transitioning ownership to partner engineering teams.

Apply at Stripe

More security engineer roles