What to Comment on a New Job Post (Beyond "Congrats")

Under a new job post, write something only you could have written about this particular move: what the person built in their last role, the problem waiting for them in the new one, or a question about the first few months that they will enjoy answering. Two or three sentences is plenty. A bare “Congrats!” is polite and invisible, because by lunchtime there are ninety of them and LinkedIn often offers it as a one-tap reply.

This matters more if you sell to the person who just moved. A new job LinkedIn comment is often the first thing a prospect ever sees from you, and it arrives in the one week when they read every notification they get.

Why this post deserves a real sentence

People starting a role are unusually attentive. They are meeting a new team, reading everything, and noticing who shows up. The announcement is often one of their most-seen posts of the year, and they scroll the whole thread.

Most of that thread is identical. Former colleagues, recruiters and vendors write the same three words. A comment with an actual observation in it stands out without trying hard.

Announcements come in two kinds, and they need different handling.

  • The automatic one. When someone edits their profile with sharing switched on, LinkedIn can tell their network. Its Help Center says this “may generate a post in your network’s feed, an in-app notification, or an email notification”. The post is one line: “I’m happy to share that I’m starting a new position as…”. It gives you nothing to respond to, so the substance has to come from their profile and their previous work.
  • The written one. Three paragraphs on why they left, what they are walking into and who they want to thank. It hands you lines to choose from. Pick one, the way you would on any post. The basic method is in how to comment on LinkedIn posts.

The pull to pitch, and why to wait

New leaders review what they inherited, and that often includes tools, suppliers and agencies. Every seller knows this. So the new VP’s inbox fills with “congrats on the role, quick question” messages within days, all from strangers, all the same shape.

A pitch in the comments is worse than one in the inbox, because the new boss and the new team can read it. It also asks for a buying decision from someone who has not yet found the coffee machine. This week your comment has one job: to make yours the name they remember as thoughtful when everyone else was selling. The conversation comes later, and the signs that a lead is ready for a message have little to do with a start date.

Fourteen comments for seven kinds of move

Each pair below sits under an invented but typical announcement. Notice that none of them needs the word “excited”.

A senior hire walking into a known problem

A new VP of Revenue Operations joins a 300-person freight software company. Her post says job one is “a single forecast that sales, finance and the board all believe”.

“A single forecast everyone believes” is a brave thing to put in writing in week one. In my experience the numbers are the easy part and the definitions are the fight. Whose version of “committed” wins? Good luck with it.

It quotes her own line and shows you know where that work gets hard. The question is one she is already asking herself.

From a three-person RevOps team to running a department is a change of sport as much as a promotion. Curious which habit from the small team you plan to keep.

This one comes from reading her previous role on her profile. It is easy to answer and flattering without being flattery.

A first-time manager promoted from inside

A support lead with six years at a ticketing software company announces she is now Head of Customer Support.

Six years on the queue before running it. You will be the rare support leader who knows exactly what a bad macro costs. Properly earned.

Promotions from inside are about tenure and credibility. Name both.

The hard part of this move, from what I’ve seen, is no longer being the one who fixes the ticket. I hope the team lets you keep a few of the strange ones.

It recognizes a real difficulty of the transition without handing out advice.

A move across industries

A Director of IT leaves a hospital system for a health insurer.

Provider side to payer side. You get to see the same claims data from the other end of the pipe now. I’d read a post on what surprised you after 90 days.

It names what is interesting about this move in particular, and it invites a future post you can come back to.

Anyone who has kept clinical systems up through a go-live will find most outages calm by comparison. The insurer has hired someone who knows what downtime means to a ward at 3am.

Compliments work when they are specific enough to be checked.

A founder who has joined a bigger company

A founder writes a long post. The startup is winding down after four years and he is joining a larger company as Head of Product.

The paragraph about phoning your last four customers yourself says a lot. Plenty of people would have sent an email. The product team you are joining gets someone who has carried the whole thing.

This is a post with mixed feelings in it. The comment respects the hard part instead of treating the news as pure celebration.

Four years of doing the sales calls, the support and the roadmap yourself is an odd and useful education for a product leader. Which of the three do you think you will miss?

A light question gives him a way to talk about the old company fondly.

Your champion has moved

The operations manager who brought you into an account announces a regional role at a different company.

The warehouse relabel was the most organized project I worked on last year, mostly because of your Friday checklists. Your new team is about to meet them. Congratulations.

Public, specific credit that their new colleagues will read. It is about them, not about you, and it does not say “let’s work together again”. They know where you are.

Three sites instead of one. Well deserved. I hope the checklists scale.

