Building in public for inbound recruiter DMs

Status: Outline — full guide coming soon. Get notified when it ships →

What this covers

• The 3-channel cadence (X, LinkedIn, blog) and why each does a different job
• The 5 post formats that actually produce inbound: demo loom, lessons learned, before/after, anti-pattern call-out, weekly progress
• Why "I'm learning X today" posts don't work
• The minimum-viable cadence (it's lower than you think) and the public-progress flywheel

Why this matters for Indian devs going remote

Outbound applying is slow and lossy. Inbound DMs from recruiters who already saw your work convert at 5-10x the rate. For Indian devs without strong campus or company networks, building in public is the cheapest way to manufacture inbound — every shipped weekend project is a recruiter touchpoint.

Outline

The 3-channel split

TODO — X for dev community / inbound, LinkedIn for recruiter pipeline, blog for SEO + interview prep.

The 5 post formats that convert

TODO — demo loom, lessons learned, before/after, anti-pattern, weekly progress. One example per format.

Posts that don't work

TODO — "started learning Rust today", motivational, generic news commentary, gratitude posts.

Minimum cadence

TODO — 2 X posts/week + 1 LinkedIn/week + 1 blog/month. The flywheel kicks in at week 8.

Common mistakes to avoid

• Posting only when you have something to "announce" (you'll post twice a year)
• Cross-posting the identical text to all 3 channels
• Engagement-bait threads — they attract followers, not recruiters

Templates / examples

TODO — a weekly content calendar template, 5 post format examples with real metrics, and a "what to post when you have nothing to post" idea list.

Related guides

• The 6 blog posts that make you look senior
• LinkedIn profile for the Forward Deployed Engineer positioning

---

Have a question about this? DM me on LinkedIn or drop your email to get the full guide as soon as it's published.