Senior / Strong Middle Backend Developer

Senior / Strong Middle Backend Developer
We are expanding our engineering team and looking for a Senior / Strong Middle Backend Developer with substantial hands-on experience in iGaming.
iGaming experience is a mandatory requirement.
The domain itself is more complex than the development work: bonus wagering, payment cascading, jurisdictional restrictions, anti-fraud, and compliance requirements are all part of the day-to-day reality. You are expected to understand these concepts before starting work on the relevant tasks. We are not looking for someone who needs to learn the iGaming domain from scratch.
The product is already live and actively evolving. You will own a specific area of the product end-to-end and be responsible for its outcome, rather than simply working through a stream of small, isolated tasks.
Tech Stack
Core — daily work
Node.js 20+
TypeScript with strict typing
PostgreSQL as the primary data store — schema design, migrations, and query optimization
Drizzle ORM, with direct SQL where using an ORM would be excessive
Redis for caching and inter-service event communication (Pub/Sub)
Microservice architecture — 20+ services, with a shared data model and common utilities extracted into versioned libraries
Express
REST APIs
WebSockets for real-time communication
Infrastructure — confident working knowledge required
Docker
Kubernetes
Helm
GitLab CI — build and deployment triggered by merges
HashiCorp Vault — service- and environment-specific secret management
Nginx / Ingress controllers
Nice to have
React, Vite, Tailwind CSS
ClickHouse and analytical data marts
Monitoring and alerting built around the event bus
Requirements
4+ years of commercial backend development experience, including at least 2 years in iGaming — casino, sportsbook, poker, or lottery products
Experience working on production systems, not educational or demo projects
Strong proficiency in Node.js and TypeScript
Deep knowledge of PostgreSQL, including:database schema design
running migrations on live production databases
query optimization on large data volumes

Hands-on experience designing and operating microservices and inter-service event communication, including:message queues or event buses
idempotency
delivery-order guarantees
handling message loss and failures

Practical experience with Docker
Kubernetes knowledge sufficient for independent troubleshooting, including working with logs, pods, deployments, and configuration
Strong expertise in at least one major iGaming domain, such as:bonuses and wagering
payments and PSP integrations
game content aggregator integrations
KYC/AML
responsible gambling tools
affiliate programs and CPA models

Ability to independently break down complex tasks: take a high-level requirement, identify missing information, clarify what is needed, and return a structured implementation plan with an effort estimate
Nice to Have
Experience with white-label and multi-brand platforms, including:brand resolution
data isolation
brand-level configuration

Experience integrating external providers:game content aggregators
payment gateways and PSPs
KYC providers
SMS and email services

Experience working in a licensed iGaming environment and participating in audits
Experience handling high-volume financial operations, including transactions, locking, reconciliation, and consistency guarantees
How We Work
All tasks are managed through a project tracker and picked up from there — not from chat messages or ad-hoc conversations.
Our workflow is:
Specification & estimate → Development → Code review → Testing → Release
Code review is mandatory, but it is designed not to become a bottleneck. Reviewers may batch reviews and review multiple changes together. Once a merge request has been submitted, the developer moves on to the next task rather than waiting for the review to be completed.
The team already includes dedicated QA engineers, designers, and a DevOps engineer, so the backend developer can focus on backend development and ownership of their area.
Estimates are agreed and recorded upfront. After completion, we compare the actual effort against the original estimate to improve future planning.
About the Project
The product has evolved rapidly, and as a result, there is technical debt — as is common with systems that have grown faster than they have been systematically refactored.
The technical debt is identified, documented, and being addressed according to an established plan. We believe it is important to be transparent about this from the beginning.
If your priority is joining a project with a completely clean and fully polished codebase, this project may not be the right fit.
If you are interested in working with a live, actively evolving system and having a real impact on its architecture and technical direction, we would be happy to talk.