In Critical Strike project, I was responsible for end-to-end product development and live service operations. My contributions covered a wide range of areas including:

• Live Operations Design: Seasonal systems, limited-time events, and engagement pipelines were designed and run on a calendar that balanced novelty with operational feasibility. Event goals, reward ladders, and return incentives (streaks, login bonuses, comeback gifts) were defined; difficulty and pacing were tuned per segment to protect retention while avoiding reward inflation.

  
  

• Game Design: Core systems and balance frameworks were maintained through telemetry- and playtest-driven iteration. Weapon and equipment parameters (damage, fire rate, recoil, accuracy bloom, projectile speed) were tuned to target stable Time To Kill bands across ranges and modes. Progression curves and feedback systems (XP, level-ups, unlock timing) were adjusted to improve early stickiness without compressing long-term goals. Matchmaking (ELO) settings were refined to reduce mismatch outliers.

  
  

• Game Economy Design (Monetization): Progression, reward loops, and sinks were defined and continuously rebalanced. Currencies (soft/hard), earn/spend flows (matches, quests, events, pass), and reward cadence (daily streaks, seasonal milestones) were aligned to limit inflation. Chest/drop tables incorporated pity thresholds and duplicate-to-resource conversion to preserve value over time. Economic health was monitored via source/sink dashboards and cohort spend/earn deltas. Monetization structures were expanded and localized: starter and first-purchase bundles, No-Ads options, seasonal/segment-aware offers, and pass upsell points. Value communication was standardized (content breakdowns, “best value” badges), and chest info screens were updated to disclose drop rates transparently. Offer impression frequency and placement followed user-level segmentation (progress, spend propensity, churn risk) with guardrails to avoid early paywall pressure.

  
  

• A/B Testing: Hypothesis-driven experiments were run across pricing, feature releases, and UX flows. Success metrics (retention, conversion, ARPPU/LTV) were predefined; variants shipped via feature flags and staged rollouts. Analyses focused on statistical significance and practical lift, with documented learnings feeding design standards and future test backlogs.

  
  

• Data Analysis: Telemetry and cohort analyses guided roadmap decisions and live ops adjustments. Cohorts, funnels, and segments were used to track retention, engagement depth, conversion, and churn signals. Mode/region/device breakdowns surfaced imbalance and performance hotspots; event schemas were maintained to ensure reliable measurement of key product and monetization flows.

  
  

• Game UX Research and Design: Competitive and heuristic reviews informed information architecture; user flows and wireframes/prototypes were produced and validated. Scope included onboarding/FTUE, controls, main menu, inventory/arsenal, missions/quests, store/offers, profile, settings, and post-match. Usability tests, targeted surveys, and live playtests were used to refine discoverability, reduce friction to first match, and improve inventory readability via card templates (rarity/level/stat hierarchy).

  
  

• Localization: Feature strings and store assets were localized and validated across 13+ languages. Processes covered glossary management, context notes for strings, right-to-left checks (where applicable), layout resilience, and post-release linguistic QA. New-language onboarding workflows were defined to reduce time-to-ship for additional locales.

  
  

• QA Testing: Test plans and acceptance criteria were maintained; smoke/regression passes were executed across target device/OS matrices. Performance (FPS, memory, crash rate), networking/matchmaking behavior, and event-schema integrity (e.g., equip, upgrade, chest_open, pass_claim, purchase) were verified. Bug triage followed severity/repro guidelines; pre-release checklists and staged rollouts (with rapid rollback paths) reduced launch risk.

  
  

• Project Planning & Team Management: Roadmaps were owned from concept to release; sprint and release planning synchronized design, engineering, art, data, and marketing. PRDs and UX specs defined scope, acceptance criteria, and success metrics. Post-release reviews tied outcomes to hypotheses and informed subsequent iterations.

This role demonstrates my ability to scale and operate a high-performing F2P live mobile game through data-informed product thinking, hands-on design work, and coordinated team leadership.