The work anniversary LinkedIn post: what to write, and when to skip it entirely

Most work anniversary LinkedIn posts are filler, and the honest advice is either to make yours a real reflection or to skip it. LinkedIn already notifies your network when you hit an anniversary, so a written post is a second, optional thing that has to earn its place. It earns it only when it names something that changed in you, ideally something that cost you something. If you cannot name that thing in one sentence, publish nothing and write a different post that week.

Should you post about your work anniversary at all?

Start from the default of no, then argue yourself into it. That is the opposite of how most people approach this, and it is why the genre has the reputation it has.

The reason is simple. Everyone in your network already knows roughly how long you have been at your job, because it is on your profile. A post that reports the elapsed time tells them something they could already see. The only content a post can add is the part the profile cannot hold: what the time did to you.

The cost of getting this wrong is not a one-post cost. Every post teaches your audience what to expect from you, and a date plus a thank-you list trains them to scroll. One is a small tax. The problem is that it is usually part of a pattern of small taxes.

So the test is not “is this post good?” It is “would I publish this sentence if there were no anniversary?” If yes, the anniversary is a convenient date to attach it to, which is a fine reason to post. If no, the entire content is a number.

What is the difference between the LinkedIn anniversary notification and a post you write?

This is the mechanic almost nobody explains properly, and it changes what your post is for.

LinkedIn's own help documentation on sharing profile updates with your network confirms that three kinds of profile event can notify your network: job changes, education changes, and work anniversaries. Those notifications can appear as a post in your network's feed, an in-app notification, or an email. The timing differs by type. Job updates may take up to two hours to reach your network and education updates up to 24 hours, while work anniversary notifications go out within that month.

That has a practical consequence. Your network is prompted to congratulate you on a schedule LinkedIn controls, not on the exact day you care about. The wave of “congrats on 3 years!” is a response to the platform, not to you, and most of the people leaving it have not seen anything you wrote.

The failure mode follows directly. Most anniversary posts duplicate the notification: they restate the fact it already delivered, in more words, and ask for the same single click. The post loses that competition, because the notification is shorter and arrives with a button attached. Treat the notification as the announcement and your post as the commentary. Announcements are handled. You are writing the part nobody else can generate.

What separates a real reflection from filler?

A test you can apply in ten seconds. Read your draft and ask: could a stranger who has never met me have written this about their own job? If yes, it is filler. Gratitude for a supportive team, excitement about what is ahead, pride in how far things have come: every one of those is portable to any person at any company in any year, and portable sentences carry no information.

The non-portable version has one of three things in it.

• A belief you dropped. Something you were confident about a year ago and are not confident about now. This is the strongest version because it is unfalsifiable by anyone but you, which makes it credible, and it is uncomfortable to write, which makes it rare.
• A cost you paid. The thing the year took from you. Time on a project that went nowhere, a relationship you handled badly, a skill that atrophied while you built a different one. Cost is what separates reflection from a status update.
• A specific you can name.Not “we shipped a lot,” but the one decision you would make differently, with enough detail that a reader in your field recognises the situation.

All three are about change, and none are about duration. Duration is what the notification handles. Change is what a post is for, which is the same principle behind how to tell a story in a LinkedIn post.

One more test, for the gratitude section. If you thank people, name what each one did. “Thanks to my incredible team” is written to be safe. “Priya spent a Saturday rewriting the onboarding doc I had been avoiding for six weeks” is written to be true, and it gives Priya something worth resharing.

What do 1,389 career growth posts say about the format?

The anniversary post sits inside the career growth topic in our dataset. The numbers below are a within-topic split: the best career growth posts against the weakest career growth posts, not career growth against everything else.

The topic covers 1,389 posts from 50 authors. Its own top decile is 138 posts from 19 authors, median 354 reactions and 111 comments. Its own bottom half is 695 posts from 33 authors, median 78 reactions and 6 comments. The comment gap is the one to watch: 111 against 6.

