Backend Engineer -Java/Scala/go

Our systems answer questions like: can this user play this content here, which features are available for it, and what restrictions apply? Every playback and every content surface depends on these decisions being correct, fast and reliable. Our current priorities include moving access decisions onto a shared, configurable model, consolidating gating logic across clients, and making our core access systems more resilient and easier to operate. You will contribute to all of these.

This is a role for someone who thrives on variety, context switching, and building trusted relationships across engineering teams. You will need to be comfortable operating with autonomy, adapting to different team cultures, and influencing technical direction in codebases you did not originally build.

What you'll do

• Build and operate high-availability, low-latency backend services that make content and feature access decisions for clients.

• Deliver features and improvements on the team's roadmap, working closely with the other engineers and the engineering manager.

• Improve the resilience and operability of core access systems, including caching, invalidation and incident readiness.

• Contribute to design discussions, code reviews and technical decisions within the team.

• Work with partner teams across catalog, playback, client and trust and safety to land changes safely.

• Keep documentation current and share context, so knowledge stays with the team.

Who you are

You have solid experience building and operating backend services and APIs in production at scale, and you are proficient in a backend language such as Java, Scala, Go, or similar.

You understand API design, schema evolution, and backward compatibility in systems where stability matters, and you are comfortable modelling data for auditability, versioning, and efficient querying.

You have worked with data pipelines and understand the tradeoffs between real time and batch processing. You are comfortable navigating unfamiliar codebases, ramping up quickly in new domains, and contributing meaningfully without needing to own the full context from day one.

You think carefully about the downstream impact of what you build, from how policy logic is structured to how it surfaces in enforcement decisions and regulatory reporting.

You have worked in regulated or compliance sensitive environments, or you are keen to develop that experience.

You collaborate well across teams and can build trust quickly with new groups.

You communicate technical decisions clearly to both technical and non technical stakeholders.