When you have a real relationship, short and slightly private is warmer than long.

The first hire in a function

A marketer joins a 12-person seed-stage company as its first marketing hire.

First marketer at 12 people means you are the brand team, the demand team and the person fixing the website at 11pm. Which one are you starting with?

It shows you understand the job as it really is, and the question is fun to answer.

The best part of being first is that nobody can say “we tried that”. Enjoy the blank page while it lasts.

No question, no ask. Some comments should simply be pleasant to receive.

A new executive at a company in transition

A CFO joins a private-equity-backed manufacturer that is merging two plants.

Two plants, two charts of accounts and a sponsor who wants monthly numbers. That is a lot of archaeology before any strategy. Wishing you a clean first close.

With senior people, fluency in their world is the whole comment. Keep it brief and ask for nothing.

Congratulations. A finance leader who ran a plant P&L before running the whole one is rarer than it should be.

One sentence drawn from their career history. Executives get praise all day and very little of it shows that anyone looked.

Comments that do not land

Congrats! 🎉

Fine as manners. As a way to be remembered, it does nothing, because it is indistinguishable from the eighty above it.

Congratulations on the new role! As you settle in, if you’re reviewing your forecasting stack, we help RevOps teams like yours. Happy to share more!

A pitch, in public, in front of the people she met on Monday. She will not reply, and she will remember the company name for the wrong reason.

Huge move! You’re going to crush it! Can’t wait to see what you do next!

All energy, no content. It could sit under any announcement by anyone, which is why it reads as automated. See the comment mistakes that make you look like a bot.

Congrats! First thing I’d do in your seat is audit the tech stack and cut half of it.

Unrequested advice from a stranger to someone senior. Even when the advice is right, the posture is wrong.

Timing, and the post after the announcement

Comment on the first day if you can. The author is watching the thread, and early comments are seen by everyone who arrives afterward. If you missed it, comment anyway. A notification on day four gets read too.

The bigger opportunity is what comes next. People in a new role tend to post again within weeks: a first hire, a first observation, a “30 days in” reflection. Those posts get a fraction of the comments and contain far more to respond to. If the announcement is your only touch, you were one of ninety. If you are also there for the next three posts, you are someone they recognize. That pattern is the subject of how to warm up leads on LinkedIn before you pitch.

Hold the connection request for a few days as well. Sent straight after a comment, with a pitch in the note, it undoes the comment. Sending the request after you have commented covers the wording.

When there are too many profiles to watch

With a list of twenty people you will see every move. With two hundred, announcements slip past, and the follow-up posts slip past more often. Icebreakly is built for that second problem. You add the LinkedIn profiles you care about, it checks them on a daily rotation and drafts a comment on each person’s latest post in a Voice trained on how you write, so on a long list a draft usually arrives within a few days of the post. In Approval mode the draft waits for you, and a job announcement is a good one to edit by hand, since the best comments lean on what you know about the person.

It will not discover job changes across the market for you. It only watches the leads you add, and it does not send messages or connection requests. The steps are on how it works.

What to do this week

Go through your target list and find everyone who has started a role in the last 60 days. For each, read the announcement, then read the job they left. Write one comment that mentions something from either. Then check back in two weeks for their next post, which is where the relationship actually starts.

If you want patterns for other kinds of post, these 60 comment examples cover the rest of the feed. And when you want a draft to rework, paste the announcement into the free comment generator, then add the detail about the person that only you know.

Frequently asked questions

Is it too late to comment on a new job post a week or two after it went up?

No. The author still gets a notification, and a late comment on a quiet thread is more likely to be read than one posted in the first-day rush. You do not need to apologize for the delay. After about a month, skip the announcement and comment on whatever they have posted since, which will usually be about the new role anyway.

Should I comment or send a direct message when a prospect changes jobs?

If you have never spoken to them, comment. A message from a stranger in their first week competes with a wave of vendor messages and asks for a reply they do not owe you. If you already know them well, do both: a public comment that credits their work, and a short private note with something more personal. Keep any business conversation for later.

What should I write when someone announces they were laid off or are leaving without a new role?

Leave out “congratulations” unless they frame it as good news. Say one specific thing about their work that a future employer would want to read, because hiring managers do look at those threads. Offer help only if it is concrete, such as an introduction to a named person or team. Never use that post to mention what you sell.

Should I congratulate a contact who has joined one of my competitors?

Yes, briefly. A short, warm comment costs nothing and is noticed by everyone who knows you compete. Keep it about the person and their work, avoid jokes about the rivalry that could read as sour, and do not mention either company’s product.