Senior Engineer - Backend / Fullstack

Role Overview

ETV is building out its publishing platform: integrating a new CMS, creating new authoring experiences for the newsroom, and standing up subscription services. This role owns the backend modules and services behind that platform, with enough full-stack range to carry a feature through to the interface. It is a build-and-own role rather than a build-and-hand-off one - you keep what you ship running, and you evolve it as traffic and requirements change. Experience required: 3-5 years.

What You'll Work On

• New CMS integration and new authoring experiences across the publishing platform ecosystem
• Subscription services, built as a real platform capability
• Internal tools for editorial and operations teams
• REST APIs consumed by the website and the Android and iOS apps
• Platform scalability and reliability improvements, and production troubleshooting

Who Is Right for This Role

• 3-5 years building backend services in Go or Java, with genuine system design ability
• Has designed or operated services handling 100K+ DAU
• Comfortable across horizontal scaling, caching, databases, queues, and observability - Kafka or RabbitMQ, Redis, Elasticsearch, SQL and NoSQL
• Has owned a production service for at least 1-2 years and made real architectural changes to it as scale and requirements evolved
• Can take an ambiguous, evolving requirement through to production without waiting for a finished spec
• Writes clean, maintainable code, reviews others' work, and collaborates with product and engineering rather than working in isolation

Who Isn't a Fit

• Has not owned, maintained, or evolved a production service over a sustained period of at least 1-2 years
• Has not been responsible for meaningful architectural changes to a production service as requirements, traffic, or scale evolved
• Has worked primarily from well-defined requirements, with no track record of navigating ambiguity through to production

How You'll Work

• Willing to spend up to 10 days in the office during onboarding to get to know the team and engineering ecosystem.
• Actively participates in daily standups and weekly connects.
• Actively participates in technical discussions.
• Communicates clearly and proactively.
• Uses asynchronous communication effectively, providing enough context to make decisions offline.
• Available and responsive for important calls and team discussions during regular office hours and occasionally outside of them.