About / Working style
I work across the product—not around the interface.
I started in visual design and quality engineering, moved through full-stack and mobile delivery, and found my strongest ground owning the product behavior, system boundaries, and interface together.
How I work
Close to the user. Close to the numbers.
I do my best work on products where the interface carries real operational or commercial weight. That can mean activation time in fintech, an evidence trail for field work, or a coaching recommendation someone will act on.
I am comfortable owning a product workflow, shaping requirements with product and design, and moving across the stack when the system requires it. AI-assisted development now accelerates that work; it does not replace review, measurement, or responsibility for the result.
Read the full experience timeline →01 / Range
Depth with useful edges.
Product ownership across web and mobile, current AI product patterns, and deep frontend architecture experience where the interface carries the workflow.
- Product engineering
- Workflow framing, architecture, implementation, release boundaries, validation, measurable outcomes
- Applied AI
- Structured outputs, evaluation fixtures, deterministic validation, human review, cost controls
- Frontend depth
- React, TypeScript, Next.js, React Native, GraphQL, Apollo, complex product interfaces
- Product systems
- Activation funnels, experimentation, analytics, reusable patterns, migrations, delivery risk
02 / Principles
What survives the framework.
The implementation changes. These expectations do not.
- 01
Start with the workflow
Clarify the user, commercial stakes, inputs, decisions, and useful output before choosing architecture.
- 02
Constrain the AI
Give models a bounded responsibility, deterministic evidence, explicit cost controls, and a human acceptance point.
- 03
Make the result inspectable
Expose failure states, tests, decision records, and honest boundaries so another person can verify the claim.