I spent my first five years as a software engineer treating personal branding like a dirty word. I told myself the code would speak for itself. It didn't. My code was buried in a private repo, my documentation lived in a wiki nobody outside my team could read, and my conference talks were zero because I never applied. Meanwhile, a colleague with half my technical depth was getting invited to speak at meetups and interview for roles I wanted. The difference wasn't skill. It was visibility.
That realization stung. I remember sitting in a performance review where my manager said, "You're one of our strongest engineers, but nobody outside this team knows it." He wasn't wrong. I'd spent years optimizing for being right in code review while ignoring the fact that career growth in tech is largely a social exercise. Not in a slimy networking way. In a "make it easy for people to understand what you care about and what you're good at" way.
So I started small. I didn't launch a YouTube channel or start a newsletter. I wrote one blog post about a gnarly bug we'd hit with database connection pooling. It took me three hours. I almost didn't publish it because I felt like the topic was too obvious. That post got shared by a senior engineer at another company and led to two job interviews I never applied for. That's when the lightbulb went off.
The biggest mistake I made early on was waiting until I had something "impressive" to share. I thought a personal brand meant being an expert. It doesn't. It means being a person who documents their learning in public. Every time I tried to write about a topic I knew deeply, I'd freeze up because I was afraid of being wrong. When I wrote about something I'd just learned, it flowed. The vulnerability was the whole point. People don't follow you because you have all the answers. They follow you because you're clearly working through the same problems they are.
Over time, I developed a simple rhythm. I write a short post every couple of weeks about something I fixed, something that confused me, or a tool I actually use. No hot takes. No engagement bait. Just honest notes from the trenches. I also started answering questions in a few niche forums where I already lurked. That felt less like "building a brand" and more like helping people, which is exactly why it worked.
If I could go back and give my younger self one piece of advice, it would be this: your personal brand already exists. It's the impression people form when they see your name in a commit, read your code review comments, or hear you speak in a meeting. The question isn't whether to build a brand. It's whether you're being intentional about the one you're already creating.