The new job announcement LinkedIn post: a skeleton, and the social math behind it

A new job announcement LinkedIn post should put the news in the first clause, say in one sentence what you will actually be doing, thank one named person instead of a category of people, and end with something a reader can do other than click congratulate. That is the whole structure, and it fits in about 80 words. The harder decision is sequencing, because LinkedIn already tells your network you changed jobs the moment you update your profile. Your written post is a second visit to the same audience, and most of them fail because they repeat what the notification already delivered.

What is the difference between LinkedIn's job change notification and the post you write?

This is the part almost every template skips, and it changes what your post is for.

LinkedIn's own documentation on sharing profile updates with your network says that three kinds of profile change can notify your connections: job changes, education changes, and work anniversaries. The notification can appear as a post in your network's feed, as an in-app notification, or as an email. For job changes specifically, LinkedIn says the update may take up to two hours to be shared with your network.

The consequence is easy to miss. Editing one field on your profile generates reach. Your connections get told, in the feed and in their notifications and possibly in their inbox, with a congratulate button sitting next to it, and the wave of congratulations most people get is mostly a response to that prompt rather than to anything they wrote.

So a new job gives you two shots at the same audience, not one. The first is automatic, short, and formatted by LinkedIn. The second is whatever you decide to write. The common failure is spending the second shot on the content of the first: name of company, name of role, expression of excitement. That post is competing with a notification that says the same thing in fewer words and arrives with a button attached. It loses.

Treat the notification as the announcement, which is handled, and treat your post as the thing the notification cannot generate: the reasoning, the problem you now own, the ask. The same split applies to work anniversaries, covered separately in the work anniversary post guide.

The notification is also a setting, not a law. If you would rather your post carry all of it, turn off sharing profile updates before you edit the profile. Anyone doing a quiet move, or backfilling a role they started months ago, usually should.

Should you update your profile first or publish the post first?

Three orders are possible and they produce genuinely different results.

The recommendation is the first row. Let the notification do the announcing, wait a day or two for the congratulations wave to peak, then post the thing the notification could not say. By then your network already knows the fact, which frees your first line from having to be a headline. You can open on the reason, the doubt, or the problem instead, which is a much stronger position. Opener craft is covered in how to start a LinkedIn post.

The second row has one real use. If the bare facts read badly without context (a smaller company, a shorter tenure than anyone expected, a title that looks like a step down), publish your version first. A notification saying you moved from a well-known company to one nobody has heard of invites people to invent a reason.

The same-hour option is what most people default to and it is the weakest. The two-hour delay means you cannot control which lands first anyway.

What do 1,389 career growth posts say about announcement posts?

New job posts sit in the career growth topic in our dataset. The comparison below holds subject matter constant: the best career growth posts against the weakest career growth posts, not career growth against everything else. That distinction matters, because comparing a topic to the whole cohort mostly tells you what the topic is, not what works inside it.

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

The second-person figure is the awkward one for this genre, and worth naming rather than talking around. An announcement is structurally about you, and the strongest posts in the topic put the reader into the text at nearly twice the rate of the weakest ones. The fix is not a bolted-on question at the end. It is choosing which part of the news to describe: the problem you are taking over is often a problem your reader also has, and describing it in their language puts them in the post without pretending the post is about them.

The emoji row is the one to read carefully. 34.1% against 3.3% is a large gap, but adding a rocket is not what produced it. Emoji use tracks formatting effort and posting style generally, so read it as evidence that the weakest posts here are unconsidered, not as an instruction.

The shared-link row is the actionable one. Link posts make up 15.9% of the topic's top decile against 34.7% of its bottom half. Announcements that end with a link to the company careers page or a press release are putting themselves in the over-represented weak category. Put the link in the first comment if you need it at all.

Against the whole cohort of 12,988 posts by 65 creators: first-person openers appear in 19.6% of top-decile posts against 10.1% of the bottom half, and 47.5% of top posts put “you” somewhere in the visible hook against 32.7%. The top-decile median post earns 235 reactions and 72 comments; the bottom-half median earns 80 and 5. Reactions roughly triple. Comments go up more than fourteenfold. Full method is in our study of 12,988 ranked posts.

