Hello amazing people, I am doing a survey for compensation in DevRel for an upcoming YouTube video. No personal info collected.

https://6va3ba4pzuw.typeform.com/to/abH5xLJ7

If you were building a dev rel organization from scratch. Who in the dev rel community would you tap to kick things off?

Know any devrel startups, consultancies or one man consultants, lets talk about what good they are doing and how?

We're BLACKBOX AI, and we're hunting for a LEGENDARY DevRel to join our team building the most advanced AI coding agent on the planet – we're talking about an AI that doesn't just write code, it thinks like a senior engineer, backed by serious investors and working alongside ex-Navy SEALs who bring the same precision and intensity to code that they brought to special operations, combined with the most ridiculously talented engineering team you've ever seen (we're talking people who've built systems at scale for millions of users and now they're laser-focused on revolutionizing how developers code forever) – so if you're a developer advocate who lives and breathes developer experience, can create content that makes other devs say "holy shit, I need this in my workflow RIGHT NOW," and wants to be part of a team that's literally redefining the future of programming with the kind of backing and talent that makes Silicon Valley legends, then DROP A COMMENT or DM us because this isn't just a job, this is your chance to change how every developer on Earth writes code! 🚀💥

One thing I've noticed after working around DevRel/community/events for years is that the actual event is often the easy part.

The messy part is everything around it. You discover conferences in 10 different places. CFPs have different deadlines. Sponsorship opportunities live in emails. Travel is somewhere in a spreadsheet. Team attendance is in Slack.

Talk submissions are in docs. And then after the event, you're trying to answer questions like:

• How much did we actually spend?

• Which conferences generated useful leads?

• Which events should we attend again?

• Who from the team is going where?

• Which CFPs are we about to miss?

I'm curious how other DevRel teams handle this today.

Do you have one system for this, or is it still some combination of spreadsheets + Slack + calendars + bookmarks + Notion + “I'll remember this”? 😅

I'm asking because I'm building a tool in this space called WIMNE https://wimne.tekents.com/, and I'm trying to understand whether this is actually a problem worth solving or just something DevRel people have collectively accepted as normal.

Disclosure: I'm the founder of Tekents, which is building WIMNE, so yes, I have a horse in this race. I'm primarily looking for honest feedback from people actually doing DevRel/community work.

What does your current workflow look like?

Hello,
Suppose someone wanted to make a Developer Affiliate and Influencer Program for a devtool as a Developer Relations person. How would you do it?

Who would you target and why, and how would you measure success, ROI and other important metrics?

Hi all, I'm badly in need for a job, so resorting to posting here too

I am 6 years of working experience across software engineering and devrel. Has managed communities, scaled user group program as well as guven talks at varios enterprise events at a lot of companies, community days and college events.

I am based out of India but ok for relocation too. If anyone is hiring, please dm.

Hi! I work at a data quality company called Soda Data, and we’re looking for a Developer Relations Intern. Someone who understands data engineering, loves to build, teach, and share their work with the world.

Here are some things you’ll be excited to learn and do in this role:

• Build open-source projects and example repositories that showcase Soda’s products

• Write clear, technically accurate content:

  • Tutorials, guides, walkthroughs, and engineering blog posts

  • Integration how-tos and community success stories

• Talk to users and help them solve technical problems

  • Answer questions on Slack, GitHub, and community forums

  • Triage issues, gather feedback, and relay it to the team

• Present at community calls, webinars, and conferences

• Collaborate with product and engineering teams to improve the developer experience

• Help grow and support our open-source contributor community

If this sounds like something you’d enjoy, feel free to apply here: Developer Relations Intern

Developer Relations is like customer service for companies whose users are software developers and it has caught the attention of so many.

If you are interested in Developer Relations, read this article I wrote on Hashnode to learn about the What, why, who, and where of Developer Relations.

https://musab19.hashnode.dev/developer-relations-the-what-why-who-and-where

Disclosure: I develop a desktop client for Antora, which I mention at the end.


Docs-as-code is great for versioning and review, but in my experience the toolchain (Git, YAML playbooks, CLI builds) is where non-developer writers lose the most time. Typical friction points I keep seeing:


- setting up components and versions without breaking the structure
- finding out what a rename or move breaks before the build fails
- getting a trustworthy preview without a full site build


How do you handle this in your team? Do you put a layer of tooling or training on top, or do writers just learn Git?


I develop AsciiLore, a desktop client for Antora (closed source, paid, 14-day trial), built to attack exactly these points, so I'm biased. I'm more interested in your answers than in selling anything. If you use Antora, I'd like to know what would make you consider such a tool at all.

With Smoower.com we built a page to compare and measure developer relation effots across organizations. In past this was not as simple, impossible in parts. LLM's and AI make this possible now.

We collect public signals (documentation freshness, content cadence, community presence, conference participation, plugin ecosystems, response times in public channels, and a few other things), score them against a methodology that is documented and open, and produce a comparable per-company score over time. You can look up your company. You can look up your competitors. You can see how a category like "AI infra" or "developer tools" trends quarter over quarter.

It is not a productivity tool for individual DevRel folks. It is a visibility layer for the field as a whole. The point is not to grade humans. The point is to make the discipline legible to the people who decide whether the discipline continues to exist next year.

If you are running DevRel right now and you want a way to walk into a budget conversation with something other than vibes, that is who this is built for.

Wdyt? Let me know!

Since DevRel is a hard profession to quantify, what skills, behaviors, or approaches make the best stand out?

So mu company has offered me a title change from a devrel to a growth hacker. It's upto me to choose that path or not.

Honestly, I want to stay as a Devrel, but I don't know, is a growth hacker better? Does it open door to better opportunities?

Thanks for all the suggestions in advance 🙏

Launching a Developer Share of Voice dashboard at Weavr.ai to see the impact of content initiatives, events, webinars and more. Feedback from this group would be greatly appreciated.

1. Select sources (Github, Stackoverflow, Hackernews, Reddit etc.)

2. Select products to compare with

3. Click to see the actual posts

4. Download & share it with the team

https://youtube.com/watch?v=8GVYwDdAcSs&feature=share