Joined a newly launched betting platform and became responsible for much of its frontend architecture and continued development. Built live-data handling and caching for a single-page application, using Shadow DOM-based component isolation. Implemented server-side localization with caching, later extending the system to support customer-specific content and feature toggles without redeployment.
Took ownership of UI improvements and user-flow analysis, set up Google Tag Manager and used Google Analytics to identify user drop-off points and improve the experience. As the platform grew, led a redesign focused on usability, scalability, and maintainability as more games were added.
When the platform's outdated Polymer version became a risk, he took responsibility for upgrading the application to the final supported version. With approximately 600 files requiring changes and the official migration tooling unable to handle everything, developed additional migration scripts and manually resolved edge cases. After two weeks of intensive migration and build-system work, successfully deployed the upgraded platform to production.
During a major football tournament, helped deliver a new betting game under an extremely compressed deadline. Worked with another developer to break the scope into essential and post-release functionality, prioritizing the critical path and coordinating development under significant time pressure. Despite an estimated three months of work being compressed into roughly one month, the game was successfully released several days ahead of schedule.