Skills this job asks for
Machine learningProduct managementLeadershipAccountingLLMs
Add your CV (free) to see which of these your CV is missing.
Sponsorship verdict
Sponsorship possible
One solid signal, not two. Worth applying, and worth asking about sponsorship early.
-
✓
Employer is on a government sponsor recordThe US Department of Labor certified 260 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
What Stripe paid sponsored hires in similar roles1 certified filing for “Machine Learning Engineer” (Software Developers) in NJ: $161k–$161k, median $161k.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- Employer is on a government sponsor record
- The US Department of Labor certified 260 H-1B/E-3 labor condition applications for this employer between Oct 2025 and Jun 2026 (latest Jun 2026) — the step every H-1B hire needs first. Source: LCA disclosure data (US Department of Labor (OFLC)).
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
- What Stripe paid sponsored hires in similar roles
- 1 certified filing for “Machine Learning Engineer” (Software Developers) in NJ: $161k–$161k, median $161k. Most were filed at wage level III (100%) — 3 lottery entries, ≈46% projected selection odds for cap-subject employers. Source: US Department of Labor LCA disclosure data (Oct 2025 – Jun 2026).
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
About the role
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
The Radar ML team builds the machine learning systems that power Stripe’s Radar fraud and abuse product suite. Our models make real-time decisions across a significant share of internet commerce - helping businesses stop fraud, increase authorization, and grow safely. By turning economy-scale datasets into compelling ML products, the team directly improves customer outcomes and drives meaningful revenue for Stripe.
The team is growing, and expanding into multiple new areas. We are building abuse protections across the full customer life-cycle, adaptive and customizable fraud systems for enterprises, and risk intelligence for 50+ global payment methods.
What you’ll do
You will lead the machine learning strategy for abuse prevention across the full customer lifecycle. Abuse doesn't stop at the payment. Bad actors create fake and duplicate accounts, take over legitimate ones, farm free trials and promotions, resell access they obtained below cost, use services they never intend to pay for, and file bad-faith refunds and disputes. For AI companies, every abusive account burns real compute, and the same actors keep moving from one account, product, and access path to the next.
Stripe is uniquely positioned to solve this. Our network sees consumers across millions of businesses, so we can recognize a bad actor at signup, at login, at payment, and long after. Radar has already shipped the first building blocks: account evaluations at signup and login, customer-level abuse risk, and APIs that let businesses report their own abuse outcomes. You will turn these building blocks into a unified abuse prevention layer that understands the consumer behind every event and helps businesses act consistently across all of that consumer's accounts. This is a large growth opportunity for Radar, and a strategic priority for Stripe.
This is a fast-moving 0→1 area, built alongside some of the world's leading AI companies, and the attacks are real today. Labels are sparse, delayed, and differ by business. Much of the customer journey is only partly visible to us. Adversaries adapt as soon as we ship. You will set the technical direction, make the hard architecture calls, and personally build the hardest pieces.
Responsibilities
• Set the technical strategy and multi-quarter roadmap for lifecycle abuse ML, with product and engineering leadership: which abuse vectors to take on, in what order, and with what approach.
• Design a persistent, continuously updated consumer risk profile that combines signals from signups, logins, payments, product usage, refunds, and disputes. Evolve it from explainable composite scores toward model-driven risk scores for each type of abuse.
• Lead development of models for abuse vectors such as multi-accounting, account takeover, bots, free-trial and promotion abuse, unauthorized resale, non-payment, refund abuse, and friendly fraud. Use graph, sequence, and LLM-based approaches over payment, account, and product-usage data.
• Solve the label problem by designing ways to learn from sparse, delayed, merchant-specific, and weak labels, including merchant-shared feedback, LLM-assisted labeling, and network-level signals.
• Define how we measure success: evaluation frameworks, impact and ROI
Apply on employer site ↗