📝 LinkedIn Templates

10 LinkedIn Connection Request Templates for Developer Relations & Community Builders

Copy-paste LinkedIn connection request templates built for DevRel professionals and developer advocates. Grow your network, build community, and drive developer adoption faster.

Get Started Free

Building a developer community at scale starts with the right connections. Whether you're recruiting contributors, meeting fellow DevRel pros, or expanding your conference network, your LinkedIn connection request is the first impression. These 10 templates are built specifically for DevRel professionals — direct, credible, and easy to personalize.

Templates for Devrel

The Fellow DevRel

1/10

Connecting with another developer advocate or DevRel professional

Hey [NAME], I'm a [YOUR_ROLE] at [YOUR_COMPANY] working on [COMMUNITY_FOCUS]. Saw your work on [THEIR_PROJECT_OR_COMMUNITY] — always looking to connect with other DevRel folks. Would love to trade notes.

Example

Hey Priya, I'm a Developer Advocate at Stripe working on our API community. Saw your work on the Twilio developer community — always looking to connect with other DevRel folks. Would love to trade notes.

💡 When you want to build your peer DevRel network. Mutual peer relationships in DevRel are gold — use this to open the door without a heavy ask.

The Conference Follow-Up

2/10

Reconnecting after meeting at a developer conference

Hey [NAME], great talking at [CONFERENCE_NAME] — your point about [SPECIFIC_TOPIC] stuck with me. Wanted to connect here so we can keep the conversation going.

Example

Hey Marcus, great talking at KubeCon — your point about onboarding enterprise contributors stuck with me. Wanted to connect here so we can keep the conversation going.

💡 Within 48 hours of a conference or meetup. Specificity is everything here — reference something real from your conversation to separate this from a generic add.

The Speaker Admirer

3/10

Reaching out after watching someone's conference talk or webinar

Hey [NAME], just watched your talk on [TALK_TOPIC] at [EVENT]. Your take on [SPECIFIC_POINT] was exactly the framing I needed. Would love to connect and follow your work.

Example

Hey Anita, just watched your talk on developer onboarding at DevRelCon. Your take on reducing time-to-first-API-call was exactly the framing I needed. Would love to connect and follow your work.

💡 After watching a talk, recorded or live. DevRel folks respect people who do the homework — citing a specific point proves you actually watched it.

The Open Source Contributor

4/10

Connecting with an active contributor to your project or a related OSS project

Hey [NAME], noticed your contributions to [PROJECT_NAME] — specifically [SPECIFIC_CONTRIBUTION]. I work on DevRel at [YOUR_COMPANY] and we're always building relationships with engaged contributors. Would love to connect.

Example

Hey Daniel, noticed your contributions to the OpenTelemetry SDK — specifically the Python instrumentation fixes last month. I work on DevRel at Datadog and we're always building relationships with engaged contributors. Would love to connect.

💡 When recruiting community champions or building relationships with power users. Contributors who already engage with your ecosystem are the easiest people to activate.

The Community Builder Exchange

5/10

Connecting with a community manager or builder at a non-competing company

Hey [NAME], I run the developer community at [YOUR_COMPANY] and saw you're building the community at [THEIR_COMPANY]. I'm curious how you're approaching [SHARED_CHALLENGE]. Would be great to connect and share what's working.

Example

Hey Lena, I run the developer community at HashiCorp and saw you're building the community at Grafana. I'm curious how you're approaching contributor recognition at scale. Would be great to connect and share what's working.

💡 When you want a peer knowledge exchange. Non-competing community builders are often willing to share playbooks — this framing makes it a two-way conversation from the start.

The Developer Evangelist Outreach

6/10

Connecting with a developer who is already publicly advocating for your product or category

Hey [NAME], I saw your [POST_OR_PROJECT] about [TOPIC] — you're clearly doing interesting work with [TECHNOLOGY_OR_PRODUCT]. I'm on the DevRel team at [YOUR_COMPANY] and would love to connect. No pitch, just want to stay in touch.

Example

