Contribute-to-hire: turning a merged PR into an offer

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

What this covers

• The 48-hour-post-merge DM to the maintainer that opens the conversation
• How to frame "I'd be interested in working on this full-time" without sounding desperate
• The interview-skipping path: maintainer → hiring manager → trial week → offer
• What to do if the company isn't hiring — keep contributing, get the network

Why this matters for Indian devs going remote

Most OSS contributors stop after the merge — assuming the merge itself will magnetize an offer. It rarely does. The maintainer is too busy. The conversion happens because you ask, on a specific timeline, with a specific frame. For Indian devs, this is also the path that most consistently bypasses the standard hiring funnel.

Outline

The 48-hour post-merge DM

TODO — exact message structure: gratitude (1 line), interest (1 line), proof (1 line), ask (1 line).

Framing interest without desperation

TODO — "interested in contributing more / full-time if there's a fit" vs "do you have openings".

The maintainer → HM → trial path

TODO — what each step looks like, expected timeline, what to ship in a trial week.

When the company isn't hiring

TODO — keep contributing on a 2-week cadence; ask for intros to peers; build the next merge.

Common mistakes to avoid

• DM-ing the night you merge (looks transactional)
• Asking for a referral before the second merged PR
• Sending the same DM template to 5 maintainers in a week — they're in the same Slack

Templates / examples

TODO — the 48-hour DM template, a 4-step post-merge follow-up cadence, and 2 real conversion stories (anonymized).

Related guides

• Contribute-to-hire: writing a PR that gets merged
• Working with OSS maintainers without getting ghosted

---

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