Most recruiters post on LinkedIn when they remember to, which means they post inconsistently, repeat themselves, and wonder why their profile isn't winning them more business or attracting better candidates. The fix isn't posting more. It's posting with intention across a small number of content types that each do a different job for you.
A good recruiter's LinkedIn presence does four things in rotation: it sparks conversation, it proves expertise, it builds trust through personality, and it shows results. Lean too hard on any one of these and your feed starts to feel one-dimensional. Rotate across all four and you become the recruiter people look forward to hearing from, which is the only real way to win on this platform.
Every idea below is specific enough to write this week. They're framed for Tech recruitment because that's where the richest, most debatable content lives, but the structure works whatever your niche. Pick two or three ideas from different pillars, draft them in one sitting, and schedule them out. You'll have a month of content sorted before lunch.
Pillar 1: conversation starters
- Ask your network whether they think a computer science degree still matters for a software engineering role, and share your own honest take in the comments rather than the post itself.
- Post a simple poll asking candidates to pick the one thing that would make them leave a stable tech job right now, with four realistic options like better pay, remote flexibility, more interesting work, or a stronger team.
- Ask hiring managers in your network whether they'd rather interview five perfectly qualified candidates or ten candidates who are a strong culture fit but need some upskilling.
- Share a controversial take from a tech founder or CTO you heard recently (without naming them if they spoke off the record) and ask your network if they agree.
- Pose the question of whether tech recruiters should be expected to understand code, and invite developers in your network to tell you where they think the line is.
- Ask your followers what a hiring process needs to look like in order for a senior engineer to complete it, because most of them have dropped out of one midway.
- Post a this-or-that question for tech candidates: fully remote with a lower salary, or in-office three days a week with a higher one, and ask them to explain their answer.
- Ask your network what the single most outdated thing still happening in tech hiring is, then pin the best answer in the comments at the end of the week.
Pillar 2: valuable posts (expertise)
- Write a short breakdown of the difference between a first-stage technical screen and a take-home test, and explain when each one makes a hiring process stronger or weaker.
- Share three things you've noticed in the CVs of senior engineers who tend to get offers quickly, focusing on structure and specificity rather than buzzwords.
- Explain what a good job brief from a hiring manager contains, and contrast it with the vague one-paragraph description most recruiters receive and have to work from.
- Write a post explaining what counter-offer acceptance usually looks like six months down the line, based on patterns you've observed across placements.
- Describe the difference between a candidate who says they're open to opportunities and one who is active, and explain why that distinction changes how you approach the conversation.
- Share your opinion on why so many tech companies are struggling to hire mid-level engineers specifically, covering the gap that exists between junior pipelines and senior retention.
- Write a post walking through how you prepare a candidate for a final-stage interview at a scale-up, covering the specific things that trip people up at that stage.
- Explain the signs you look for in a job spec that suggest the role has already been open too long and is unlikely to close cleanly, so that candidates can spot them too.
- Break down what a strong LinkedIn profile looks like for a software engineer who isn't actively job hunting but wants recruiters to find them, with concrete section-by-section advice.
Pillar 3: personal posts
- Tell the story of a placement that nearly fell apart at the offer stage and what you did (or didn't do) to hold it together, keeping the focus on what you learned.
- Share what you got wrong in your first year as a tech recruiter and how you'd approach the same situation differently now.
- Write about a moment when a candidate turned down a role you were certain they'd accept, and what that taught you about listening vs. assuming.
- Post about a habit or routine that's made a real difference to how you manage the emotional side of recruitment, like dealing with drop-outs or a slow market.
- Share what drew you to tech recruitment specifically, not the corporate version of this story but the real one, including any wrong turns you took before you landed here.
- Write a post about the piece of advice a hiring manager or candidate gave you that changed the way you work.
- Tell your network about a role you once talked yourself out of filling because the brief wasn't good enough, and explain why you think that was the right call.
Pillar 4: success stories
- Share the story of a candidate who had been unemployed for longer than average and how you worked with them to reframe their experience before they secured a strong offer.
- Write about a time you helped a tech start-up hire their first dedicated engineering lead, covering what made that search different from a standard role.
- Post about a candidate who relocated for a role you placed them in and is now thriving, focusing on what made both sides of that decision the right fit.
- Share how you helped a hiring manager rewrite a job spec that wasn't attracting the right people, and what changed in the quality of applications as a result.
- Tell the story of a candidate who came to you at a real crossroads, deciding between two very different career directions, and how the conversation you had helped them choose.
- Write about placing someone into a tech role who came from a non-traditional background, and what the hiring manager said when they reflected on the decision a few months later.
How to use these
Pick one idea from each pillar per week, and you'll have a balanced, rotating content schedule that covers all four bases without repeating yourself. Don't try to write all 30 posts at once. Instead, sit down each Monday, choose the ideas that feel most alive to you right now, and draft them while they're fresh. The conversation starters work well at the start of the week when engagement tends to be higher. Save your personal and success story posts for mid-week, when your audience is settled into their feed. Keep a notes app or doc open throughout your working day and drop in real observations as they happen, because the best raw material for any of these posts is already sitting in your inbox or your last candidate call.
How often should a recruiter post on LinkedIn to see real results?
Should I be writing posts myself or using a tool to help draft them?
What's the best way to handle negative comments or pushback on a controversial post?
Do I need a large following for LinkedIn posts to bring in leads?
Is it unprofessional to share personal stories on a recruiter's LinkedIn profile?
How do I write a success story post without it sounding like I'm boasting?
MyCopyPal is a LinkedIn content tool for recruiters who want to write posts that generate inbound leads. MyCopyPal builds you a personalised content strategy, tells you what to write each day, and writes posts in your voice. Want to try it out? You can write your first 3 posts for £5.
