Principal Software Engineer – Platform Engineering

Role overview Set architectural direction and deliver hands-on changes that help a large microservices platform scale across regions, independent deployment cells, and private or isolated environments. The role focuses on service architecture and runtime configuration, working directly in product services and shared components so deployments can evolve without environment-specific assumptions embedded in application code.

Responsibilities - Design and implement service-side changes needed to support a cell-based architecture, including re-architecture and shared libraries. - Break large service estates into subsystems that can evolve and release independently. - Identify and address horizontal scalability constraints across regions, cells, and deployment models. - Own the application configuration framework for managing environments as a fleet, and build services and libraries for private or isolated deployments. - Deliver architectural changes in collaboration with teams that own the affected product services. - Define patterns and reference implementations, clarify service and platform responsibilities, and mentor senior engineers. - Use AI tooling in day-to-day development and help guide its wider engineering use.

Requirements - Deep hands-on architectural experience with microservice estates numbering in the hundreds. - Strong Java and Python skills, with willingness to work across other technology stacks. - Demonstrated success decomposing services into independently evolving subsystems and designing for horizontal scale across regions or deployments. - Experience with cell-based, multi-tenant, or multi-region architectures. - Cloud-native experience with Kubernetes, containers, and AWS. - Experience externalizing configuration and reducing environment-specific dependencies in application code. - Ability to deliver significant changes in code owned by other teams and anticipate architectural limits before they cause incidents.

Nice to have - Experience with Vespa, private or air-gapped deployments, or shared libraries and internal frameworks used across many teams.

Benefits and work setup The role may include performance-based bonus, equity, and a benefits program.