GSDR publishes and operates a portfolio of ACGN, otome, and narrative-driven mobile games across Southeast Asia. Our portfolio includes live titles at different lifecycle stages — post-launch honeymoon, mature LiveOps, and pre-launch preparation — each with distinct player audiences and monetization dynamics.

The role in one line

You are the owner of LiveOps strategies and executions. You leverage the product strategy into running LiveOps calendars — event design, content sequencing, monetization pacing, community moments — and hold the working relationships with Marketing, Customer Support, Developers, and any other teams that keep the title running.

What you'll own
1. Light and Night LiveOps — deep ownership

• Own the game LiveOps calendar end to end: character/content events, monetization pushes, community moments, retention interventions, competitive responses.
• Own the "next 4–8 weeks" view at any given moment. Keep it current, defensible, and aligned with product strategy.
• Bring proposals, not blank slates. When a gap opens in the calendar, come with two or three options and a recommendation.
• Anchor decisions in data: past event performance, cohort behavior, competitor movements, IP release cadence upstream from the developer.

2. Portfolio-level market intelligence and audience knowledge

• Build and maintain the knowledge base for the audiences the team serves across its portfolio: who they are, what they play, what they spend on, how they behave, where they gather, what they respond to.
• Maintain a portfolio-wide view of who plays what and why — the audience profile for each title, the overlaps between them, the segments that are underserved, the emerging player behaviors worth watching.
• Feed insights back to the team regularly. When Marketing plans a campaign, when Customer Support asks for users experience, when Dev asks about regional adaptation — you are the person with the audience answer.

3. Cross-functional orchestration — the four nodes

• Marketing. Align event content with the marketing team. Feed Marketing the event narrative early enough that creative production can catch up. Flag when a LiveOps beat needs Marketing amplification and when it should stay in-game only.
• Customer Support. Brief CS ahead of every content drop on your anchor title, and support CS-facing communication for the broader portfolio. When issues escalate from CS, you're the first triage layer.
• Developers. Own the working relationship with your anchor title's upstream developer on LiveOps content requests. Escalate regional needs (adapted events, payment flow tweaks, market-specific pricing). Translate "we need X for this region" into a form the developer can act on. Manage version drift, approval loops, and upstream ticketing workflows.
• Game Publishing Platform. Coordinate with the platform team on store optimization, payment integration issues, webshop deployment, campaign go-live gates across the portfolio.

What we're looking for

Must-have

• 3–4 years of LiveOps, product operations, or content operations experience on a live mobile game. At least one of those years on an ACGN or narrative-driven title (otome, anime IP, HoYoverse-style gacha, or narrative-heavy female-oriented game).
• Demonstrated ownership of a LiveOps calendar — you've run events end to end, not just executed pieces of them. You can walk through the last major event you owned, what you decided, what you delegated, and what you'd do differently, within 90 seconds.
• Understanding of parasocial IP economics. You can articulate why a character-driven event operates differently from a generic seasonal event, and why emotional scarcity outperforms economic scarcity for narrative audiences.
• Portfolio thinking, not single-product thinking. You can hold deep context on one title while maintaining useful working knowledge of others, and you can spot which patterns transfer and which don't.
• Cross-functional operator, not a project manager. You can hold four working relationships (Marketing, CS, Dev, Platform) at once, know what each needs from you, and never let a handoff drop. You bring proposals to meetings, not status updates.
• Vietnamese (native) and English (fluent).
• Data-anchored decision-making. When you recommend an event, you can name the past event data, cohort behavior, or competitive benchmark that supports it. "I think it'll do well" is not an answer.