Why do I call myself a product engineer?

In high school I was doing graphic design. Not as a career plan just because I had Photoshop and I liked making things. It felt cool to create things out of thin air like logos and flyers and posters for people around me. At some point my friend asked me if I could make him a website and I said yes without knowing a single thing about websites.

I designed the whole thing in Photoshop! Then I sliced it into PNG images and put them inside an HTML file. That was the website. It looked exactly right on my screen and whether it worked anywhere else is a different question but I shipped it and someone paid me and that felt like something real had happened.

Around that same time I was deep into the Counter Strike 1.6 community. I wanted to manage servers but I was too young so I lied about my age to get into the staff of a local gaming community. They gave me the credentials and I spent whole days just hanging out in their FTP servers. I was modifying config files and testing AMX plugins and trying to fix server lag. If something broke players would flame me immediately. It was my first time seeing what happens when real people use something you manage.

Then I actually learned to program. Started with Pascal and HTML and CSS and JavaScript. I remember the exact feeling when it clicked in a Vue js course. It was not like studying for an exam. It felt like someone had quietly handed me a superpower and walked away! You could describe what you wanted and the machine would do it. Not a drawing of a thing but the actual thing running that other people could open and use. I was in high school and I had access to such power. That felt insane to me.

I kept going because I kept hitting walls. I understood the frontend but not what was behind it so I learned backend. Then I didn’t understand how any of it got onto a server so I went back to the FTP stuff I learned from CS 1.6 and figured out deployment then infrastructure. Not because someone told me to. Because every part I didn’t understand felt like a ceiling I wasn’t supposed to touch and I have always had a problem with ceilings.

At my first real job I was doing all of it. Writing the frontend and reviewing the API design and configuring the machines then opening the browser to make sure the button still looked right. I was doing support and sitting in client calls and pushing back in standups and writing specs that didn’t exist yet. Nobody asked me to do all of that. It just felt wrong to stop at the edge of what I was officially responsible for.

That is when I started understanding what the title actually means. It is not about knowing frontend and also knowing backend. Plenty of people do that. It is about caring what happens after you ship. It is about sitting with the outcome instead of handing it to someone else the moment the PR is merged.

A product engineer is someone who asks why are we building this before asking how. Someone who watches what happens in production and feels responsible for it. Someone who does not wait for a ticket when the client says the app feels slow. They open the profiler.

I did not set out to become that. I was just a kid who made a fake website out of PNG images and messed around with game servers because I wanted to figure things out. Everything after that was following the same instinct: close the gap between what you can imagine and what you can actually ship.

The title product engineer is just what you call it when you never really stopped doing that.