Where it started
My curiosity for technology started long before I knew what product design was. I was always taking apart computers, experimenting with software, and trying to understand how things worked. I built my first website when I was 15, and I immediately fell in love with turning an idea into something someone could actually use.
I attended Clark Montessori High School through Cincinnati Public Schools and joined the University of Cincinnati's Early IT program as a freshman. By graduation, I had completed more than 72 college credit hours and an internship rotation toward my Bachelor of Science in Information Technology.
How I work
My technical and design background shapes how I approach problems. I enjoy understanding how products work behind the scenes just as much as I enjoy designing what someone sees on the screen. Being able to speak the language of designers, developers, researchers, and product managers has made collaboration one of my favorite parts of the job.
The best ideas rarely come from sitting in front of a Figma file. They come from talking to people, asking better questions, observing behavior, and understanding what life is actually like for the people you're designing for.
What keeps me interested
I love getting into the messy parts of product design, where problems are still being defined and every conversation uncovers something new. I'm not attached to my first idea. If something I made is not meeting someone's needs, I want to know.
Accessibility has become a huge part of that. To me, it is not about compliance or checking a box at the end of a project. It is about making sure people are not left behind. Designing for edge cases almost always creates a better experience for everyone.
Where I am now
Today, I work across product design, UX research, accessibility, and design engineering while pursuing dual Bachelor of Science degrees at the University of Cincinnati, along with my MSIT. I use tools like Claude, Claude Code, and ChatGPT to synthesize research, organize documentation, analyze codebases, and make more room for the human parts of the work.
At the end of the day, I do not design because I love interfaces. I design because I love solving problems for people. If I can make something clearer, easier, or more accessible for someone else, then I've done my job.
