I spent six years writing solid code before anyone outside my team knew my name. That was a mistake. Not because I needed fame, but because opportunities stopped finding me. The engineers who got tapped for the interesting projects, the conference invites, the leadership roles — they had something beyond a clean commit history. They had a brand.
Branding sounds like marketing fluff. It's not. It's just the answer to the question: what do people think of when they hear your name? If the answer is nothing, you've got work to do.
Start with one thing you actually care about. Not what's trending. Not what you think sounds impressive. I picked observability because I'd spent two years debugging distributed systems at 2 AM and I had opinions. Strong ones. I wrote a short post about tracing failures across microservices. It was rough. I published it anyway. Three people read it. One of them was my mom. But the fourth post caught the attention of a team lead at another company who needed exactly that perspective.
Consistency beats quality early on. I committed to one post every two weeks for a year. Some were good. Some were terrible. The terrible ones taught me more than the good ones because I actually revised them instead of just feeling proud and moving on. You learn by shipping, not by polishing.
Speaking at meetups helped more than writing. I know that's uncomfortable. I threw up before my first talk. Literally. But standing in front of thirty people and explaining how we reduced our incident response time from forty minutes to six — that stuck in people's minds in a way a blog post never could. People remember faces and voices, not URLs.
The mistake I see engineers make is trying to be known for everything. You can't be the Kubernetes person and the frontend person and the AI person. Pick a lane. Go deep. You can always expand later. I spent eighteen months being the observability guy. Then I became the observability-and-reliability guy. Then the reliability-and-engineering-culture guy. Each expansion was natural, not forced.
Your brand also lives in how you show up on your own team. I started writing better design docs. Not longer — clearer. I started asking questions in code reviews that made people think instead of just pointing out style issues. That reputation inside your company is half the battle. The other half is making sure people outside your company can find evidence of it.
One thing I'd do differently: I'd start earlier. I waited until I felt ready. You're never ready. The engineers I admire most started sharing their work when they were still figuring things out. That vulnerability is part of the brand. Nobody trusts someone who claims to have all the answers.
So pick the thing you know best. Write about it. Talk about it. Do it badly at first. The brand builds itself after that.