Hey Carlos, I saw your GitHub repo on building with the OpenAI API — you're clearly doing interesting work with LLM integrations. I'm on the DevRel team at OpenAI and would love to connect. No pitch, just want to stay in touch.

💡 When identifying potential developer champions or ambassadors. The 'no pitch' line builds trust immediately — save the ask for a later conversation.

The Podcast or Newsletter Listener

7/10

Reaching out to a DevRel podcaster, newsletter writer, or content creator

Hey [NAME], been following [PODCAST_OR_NEWSLETTER] for a while — your episode on [SPECIFIC_EPISODE_TOPIC] changed how I think about [CONCEPT]. I'm doing similar work in DevRel at [YOUR_COMPANY]. Would love to connect.

Example

Hey Erin, been following DevRel Weekly for a while — your episode on measuring developer community ROI changed how I think about justifying headcount. I'm doing similar work in DevRel at MongoDB. Would love to connect.

💡 When building relationships with DevRel thought leaders and content creators. Specificity beats flattery every time — name the episode, name the concept.

The Developer Program Invite

8/10

Inviting a developer to join your ambassador or champion program

Hey [NAME], I've seen your work with [TECHNOLOGY_OR_FRAMEWORK] — you clearly know this space well. I'm building a developer champion program at [YOUR_COMPANY] for people like you. Would love to connect and share more details.

Example

Hey Tariq, I've seen your work with Kubernetes operators — you clearly know this space well. I'm building a developer champion program at Red Hat for people like you. Would love to connect and share more details.

💡 When actively recruiting for a formal advocacy or ambassador program. Lead with recognition of their expertise before mentioning the program — developers respond to credibility, not recruitment pitches.

The Content Collaborator

9/10

Proposing a guest post, co-webinar, or content collaboration

Hey [NAME], your writing on [TOPIC] at [THEIR_PUBLICATION_OR_BLOG] is some of the clearest I've read. I'm the [YOUR_ROLE] at [YOUR_COMPANY] and think our audiences overlap. Would love to explore a collab — connecting here first.

Example

Hey Sophie, your writing on developer experience metrics at DX Tips is some of the clearest I've read. I'm the Head of Developer Relations at Vercel and think our audiences overlap. Would love to explore a collab — connecting here first.

💡 When building co-marketing or content partnerships. Establish the connection before pitching the collaboration — one step at a time.

The Community Feedback Loop

10/10

Connecting with a power user or vocal community member to gather product feedback

Hey [NAME], saw your feedback on [FORUM_OR_PLATFORM] about [SPECIFIC_ISSUE_OR_FEATURE] with [PRODUCT_OR_TECHNOLOGY]. That's exactly the kind of insight we need. I'm on the DevRel team at [YOUR_COMPANY] — would love to connect and hear more.

Example

Hey Ben, saw your feedback on the GitHub Issues thread about the rate limiting behavior with the Shopify API. That's exactly the kind of insight we need. I'm on the DevRel team at Shopify — would love to connect and hear more.

💡 When turning critics or power users into community partners. Acknowledging their feedback publicly before the DM shows you're paying attention — not just fishing for compliments.

Pro Tips for Devrel

Keep it under 300 characters. LinkedIn caps connection request notes at 300 characters on mobile — write short, cut ruthlessly, and lead with your strongest line.

Reference something specific. Generic requests get ignored. Name the talk, the repo, the post, or the comment. Specificity signals you did the work and separates you from every other cold add.

Skip the pitch in the first message. DevRel relationships are built on trust, not transactions. State why you want to connect, not what you want from them. The ask comes later.

Your job title builds instant credibility. DevRel professionals are recognizable to other developers. Include your role and company — it answers 'why is this person reaching out?' before they have to ask.

Follow up with a comment before you connect. If you want a high acceptance rate, comment on one of their posts before sending the request. It warms the connection and gives you a natural reference point in your message.

Ready to use these templates?

Remarkly helps you comment smarter, build pipeline, and grow your personal brand on LinkedIn.

Get Started Free