Engineering Manager · Android · security, scalability, stability
I make the scary parts of an app boring.
I lead mobile at Marrow: content stays locked, the app stays up, and exam-night crowds land like a normal Tuesday.
What I have solved
Content protection and antipiracy
business criticalLed successive waves of protection for premium medical video, the paid product. The hard part is doing two things at once on real devices: keep content safe from leakage while making sure legitimate paying users never feel the protection. Described by outcome only.
Mobile stability system
99.85% crash-freeOwn app stability across a huge, low-end-heavy device fleet on patchy networks. Reproduce field crashes and ship targeted fixes (video threading, player-screen memory leaks, lifecycle and binding races, OS-specific crashes) to hold 99.85%+ crash-free for years, and hardened cold start so successful launch rate went from 68% to 95%. Lifted iOS from about 98% to over 99% too.
Payments and subscription flows
zero room for bugsWork across the monetization surface: payment gateways, coupons, renewal flows for specialized exam tracks, purchase edge cases, and eligibility checks. The revenue path has no room for error, so this is where I am most careful.
How I ship Every rollout is a bet I verify. BigQuery event trends make the call, halt, scale, or roll back, and each ship gets measured after it lands, not just before.