Staff Software Engineer, Cloud Inference Safeguards

Anthropic Anthropic · AI Frontier · San Francisco, CA +1 · Safeguards (Trust & Safety)

Staff Software Engineer to build and operate safety, oversight, and intervention mechanisms for AI models (Claude) on third-party cloud service provider (CSP) platforms. This role ensures requests are monitored for misuse, enforced against policy, and compliant with data residency and privacy commitments. The engineer will integrate Safeguards into the CSP inference serving path, focusing on real-time enforcement, telemetry, and privacy architecture, while maintaining serving-path latency and scale. The work directly impacts the ability to ship frontier models on CSP platforms safely.

What you'd actually do

  1. Build, deploy and operate real-time safeguards infrastructure—classifiers, rate limits, enforcement actions, and intervention hooks—embedded directly in the third-party CSP inference serving path
  2. Design and maintain the data residency and privacy architecture for safeguards signals on CSP platforms, ensuring we can detect abuse and monitor model behavior while honoring regionalization boundaries and enterprise contractual commitments
  3. Develop telemetry, logging, and evaluation pipelines that give Safeguards, Policy, and T&S operational teams situational awareness over CSP traffic and close the visibility gap between third-party and first-party serving
  4. Dive into the CSP serving stack to identify the lowest-impact points to gather signals or introduce interventions without degrading latency, stability, or overall architecture
  5. Hold a high operational bar: own on-call, drive root-cause analyses and postmortems for safeguards incidents on CSP platforms, and build systems that reduce the human intervention required to keep Claude safe

Skills

Required

  • Python
  • high-scale, high-reliability software development
  • trust & safety, anti-abuse, fraud, or integrity systems
  • scaling infrastructure
  • adversarial thinking
  • communication skills

Nice to have

  • TypeScript
  • Rust
  • agentic coding tools
  • building trust and safety, anti-spam, fraud, or abuse detection and mitigation mechanisms for AI/ML systems
  • infrastructure to support these systems at scale
  • Machine learning serving infrastructure (GPUs/TPUs, inference servers, load balancing)
  • operational realities of running models in production
  • Major cloud platform internals—IAM, Network/service perimeter controls, regional resource constraints, cloud-native logging/monitoring
  • shipping software that runs inside a partner’s cloud
  • Data residency, privacy engineering, or compliance-constrained architectures
  • working closely with operational and human-review teams
  • adversarial mindset: has shipped defenses against motivated attackers before
  • intersection of platform/infra engineering and trust & safety
  • shipped software that runs inside someone else’s infrastructure
  • own a cross-team seam independently
  • drive consensus across orgs
  • make latency/safety tradeoff calls without escalation

What the JD emphasized

  • enterprise CSP customers expect
  • serving-path latency and scale
  • without gaps
  • in real time
  • situational awareness
  • without degrading latency, stability, or overall architecture
  • high operational bar
  • keep Claude safe
  • production enforcement
  • high-scale, high-reliability software development
  • trust & safety, anti-abuse, fraud, or integrity systems
  • serving stack
  • latency and reliability within tight budgets
  • advanced AI systems
  • safe development
  • risk tradeoffs
  • fast-paced, early environment
  • rapidly evolving AI space
  • infrastructure to support these systems at scale
  • ML serving infrastructure
  • operational realities of running models in production
  • Major cloud platform internals
  • shipping software that runs inside a partner’s cloud
  • Data residency, privacy engineering, or compliance-constrained architectures
  • regional or contractual boundaries
  • motivated attackers
  • sprint to close a gap before it becomes an incident
  • platform/infra engineering and trust & safety
  • control the whole stack
  • own a cross-team seam independently
  • make latency/safety tradeoff calls without escalation

Other signals

  • building and operating safety, oversight, and intervention mechanisms for AI models on third-party cloud platforms
  • ensuring requests served through CSP partners are monitored for misuse, enforced against policy, and compliant with data residency and privacy commitments
  • making safeguards run reliably inside CSP partner infrastructure at serving-path latency and scale
  • building, deploying, and operating multi-layered defenses that catch unwanted model behavior in real time
  • developing telemetry pipelines and enforcement hooks for rapid action when issues arise
  • shipping frontier models on CSP platforms with the same safety bar as first-party API