About
My background is in software engineering, but my attention has moved closer to the product questions around the interface: what people need, where the friction is, and how a system should behave.
My interest in technology began with a simple question: “how does this work?” As a kid, I was fascinated by how things functioned beneath the surface, spending ages staring at old electronics and wanting to take them apart just to understand them better. That urge to explore how systems work never really left, and it shaped the way I looked at the world from an early age.
The same mindset eventually led me to programming. What first drew me in was the realisation that software was not only something to use, but something I could understand and create myself. It gave me a way to solve problems directly, build things that had not existed before, and turn ideas into something practical and real. Over time, that curiosity grew into an interest in how people actually used the things I built, and what they experienced while using them: what felt intuitive, what caused friction, and why some interactions felt natural while others did not.
That curiosity is what now pulls me toward UX engineering and product design. I enjoy understanding how people think through a task, exploring the decisions they make along the way, and designing experiences that make those journeys feel clear and purposeful. I am interested in why users like what they like, why some layouts feel obvious while others create friction, and how small design choices can change the way someone understands a product.
My engineering background still matters because it helps me think about how ideas and designs translate into real products. I enjoy working where user experience, product thinking, and engineering meet: taking something complex, understanding it, and turning it into an experience that is useful, thoughtful, and grounded in real-world constraints. The most satisfying part is seeing that work come to life in a product that people can actually interact with.
I studied Computer Science at the University of Greenwich, graduating with a 2:1. The degree gave me a base in software engineering, human-computer interaction, data structures and algorithms, and natural computing.
In practice, that means I can reason about React, TypeScript, API-aware interfaces, validation, testing, data shape, responsiveness, accessibility basics, and maintainable code while making design decisions.
I use specs, checklists, and review loops to slow the work down at the right moments: before building, before shipping, and whenever an edge case changes the shape of the problem.