Senior DevRel / Content Strategist for Open Source Developer Tools

# Senior DevRel / Content Strategist for Open Source Developer Tools I’m looking for a senior DevRel / technical content strategist to help shape the positioning, content strategy, and launch plan for a set of early-stage open source developer tools. This is a part-time freelance role, likely a few hours per week to start. I’m building Druks, an ecosystem of open source tools around agent runtimes, sandboxing, host provisioning, and developer workflows. The first public project is Drukbox: https://github.com/clawhaven/drukbox I’m looking for someone who can help figure out how to explain these tools clearly, who to reach first, and what content or launch strategy would make developers want to try them. ## What I Need Help With I’m looking for strategy and editorial direction more than high-volume writing. You would help with things like: - Reviewing open source repos and identifying the strongest developer angle - Clarifying positioning and messaging - Deciding which audiences and use cases to focus on first - Reviewing README/docs/onboarding from a developer adoption perspective - Suggesting the first 3-5 content or launch bets - Creating briefs for blog posts, tutorials, launch posts, and social content - Reviewing or improving drafts - Suggesting where and how to promote the projects - Helping build a repeatable content and launch process Strong writing is useful, but the most important thing is judgment: knowing what will resonate with developers, what claims are credible, and what needs to be clearer before a project is launched more widely. ## Ideal Background Good candidates may have experience with: - DevRel / developer advocacy - Developer marketing for devtools, APIs, infrastructure, AI tools, or open source - Technical content strategy - Open source launches - Docs, README, or quickstart critique - Python, FastAPI, Docker, SSH, CLI tools, APIs, or infrastructure - Hacker News, Reddit, GitHub, X, LinkedIn, Dev.to, or niche developer communities - Editing or guiding technical writers You do not need to be a senior engineer, but you should be technical enough to understand a repo, ask good questions, and keep content grounded in what the tool actually does. ## First Paid Engagement I’d like to start with a small paid strategy sprint. The first deliverables would be: 1. Review Drukbox and any extra context I share. 2. Write a short positioning memo covering: - who the first audience should be - what the strongest angle is - what developers need to understand quickly - what feels clear vs confusing 3. Suggest the first 3-5 content or launch ideas. 4. Critique one existing draft, README section, or docs page. 5. Recommend the best next piece to create and why. If this goes well, the role can become ongoing part-time freelance work. ## To Apply Please include: 1. 1-2 examples where you helped shape positioning, content strategy, DevRel strategy, or a developer-tool launch. 2. A short explanation of what you contributed. 3. One developer tool or open source project whose positioning you think is strong, and why. 4. How you would approach the first 2-3 hours of this project. 5. Your availability for a short interview.