European Online Gaming Team — Frontend Work and Internal Tooling
Frontend work within an international Scrum team, covering legacy improvement, internal developer tooling, and team process contributions such as retrospectives and development-to-QA alignment.
Period: May 2024 – Jun 2025
Overview
Frontend work in an async international team, spanning internal developer tooling, legacy code refactoring, and workflow coordination between development and QA. The value of the work was not only in implementation, but also in making delivery and handoff more reliable inside a distributed team.
Context
This work took place in a 20-person international Scrum team across Europe and Asia. The team was dealing with legacy application code, an updated internal UI framework, and internal developer workflows that still involved friction. In practice, this meant working across implementation, internal tooling, and team process clarity rather than focusing on just one layer.
Challenge
The challenge was to support product and internal delivery work in a way that reduced friction for engineers and made async collaboration more reliable.
- Refactor legacy code to align with an updated internal UI framework
- Reduce manual effort through internal tooling
- Clarify dev-to-QA handoff expectations where testing criteria were inconsistent
- Keep collaboration workable across a distributed async team
Contribution
Legacy Improvement
- Refactored legacy TypeScript game code to work more cleanly with the updated internal UI framework
- Improved maintainability and clarity in parts of the codebase through structured refactoring work
Internal Developer Tooling
- Contributed to internal tools built with Vue.js and Electron
- Focused on reducing manual effort around bulk deployment workflows for engineers
Handoff & Workflow Clarification
- Helped address an unclear “dev testing” expectation that meant developers were checking different things before QA
- Proposed aligning expectations explicitly and led a discussion that resulted in a shared checklist
- This made async dev-to-QA handoffs smoother and more reliable
Cross-Functional Collaboration
- Worked across design, QA, product, and backend conversations to clarify user flows and UI expectations
- Supported team reflection and workflow improvement through retrospective facilitation
What This Case Shows
- Experience working across internal tooling, legacy improvement, and workflow coordination in a distributed product team
- Ability to support not only implementation, but also the conditions that make async delivery smoother
- Comfort working in cross-functional environments where UI work depends on shared expectations and handoff clarity
Notes
- This case is most relevant as background for internal tooling, frontend partnering, and workflow-aware support inside distributed teams
- Its value lies less in a single visible feature and more in improving reliability, maintainability, and handoff across the team