Investment banking
This is where the questions begin: decisions under constraints, dense information, and assumptions that must stay clear.
Start with the decision.
I work in investment banking, where technical questions are part of the job.
Software became how I investigate those questions, test the assumptions behind them, and build better answers.
From investment banking to public software work
Technical pressure
Recurring friction showed me that a process is hard to improve when it is hard to inspect.
Make the problem legible.
Software development
Software became the method: make assumptions visible, test ideas, and build a better answer.
Build a working answer.
Public work
I share the methods, trade-offs, and questions behind the work for technical and financial readers.
Share what stays useful.
Questions in. Working answers out.
What I’m building now.
Finance gives me the context: decisions under constraints, dense information, and the need to make assumptions clear. Recurring technical challenges kept exposing the same problem—when a process is hard to inspect, it is hard to improve.
What began as a way to examine a problem became a way to build a better answer. Code lets me test ideas and turn complex financial information into tools people can use.
Outside work, I follow fintech products and market changes, read about how people interact with money, and keep building projects of my own.
Savyy is the clearest example: a personal-finance product that brings scattered financial information into one inspectable view. It reflects the standard I care about most—complex systems should explain themselves.
Explore SavyyBring me a question worth testing.
This site is where I share that work and write about the questions behind it. If you are working on a financial product, a technical problem, or something between the two, get in touch.