What does a new job announcement look like when it works?

Here is a real one from our dataset. This is the exact post type, from an executive announcing a move into a senior technical role.

Four things are happening in roughly 200 characters, which is the whole visible budget before the fold.

• The first word is a timestamp.“Yesterday” puts the reader at a specific point in time before the sentence tells them anything else.
• The news is complete in clause one. Company and both titles, before any adjective. Nobody has to read on to learn what happened, so everyone who scrolls past still got the message.
• Gratitude comes second, and it is short. Two sentences, then done. Compare that to the standard version where gratitude is the entire post.
• The hook still has room to start the story.“In many ways, I” is where the fold cuts. Ending the visible text mid-sentence is the cheapest way there is to earn a tap on see more.

Note also what it does not do: no hashtag block, no link, no tagged colleagues in the opening. More on how much the first line carries in what the first line of a LinkedIn post has to do.

Why do new job posts earn applause instead of replies?

Look at the ratio on that post: 3,140 reactions to 162 comments, about 19 to 1. The top-decile median across our whole cohort is 235 reactions to 72 comments, closer to 3 to 1. By reach, this is one of the best posts most people will ever publish. By conversation, it is near the bottom of the distribution.

That is not a writing failure. It is what the post asks for. A congratulation is a complete response to good news: nothing unresolved, nothing to disagree with, nothing a reader knows that you do not. The notification has also primed everyone for exactly one action, and they take it. You get the highest reaction count of your year and almost none of it becomes anything.

Which is fine, if applause is what you wanted. Most people say they want that and then feel oddly flat afterwards, because what they actually wanted was for the new job to produce something: conversations inside the new company, inbound from people who have the problem they now own, old colleagues resurfacing with something concrete. None of those arrive by default. They arrive when the post asks for them.

What do you do if nobody engages with it?

Announcement reach depends heavily on how warm your network is and how recently they have seen you post. If you have been silent for two years, the notification still fires and the post is still quiet, because the feed has no recent evidence that anyone wants to read you. One quiet post proves very little.

Three checks before you conclude anything. Did the profile-update setting fire at all, or had you turned it off in a previous job? Did you publish within an hour of the profile change, so the two competed? And did you post when nobody in your main timezone was awake? Early replies keep a post alive while it is being tested, which is the argument in the golden hour breakdown. Beyond that, do not chase it. The recovery move is the follow-up post, not a repost.

What are you optimising the post for: applause, introductions, inbound, or recruiter visibility?

Four different outcomes, four different posts. Almost nobody picks one deliberately, which is why the default announcement optimises for the least valuable of the four.

The second and third rows are the ones worth choosing, and both require the same edit: replace one sentence of excitement with one sentence of specifics about the work. “I'm joining as Head of Support” asks for a congratulation. “I'm taking over a support queue that has doubled while headcount stayed flat, and the first month is entirely triage” asks for stories from anyone who has done that. One of those two sentences produces replies. The wider question of what makes people type rather than click is in how to end a LinkedIn post.

What is the skeleton for a straightforward move to a bigger company?

Here is a skeleton I wrote for this article. It is not a post from the dataset and no engagement numbers attach to it. Treat it as a shape, not a script.

1. The fact, in under fifteen words.Title and company, no adjective. “As of Monday I'm [title] at [company].”
2. What you actually own. One sentence describing the problem, not the org chart. This decides whether anyone who is not your friend keeps reading.
3. Why this one.One reason, and make it one that could have gone the other way. “Great team, exciting mission” is what everyone says about every job.
4. One named thank-you, with what they did. A single person, a specific act.
5. The ask. Specific enough that a reader knows whether it is aimed at them.

Both versions below are invented for illustration. Same news, same person, same length range.

