I'm a senior software engineer with 6+ years of experience building product features at scale in the personal finance space. I've spent most of my career at Quicken, where I've grown from contributor to front-end lead — owning architecture, driving technical decisions, and shipping features that real users depend on every day.

My work sits at the intersection of complex UI and real user impact. Financial software is unforgiving: performance problems are visible, bugs erode trust, and the data is personal. That context shapes how I approach every problem.

I care about understanding the problem before reaching for a solution. Most of the interesting work in software is figuring out what you're actually trying to do, not how to implement it.

Performance is a feature. In a product like Quicken, a 2-second lag on a core interaction isn't a minor complaint — it's a reason to stop using the product. I've seen what fixing it does to user sentiment.

I default to simple and reach for complexity only when the problem requires it. A well-named variable or a clear component boundary often does more than an abstraction.