I spent the first decade of my career actively avoiding anything that felt like self-promotion. I was convinced that writing blog posts or speaking at meetups was for people who couldn’t code, that my work would speak for itself. That mindset cost me a promotion I genuinely deserved. The feedback was a wake-up call: the hiring panel didn’t know what I’d actually done because I never talked about it outside my immediate team. My manager knew, sure, but the director who made the final decision had only seen my name on a few Jira tickets.
That stung, but it forced me to rethink what a personal brand actually means for an engineer. It isn’t about becoming a thought leader or building a follower count. It’s about making your skills and impact visible to people who might hire you, collaborate with you, or learn from you. In our field, so much work is invisible. A well-designed system doesn’t make noise. A bug that never happens doesn’t get a thank-you note. If you don’t create artifacts that demonstrate your thinking, you’re relying entirely on others to notice and advocate for you.
I started small. I began writing internal design docs not just for the architecture review, but with enough narrative that someone outside the project could understand why we made the choices we did. Then I turned some of those into a public blog post, stripping out proprietary details. The first one was a post-mortem of a database migration that went sideways at 2 AM. I was terrified to publish it because it exposed a mistake. But that post got shared internally more than any perfect success story I’d ever written. People relate to failure.
Over time, I realized that consistency matters more than polish. You don’t need a perfect website or a viral thread. You need a habit of capturing what you learn and sharing it in a way that feels honest, not performative. For me, that’s a short newsletter every two weeks where I link to something I built or a problem I solved. I skip the motivational quotes and just tell the story. Some issues have no readers. That’s fine. The act of writing clarifies my own thinking, and the archive becomes a reference I can point to during reviews or job interviews.
The hardest part was getting comfortable with the fact that some people will roll their eyes. A former colleague once told me my posts were “try-hard.” It bothered me for a week. Then I remembered that the same colleague had been stuck in the same role for five years while expressing frustration about not being promoted. Your brand isn’t for everyone. It’s for the one hiring manager who sees your post and thinks, “This person thinks like us.”
I’m not saying every engineer needs a Twitter presence or a YouTube channel. But you do need some way to demonstrate expertise beyond your resume. Write internal docs that teach. Answer questions in a public forum. Give a lunch-and-learn. The format doesn’t matter. What matters is that when someone Googles your name or pulls up your profile, they see evidence of a thinking, learning professional, not just a list of technologies. I wish someone had told me that ten years ago.