Has anyone ever put together a system for having engineers write technical posts for their blog? Looking to create one that preferably that involves little to no interviews with engineers?

Thank you for this - very helpful!

I have a loose idea of how some companies that have 800k+ monthly search visitors for dev blogs do it. TLDR: 1. List bunch of topics that need to be covered with loose briefs 2. Get engineers to volunteer to write them 3. Clean it up. Expect nothing from the engineers. They don’t want to deal with approvals, SEO, writing best practices, etc. Just count on them for the meat of it. 4. Run it through normal content process at this stage. Minimize process on their end and correct for their deficiencies with process/editing on your end.

Yeah that sounds right @square-optician-93005 I have a few engineers that are down to right - they more just need like a bare bone outline I can provide to them and they'll fill it in and then I go and clean it all up. We started playing around with this so far and our most viral article came as a result of this so we want to keep it going

I would also make sure that leadership makes it clear that they will be recognized for writing blog posts and that it is not seen as something outside their job. I know at my last role there was a Slack channel for writers and the process was integrated in Asana so that they knew where their content was in the process to publication (they cared a lot about this and would check in frequently!). I have seen 'how we did it' posts do really well where they just write up the backstory behind shipping a product or solving an engineering problem. It's not directly product marketing but add a CTA, talk a bit about the feature/launch and it works! Some people will have high concept ideas and others won't be sure what to do. Make sure both feel like they can contribute their content -- the ideas that come directly from engineers usually do best. Also, get them to turn their conference talks into blog posts. Or take a video of them and do that yourself with the transcript. I also think distribution is key. You need to get it on Hacker News and get your team to upvote it. There are also a bunch of dev newsletters that you can submit content to as well. You can target content to specific niches like PHP users for example as there are a lot of them, they have a developed newsletter system, and they're mostly at enterprise companies with money. And getting them to share it on their socials when it comes out!