I’m a software engineer drawn to problems that sit between daily behaviour and complex systems.
My products start close to home: difficulty keeping study tools connected, the gap between seeing a bank balance and understanding a pay period, or the overhead of coordinating fitness and nutrition.
That proximity matters. It gives me enough context to question the obvious solution, follow the edge cases, and care about whether the result holds up in ordinary life.
“The goal is not to add software to a problem. It is to remove enough friction that the better action becomes natural.”
I work across product definition, interface design, application engineering, and platform decisions. The common thread is ownership: understanding why the system exists and carrying that intent through its implementation.