LinkedIn truncates your post after roughly 140 characters. Everything after that lives behind a “…see more” link. Which means your first line has exactly one job: make someone tap that link. If the hook doesn’t land, it doesn’t matter how good the rest of your post is. Nobody will see it.

The standard advice is to “write a compelling hook.” Thanks, very helpful. Here are 15 specific patterns that work for technical content, grouped by what makes them tick, with real examples you can steal and adapt.

Numbers that stop the scroll

Nothing halts a thumb mid-scroll like a specific number. Not a round number, not a vague “significant improvement” — a precise figure that implies a real story behind it.

The specific number. “Reduced our API response time from 2.3s to 140ms.” This works because it’s concrete and implies a story worth hearing. The reader immediately wants to know how. The mistake people make with this pattern is using numbers that don’t mean anything in isolation — “Processed 4.2 million records” is meaningless without context. The number needs to imply a transformation or a surprise. A before-and-after number always outperforms a standalone metric.

The before/after. “Our CI pipeline: 14 minutes in January. 90 seconds now.” This is the specific number pattern’s older sibling. Two data points, separated by time, implying a journey. The gap between the numbers is what creates the hook — the bigger the gap, the stronger the pull. Don’t inflate the numbers, though. Developers are annoyingly good at spotting implausible claims, and getting called out in the comments torpedoes your credibility.

The cost/time. “This one config change saved us $400/month on AWS.” Money and time are universal. Everyone understands them. Everyone wants to save both. When you attach a specific dollar figure or time saving to a change, you’re promising the reader actionable information. The key is “one config change” — it implies the insight is transferable. If the hook suggests the reader could apply this themselves, the click-through rate goes up significantly. The trap here is clickbait framing: “This ONE WEIRD TRICK saved us thousands” reads like a spam email. Keep it factual.

The timeline. “Spent 2 weeks planning. Built it in an afternoon.” The contrast between expected effort and actual effort creates intrigue. This works especially well when the punchline is counterintuitive — you’d expect the planning to pay off, but the implication is that maybe it didn’t (or maybe it paid off so well that the build was trivial). Either way, the reader wants the story. Just make sure the post delivers on the promise. If your hook implies a surprising timeline, the body needs to explain why.

If you’re pulling from your merged PRs, numbers are usually sitting right there in the diff — performance benchmarks, line counts, config changes with measurable impact. It’s one of the reasons the PR-to-post workflow produces strong hooks naturally: the raw material is already specific.

Opinions that start conversations

LinkedIn’s algorithm loves comments. Comments come from disagreement, agreement, and “well, actually” energy. Opinionated hooks generate all three.

The hot take. “Docker is overkill for 90% of side projects.” This is a statement that a significant number of developers will disagree with, and that’s exactly the point. Hot takes work because they force the reader to have a reaction. They either nod and want to see your reasoning, or they disagree and want to tell you why you’re wrong. Both outcomes mean engagement. The line between a hot take and a bad take is whether you can back it up. If your post just states the opinion and waves its hands, you’ll get engagement but lose respect. If you explain your reasoning with specifics, you’ll get engagement and respect. Don’t be contrarian for the sake of it — genuinely believe the thing you’re saying.

The contradiction. “We switched from microservices to a monolith. On purpose.” This is a subspecies of the hot take, but it works slightly differently. The hook implies you did something that conventional wisdom says is backwards, and you did it deliberately. The reader’s brain goes “wait, why?” and that curiosity is what drives the click. The “on purpose” (or similar qualifier) is doing heavy lifting — without it, the reader might assume it was a mistake. With it, they know there’s a deliberate decision to unpack.

The honest review. “Used Cursor for a month. Here’s what I’d actually use it for.” The word “actually” is doing work here. It signals that this isn’t a sponsored puff piece — it’s a genuine assessment from someone who used the thing. Developers are starved for honest reviews because so much content is either paid promotion or tribal allegiance. If your hook signals objectivity, people will read it. The mistake is burying the verdict. Give your actual opinion in the post, not a wishy-washy “it depends.” For more on how opinion-driven posts compare to the generic AI-generated variety, the AI LinkedIn posts piece breaks down why specificity and opinions are what separate human-sounding content from chatbot output.

The simple statement. “I stopped writing unit tests for React components.” Short. Declarative. Slightly provocative. The power of this hook is its brevity — there’s no qualification, no hedging. It’s a statement that demands explanation, and the reader trusts that the explanation is coming. Keep it to one sentence. The moment you add “and here’s why” to the hook, you weaken it. Let the statement stand on its own. Let the reader’s curiosity do the work.

