OTTPlay was where I operated at consumer mobile scale.

OTT aggregation makes mobile engineering unusually practical.

Users do not care which provider, protocol, player, or edge case caused playback to fail. They only feel that the app did not work. My work focused on making that messy backend of integrations, player behavior, device differences, and product pressure feel stable on the phone.

I owned the mobile engineering loop across architecture decisions, code review, sprint planning, stakeholder communication, delivery, debugging, and release confidence.

The biggest win was reducing video playback failure from 11% to 1.5%.

• Systematically diagnosed streaming edge cases across multiple OTT aggregator integrations, improving playback reliability and retention-sensitive product metrics.
• Optimized native iOS and Android players for different streaming protocols, including HLS and MPEG-DASH paths.
• Built custom native video controls for both platforms, replacing web-based controls to improve responsiveness and playback performance.
• Resolved excessive React Native re-rendering issues, improving UI performance across a wide Android device range from low-end phones to flagship devices.
• Improved mobile observability around video playback, crashes, ANRs, performance, and release investigation.

This role is the strongest signal of my senior engineering base.

I led a team of five engineers, reviewed code, mentored junior developers, protected performance standards, and translated product needs into mobile architecture and delivery plans. It was not only feature work; it was operating a high-scale consumer mobile product with reliability, stakeholder pressure, and day-to-day team execution.

As a final Wrocus deliverable, I also built and deployed AI-SDR for agency operations: a LinkedIn and WhatsApp outreach workflow with multi-agent orchestration, Claude-powered conversation support, human-reviewed sends, and BANT-style lead qualification.