The default version:“I am beyond excited to share that I have joined Northlake as Director of Product! Huge thanks to the incredible team for believing in me, and to everyone who supported me along the way. I could not be more grateful for this opportunity and cannot wait to see what we build together. Onwards! #newjob #grateful #newbeginnings #product”

The version with content in it:“As of Monday I'm Director of Product at Northlake. I'm taking over onboarding, which is where they lose most of the customers they win. I said yes because they showed me the churn data before they showed me the offer. Thanks to Priya Raman, who told me in February that I was interviewing for the wrong kind of job and turned out to be right. If you have rebuilt a first-run experience for a product with a long sales cycle, I want to know what you would do differently.”

Four edits separate them. The excitement adjectives are gone, which costs nothing because nobody believed them. The job description became a problem description, so a reader with the same problem has a reason to be in the comments. The gratitude got a name and a specific act attached, which makes it credible and gives Priya something worth resharing. And the hashtag block came off, which the topic data supports: four or more hashtags appear in 34.1% of the career growth top decile against 46.5% of its bottom half.

The second version is also longer, and that is fine. Hook length does not separate winners from losers in our cohort: the top-decile median is 206 characters against 205 in the bottom half. What sits in those characters is the whole difference.

How do you announce a move that needs explaining?

A step sideways, a smaller company, a title that reads as a demotion, or leaving somewhere everyone watched you be happy. These are the announcements people agonise over, and the mistake is always the same: writing around the question instead of answering it. If you do not answer it, your reader will, usually less generously than the truth.

Here is a second skeleton I wrote, not a post from the dataset.

1. Say the thing they are wondering, in the first two lines.“Yes, this is a smaller company and a smaller title.” Naming it yourself removes all the awkwardness in one sentence.
2. Give the real tradeoff. Not a euphemism. You gave something up to get something, so name both halves. A tradeoff people can evaluate reads as confidence; a reframe that pretends nothing was given up reads as spin.
3. Say what you are not saying.“I'm not going to write about why I left. It is not mine to tell.” A visible boundary stops speculation better than silence does.
4. Then describe the new work. The explanation is not the post. It is what clears the way for the post.
5. Ask for something. Ending on the explanation leaves the reader holding your discomfort. Ending on an ask hands them something to do.

A short invented example of steps one to three: “I've left a 4,000-person company for a 30-person one, and yes, the title is smaller. I traded a large team for actually building again, which is the part of the job I was worst at delegating and missed most. I won't write about why I left. It was an ordinary ending and the people there deserve better than a subtweet.”

Two adjacent cases have their own treatment. A promotion is a change in what you do at the same place, and the post has a different job to do, covered in how to announce a promotion. A move into a different industry or function needs to argue for the transfer of your skills rather than just report the move, which is the career change post.

Should you tag the company and the people who helped?

Tag the company page once. That is a real upside: a reshare from the page reaches people who do not follow you, and most companies will reshare a new-hire post if you make it easy. One tag, in the text, where the company name naturally appears.

Tag individual people only where you have named what they did. The failure pattern is the wall of tags: twelve names at the bottom, most of whom appear nowhere in the text. It reads as a distribution tactic because it is one, and it makes the two tags that meant something indistinguishable from the ten that did not. If someone referred you privately, ask before you name them. A referral can be a sensitive thing inside a company and you do not always know whose permission it needed.

Worth knowing before you decide how much of the post to spend on the company: corporate good news gets the same response shape as personal news. One executive in our dataset announcing a company award drew 554 reactions and 91 comments from 24,460 followers, roughly six reactions per comment. Acknowledged, not discussed.

Should you include a photo, and how long should the post be?

A photo is fine and largely neutral. Inside the career growth topic, image posts actually appear slightly more often in the topic's bottom half than in its top decile, so an image is not doing the work people assume. What does separate the two halves is native video: 31.9% of the topic's top decile against 9.1% of its bottom half, from 138 and 695 posts respectively.

That does not mean film yourself. It means the badge graphic, the office selfie, and the stock photo of a handshake are all the same thing as far as the data is concerned, which is nothing. If you want a media format that over-indexes, thirty seconds of you saying what you are going to be working on will do more than any image, and it is the single most under-used format in this genre. The general case is in the video posts breakdown.

