My Story
I grew up teaching myself how to make things. I learned guitar on my own when I was young and spent years playing in a DIY band, which taught me a lot about problem solving and figuring things out with limited tools.
Later on, I went into marketing, then moved into UX and design, and eventually found my way into engineering because I wanted to build the things I was sketching. Before I ever wrote real code, I was the person who took on digital projects at work — building websites for a real-estate company and project-managing an app for a coffee roaster. Those early projects weren't sophisticated, but they made something click. I wanted to understand how everything fit together: the design, the logic, the decisions, the experience.
That curiosity led me to pursue an MBA in Experience Design. It gave me a more structured way of thinking about the work — how people move through an interface, how teams collaborate, and how to shape a product so everyone is building toward the same idea.
Later on, I went into marketing, then moved into UX and design, and eventually found my way into engineering because I wanted to build the things I was sketching. Before I ever wrote real code, I was the person who took on digital projects at work — building websites for a real-estate company and project-managing an app for a coffee roaster. Those early projects weren't sophisticated, but they made something click. I wanted to understand how everything fit together: the design, the logic, the decisions, the experience.
That curiosity led me to pursue an MBA in Experience Design. It gave me a more structured way of thinking about the work — how people move through an interface, how teams collaborate, and how to shape a product so everyone is building toward the same idea.
What I Do
I build front-end systems and interfaces that adapt to context and feel like they've always worked that way.
My work usually sits where design, engineering, and retrieval-based AI meet. It is the part of the project where small decisions make a big difference and where the system needs enough structure for the AI to behave predictably.
I've worked with teams at Capital One, Coca-Cola, PMI, and others on projects where the interface carries part of the experience instead of just displaying content.
My work usually sits where design, engineering, and retrieval-based AI meet. It is the part of the project where small decisions make a big difference and where the system needs enough structure for the AI to behave predictably.
I've worked with teams at Capital One, Coca-Cola, PMI, and others on projects where the interface carries part of the experience instead of just displaying content.
How I Work With AI
AI only works well when the instructions are clear, so I define the rules and structure before I let it do anything.
I map out user journeys, write scope documents, and create diagrams that outline the shape of the project. This helps keep the work aligned and avoids unnecessary guesswork.
From there, I define the tech stack, the architectural patterns, and the rules for how the agents communicate and validate their output. Once the foundation is in place, I use AI for roadmapping, exploration, and breaking down work. I design in Figma, then build in Cursor, often having agents reason through ideas or debug within the constraints I set.
The goal is to build systems that feel consistent and intentional, even when AI is part of the process.
I map out user journeys, write scope documents, and create diagrams that outline the shape of the project. This helps keep the work aligned and avoids unnecessary guesswork.
From there, I define the tech stack, the architectural patterns, and the rules for how the agents communicate and validate their output. Once the foundation is in place, I use AI for roadmapping, exploration, and breaking down work. I design in Figma, then build in Cursor, often having agents reason through ideas or debug within the constraints I set.
The goal is to build systems that feel consistent and intentional, even when AI is part of the process.