Why “consistency” is the worst advice given to senior engineers.

The advice is everywhere. Courses, LinkedIn gurus, content strategists, even well-meaning colleagues: post consistently. Three times a week. Every Monday. Set a cadence and stick to it.

It’s reasonable advice for someone trying to grow a creator business. It’s the wrong mental model for a Principal Engineer who has something genuinely important to say roughly once a month and wants that thing to land.

These are different problems. The consistency playbook solves one of them. And yet it’s handed out to both.

What consistency actually optimizes for

LinkedIn’s algorithm rewards consistent posting the same way it rewards anything that keeps people on the platform. Frequent posters get more impressions per post, more notification exposure, and a larger pool of low-stakes interactions to accumulate.

What the algorithm does not do is measure whether your posts compound. It doesn’t distinguish between “this person writes three good posts a week” and “this person writes three forgettable posts a week to stay visible.” From an impression standpoint, those two things look the same.

From an authority standpoint, they are almost opposites.

Authority on LinkedIn doesn’t come from visibility. It comes from being the person someone remembers six months later when a hard problem comes up. That memory is made by one post that was genuinely useful, not by forty posts that were technically present.

The signal most senior engineers are missing

LinkedIn shows you likes, comments, and impressions. These are the metrics the platform surfaces first because they’re the metrics most users find rewarding. They are also, for senior technical writers, largely the wrong metrics.

The metric that actually predicts professional authority is saves.

A save is a deliberate, private act. No one sees you save a post. You do it because you want to come back to it — because the thing was worth keeping. In the data across senior IC and engineering leader writing, posts with high save rates are almost never the “consistent” posts. They’re the posts with genuine depth: a migration war story, a decision framework for hard architectural tradeoffs, a clear-eyed take on a problem everyone is quietly struggling with.

These posts can generate very low like counts. They often do. The senior engineer who writes them assumes they didn’t land. In reality, they were saved by the people who matter most — the ones who don’t like posts publicly but do remember who wrote something that was actually worth reading.

Why the cadence playbook fails for senior engineers specifically

Content creators run a different business. Their value proposition is presence — being part of someone’s feed, their identity, their daily reading habit. Consistency is core to that model. A creator who disappears for six weeks loses subscribers. Their metric is reach times frequency.

A senior engineer’s authority works differently. The value proposition is expertise, not presence. Someone reads your post on distributed system trade-offs and remembers that you were the person who clearly understood that problem. Six months later, when they’re trying to make that decision, they look you up. They send you a message. They recommend you for a panel.

That conversion doesn’t require that you posted three times a week. It requires that when you posted, you said something genuinely useful that they couldn’t have found anywhere else at that quality.

When senior engineers follow the consistency playbook, they typically produce a mix: one genuinely good post every few weeks, surrounded by filler designed to maintain the cadence. The filler dilutes the signal. The people who followed you because of the good post now see the filler in their feed and start tuning you out.

Consistency, applied incorrectly, is a way of making your best work harder to find.

The model that actually compounds

The alternative isn’t to post randomly whenever inspiration strikes. It’s to maintain a strategic relationship with your posting — to ask, before you write, whether this piece has the potential to become something someone saves.

The question isn’t “should I post this week?” It’s: do I have something worth saying?

A useful diagnostic: if you can imagine writing this post in 30 minutes without accessing any of your actual work or knowledge, it probably isn’t dense enough to build authority. The posts that compound are almost always drawn from real experience — a failure you diagnosed, a decision you were part of, a pattern you recognized after seeing the same problem twenty times.

These are not daily observations. They are rare. And treating them as scarce resources — writing them carefully, letting them stand alone — is how you make them count.

What this looks like in practice

In the data from senior technical writers who have built genuine professional authority on LinkedIn, the pattern is almost never “three posts a week.” It’s more like: eight to fourteen posts a year, of which four or five are genuinely substantive, and those four or five are the ones that move the needle.

The substantive ones share a few characteristics:

• They describe a specific situation, not a general principle. (“We migrated a 40TB Postgres cluster under load. Here’s what we got wrong.” Not “Five things to know about database migrations.”)
• They contain information the reader couldn’t find by googling. The writer’s experience is the primary source.
• They take a position. A strong opinion, clearly stated, is far more memorable than a balanced survey of trade-offs.
• They are complete. Not a teaser, not a thread. One piece that says everything it needs to say.

None of these characteristics require high frequency. They require depth, honesty, and enough time to write well.

The trap of visible activity

One reason senior engineers over-post is that silence feels like absence. If you aren’t posting, you assume people have forgotten you. If you are posting, you feel productive.

This feeling isn’t wrong, exactly — presence does matter — but it conflates visibility with authority. A senior person posting twice a week about general career advice is highly visible and building very little authority in their actual domain. A senior person who posts once a month with a technically dense observation from real work is building it steadily.

The benchmark is not “am I visible?” It’s “when someone looks at my last six months of writing, does it show that I understand something specific and important?”

A better question to ask

Before deciding how often to post, ask a different question: what is the one problem I understand better than most people in my field?

The answer to that question is your authority territory. The posts that compound are the ones that go deep in that territory — not wide, not frequent, but repeatedly and specifically useful to the people who have the same problem.

Post when you have something from that territory. Skip the week when you don’t. Your authority will thank you for the discipline.

If you want to see where your authority territory actually sits — which topics in your existing body of work are already compounding and which are diluting the signal — run a free scan. The first analysis takes about 90 seconds.