Beschreibung
The Content Catalog domain sits at the heart of the Content Platform studio. Our mission is to provide a single source of truth so content can be trusted, governed, and reused consistently across the platform. We own the core systems and workflows that make catalog of content accurate, complete, and available: from catalog APIs and content lifecycle orchestration through to the quality of the content.
Impact in the role Every song, podcast and audiobook starts as an original file, and our team owns the systems that receive, store and manage those files. We can already tell when an incoming file duplicates content we hold. The next step is acting on that, so duplicates are no longer stored and processed all over again.
In this role you'll help build ways to reuse what we've already processed and keep original storage efficient, secure and compliant at petabyte scale.
Who you are
You have solid experience building and operating backend services and APIs in production at scale, and you are proficient in Java or Scala, ideally both, since our services are largely Java and our data pipelines largely Scala. 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. For us, that means file lifecycle states and the relationships between original files and their derived outputs, typically in a wide-column store.
You have worked with data pipelin
Vollständige Beschreibung, Unternehmen und Bewerbungslink — nach der Anmeldung.
AnmeldenKontaktdaten des Arbeitgebers (E-Mail/Telefon/Telegram) sind in der öffentlichen Vorschau ausgeblendet.
Senden Sie Ihren Lebenslauf — dann können Arbeitgeber Sie direkt kontaktieren.