The Challenge of Explaining What I Do
On starting in design, finding my way into software engineering, and trying to fit it all into one job title.
Introduction
I’ve spent a surprising amount of time thinking about what to call myself professionally.
Frontend Engineer? Software Engineer? Design Engineer? Maybe Product Engineer?
Depending on what I’m working on, any of those could make sense. But listing all of them on my portfolio would look a little chaotic, wouldn’t it?
The funny thing is, I’ve never had much trouble figuring out what I enjoy doing. It’s explaining it in a few words that’s been the challenge.
How I got here
I started out in design.
For about a year, I was freelancing, designing interfaces, learning Webflow, and building websites. I enjoyed the visual side of things, but I was also interested in what happened beyond the designs themselves.
Then I joined AXA Mansard through its Technology Academy, a three-month training programme that eventually led me into the Application Development team.
And that’s how I found myself working in software engineering.
But moving into development didn’t mean I wanted to leave design behind.
I still enjoyed thinking about layouts, typography, interactions, and how people experience the things we build. At the same time, I was getting more involved in the engineering side, figuring out how applications work, how different systems fit together, and how to turn ideas into something functional.
I wanted to keep developing both.
Somewhere between design and engineering
One of the things I enjoy most is being involved in the entire process of creating something.
Having an idea, figuring out what it could look like, thinking through how someone would use it, and then actually building it.
There’s a particular satisfaction in seeing something move from an idea in your head to a working product on a screen.
That’s part of what I enjoy about working on projects like JobTrackr and DOJANG. They give me room to think about the design and the experience while also getting involved in the engineering needed to make everything work.
And I don’t want to limit myself to just the visual or frontend side of development. I’m equally interested in becoming a better software engineer overall, including understanding and working on the backend.
I enjoy the creative freedom that comes with being able to move between these areas.
Of course, that doesn’t make choosing a professional title any easier.
So, Design Engineer it is. For now.
I’ve settled on Design Engineer for my portfolio.
Not because it perfectly describes everything I do, but because it comes closest to the kind of work I enjoy and the direction I want to grow in.
I like being close to both the design and implementation of a product. I want to keep improving at creating good experiences while also getting better at the engineering behind them.
And realistically, a portfolio headline doesn’t need to explain every skill, interest, or project I’ve ever worked on. That’s what the rest of the portfolio is for.
Maybe the title will change again as my career evolves. Maybe it won’t.
For now, Design Engineer feels right.