Viusasa VOD

Backend & platform work · media product at scale

A VOD product is not only an app shell. It is content, billing, notifications, moderation, analytics, and the services that keep those surfaces honest under real traffic.

Product: Viusasa · media VOD
Roles: Backend engineer → delivery lead
Scale context: High-traffic media · 100k+ DAU ecosystem

The build reality

Media platforms fail quietly when the “product” work outruns the platform work. Screens ship. Services lag. Notifications misfire. Billing edges get fuzzy. Audiences do not care which backlog owned the miss — they just stop coming back.

At Viusasa, I worked on that platform layer: the services and delivery discipline underneath a live VOD experience.

What the work covered

Early on, as a backend engineer, I contributed to services that powered web and mobile surfaces — including areas like notifications, moderation, and engagement — plus modernization and migration work that kept the stack movable instead of frozen.

Later, as Senior Systems & Program Delivery Lead, I carried multi-workstream ownership: sequencing platform work, release predictability, and the coordination required when product pressure and operational truth collide.

That arc matters. I know what this product family feels like from both sides of the wall — hands-on services work, and the program leadership that keeps shipping honest.

Related outcome

In the senior delivery tenure, the same platform pressure produced a reliability recovery program — roughly a 90% reduction in system downtime, driven by release ownership and operational clarity. That story has its own note: Cutting downtime ~90%.

Why it matters for partners

If you need someone who can ship media/platform work and still speak delivery language with executives, this is the proof pattern: product surfaces, services underneath, and ownership that survives launch day.

Details here are high-level by design. Internal systems, proprietary metrics, and confidential outcomes are not published.