<div class="show-more-less-html__markup show-more-less-html__markup--clamp-after-5 relative overflow-hidden"> <p>Backend Engineer Wallet, Game Services &amp; Real-Time Casino Platform</p><ul><li>Frankfurt Hybrid <span>(preferred)</span></li><li>Zagreb / Split Hybrid</li><li>Sofia Hybrid </li><li>Full Remote </li><li>Freelance accepted </li></ul><p><br/></p><p><strong>Every spin, every coin balance, every reward in our casino flows through the services you will own. Tens of thousands of concurrent players. </strong></p><p><strong>Sub-100 ms response times. Zero tolerance for a lost transaction.</strong></p><p>We are a small social-casino team. No committees, no Jira theatre, no five layers of approval between a good idea and production.</p><p>If you like writing code that real users hit a million times a day and you'd rather ship than slide-deck, read on.</p><p><br/></p><p><strong>What you will actually build</strong></p><p>• The wallet ledger — idempotent debits and credits, double-entry accounting, audit trail clean enough for any future regulator.</p><p>• Game services — RGS integrations, spin orchestration, jackpot pools, bonus engines.</p><p>• Account &amp; session — auth, KYC hooks, anti-fraud signals, session continuity across web and mobile. • The event spine — RabbitMQ-driven choreography between wallet, games, CRM and analytics, with DLQs that actually get replayed.</p><p>• Performance hot paths — Redis caching, query tuning, p99 latency you can defend in a postmortem.</p><p><br/></p><p><strong>Our stack</strong></p><p>Language Java 21 + Kotlin (Kotlin for new services, Java for legacy core)</p><p>Framework Spring Boot 3.x, Spring Cloud where it earns its keep</p><p>Data PGSQL primary, Redis for cache and rate-limiting</p><p>Messaging RabbitMQ with proper exchanges, DLX, durable queues</p><p>Cloud &amp; Infra AWS (EKS, RDS, ElastiCache, SQS where it fits better than Rabbit)</p><p>Build &amp; CI Gradle, GitHub Actions, Docker, Terraform</p><p>Observability Datadog APM + logs, Sentry for client-facing errors</p><p>AI tooling Cursor / Copilot / Claude — used pragmatically, not as a religion</p><p><br/></p><p><strong>You will fit here if</strong></p><p>• You have 5+ years building backend systems in Java or Kotlin, with Spring Boot in production.</p><p>• You can defend a schema design — indexes, JPA pitfalls, why you'd reach for a materialised view or not.</p><p>• You have shipped at least one system that handled real load. You know what a thundering herd is and you've fixed one.</p><p>• You think in idempotency keys, retries, and what happens when the third service in the chain dies.</p><p>• You write tests because you've been burned, not because the linter forces you to.</p><p>• You read other people's code without ego and you mentor without lectures.</p><p>• You use AI tooling daily and you can tell the difference between a model that's helping and a model that's hallucinating.</p><p><br/></p><p><strong>Worth bonus points </strong></p><p>• Experience in social casino, real-money gaming, sportsbook, fintech, or any system where money or money-shaped tokens move.</p><p>• Comfortable in event-sourced or CQRS architectures.</p><p>• You've owned an on-call rotation and you have opinions about how to do it humanely.</p><p><br/></p><p><strong>What we will not ask you to do </strong></p><p>• Whiteboard a red-black tree. We hire engineers, not interview athletes.</p><p>• Maintain a personal velocity dashboard. Ship the work; the dashboard shows itself.</p><p>• Sit in five status meetings a week. We have one weekly sync and async the rest.</p><p><br/></p><p><strong>What you get</strong></p><p>• We pay the band — not the bottom of it.</p><p>• Hybrid: 3 days in office where there is one, the rest remote.</p><p>• Top-tier laptop, your choice of OS and IDE. AI tooling subscriptions covered.</p><p>• Real ownership of a real product, not a slice of a slice of a service in someone else's roadmap.</p><p>• A growth path — Senior IC, Tech Lead, or Architect. We hire seniors who want to choose, not be slotted.</p><p><br/></p><p><strong> Interview process </strong></p><p>• 45-min chat with our tech lead — past architecture stories, the war wounds, the wins.</p><p>• 30-min culture conversation with the COO.</p><p>Total elapsed time: 2–3 weeks. We give a decision within 48 hours of the last stage. No ghosting.</p><p><br/></p><p><strong>Apply</strong></p><p>Send a CV or a GitHub link — both is great, neither is fine if you can point to something you've shipped — to jobs@ouslygames.com.</p><p><br/></p><p>If you want to talk first instead of apply first, that works too. Roger Zippel on LinkedIn. Ously is an equal-opportunity employer. We hire on the strength of the work and the way you think about it.</p> </div>