On length: stop worrying about it. Median hook length in the top decile of our cohort is 206 characters against 205 in the bottom half, and inside the career growth topic the median hook runs 206 characters or about 35 words. Those are medians for the visible portion, not for the whole post, but the point stands. Length is not the variable. An 80-word announcement with a specific in it beats a 300-word one without.

What should you post 90 days into the new job?

This is the post that does the work, and almost nobody writes it. Here is the evidence, from the same author as the announcement above, same account, same follower count.

3,140 reactions for the news that he took the job. 220 for the news that he built the team. Same person, same network, and the post with actual content in it earned roughly one fourteenth of the attention.

There are two honest readings and you need both. The first: attention on LinkedIn is front-loaded onto novelty, and no amount of craft in a follow-up will match the free distribution a job change generates. Do not judge your 90-day post against your announcement. The second: the follow-up is still the more valuable post, because 220 people who read about engineering hiring at Venmo are a more useful 220 than 3,140 people clicking congratulate. The announcement is the cheap post. The follow-up is the one that tells anyone what you are like to work with.

The example above could also be written better, which is instructive. It is still shaped like an announcement (“excited and proud to share”) rather than a report. A stronger version of the same post would name what was hard about the hiring, or what he changed after the first three hires did not work out. That is the version people forward.

Then there is the one-year callback, where you answer the question your announcement opened: did the move work out? One executive in our dataset posted exactly that at the one-year mark and earned 669 reactions and 52 comments from 24,460 followers. That genre has its own rules and its own failure modes, covered in the work anniversary post guide.

How do you write yours in ten minutes?

A sequence you can run the evening before. It ends with a publishing decision, not a draft you sit on.

1. Minute one: pick the goal. Applause, introductions, inbound, or archive. Write it at the top of the draft and delete it before publishing. Everything below depends on that one word.
2. Minute two: write the fact. Title, company, timing. Under fifteen words, no adjectives. You will not touch line one again.
3. Minutes three and four: write the problem. One sentence on what you are taking over, phrased the way you would say it to a peer at another company rather than to your new manager. The post lives on this line.
4. Minute five: write the reason. Why this job and not another. If what you write is also true of ten other jobs, it is not the reason.
5. Minute six: name one person. One thank-you, one specific act, one name. Delete every other name unless you can say what they did.
6. Minute seven: write the ask.Aim it at a describable person. “If you have done X, I want to know Y” beats “thoughts?” every time.
7. Minute eight: delete. Every adjective doing emotional work, the hashtag block, any link, and any sentence a stranger could have written about their own new job.
8. Minute nine: check the fold. Cut the draft at 140 characters. Is the news complete, and is something still unfinished at the cut?
9. Minute ten: decide the sequencing. Update the profile tonight and publish this in two days, unless the move needs explaining, in which case publish first and update the profile tomorrow.

Then do the part that matters more than the post. Reply individually to the congratulations, with one sentence that could only be written to that person. Twenty of those is worth more than the reaction count, and the notification has just handed you a list of everyone in your network who still thinks about you. More examples of this topic working are on the career growth examples page.

What this data cannot tell you

Everything above is correlational. Career growth posts that use video, address the reader, and avoid link-sharing land in that topic's top decile more often, but nothing here proves those choices caused the result. The exemplars are illustrations, not samples: a senior executive at a well-known company announcing a senior role has advantages no wording produces.

Three more limits. The cohort skews toward established creators, since every account in it has at least 1,000 followers and there are 65 of them, so treat the raw counts as directional if your network is small. Engagement numbers are lifetime totals captured at a single moment, and the posts are different ages, so an older post has had longer to accumulate. And the source text is truncated at LinkedIn's see more fold, which means every text pattern here describes the visible hook rather than the full body. For a new job announcement LinkedIn post that limitation matters less than usual, because the visible hook is where the announcement actually happens.