Festa Games
Party games played in the browser across several devices at once. Built the client architecture around a live game loop — room state over WebSocket, voice and video over WebRTC, rendering in Pixi.
festa.games ↗Staff Frontend Engineer · Engineering Lead
Nine years building web products, five leading the people who build them. I own frontend architecture end to end — real-time apps, TypeScript at scale, Vue and React — and stay hands-on in the codebase while the team grows around it. Currently leading an 8-team engineering stream at Brainrocket.
Owning the frontend of a product line: architecture, standards, delivery — with room to keep writing code.
WebSocket, WebRTC, canvas games, TV and multi-screen apps. Products where latency is the feature.
Led both a tight 8-team engineering stream and a 30-person cross-functional org across web, backend and mobile.
Party games played in the browser across several devices at once. Built the client architecture around a live game loop — room state over WebSocket, voice and video over WebRTC, rendering in Pixi.
festa.games ↗One product, two very different clients: a browser app and a smart-TV app driven from phones in the room. Shared a typed domain layer between them and kept the socket session authoritative on the TV screen.
partystation.tv ↗Mobile LCP, after partnering with Product to split desktop and mobile asset pipelines.
QA returns (and −30% reported defects), once code review, style and architecture standards became mandatory.
Implementation time on small tasks / major features, after introducing Claude Code into the workflow.
Migrated Vue 2 Options API → Vue 3 Composition API in three months, plus a shared Storybook component library.
Feature time-to-market, after adding Figma design reviews at the UX and UI stages.
Engineering onboarding time, via a structured plan, access checklist and day-one provisioning.
Open to on-site, hybrid or remote across the EU — and happy to travel for the right team.
Happy to walk through the Festa Games architecture, the Vue 3 migration, or how the AI-assisted workflow actually landed with the team.