Stories that pull people in

Humans are wired for narrative. A hook that implies a story — especially one with conflict, surprise, or failure — is almost irresistible.

The admission. “I mass deleted 4,000 lines of code I wrote last month.” This works because it sounds like a confession. The reader assumes there’s a story about why — a realisation, a mistake, a change of direction. Admissions of failure or unconventional decisions are inherently interesting because they break the LinkedIn norm of relentless positivity. The trap is making the admission too dramatic. “I almost burned down the production database” is compelling. “I once forgot a semicolon” is not.

The question that implies a story. “Ever shipped a feature that made performance 10x worse?” This hook works on two levels. First, most developers have done something like this, so it triggers recognition. Second, it implies that you have a specific story about doing this, and the reader wants to hear it. The question format invites the reader into the narrative before they’ve even clicked “see more.” Don’t confuse this with engagement-bait questions like “What’s your favourite programming language?” — those are empty. Your question needs to imply a specific, interesting story that you’re about to tell.

The unexpected outcome. “The best engineering decision we made was deleting our test suite.” This is a close cousin of the contradiction, but it leads with the outcome rather than the action. The reader’s reaction is “that can’t possibly be true,” which is exactly the reaction you want. They click to find out whether you’re serious and, if so, how on earth that worked out. The risk is that your post needs to deliver a genuinely compelling explanation. If the body of the post doesn’t justify the provocative hook, you’ll get comments calling you out — and not the good kind.

The behind-the-scenes. “Here’s the actual system design doc for our auth rewrite.” The word “actual” signals authenticity. You’re not summarising, you’re showing. Developers love looking behind the curtain of other teams’ decision-making processes. Architecture docs, post-mortems, design decisions — anything that shows how the sausage gets made is compelling. The hook works because it promises insider access. Make sure you actually deliver it in the post.

Recommendations and comparisons

Some of the most useful LinkedIn content is simply telling other developers what works and what doesn’t. These hooks frame that naturally.

The tool recommendation. “Found a CLI tool that replaced 3 of our deployment scripts.” This is genuinely helpful content, and the hook signals that immediately. People click because they want to know what the tool is and whether it would work for them. The number (“3 of our deployment scripts”) adds specificity — it’s not a vague endorsement, it’s a concrete replacement. The mistake is being too vague in the hook. “Found an amazing tool” is weak. “Found a CLI tool that replaced 3 scripts” is strong because it tells you the category and the scale of impact before you even click.

The comparison. “Tried both Drizzle and Prisma on the same project.” Developers love comparisons because they’re constantly making technology choices and want data points from people who’ve actually used the options. “On the same project” is what makes this hook work — it signals a fair, apples-to-apples comparison rather than someone who used Prisma two years ago and Drizzle last week. The mistake is writing a comparison that doesn’t actually pick a winner. Fence-sitting is boring. Have a preference and state it.

The lesson frame. “3 things I learned migrating 2TB of Postgres data.” The lesson frame works because it promises structured, actionable information. The specific detail (“2TB of Postgres data”) signals that this is a real experience, not a hypothetical listicle. Keep the number of lessons low — three is ideal. Five is fine. Ten is a listicle, and listicles are a different format. The hook’s job is to signal “small number of high-value insights from real experience.” Check out the developer LinkedIn post examples page for more templates that use this pattern effectively.

Making hooks a habit, not a chore

The patterns above aren’t formulas to fill in mechanically. They’re starting points — structural shapes that you pour your own content into. The specifics have to come from your actual work: real numbers, real tools, real decisions.

If you find yourself staring at a blank post trying to craft the perfect hook, you’re overthinking it. Start with the most interesting fact, number, or decision from whatever you’re writing about. Put that first. Cut everything before it. That’s your hook.

And if you’re generating posts from PRs or project URLs, tools like ShipPost produce hooks in this vein automatically — because the input is already specific. When you feed in a PR that reduced bundle size by 40%, the generated hook naturally leads with that number. When you feed in a URL about a tool migration, the hook naturally leads with the comparison. Specificity in, specificity out.

The first line is the whole game. Get that right, and the rest of the post has a fighting chance. Get it wrong, and you’re writing for an audience of zero.

Try ShipPost free — no credit card, no subscription. Bring your own API key. See what hooks it generates from your actual work.

Numbers that stop the scroll

Opinions that start conversations

Stories that pull people in

Recommendations and comparisons

Making hooks a habit, not a chore

Related reading