Comment like an engineer
You just have to do the thing you’re already great at.
Every piece of LinkedIn advice eventually gives you the same order: post. Post consistently, post bravely, post at 7 a.m. with a hook about how a junior dev taught you a life lesson. And for a lot of brilliant engineers, that single word — post — is exactly where the whole thing dies.
So let me hand you the permission slip nobody else will.
You can build a real presence on LinkedIn in 2026 without ever publishing a post. Not once. No carousels, no “I’m humbled to announce,” no manufactured vulnerability. There’s a side door into all of this — and right now it might be the better one.
The room nobody is standing in
Start with a number that should bother you more than it does.
In 2026, only about 3% of LinkedIn’s roughly 1.3 billion members post more than once a week. Everyone else reads, scrolls, and lurks. The platform has a name for them in its own data — passive observers — and they make up something like 70% of users.
Most people read that and feel a little hopeless: the deck is stacked, the loud people win. Look at it the other way. Almost nobody is actually talking. The room is enormous and nearly empty in the middle. You don’t need to outshout the 3% who post. You need to be one of the few people who says something worth reading — and posting was never the only way to do that.
The 97% stay invisible not because they have nothing to say. They stay invisible because they decided “having something to say” means writing a post. It doesn’t.
What changed under the hood (and why it helps you specifically)
LinkedIn quietly rebuilt its engine. Across late 2025 and into 2026 it replaced a pile of separate ranking models with a single AI system, and shifted from mostly showing you content from people you know to content about topics you care about.
One consequence matters enormously for engineers who hate the spotlight: the algorithm now reads text and matches it to interested readers, whether or not they follow you. A sharp take on a narrow topic can reach thousands of the right people from a 500-connection account, while a generic post can stay trapped in your own network even with 10,000 followers.
And the signal it rewards above all others is conversation. Several 2026 analyses now rank comments as the single strongest organic signal — some estimates put a comment at roughly 15x the weight of a basic like, with more conservative, quality-aware analysis landing closer to 2x. Either way, the gap is huge. Then, in late May and early June 2026, LinkedIn pushed updates that went further: outsized reach for what it calls substantive debate — genuine back-and-forth in the comments.
One June 2026 test made the point brutally clear. Two similar posts from the same account: one collected a dozen quick “great post” replies; the other sparked seven people arguing across 23 comments. The debate post reached 3.2x more people — with fewer total commenters.
Sit with that for a second. The reach didn’t go to the loudest poster. It went to the conversation. And conversations need good commenters far more than they need more posts.
You already do this. It’s called a code review.
Now the part that should feel oddly familiar.
You are, professionally, one of the best commenters alive. You do it every single day. Someone opens a pull request; you read it carefully, catch the edge case they missed, suggest the cleaner approach, ask the question that makes the whole thing better. You don’t agonize over your “personal brand” before leaving a PR comment. You don’t feel like you’re bragging. You just see something worth saying on someone else’s work, and you say it.
That is exactly the skill LinkedIn now rewards most.
A great comment on someone’s post is a great PR review, in public. You’re not broadcasting look at me. You’re reacting to a specific thing with a specific thought — which happens to be the one mode of self-expression engineers are completely comfortable in. The cringe part, the part you actually hate, just evaporates. What’s left is being useful where people can see it. 🙈
The commenting playbook for people who hate posting
Pick your “repos to watch” Follow five to ten people who post about your exact stack or domain — the database people, the platform people, whoever lives in your corner. That’s your watchlist. Treat their posts like incoming pull requests landing in your inbox. You’re not browsing a feed anymore; you’re reviewing.
Comment like you’re reviewing code, not cheering. “Great post! 🙌” is dead — actually worse than dead. LinkedIn’s language models now read your comment text, and a three-word cheer carries zero semantic value; the platform is actively suppressing low-effort and automated comments. Aim for the sweet spot the system reads as depth: roughly 30 to 80 words. Long enough to add one real thing. Here’s the difference in practice. Dead comment: “So true, thanks for sharing!” Engineer comment: “This matches what we saw, but with one caveat — under high write load the cache-aside pattern you mention started returning stale reads for us, and we only caught it after a nasty incident. We ended up adding a short TTL plus write-through for the hot keys. Curious if you hit that too?” Same person. Wildly different outcome. The second one is a code review. It also happens to be the thing the 2026 algorithm bends over backwards to spread.
Be early, then come back. A thoughtful comment in the first hour helps the post catch fire — and you ride along. But 2026 also rewards delayed engagement: a substantive reply 24 to 72 hours later signals to the system that the conversation has lasting value. So drop your comment, then return the next day to answer whoever replied to you. That second visit costs you ninety seconds and feeds the exact back-and-forth being boosted.
Disagree on purpose (kindly). Agreement is forgettable; the reach goes to threads, and threads need a little friction. “100% this 🔥” adds nothing. “I’d push back on point two, because in my experience X breaks down once you’re past a few thousand requests a second” starts a real debate — the kind the algorithm now amplifies hardest. It also signals more competence than any pile of fire emojis ever could. You’re allowed to be the person who respectfully says well, actually. Engineers are world-class at this.
Let your profile do the closing. Every good comment is a tiny advertisement you didn’t have to write. Someone reads something sharp, glances at the name, and clicks. So make sure your headline and the first two lines of your profile make sense to a complete stranger who just met you in a comment section under someone else’s post. The comment opens the door; the profile is the room they walk into.
“But this just makes other people go viral”
The most common objection, and a fair one: why pour your best thinking into someone else’s post and help them win?
Because in 2026, your comment is content. The algorithm reads it semantically and can surface it — and you — to people who care about that topic. That’s the same audience you’d never reach from your own small account. A two-line insight under a post with 50,000 views puts you in front of a crowd you couldn’t buy your way to. The original poster notices. The other commenters notice. The recruiters and engineering leads who quietly follow that topic notice. You borrowed someone else’s stage and said something worth remembering on it. That isn’t charity. It’s leverage — the cheapest leverage on the platform.
And it compounds in a way posting often doesn’t. One small example from my own life. A while back I left a comment on someone’s post about a database migration that had once burned my team — nothing clever, just the specific thing that bit us and how we crawled out of it. Three short paragraphs. I forgot about it within the hour. Two weeks later a hiring manager messaged me. He hadn’t seen a single post of mine. He’d seen that comment, screenshotted it for his team, and wanted to talk. I never wrote one word “about myself.” I just answered a real question in public, the way I’d answer it in a PR.
That’s the quiet trick. The people most worth impressing aren’t only watching who posts. They’re reading the comments to find out who actually knows things.
Start with one
You don’t need a content calendar. You don’t need a brand. You don’t need to announce anything, ever.
This week, find one post in your field where someone is slightly wrong, or slightly incomplete, and you happen to know the missing piece. Leave the comment you’d leave on their pull request — specific, useful, a little brave. Then come back tomorrow and reply to whoever answered.
The stage was never the point. The good comment was. 👉🏻