Senior Backend Engineer

Every purchase, promotion, and reward inside a Wildlife game flows through the systems the In-Game Economy team builds. Every live game in the studio depends on us running smoothly.

You'll thrive here if you spot the risk before it becomes an incident, propose the fix, own it end to end, and leave the system in better shape than you found it. You'll lead concrete architectural decisions, make engineers around you better as a natural consequence of your technical work. You'll design and evolve the services and SDKs that power monetization across the whole studio, working directly for the game teams that ship them. The impact of your decisions is visible in the metrics and the product, immediately with measurable consequences in production, every day.

Our stack: Unity/C# on the client, Go on the backend, AWS and Kubernetes for infrastructure.

WHAT THIS LOOKS LIKE DAY-TO-DAY

• Own significant parts of the In-Game Economy stack: Purchases (SKU management, receipt validation, external stores), Popup/Offers, Player Journey, and the SDKs games embed to consume them.
• Leading the design and implementation of complex features across mobile and backend, with sound, explicit architectural trade-offs.
• Owning technical decisions for your area: architecture, performance, scalability, and the accountability that comes with each.
• Design and implement backend services in Go, running on Kubernetes, with DynamoDB, Redis, Kafka, and gRPC in the daily toolbox.
• Investigate and act on production behavior: latency spikes, scale bottlenecks, unexpected provider changes (Apple/Google notification updates, store policy shifts). You diagnose and drive the response.
• Improve reliability and cost of services you own: run load tests before pushing changes, resize what is over provisioned, remove what is no longer needed.
• Partner directly with game teams (Tennis Clash, Zooba, Sniper 3D, and others) to unblock integrations, validate new features under real load, and adjust the platform when game requirements evolve.
• Raise the bar for the engineers around you through code review, design discussions, and pairing, as a natural consequence of your technical approach and work output.