I’ve always been fascinated by how the 'small things' in daily usage define a product’s success—from the tactile feel of an iPod 20 years ago to the intuitive interface of a modern car. From sending messages to aliens 👽 in the 70s to training modern Large Language Models (LLMs) today, everything is the result of deeply considered design. I started tinkering with tech in school, voiding Nokia 📱 warranties before I even had a driver's license. I was obsessed with overhaulng Symbian UIs just to make them look cool. That eventually spiraled into a full-blown obsession with the Nexus 7, where I spent way too many nights flashing CyanogenMod over KitKat 🍫 and praying I didn't end up with a very expensive paperweight. I chose design because I wanted to understand how user experience shapes and improves a product over time. My journey began with an obsession with Material Design, which taught me that great design isn't just about color; it’s about research-backed systems that scale. I thrive on understanding user perspectives, validating flows, and iterating based on feedback to bring creative clarity to complex systems.

Beyond systems, I am deeply driven by the psychology 🧠 of interaction. I am fascinated by frameworks and systems of Socionics and MBTI to better understand the vast spectrum of human personalities—specifically how common sense varies and why some users think in 'fact-based' logic while others rely on 'intuitive' patterns. I thrive on translating these diverse user perspectives into validated flows, using feedback to bring creative clarity to complex systems.

Working with different teams has taught me that every company has a unique culture, workflow, and set of priorities. I’ve learned how to quickly map out new processes and integrate them into efficient flows. Most importantly, I’ve realized that being a great teammate means being reliable and accountable. I prioritize moving fast with quick validations and constant feedback loops. I’ve also learned never to compromise on communication; I make it a point to seek out and accept feedback early and often to ensure I’m collaborating effectively across different departments.

I believe every company or client has a different way of working. I like to move quickly by first understanding the project goals, performing a quick competitive audit, and analyzing any available data or requirements. Once I have the flows built, I get them in front of users and the team as fast as possible. For me, asking questions and taking feedback early and often is the only way to move from just a ‘beautiful interface’ to a validated, scalable system that actually solves the human problem.

The rapid evolution of AI tools in 2025, from Figma’s automation features to Cursor, has fundamentally changed our workflow by acting as a powerful accelerator for building design systems and rapid prototyping. I believe AI is excellent at handling the 'heavy lifting' of UI components and helping us validate ideas quickly; however, it still hits a wall when it comes to truly complex user flows and unique business logic. In my experience, the most critical design data often exists offline—in the physical way a user interacts with their environment or in specialized workflows that haven't been documented on the internet. Ultimately, while AI can assist in the process and help us visualize solutions, it cannot replace the deep, human-centric research and empathy required to solve original, high-stakes problems that require a real understanding of a user's unique context.

Ultimately, it comes down to taking ownership and being responsible for every design decision—something a tool can't do (as of now 🤐).