As Product Manager, I worked across Galactix from pre-launch through launch and continuous development, spanning casino gameplay, engagement, rewards, integrations, and Back Office.
I worked across the casino and Galactix Originals experience, including mobile gameplay, registration, and Quest onboarding. Engagement work spanned progression through Galaxies, Worlds and Missions, alongside rewards, events, items, VIP and broader retention mechanics.
Bonuses and Free Spins needed player-facing rules and configuration; referrals, payments, and affiliates brought integration work. My scope also included the Rewards Activity Hub, game settings, responsible gambling, and Back Office navigation and improvements.
I refined roadmap and backlog priorities, worked with design on flows and responsive behavior, wrote requirements, user stories, and acceptance criteria, and used competitor and user/support input. Cross-functional delivery also involved defects, integrations, release readiness, validation, and SDLC improvements.
The mixed-product board shows Back Office, integration, game, bonus, registration, and defect work across delivery states. It does not establish authorship of every visible item.
Casino play, games, progression, bonuses, and rewards needed defined behavior across desktop and mobile.
Bonus conditions, Quest content, and payment-related work needed Back Office requirements aligned with player-facing behavior.
The roadmap evolved through integrations, defects, release needs, and continuous product improvements from pre-launch onward.
Games and platform actions did not by themselves create a progression journey. Galaxies, Worlds, and Missions frame Quests as objectives with visible progress, unlocking, and rewards.
ContributionShaped Quest, Mission, and World progression requirements
A Free Spins offer needs more than a reward amount. No-deposit and deposit-required paths, wagering, validity, limits, and activation define what a player can claim and use.
ContributionWorked through bonus requirements and configuration
Player-facing systems need administration rules behind them. The Quest specification defines content and reward controls, deactivation, and deletion safeguards within wider Back Office work.
ContributionSpecified and refined Back Office requirements
