Problem framing
I work best where the product is still ambiguous — where the user need is not yet fully defined, the data model has tradeoffs, and the interface needs to explain the complexity.
A software engineer for product teams that need systems thinking and shipping discipline.
I work across backend, frontend, cloud, automation, and AI/data workflows, with a bias toward products that stay understandable after the first version ships.
How I work.
System thinking
I translate problems into product flows, API boundaries, interface states, automation paths, and maintainable implementation plans.
Engineering judgment
I care about clear systems, readable interfaces, honest tradeoffs, and the details that make software credible to both users and engineering teams.
Open to roles and collaborations where full-stack product engineering matters.
Best fit: full-stack roles, backend roles, product engineering teams, AI/data-oriented products, workflow automation, and technical collaboration.