Principal Backend Engineer

We are looking for a Principal Software Engineer who is not just a coder, but a true architect. While you will sit at the forefront of our technology stack (Golang, GCP, Kubernetes), your primary mission is specific: You will lead the architectural overhaul of our core matchmaking system.

We process over 30 million matches monthly for a user base of 26 million registered users. We need an elite individual contributor who can look at this scale not just as a traffic challenge, but as an abstraction challenge. You will design the systems that define how our players compete, ensuring our architecture is decoupled, extensible, and capable of handling the next 100 million users.

What You Will Do

• Architect the Future of Matchmaking: Lead the design and implementation of the next generation of our matchmaking engine. You will work closely with the rest of the team on reshaping our Matchmaking for the future of the platform;
• Master of Abstraction: Create clean, robust interfaces and high-level abstractions. You won't just solve today's bugs; you will build the "Lego blocks" that allow our cross-functional teams to build features rapidly without getting bogged down in complexity;
• Scale & Reliability: Tackle complex distributed system challenges. You will ensure our microservices can handle massive throughput with minimal latency, utilizing GCP and Kubernetes to their fullest potential;
• Technical Leadership: While this is an IC role, you will be a force multiplier. You will drive technical standards, conduct high-level code reviews, and mentor senior engineers on design patterns and architectural best practices.

• Proven Backend Expertise: Deep experience designing, developing, and deploying robust APIs and microservices in production. Golang experience is highly preferred;
• Architectural Vision: Proven experience re-architecting legacy systems into distributed, modern microservices. You understand Domain-Driven Design (DDD) and know how to draw the boundaries between services correctly;
• Scaling Instincts: You understand the nuances of database locking, eventual consistency, distributed caching, and race conditions.