The work anniversary post is the easiest LinkedIn post to write badly. LinkedIn prompts you, you type “one year at Acme, what a journey”, and it disappears into the feed. The posts that get read say something specific that only someone who did the job could say.
LinkedIn shows about two lines before “see more”, so the first sentence is the entire pitch for the rest. Below are 22 originals, grouped by tone.
Year one
The first anniversary is the one where you can still remember being new, which is the most interesting thing you have.
- “One year at Halloway. The thing I was most worried about in week one was the technical stack. It turned out to be the least of it. The hard part was learning who actually makes decisions here.”
- “A year ago today I did not know what a chargeback was. I now spend about a fifth of my week on them. Here is what I’d tell someone joining a payments team.”
- “Twelve months in. I’ve shipped four things. Two of them nobody uses. I’d like to talk about those two, because the retrospectives were more useful than the launches.”
- “One year in this job. I still get the org chart wrong. I’ve stopped apologising for it and started just asking.”
- “First anniversary. The biggest change is that I now say ‘I don’t know’ in meetings without rehearsing it first.”
Longer stretches
Five and ten years let you talk about how the job or the industry changed, which is more useful than nostalgia.
- “Five years at Renwick. When I started, our biggest competitor did not exist. That’s the whole story of this industry in one sentence.”
- “Ten years at the same company, which apparently is unusual now. The honest reason is that the job changed four times and I never had to leave to get a new one.”
- “Seven years here. I’ve had five managers. Three were good and I learned something specific from each. I’ve written those three things down.”
- “Three years today. The thing I underestimated: how much of a senior role is repeating the same explanation until it sticks.”
- “Eight years in the same building, three different jobs, one very long argument about naming conventions that I eventually lost.”
Honest and unpolished
These get read because they are not celebrating. Restraint is unusual enough on LinkedIn to be a hook.
- “Two years today. It’s been a mixed one. The team is better than it was, the product is not, and I’m not sure yet which of those I’m more responsible for.”
- “Four years at this company. I nearly left twice. Both times someone had a specific conversation with me rather than a generic retention one, and that’s why I’m still here.”
- “One year. I’ll be honest, I don’t feel like celebrating. Two people I hired left this quarter and I’m still working out what I got wrong.”
- “Six years, and I’ve noticed I’ve stopped learning. That is not a complaint about the company, it’s a note to myself.”
Crediting the team
The generous version. Specific credit reads as real, a list of tags reads as an obligation.
- “Three years at Marrick. The reason I’m still here is Dana, who spent her first month covering for my second month, and never mentioned it again until I found out.”
- “Five years today. I want to name the night shift ops team, who are the reason none of my releases have ever taken the site down for more than four minutes.”
- “One year. The most useful thing anyone did for me here was Femi’s habit of writing down what was decided in every meeting. I’ve copied it and it has saved me hours.”
- “Two years. The team has doubled and the thing I’m proudest of is that the onboarding doc is now written by the last three people who joined, not by me.”
Short
Sometimes the best version is four lines with nothing to skip.
- “Two years today. Still here, still enjoying it, still cannot pronounce the name of our German subsidiary.”
- “Nine years. I’ve now been here longer than I was at university, which is a strange thing to notice on a Tuesday.”
- “Five years at Corran. No lessons, no takeaways. Just a good job with people I like.”
- “One year. Ask me again at three and I’ll have something to say.”
What to avoid
The canonical bad opener is “I’m thrilled to announce”. Its work anniversary siblings are “what a journey”, “time flies”, and “I can’t believe it’s been X years already”. These are the default phrases LinkedIn’s own prompt nudges you toward, which is exactly why they read as automatic. Because only two lines show before the fold, a stock opener means half your visible post says nothing.
| Habit | Why it hurts | Do this instead |
|---|---|---|
| “What a journey” / “time flies” | The most predictable line on the platform | Open with the specific thing that changed |
| Listing every promotion and project | Reads as a CV, not a post | Pick one moment and go deep |
| Generic gratitude to “the whole team” | Credits nobody | Name one or two people and what they did |
| Thanking the company as if it can read | Companies do not have feelings | Thank people |
| Posting only because LinkedIn prompted you | It shows | Skip it if you have nothing to say |
| Using it to hint you are open to offers | Confuses two different posts | Write the job hunting post separately |
Skipping a work anniversary entirely is a perfectly reasonable choice. A post with nothing in it costs you more attention than not posting.
A structure that works
- Line one: the number of years plus one specific fact. Not a feeling.
- Line two: the honest or surprising part.
- Body: two to five short paragraphs. What changed, what you got wrong, what you would tell someone starting.
- Close: name a person, or ask a real question, or stop.
Check the fold before you post with the LinkedIn character counter. If you have the anniversary but not the angle, the AI LinkedIn post generator will produce a draft you can cut into something that sounds like you.
The short version
Lead with a specific fact, not a feeling. Say one thing that only someone who did this job for this long would know. Name people rather than the company. Avoid “what a journey”. If you have nothing specific, do not post.
Scheduling recurring posts
Anniversaries are the one social post you can genuinely plan a year ahead, because the date never moves. If you run a company page and want to mark team anniversaries reliably rather than remembering on the day, BulkPublish supports repeat posts and a content calendar so a fixed date post is set up once. The wording still has to be written by a person who was there.