Release & Launch Manager — games and live-service platforms
Release readiness is not certainty. It is an accountable decision about which risk to accept, under what conditions, with the right owners and recovery options in place.
I coordinate release readiness across technical and operational teams, turn incomplete signals into controlled decisions, and communicate the accepted risk clearly enough for teams to act.
Based in Indonesia (UTC+7). Currently between roles and available immediately for international remote opportunities or employer-supported relocation.
- Live-service launch readinessOwned readiness across a portfolio of launches in the past year, spanning indie through AAA-scale contexts.
- 7+ years at AccelByteProgressing through technical documentation, technical project management, technical production, and release/launch ownership. Career experience.
- Proactive launch monitoring & incident commandMonitor live-service launches in real time to catch anomalies early and prevent them from becoming customer-visible issues, then step into incident command when a launch or release still calls for it.
- Faster evidence, same validationA report — a launch read, a release summary, or a customer usage view over any window — draws on signals like service usage, latency, error rates, and regional or cohort behavior to decide what needs attention next. Gathering that first pass now takes minutes when access and tooling are ready — validating it against source evidence still takes real time, because catching a wrong conclusion before it's used is what actually protects the outcome.
- Delivery across studios and publishersI have experience owning platform delivery across external studio and publisher customer accounts, from indie to AAA scale.
Case Studies
A curated view of how I own delivery, turn launch data into an accountable read, and respond when a correct process still produces a difficult outcome. The operating approach also reflects lessons earned through real delivery, including mistakes and misjudgments that changed how I handle the next release.
Professional cases are real experience generalized to protect confidentiality. Representative cases are built from recurring real patterns to show a decision pattern. Every case is labelled.
Owning a AAA Live-Service Delivery, End to End
Owning delivery and integration for a AAA live-service launch, including coordinating mitigation and communication during a live issue.
Reading a Report by the Numbers — AI-Assisted, Human-Validated
Using AI assistance to make operating reports — release, launch, or a customer usage read — faster and more repeatable while keeping every conclusion under human validation.
A Release That Went Wrong — and What I Owned
A representative release passes every checklist, then PC players hit a live issue because a service configuration was validated only through the console path.