Job Opportunities API

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. Share the on-call rotation: respond to incidents on services you know deeply, document what you learned, and push follow-ups that prevent the next occurrence. WHAT YOU'LL NEED Solid experience designing and operating backend systems at scale: service decomposition, asynchronous processing, event-driven architectures, and the trade-offs each involves. A demonstrated ability to lead technical initiatives and raise the bar for those around you. Strong hands-on skills in Go and comfort working in Node.js, or comparable languages with willingness to ramp up quickly. Practical experience with DynamoDB or another NoSQL store at scale, Kafka or another streaming platform, and Kubernetes-based deployments. Comfort operating in production: observability tooling (Datadog, Prometheus, distributed tracing), load testing, incident response. Working proficiency in English. The team collaborates with stakeholders across regions. WHAT WE'D LOVE TO SEE Experience with mobile in-app purchase ecosystems (Apple StoreKit, Google Play Billing, receipt validation, refund and chargeback flows). Prior work on SDKs or client-facing libraries that other engineering teams consume, with hands-on experience in C# (for the Unity SDKs we maintain) targeting mobile development. Hands-on experience with native mobile development in Kotlin (Android) and Swift (iOS), useful for the Platform SDK's multi-architecture native core. Familiarity with Dart (Flutter) and TypeScript (Capacitor), useful for tooling that generates code into game projects. Exposure to games or other high-throughput consumer products with strong event-driven components. Familiarity with Kubernetes, AWS, Terraform, gRPC/Protobuf, and