The strongest career growth posts put the reader into the text at nearly twice the rate of the weakest ones (64.5% against 34.4%). Hashtag stuffing runs the other way. Shared links over-index badly in the bottom half, which matters because the standard anniversary post often ends with a link to the company careers page.

The second-person figure is the awkward one here, because an anniversary post is structurally about you. Worth naming rather than pretending away: this is the least reader-facing thing you can publish, and the topic data says reader-facing wins. The fix is not a faked second-person hook. It is picking the reflection that generalises, so the reader recognises their own situation in your specific one.

One number from the wider cohort is worth adding here as reassurance. Across 12,988 posts, median hook length in the top decile is 206 characters against 205 in the bottom half. Length does not separate winners from losers. Your anniversary post does not need to be long, and the three-line version below is not a compromise.

What happened when one executive posted the same anniversary post four years running?

This is the most unusual piece of evidence in our dataset for this genre. The same person, the CEO of TransUnion Africa, published a work anniversary post in four consecutive years. The posts are almost interchangeable. So are the results. One note on the follower figure below: our source records an author's follower count once, at collection time, so the same 24,460 is attached to all four posts. It is the denominator we scored them against, not a measurement of the audience on the day each went out.

The honest reading cuts both ways, so take both halves.

First half: these worked. All four cleared 5.95 per 1,000 followers, the top-decile threshold across our cohort of 12,988 posts. Not marginally: between six and eight times it. Anyone telling you anniversary posts flop is wrong. A recognisable executive with an established audience can publish the most formulaic post on LinkedIn and land in the top decile.

Second half: nothing grew. Four years of near-identical wording produced four near-identical numbers. Year 1 was 35.85 per 1,000, year 4 was 41.5. Reactions moved from 669 to 755 and comments from 52 to 65 over four years, which is drift rather than growth. We cannot tell you whether the audience grew, because the follower figure is a single snapshot. What we can see is that four repetitions of the same post produced four versions of the same result: no compounding in the response, no argument advanced. The posts are a floor, a reliable and entirely repeatable result from a fixed prompt.

A floor is worth having. But a floor is not a lever. If your goal for the quarter is to be known for something, these four posts are what not-moving looks like when it performs well. That distinction, between posts that produce a number and posts that produce a position, is the reason to be selective about which anniversaries you mark. More on allocating those slots in building a LinkedIn content calendar.

Why do anniversary posts get applause instead of replies?

Look at the ratio. Across those four posts, reactions run roughly ten to one against comments: 669 to 52, 785 to 72, 811 to 73, 755 to 65. The top-decile median across our whole cohort is 235 reactions to 72 comments, closer to three to one. Anniversary posts skew toward applause by a factor of about three compared to what strong posts normally produce.

That is not a flaw in the writing. It is what the post asks for. A congratulation is a complete response to a milestone, and there is nothing further to say. Compare it to a career change post from our dataset that gave readers something to respond to.

Same genre family, entirely different response shape. The second post contains something unresolved. Readers who have closed a company, or lost someone, or made the same promise to themselves in 2016 have a reason to type. Nobody has a reason to type under “celebrating four years.” The wider pattern is in our study of 12,988 ranked posts.

What should you write for year 1 versus year 5 versus year 10?

Nobody segments this, and it is the most useful distinction in the genre. Each anniversary year corresponds to a different question your reader is quietly holding. Answer that question and the post has content. Ignore it and you are back to reporting elapsed time.

That is not numerology. Year 1 closes a loop your audience opened when they saw your new job announcement. Year 3 is roughly when a role stops being new and starts producing transferable knowledge. Year 5 is when a specialism becomes legible from outside. Year 10 is rare enough to be interesting by itself.

A note on the adjacent genres, since people conflate all three. A promotion is a change in what you do, and the post should explain the new remit, which is covered in how to announce a promotion. A new job is a change in where you do it. An anniversary is neither: nothing changed, which is exactly why it is the hardest of the three to write and the easiest to skip.

What are the templates worth using?

The three skeletons below are ours, written for this article. They are not from the dataset and no engagement numbers attach to them. Treat them as shapes, not scripts.

