You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Perplexity

Member of Technical Staff (Software Engineer, Fraud Prevention)

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay £95K - 130K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The fraud prevention team guards the company's products, users, and infrastructure against fraud and abuse at every stage: sign-up, authentication, payments, API usage, and product features.

The team builds and runs a real-time decisioning platform, along with the data pipelines for detection and model training, the integrations with product and payment systems, and the internal tools used for investigation and response.

As a software engineer, you take services from design through production operations and work alongside fraud analysts, ML engineers, and product teams. The aim is to make abuse costly for bad actors while keeping legitimate use smooth for everyone else.

Responsibilities

  • Design, build, and run high-throughput backend services with low latency for fraud detection and prevention.
  • Build data pipelines and real-time feature calculations that feed detections and ML models.
  • Collect and process trust signals.
  • Connect fraud decisions into product, authentication, and payment flows across the company.
  • Keep production services reliable through monitoring, alerting, safe rollouts, and incident response.
  • Build internal tools for investigation, enforcement, and audit trails.
  • Work with fraud analysts to move newly observed abuse patterns into production detections quickly.

Requirements

  • At least 5 years of building and operating high-throughput, latency-sensitive backend systems in production.
  • Strong systems programming background. Experience with Rust, Go, or C++ is preferred, since the team writes Rust.
  • Hands-on work with Kubernetes, Terraform, and cloud infrastructure.
  • Solid grounding in data: stream and batch computation, and the trade-offs between caching and storage.
  • A pragmatic, ownership-driven way of working: ship in small steps, measure results, and make failures degrade safely.
  • Experience in fraud prevention, anti-abuse, or payments risk.
  • Experience serving ML models in production.
  • Client-side experience on web or mobile for collecting signals.

Where you’d work

Part of the week in the office

You can work from

  • United Kingdom

About the company

Perplexity

  • Industry: AI

Office in London, United Kingdom

Also hiring in San Francisco, United States, New York City, United States, Washington D.c., United States and 3 more places

2 of their 27 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 2 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

2 red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Go
  • Kubernetes
  • Terraform
  • C++
  • Rust
Seniority
Staff
Type
Full-time
Industry
AI
Specialty
Backend
Region
United Kingdom
Show 7 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Staff
Experience
5+ years
Tech stack
  • Go
  • Kubernetes
  • Terraform
  • C++
  • Rust

Location

Work model
Hybrid
Region
United Kingdom
Office
  • London, United Kingdom
Remote from
  • United Kingdom

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
AI

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason