Skip to content

Posting on LinkedIn for inbound

Optional. For students and early-career engineers who can spare 2 to 3 hours a week. You finish with one topic lane, a cadence, 7 copy-paste templates, a daily comment habit, and a 30-day calendar.

Posting was part of the system that got me 47 recruiter messages in a month (How I got 47 recruiter messages within a month). In 2026 I put the LinkedIn part of my search this way: fix the headline, write an About that reads like a story, and "post your work weekly. When I did this, my profile views jumped 340% and recruiters started messaging me" (The job-search tool stack I'd actually use in 2026).

Should you post at all?

Your situation Do this
Profile not finished Stop. Finish the profile build first. Posts send people to your profile
Onsite or OA in the next 4 weeks 1 post a week at most. Prep comes first (Coding interviews)
Learning or building something now 2 to 3 posts a week, Jugal's student cadence
Actively job seeking 3 to 4 posts a week, Jugal's job-seeker cadence
Hate posting Skip posts. Do the 15-minute comment habit instead. It still puts your name and headline in front of the right people

You do not need to go viral. Jugal's playbook: "You need to show up consistently enough that LinkedIn's algorithm keeps surfacing you" (The LinkedIn Profile Playbook).

How the feed decides who sees your post

LinkedIn's official ranking signals (LinkedIn relevance):

Signal group What LinkedIn says it uses What it means for you
Identity Your location, workplace, and skills Your headline and Skills tell the feed who your posts are for
Content How often a post is viewed or engaged with; what it is about and "whether it provides knowledge or advice"; how recent it is; how constructive the conversation is Teach something specific. Reply to comments well
Activity What viewers reacted to, commented on, shared; who they interact with; what they spend time viewing Comment in your lane so the people you want see you

What changed in 2026: on March 12, 2026 LinkedIn rebuilt feed recommendations on LLM-based retrieval. It surfaces posts by topic from people a viewer has "never connected with before" and refreshes within minutes (LinkedIn Engineering; plain-English version: ByteByteGo). A post on one clear topic can reach engineers outside your network.

What gets less reach:

Step 1: Pick one lane

  1. Write your lane in one sentence: "[topic] for [audience]". Example: "Backend and AWS, for new grads learning production systems."
  2. Check it matches your headline and top 5 skills. If your headline says ML engineer and you post about React, the feed gets two signals.
  3. Follow 20 engineers who post well in that lane. Turn on notifications for 5 of them so you can comment early.
  4. Keep 80% of posts inside the lane for 8 weeks before you widen.
Lane Who it attracts First 3 post ideas
Backend and cloud Backend and infra recruiters, platform teams A bug you fixed in your API; how you cut a query from 800ms to 40ms; what you learned deploying on AWS free tier
LLM apps and AI engineering AI startups, AI teams at big tech Your RAG project and how you measured retrieval quality; one eval that broke your app; prompt change log with results
ML research Research labs, applied science teams One-paragraph summary of a paper you reproduced; your ablation result; a plot you made
Frontend and product engineering Product teams, startups A UI performance fix with before and after numbers; accessibility audit of your project
Data engineering Data platform teams A pipeline you built and its failure modes; batch vs streaming choice in your project
Interview prep in public Peers, some recruiters Pattern you finally understood; mock interview lesson; your weekly prep log (never share real OA questions)

Step 2: Set cadence and timing

Source Cadence Timing
Jugal (47 messages post, 2025) Students 2 to 3 a week; job seeking 3 to 4 a week Tuesday to Thursday, 8 to 10 AM or 1 to 3 PM, your time zone
Buffer, 2M+ posts (LinkedIn algorithm, Dec 2025) 2 to 5 a week improves impressions and engagement n/a
Buffer, 4.8M posts (Best time to post, Sep 2026) n/a Weekdays 3 to 8 PM local; best slot Wednesday 4 PM; best days Wednesday to Friday

The two timing sources disagree. Buffer's is the newer dataset; Jugal's is his own experience. Test both:

  1. Weeks 1 and 2: post at 9 AM Tuesday and Thursday.
  2. Weeks 3 and 4: post at 4 PM Wednesday and Friday.
  3. Compare impressions and profile views per post. Keep the winner.
  4. Post when the audience you want is awake. If you are in India targeting US teams, schedule for US daytime, not yours.
  5. Use LinkedIn's built-in scheduler: write the post, click the clock icon in the post editor, and pick a time 10 minutes to 3 months ahead (Schedule posts). Write all of a week's posts on Sunday.

Step 3: Use a content mix

Jugal's mix from his LinkedIn Step By Step guide:

Pillar Share At 3 posts a week
Learning and growth 40% 1 post every week
Project showcases 30% 1 post every week
Industry insights 20% Alternate weeks
Career and networking 10% Alternate weeks

LinkedIn's own student guidance says "Not every post needs to celebrate a big win." Its prompts: "Start with a question", "Share the messy middle", "Post what you learned" (LinkedIn for students).

Post types that work for students

Type Format When Opening line example
Project showcase Text + screenshot, GIF, or 30 to 60 second demo video The day you ship "I built a rate limiter in Go that held 20k requests per second. The hard part was not the algorithm."
Learning post Text only Weekly "Week 3 of learning Kubernetes. The thing that finally clicked: a Service is just a stable name for pods that keep dying."
Explainer carousel PDF document, 6 to 10 slides After you understand a concept well "Consistent hashing in 7 slides, from the version I wish I had read first."
Internship recap Text + team photo (with permission) Last week of the internship "12 weeks at [Company], 3 things I shipped, 1 thing I got wrong."
Hackathon or team project Collaborative post with teammates Within 2 days of the event "48 hours, 4 people, 1 working demo. Here is what we built at [Hackathon]."
Open-source PR merged Screenshot of the merged PR + link The day it merges "My first PR to [project] got merged. It fixed [bug] that affected [users]."
Prep reflection Text Monthly "100 problems in, these 5 patterns covered most of them."
"Open to" announcement Text, once per search When your profile is finished "I'm looking for new grad backend roles from June 2027. 3 things I've built:"
Offer or return offer Text + thanks After you sign "Joining [Company] as a new grad SWE in [team]. Thank you to [people] who helped."
Industry commentary Text When news hits your lane "[News] matters for students for one reason: [specific point]."

Format notes:

  • Buffer's analysis of 1M+ posts found PDF carousels got about 3x the engagement of video or image posts and nearly 6x that of text-only posts (Buffer). Make one in Google Slides, export as PDF, and upload it as a document post.
  • Collaborative posts (early access as of Oct 2026) let you invite up to five connections or Pages as co-authors, and the post appears on their profiles too (LinkedIn Help). Use it for team projects and hackathons.
  • Use your own screenshots and diagrams. No stock photos.

Anatomy of a post

About 210 characters show before "see more" on desktop and about 140 on mobile (AuthoredUp). The first line decides whether anyone reads the rest.

Line 1 (hook):      [A number, a result, or a tension. Under 140 characters.]
Lines 2 to 3:       [Context: what you were doing and why.]
Lines 4 to 7:       [What you did, as 3 short lines or bullets. Name the tech.]
Line 8:             [One lesson in one sentence.]
Line 9:             [A real question for people in your lane.]
Link:               [GitHub, demo, or carousel. In the post or the first comment.]
Hashtags:           [0 to 3]
  1. Keep text posts under 200 words, the length Jugal's prompts use.
  2. Use at most 3 hashtags. Buffer calls them "nice to have" (Buffer).
  3. Links: Buffer found no penalty for external links when the post has value, and LinkedIn has no official statement either way. Test link-in-post against link-in-first-comment.
  4. Tag a person only if they were part of the work.
  5. Reply to every comment in the first few hours. Replies are conversation, and conversation is a ranking signal.
Version Post opening
Weak "Excited to share that I have completed my project. Grateful for this experience. #coding #developer #100DaysOfCode"
Strong "My Go rate limiter held 20k requests per second in load tests. The first version fell over at 3k because of one lock."
Version Post opening
Weak "Thrilled to announce I completed my internship at [Company]. So grateful."
Strong "I spent 12 weeks on [Company]'s payments team. I shipped 2 services, cut refund tickets by 60%, and broke staging once. Here is what each taught me."

A full post in this shape (fictional student, for shape only; every number in yours must be real):

My Go rate limiter held 20k requests per second in load tests. The first version fell over at 3k.

I built it for my distributed systems class project: a token bucket in front of a small URL shortener.

What I changed:
- Moved the bucket state from a mutex-guarded map to Redis with a Lua script
- Batched refills instead of updating on every request
- Load tested with k6 after each change, not at the end

Lesson: measure before you optimize. The lock was 80% of the latency and I had guessed it was the network.

Backend folks: do you rate limit at the gateway or in each service?

Code and load test results: github.com/[user]/[repo]
#golang #backend

Templates

Sources, with emojis and hype words removed: the project showcase and learning post come from the sample posts in Jugal's LinkedIn Step By Step guide, and "I tested X" comes from his 47 recruiter messages post. Fill every bracket with real facts.

Project showcase

Just deployed [project].

Problem I solved: [problem, who had it].
My solution: [what it does, in one sentence].
Tech stack: [stack].
Features: [2 to 3 features].

Biggest challenge: [the hard part].
How I solved it: [what you did].

Link in comments. Would love feedback from [backend / ML / frontend] engineers.

Learning post

Week [N] of learning [tech].

Key breakthrough: [what clicked] when I built [thing].

The insight: [one sentence].

What concept took you multiple attempts to learn?

Internship recap

[N] weeks on [team] at [Company]. 3 things I shipped:

1. [Thing], [a result you are allowed to share]
2. [Thing], [a result you are allowed to share]
3. [Thing], [a result you are allowed to share]

One thing I got wrong: [mistake] and what I do differently now: [change].

Thank you to [manager] and [mentor] for [specific help].

Check with your manager before posting. Never share internal metrics, code, or roadmaps.

"Open to" announcement

I'm looking for [new grad software engineer / Summer 2027 SWE intern] roles, starting [Month Year], in [cities] or remote.

What I've built:
- [Project or internship result with a number]
- [Project or internship result with a number]
- [Project or award]

I work mostly in [stack]. If your team is hiring, or you know someone who is, I'd be grateful for a message or a referral.
Resume and projects: [link]

Slide 1: [Concept] in 7 slides
Slide 2: The problem it solves, with one real example
Slide 3: The naive approach and why it breaks
Slide 4: The idea, as one diagram
Slide 5: How it works, step by step
Slide 6: Where you see it in real systems (name 2)
Slide 7: One-line summary + "I used this in [project]: [link]"
Post text: 3 lines on why you made it + a question

"I tested X" (only with your own real data)

I spent [timeframe] testing [assumption or approach].

The result: [finding, with a number].

What I tried:
- [Test 1]: [result]
- [Test 2]: [result]
- [Test 3]: [result]

The surprise: [most unexpected finding].

[Engineers in your lane]: what has your experience been?

Hackathon or team project

Send it as a collaborative post if you have access.

[N] hours, [N] people, 1 working demo at [Hackathon].

We built [project]: [what it does, for whom].
My part: [what you built, with the tech].
Result: [placement, users, or what judges said].

Built with [teammate names]. Demo: [link]

AI prompts for drafts

Jugal's prompts from the 47 recruiter messages post. Give the model real facts, then rewrite the draft in your own words. Delete anything you did not do.

Write a LinkedIn post about my experience learning [technology/skill]. Include:
- Specific challenge I overcame
- Technical insight I gained
- Question to engage my network
- Relevant hashtags for [your field]
Keep it conversational and under 200 words.

Create a LinkedIn post showcasing my project: [brief description].
Include:
- Problem solved and target audience
- Key technical features (mention: [specific technologies])
- One major challenge and how I solved it
- Call-to-action for feedback
Format with bullet points and relevant hashtags.

Write a LinkedIn post commenting on this industry trend: [trend/news].
Include:
- Personal perspective as a [your major] student
- One specific insight or question
- Connection to my career interests in [field]
- Engagement question for my network

Two-version prompt from The LinkedIn Profile Playbook:

Help me write a LinkedIn post. Here is what I want to share:
Topic or story: [e.g. I fixed a bug that had been in our app for 6 months. Here is how I found it.]
My audience: [e.g. software engineers early in their careers, tech recruiters]
Tone I want: [e.g. conversational and honest, like I am talking to a friend]
Outcome I want: [e.g. comments from engineers who hit the same problem]

Write me 2 versions. Version 1: short, 5 to 8 lines, punchy single-sentence paragraphs, strong first line. Version 2: longer story, 15 to 20 lines, a lesson at the end, a question to drive comments. No em dashes. No hashtag spam. No corporate language. Do not add any fact or number I did not give you.

Comments: the 15-minute daily habit

A specific comment on a well-followed post puts your name and headline in front of that person's whole audience (The LinkedIn Profile Playbook).

  1. Every weekday, find 3 to 5 posts in your lane: hiring and product posts from target companies, technical posts by senior engineers, career advice from people in your field.
  2. Prefer posts under 50 comments and 2 to 4 hours old, Jugal's targets. Your comment is more likely to be seen.
  3. Write each comment with Jugal's framework: personal experience or insight + a question or extra perspective + tag a relevant person (optional).
  4. Once a week, repost something useful with 2 to 3 sentences of your own take.
  5. Never comment "Great post!" or "Congrats!" alone. Jugal's guide lists those as red flags.
  6. Never use comment automation tools. LinkedIn may hide comments made with them.
Framework: [Your experience or insight] + [Question or another angle] + [Optional: @person who would know]

Example (Jugal's): "This resonates with my experience building APIs in Node.js. The error handling patterns you mentioned saved me hours of debugging. Have you experimented with GraphQL error extensions for more detailed client feedback? @[relevant connection] might have insights on this too."

What not to post

  • Real OA or interview questions from a company. Many companies and OA platforms ask candidates to keep questions confidential. See the integrity rules in OA strategy.
  • Internal metrics, code, screenshots, or roadmaps from an internship.
  • Your resume with phone number and home address. Posts can be visible off LinkedIn (LinkedIn Help).
  • Political fights and oversharing, both on Jugal's red-flag list.
  • Posts that only ask for jobs. One "Open to" post per search is enough; the rest should show your work.
  • Rants naming a recruiter or company. Recruiters read profiles before they message.
  • AI drafts you did not edit. Readers spot them in one line.

Measure what works

  1. After each post, note impressions, reactions, comments, and profile views 48 hours later.
  2. Every Monday, check Analytics > Search appearances and recruiter messages (LinkedIn Help).
  3. Targets from Jugal's guide: 50+ profile views a week and about 5% engagement per post.
  4. After 4 weeks, double down on the 2 post types that brought the most profile views. Drop the rest.
  5. A/B test your headline monthly: change one part, compare search appearances over 2 weeks.
Post log
Date | Type | Hook (first line) | Time posted | Impressions (48h) | Comments | Profile views (week) | Recruiter messages (week)

30-day calendar

Week 1:

  • Write your lane sentence; check headline and skills match it
  • Follow 20 engineers in your lane; turn on notifications for 5
  • Publish one learning post
  • Comment on 3 to 5 lane posts every weekday

Week 2:

  • Publish one project showcase with a link
  • Publish one learning post
  • Comment on 3 to 5 lane posts every weekday
  • Repost one useful post with your own 2 to 3 sentence take

Week 3:

  • Publish one explainer carousel (PDF, 7 slides)
  • Publish one industry insight post
  • Comment on 3 to 5 lane posts every weekday
  • Switch to the other posting time slot for the timing test

Week 4:

  • Publish one project or internship post
  • Publish one career post (or your "Open to" post if job seeking)
  • Review the post log; pick the 2 best post types
  • Change one part of your headline and note search appearances

Checklist

  • Profile finished before the first post
  • One lane, written down, matching headline and top skills
  • Cadence chosen: 2 to 3 a week (student) or 3 to 4 (job seeking)
  • Timing test running for 4 weeks
  • First 140 characters of every post carry the hook
  • Every number in every post is true and explainable
  • At most 3 hashtags; no engagement bait; no pods
  • Comment habit: 3 to 5 comments every weekday
  • Replies to every comment on your own posts
  • No OA questions, internal data, or personal contact details in posts
  • Post log updated after every post

Resources

Turn inbound into conversations with Message templates and Referrals. Jugal's networking posts are mapped in Substack index.

Next: Outreach strategy