Ship, then iterate
Get a working version out early. Refine based on real feedback, not assumptions.
I design and ship mobile systems that hold up at scale - from monetization infrastructure to offline-first sync. Pragmatic, outcome-driven, and obsessed with the details users feel.
Former Mobile App Engineer @ Meta · Instagram
I believe in shipping early and iterating fast. I write code that’s simple to read, easy to change, and focused on real user impact - and I care about owning outcomes end-to-end, not just closing tickets.
Get a working version out early. Refine based on real feedback, not assumptions.
Code should be easy to read, change, and delete. Boring is usually better.
Think beyond the ticket. Focus on what the user actually needs.
Write modular code that adapts. Requirements will change, and that’s okay.
Implemented a cross-surface injection system at Meta that converts unmonetized dwell time into Reels ad impressions using a custom Android session tracker.
Built an impression recovery system at Meta that captures lost revenue for Instagram Reels by auto-scrolling to high-value ads using Kotlin and Android.
Strategies for large-scale refactors that keep production stable, covering parallel runs, feature flags, gradual migrations, and verification techniques.
A retrospective on architectural decisions that seemed right at the time but aged poorly, and what I would choose instead with the benefit of hindsight.
A deep dive into building a reliable sync engine that keeps mobile apps functional without connectivity, covering conflict resolution, queue management, and real-world trade-offs.