I’m a product engineer with deep iOS roots. I’ve spent most of my career building consumer apps, but the work that keeps pulling me in reaches a little beyond any one platform.
I like the messy middle where user experience, engineering constraints, and team speed all pull on each other. Sometimes that means iOS architecture or performance work, sometimes subscription systems, telemetry, experiments, test automation, or internal tools.
Most recently, Wolt (DoorDash) in Tokyo: Wolt+ membership across cart, checkout, and signup, from proposal through the experiments after release. The work sat where product decisions become engineering plans, and I got the most out of splitting a big idea into changes we could ship and measure.
Before that, four years at SmartNews shipping iOS features to millions of people: onboarding, the feed, article rendering, and server-driven UI. Before that, five years at Bodybuilding.com, where I took ownership early and learned what 60fps actually feels like under load.
Across all of it, the pattern holds. I end up where product requirements meet engineering constraints: simplifying flows, making systems predictable, and checking what happened after release. When the friction sits in the engineering workflow instead, I build the tool that removes it. Telemetry Viewer came out of that habit, and it explains why testing and automation have always felt like part of the job.
After years of shipping features, I notice more of the systems that make a team good at shipping them: observability, experimentation, telemetry, and developer tooling. AI tools now belong on that list. I care less about “learning AI” as a separate lane than about where these tools change implementation, evaluation, and feedback loops, and where the work still needs checking. I work through that in Sparra.
What I’m good at
Owning consumer features end to end. Reading a funnel and finding the four pixels of friction nobody’s looking at. Breaking large efforts into experiments a team can ship. Evolving iOS codebases without slowing the team down. Debugging the problems that only show up on a real device. Building telemetry, tests, and internal tools that other engineers trust enough to act on.
What I’m learning
How the services and infrastructure behind a product behave. How to evaluate and observe software that changes quickly, AI features included. And how to keep iOS depth as a foundation without letting it become the whole boundary of the work.
Outside the editor
I live in Fujisawa, near the ocean south of Tokyo, in a house designed around airtightness, solar, and a V2H-equipped EV.
Two young daughters. A very patient wife. Cycling year-round, snowboarding in winter, and re-learning to skateboard. Still anticipating the day I finally start surfing.