Personal Brand & Social Presence

Start with positioning: the intersection of what you know, what you enjoy and what your target audience needs. Write it as one sentence:

I help ___ (audience) do ___ (outcome) through ___ (your angle).

For example: "I help frontend developers adopt accessible design systems through practical tutorials and talks."

Then build proof around it:

• Signature content: 3–5 pieces that define you (a popular tutorial, a talk, an open source project).
• A home base: a simple personal site with your positioning, best work, talks and contact info. You own it; platforms change.
• Consistency: the same name, photo and one-line bio everywhere.
• Generosity: share others' work, answer questions and credit people. Brands built on generosity are the most durable.

Narrow is powerful. You can broaden later, but being "the person who knows X" opens doors that "a developer advocate" doesn't.

Your voice is how you sound across everything: posts, talks, replies. The best DevRel voices feel like a knowledgeable friend: clear, honest, a little personal.

Find yours:

• Read your last 10 posts and circle the lines that sound most like you. Do more of that.
• Pick three adjectives (e.g. practical, curious, warm) and check new content against them.
• Have opinions, kindly. "I prefer X for Y because Z" is more memorable than neutral summaries.
• Share the struggle, not just the success. The bug you spent two days on is more relatable than the polished win.
• Stay authentic to your culture and background. Your perspective is an asset, not something to sand down.

When you represent a company, align with its voice but keep your personality. Audiences follow people, not logos.

LinkedIn is where hiring managers, event organisers and decision-makers see your work. For DevRel careers it's often the highest-leverage platform.

What works:

• Profile: a headline with your positioning (not just your title), a featured section with your best work, and an About section written for your target reader.
• Posts: lessons learned, behind-the-scenes of projects, frameworks, event recaps and career insights. Lead with a strong first line; the preview cuts off quickly.
• Native content: the algorithm tends to favour content on the platform, so post a summary and put links in the first comment or at the end.
• Engagement: thoughtful comments on others' posts can build as much visibility as your own posts.
• Consistency: 1–3 posts a week beats bursts.

Share your Compass Challenge outputs here. Each is a ready-made post: what you did, what you learned and a link.

X is real-time and conversational. It's where many developers share quick discoveries, react to launches and talk to each other directly. Depending on your community, Bluesky, Mastodon or Threads may matter as much, so follow your audience.

What works:

• Threads that teach: "7 things I learned building X" with code snippets or visuals.
• Quick wins: a tip, a snippet or a before/after.
• Replies: being helpful in replies to people in your niche builds relationships faster than broadcasting.
• Live coverage of events and launches.
• Lists to follow your niche without drowning in noise.

Keep it professional-casual. Avoid dunking on people or products. It's memorable in the worst way, especially when you represent a company.

Consistency beats intensity. Showing up weekly for a year does more than a burst of daily posts followed by silence.

Systems that make it sustainable:

• Pick a realistic cadence: for example, one long piece a month and two short posts a week.
• Batch: write several posts in one session; schedule them.
• Keep an idea bank: questions you've answered, mistakes you've made, things you've learned this week. You'll never start from a blank page.
• Repurpose: one tutorial → a thread → a LinkedIn post → a short video → a talk.
• Protect your energy: plan off-weeks. Burnout is common in DevRel; a sustainable pace is a professional skill.

Track your cadence rather than your follower count for the first six months. Output is in your control; reach follows.

Each platform has its own format and audience. Repurpose, don't copy-paste.

A repurposing chain for one tutorial:

1. Blog post: the canonical, full version on your site.
2. LinkedIn: the story and lesson, with a link in comments.
3. X/Bluesky thread: the steps as a visual thread.
4. Short video: the most surprising moment in 60 seconds.
5. Newsletter: a teaser plus the link.
6. Community: share in relevant communities if it genuinely helps and follow their self-promotion rules.

Collaborate with other creators: co-write, guest on each other's streams and trade newsletter mentions. Collaboration introduces you to audiences that already trust someone.

Always point back to one canonical URL you own, so authority accumulates in one place.

Building in public means sharing your work, learning and process as you go, not just finished results. It's one of the most effective growth strategies in DevRel, and it's how many practitioners got their first role.

Why it works:

• People follow journeys; progress updates create a reason to come back.
• Your mistakes help others avoid them, which is generous and memorable.
• It creates evidence of skill that no resume can.
• It attracts collaborators and feedback early.

How to start: pick a project or skill, post weekly updates (what you did, what broke, what you learned), share code, and ask for input. swyx's essay Learn In Public is the manifesto. Read it today.

Boundaries matter. Don't share confidential employer information, and it's fine to keep some things private.

Instagram is optional for most DevRel roles, but powerful for visual storytelling and human connection, especially for events, community and developer-lifestyle content.

What works:

• Event coverage: stories from conferences and meetups, speaker moments and community faces (with permission).
• Behind the scenes: your setup, your preparation for a talk, a day in the life.
• Carousels that teach: a concept in 6–10 visual slides; these are often saved and shared.
• Reels: short clips of demos or tips; repurpose from other video.

Keep it visually consistent (a few colours and fonts), use captions for accessibility, and focus on community and people rather than product. Treat it as a secondary channel unless your audience is clearly there.