About the role
What you'll Do
- Define the technical direction for policy enforcement infrastructure
- Architect enforcement capabilities as a shared platform designed to be consumed by multiple product teams rather
- Design and evolve multi-signal orchestration systems that enable configurable, auditable policy enforcement at scale across content types and product surfaces
- Build the data foundation that makes enforcement decisions durable and reusable
- Own the hardest API and contract decisions: schema design, versioning strategy, and how enforcement interfaces evolve without breaking the teams that depend on them
- Establish integration standards for teams onboarding onto shared enforcement infrastructure, and work directly with consuming teams to execute migrations with clean cutoffs and clear end states
- Influence architecture across detection, signal processing, and enforcement workflows so that the underlying primitives stay coherent as the platform scales
- Mentor engineers and set the bar for how the team reasons about API design, data modeling, and the downstream compliance consequences of infrastructure choices
Who You Are
- Deep experience designing and operating large-scale distributed systems, APIs, event-driven pipelines, rule engines, and decision systems running in production across high-throughput environments
- Proficient in backend engineering at scale, with strong command of languages like Java, Kotlin, Go, or similar; comfortable owning data models, service contracts, and storage layer decisions
- Experienced with stream processing and event-driven architectures (Kafka, Pub/Sub, or equivalent) and the tradeoffs between batch and real-time enforcement pipelines
- You have designed systems where schema and contract stability matter as much as correctness
- Experienced with workflow orchestration and distributed coordination, whether through dedicated orchestration frameworks like Temporal or Airflow, choreography-based event systems, or hybrid approaches, and understand the tradeoffs between each in the context of long-running, stateful enforcement workflows
- Experienced with relational and non-relational storage systems and know how to model enforcement data for auditability, immutability, and efficient querying at scale
- You understand platform engineering patterns: multi-tenant APIs, configurable rule engines, policy-driven actioning systems, and the difference between building for one team and building for many
- Familiar with observability and operational excellence, distributed tracing, structured logging, alerting, and the tooling that makes enforcement systems debuggable and auditable in production