Back to projects

Case study / Multi-brand e-gaming platform

March 2023 — June 2024

Platform under NDA.

Multiple brands. One platform.

Role

Fullstack Team Lead

frontend download size
−30%
Vite and client-specific code splitting

Context

I worked on a configurable e-gaming platform serving multiple brands. The company name is covered by an NDA. As Fullstack Team Lead, I combined engineering management, architecture, and hands-on development.

01

The challenge: scale a shared product

The shared platform needed to accommodate different brand themes, features, and configurations. It also needed tenant isolation, real-time operations, and a maintainable shared codebase.

02

My contribution and leadership

I led frontend and backend developers, shaped the backlog, and aligned architecture with the business and partners. I owned hiring, task allocation, documentation, code review, and releases.

Alongside leadership, I worked across the stack: designing the multi-tenant NestJS architecture, GraphQL schema, admin interfaces, and WebSocket/RxJS event flows.

03

Architecture and performance

I designed modular backend components with dependency injection and flexible configuration. I implemented tenant isolation, theming, and feature control. On the frontend, I used Vite, dynamic imports, and client-specific code splitting.

The build and code-splitting changes reduced frontend download size by 30%.

04

Observability and team practices

I introduced tenant-scoped Sentry and Grafana dashboards for SLA visibility. Within the team, I established collaborative code reviews with mentoring, retrospectives, daily meetings, and engineering metrics.

Behind the outcomes

A multi-brand platform connects architecture with product flexibility. My contribution was a shared technical foundation, hands-on engineering, and a team organized around one product.

Project technologies

ReactTypeScriptNestJSGraphQLRxJSWebSocketsViteSentryGrafana
Next caseMarpla

Contact

Let’s talk about your challenge.