For the first six years of my career, I treated my GitHub like a secret diary and my LinkedIn like a boring resume I updated once a year. I genuinely believed that if I just wrote clean code and shipped features, the right people would notice. My manager did, sure. But when a startup reached out about a principal engineer role with a salary I actually paused at, the recruiter said something that stung: You don't have much of a public footprint. We couldn't find a single thing you've written or shared.
That was the first time I realized being good at your job and being known for being good at your job are two different skills. I had spent years optimizing queries nobody saw and refactoring modules nobody knew existed. The work was real, but it was invisible outside my team. I'd never posted a write-up, never given a talk, never even answered a Stack Overflow question. I had built a career on word of mouth in a world that increasingly runs on search results.
So I started small, and I mean embarrassingly small. I wrote a LinkedIn post about a Postgres deadlock I spent three days debugging. No hot take, no life lesson, just the actual error log and what fixed it. It got something like forty likes, but a week later a developer from another company messaged me saying that same post saved his team an afternoon. That felt better than any code review I'd ever received.
My mistake early on was thinking a personal brand meant being an influencer. It doesn't. It means letting people see how you think. I started writing a short blog post every month, mostly about things that broke and how I fixed them. I answered a few questions on Reddit and in Discord communities. I didn't chase followers or try to be witty. I just documented my work in public. Within a year, I got two conference talk invitations and a consulting offer from a company I'd never even applied to. The recruiter said they'd found my article on event sourcing and wanted to chat. That never would have happened if I'd kept everything in private repos.
The hardest part isn't writing or recording. It's getting over the feeling that nobody cares. Most of my early posts got a handful of reads. That's fine. The goal isn't virality. It's compounding. Every answer you leave, every pull request you open on a public project, every honest write-up is a small deposit. People don't read your blog at 2 a.m., but when they search for that specific error message, they find you. And one of those people might be your next boss.
I still don't have a newsletter. I don't have a personal logo or a color scheme. I'm not trying to become an engineering celebrity. I'm just no longer hiding the work. The difference is that now, when someone asks what I've been building, I can point them somewhere real. And when a recruiter looks me up, they see a person who thinks in public, not just a name on a resume.
So if you're early in your career and you think personal branding is for other people, I get it. I was you. But ask yourself this: if a perfect job opened up tomorrow and the hiring manager had to choose between you and someone with the same skills but a stack of public documentation, who would they call? The answer isn't about ego. It's about being findable.