Why I Am Building Product-Facing Software Now

For a long time, I worked in environments where technical correctness was the center of gravity. The software had to be right, fast, and operationally reliable. That work sharpened my instincts, but it also made me notice something: I cared just as much about whether the system was useful, teachable, and understandable as I did about whether it was efficient.

That is the real reason I am moving toward product-facing software. I do not want to stop solving hard technical problems. I want to solve them in service of something a person can feel.

The work I want to do now

I am most interested in product engineering work where the technical system and the user experience cannot be separated cleanly.

• onboarding that has to earn trust quickly
• workflows that need to feel simple even when the underlying logic is not
• financial or operational tools where clarity matters as much as correctness
• products that need fast iteration without losing technical discipline

That is why the fintech learning platform matters to me. It is not just an app idea. It is a place to work through questions about simulation, progression, feedback loops, and explanation. Those are product questions, but they only become real when the implementation can support them.

What I want this writing to be

This blog is not meant to become a generic engineering journal. I want it to be a small set of essays about building products with systems rigor: what changed in my thinking, what tradeoffs matter, and what becomes visible when you move closer to the user.

Some posts will be technical. Some will be more product-facing. The common thread is that they should help someone understand how I approach the work.

A better optimization target

The biggest shift for me has been this: technical excellence is still necessary, but it is no longer the final score.

The better question is whether the software helps someone make progress with confidence.

That is a harder bar in some ways. It demands good engineering, but it also demands judgment, restraint, and a willingness to let user understanding shape the build. That is the kind of work I want more of, and that is what this portfolio is moving toward.