The three-line reflection

Line one states the fact and gets out of the way. Line two is the whole post. Line three gives the reader somewhere to go.

1. The fact, in under ten words.“Three years at [company] this week.” No adjectives, no celebration language.
2. The thing that changed, with a cost attached.“I came in convinced that [belief]. I spent [specific amount of time] proving myself wrong, and the version that worked was [the thing you actually do now].”
3. The open question.Ask the thing you still have not resolved. Not “what do you think?” but the actual open problem, phrased so a peer who has hit it can answer.

That is a complete post at roughly 60 words, and most of something that short sits above the fold anyway. Getting the opening right matters more than getting it long, which is the argument in what the first line of a LinkedIn post has to do.

The one-liner, for people who want to acknowledge it and move on

“[N] years at [company] today. Still the best decision I made in [year], and the clearest reason is [one specific].” That is it. One sentence, one specific, no gratitude block, no tagged colleagues, no hashtags. It reads as confident precisely because it does not ask for much.

The rewrite pair

Both of these are invented. The point is the size of the edit, which is smaller than people expect.

Default version:“Today marks 3 amazing years at Northlake. I am so grateful for the incredible team around me and everything we have built together. Excited for what is ahead. Thank you to everyone who has been part of this.”

With a real specific in it:“Three years at Northlake today. I joined convinced that our churn problem was a pricing problem. It took me most of year two, and one very patient customer success lead, to accept it was an onboarding problem. We rebuilt the first two weeks of the customer experience and churn fell by a third. I still think I was too slow to listen. What made you change your mind about something you were sure of?”

Same event, same length range, same tone. The second one contains a claim that could be wrong, an admission that costs something, and a question a peer can answer from their own experience. That last element is what produces replies rather than applause, and the fuller treatment is in how to end a LinkedIn post.

What do you write when you are not happy at the job?

Nobody addresses this, and it is the situation a lot of people are actually in when the notification fires.

Do the reputational maths first. A warm post you do not mean has three audiences. Colleagues, who know the reality and read it as performance. Your network, who believe it. And your future self, six months into a job search, explaining why you published “best team I have ever worked with” in March and left in September. That last one is the expensive audience. Enthusiasm you do not feel creates a record that constrains your next move and makes the eventual career change post harder to write honestly.

Four options, roughly in order of how often they are right.

• Post nothing. The correct answer most of the time. Silence on an anniversary is invisible. Nobody audits who did and did not publish. The notification goes out either way and you can thank people in the comments without endorsing anything.
• Post something quiet and factual.“Two years at [company] today. Thanks to the people who made the hard parts easier.” True, warm to the individuals who deserve it, and it commits you to nothing about the company. This is the honest middle option and it is underused.
• Post about the work, not the workplace. If the job is bad but the problem is interesting, write about the problem. The anniversary becomes the occasion, and the content is technical or strategic. Nothing you write will need retracting.
• Post the honest difficulty.Rarely right, and only when you have already decided to stay and you can write about the hard part without naming a villain. “This was the hardest of my three years here and I nearly left in April” is a real post if the next paragraph explains what changed. It is a landmine if it is a complaint with a company name attached.

What not to do: the passive-aggressive version, where the post is technically positive but the omissions do the talking. Colleagues decode it instantly, and everyone else just reads a strangely thin post. If you would need to explain the subtext, you have written a private message in public.

Should you tag your employer, and what about hashtags?

Tag the company page once, if you want the page to have the option of resharing. That is the entire upside and it is a real one. Tag individual colleagues only where you have named something specific they did. The failure pattern is the wall of tags: fifteen names at the bottom, most of whom appear nowhere in the text. It reads as a distribution tactic because it is one, and it dilutes the two or three tags that would have meant something.

On hashtags, the within-topic career growth split points the same direction as everything else we have measured. Four or more hashtags show up in 34.1% of that topic's top decile (138 posts, 19 authors) against 46.5% of its bottom half (695 posts, 33 authors). Two tags at most, and only ones you would actually follow.

