Backend Software Engineer, Trust & Safety (Anti-Fraud)

• Fraud prevention, payments risk, or platform abuse experience.
• Integrating risk-scoring services or building rules engines and rate limiters.
• Case management, appeals, and risk operations tooling.
• Familiarity with Stripe.
• Experience building real-time scoring, graph-based account linkage systems.
• Python/Go experience.

Why this role exists

Our ML and analytics teams already work on fraud detection and risk analysis. This role owns the backend that turns their signals into reliable protections across accounts, credits, payments, and generation. You'll integrate risk checks into product flows, build enforcement services and operator tools, and make sure controls work correctly in production. We're looking for an engineer we can trust to take a backend problem from an unclear starting point to a working solution.

• Risk integrations: connect existing ML scores and risk signals to account creation, credit usage, payments, and generation flows, with clear timeouts and fallback behavior.
• Enforcement services: implement configurable rules, rate limits, account restrictions, and credit or payment controls with consistent behavior across services.
• Operator tooling: build APIs and workflows for reviewing cases, inspecting decision history, and safely applying or reversing restrictions.
• Production reliability: handle retries, duplicate events, concurrent requests, and safe rollouts; add monitoring and audit trails so failures can be traced and fixed.
• Work in other teams’ codebases to add signals or interventions without hurting their stability or architecture.
• Ownership: clarify the control with ML, analytics, and operations → scope the smallest useful implementation → ship → verify production behavior and review impact with the team. Our release cycle is days, not quarters, so your first shipped protection happens fast.

• You prefer problems where requirements stay stable after launch.
• You prefer work centered on training models or producing analysis rather than building and operating backend services.

• Recruiter screen: role expectations, logistics, and fit.
• Technical interview: a difficult system you shipped, what you personally decided and built, and how your work made the team more capable without leaving it dependent on you.
• Additional technical interview, if needed: a deeper discussion of technical skills and open questions.
• Product fit interview: take an existing risk signal and an operator need, scope a backend protection, and work through failure cases and effects on legitimate customers.
• Offer.

Competitive base in USD, equity, relocation support, and ownership of protections that preserve both company revenue and customer trust.