Start with the people
Every project starts with one question: what purpose does this serve? Understanding the person behind the problem is how I avoid building the wrong thing well.
I'm a software engineer in Hoboken, New Jersey, focused on the front end. I care about the people on the other side of the screen, and I love turning hard problems into things that feel simple.

I started in marketing, designing campaigns, ad funnels and websites for real estate listings and clients across the US. Then I moved to Japan and spent three years teaching English to more than 620 students, from one-year-olds to adults. In 2022 I came home to New Jersey, taught myself to code, and within a year I was solving real merchant problems at Rebuy Engine.
At Rebuy I grew from Support Engineer to Software Engineer 1 in just over three years, across four roles. I launched more than 200 custom storefronts, helped scale Bundle Builder to $6M a month in merchant revenue, and led the greenfield Selectable Gift with Purchase widget from its admin panel all the way down to the database. Along the way I mentored teammates, helped interview new engineers, and became a go-to person for the widgets and cart that serve more than 8,400 Shopify merchants.
Today I'm building Kanji Kaku, an iOS and Android app for learning to write Japanese kanji. I design the system and direct AI coding agents to build it, backed by more than 240 automated tests. The tools keep changing. My job stays the same: understand the problem, own it, and ship something reliable.
Every project starts with one question: what purpose does this serve? Understanding the person behind the problem is how I avoid building the wrong thing well.
From a support ticket to a brand-new product, I treat the problem as mine until it's solved. Three years of triaging merchant issues taught me to follow a bug all the way to its root.
As AI changed how software gets written, my work shifted toward architecture: shaping the data, the boundaries and the tests, then directing agents to build inside them.
Teaching kindergarten in a second language taught me patience and clarity. I bring the same care to interfaces: every state, every edge case, accessibility, and motion that helps instead of distracts.
“What purpose does this serve?”
How products get sold, and who they're sold to. I still think about the funnel when I build a UI.
How to explain anything to anyone, in a second language, to an audience of 1 to 55-year-olds.
HTML to Next.js on my own, and the first version of this site.
Four roles in three years, from answering tickets to leading a new product.
Everything at once: product, design, architecture and teaching, in one app.
I'm looking for a team that cares about its users as much as its code. Front end, full stack or mobile, I'd love to hear what you're working on.