Shared article or link posts make up 15.9% of that topic's top decile against 34.7% of its bottom half. The anniversary post that ends with a link to the careers page is putting itself in the over-represented weak category for no obvious return. If you want to point at open roles, put the link in the first comment.

When should you skip it, and what should you write instead that week?

Skip when any of these are true. This is the plain version.

• You cannot name one thing that changed in you over the period.
• The honest reflection would be negative and you are not ready to publish that.
• It is year 2 or year 4 and you already posted a year 1 or year 3 reflection.
• You posted something in the last week that you would rather people saw.
• The draft would be indistinguishable from your last anniversary post.

Skipping costs nothing, but leaving the slot empty is a waste. The anniversary is a prompt, and the prompt is useful even when the post is not. Three things to write instead, using the same material without the format problem.

• The lesson without the date. Take the one real insight you would have buried in paragraph three and make it the whole post. No anniversary framing at all. It will outperform the anniversary version because it leads with content instead of an occasion.
• The thing you got wrong. Anniversaries surface these naturally, since you are already reviewing the period. Publish the mistake and the correction. This is the post most people will not write, which is exactly why it lands.
• The credit post. Instead of thanking everyone vaguely, write one post about one person and what they specifically taught you. It is warmer than a tag wall, it is genuinely useful to them, and it does not require an anniversary to justify it.

The anniversary slot is one of the easier ones to trade away. What you should protect is frequency, and how much you need is in how often to post on LinkedIn. More examples of what this topic looks like when it is working sit on the career growth examples page.

How do you reply to the congratulations you get?

Separate the reply problem from the post problem, because the replies are where the actual relationship value sits and almost nobody works them.

Remember what those congratulations are. LinkedIn prompted them within the month of your anniversary date, and most people clicked a suggested response without reading anything. That sounds dismissive, but it is an opportunity: a prompted, low-effort message from someone you have not spoken to in two years is still an open door.

Reply individually and specifically. Not “thanks!” but one sentence that could only be written to that person. “Thanks Dan. Still using the pricing framework you sketched on a napkin in 2023.” Twenty of those is worth more than any anniversary post will return. It stops scaling somewhere around thirty replies, at which point pick the fifteen people you actually want to talk to. A generic thank-you post addressed to everyone looks efficient and returns nothing.

How do you write yours in five minutes, or decide not to?

A sequence you can run when the notification fires. It ends in a decision either way, which is the point.

1. Minute one.Write one sentence completing: “A year ago I thought [X], and now I think [Y].” If you cannot fill both halves, stop here and do not post. You are done in sixty seconds.
2. Minute two. Add the cost. What did learning that take from you? Time, money, a relationship, an assumption you liked. One clause is enough.
3. Minute three. Write the opening line. State the anniversary in under ten words, then go straight into the sentence from minute one. Do not warm up.
4. Minute four. Write the closing question. Make it the thing you have not resolved, phrased so someone who has hit the same wall can answer from experience.
5. Minute five. Delete. Remove every portable sentence, every adjective doing emotional work, the hashtag block, and any tag of a person you did not name in the text. Check the first 140 characters and read them as a stranger would.

Two checks before publishing. Would you send this to a peer in a direct message? And could you have published this exact post last year with the number changed? If yes, you have written the notification again.

What this data cannot tell you

Everything above is correlational. The anniversary posts that cleared the top decile did so alongside factors we cannot separate, including the author already being a recognisable executive with a warm audience. Nothing proves the wording caused the result, and the four-post case study is one author: an illustration, not a sample.

Three more limits. The cohort skews toward established creators: everyone in it has at least 1,000 followers, across 65 accounts, so treat the raw counts as directional if you are starting from a small network. Engagement numbers are lifetime totals captured at one moment and the posts are different ages. And the source text is truncated at LinkedIn's “see more” fold, so every text pattern here describes the visible hook rather than the full body. For this genre that matters less than usual, since the visible hook is where these posts live or die.