Technical Writer — AI / DevTools
About the job
We're building a real content engine for AI-native devtool and platform companies, and we need someone who can actually understand the products before writing a word about them. This is not a "good writer who'll pick up the tech" role : it's a technical person who can write.
Setup
- Remote, contract
- ~30 hrs/week
- Ongoing
- Good performance can also translate to full time
Who you are - required
- You have real hands-on experience with the AI/devtools space: you've built with APIs, SDKs, LLMs, vector DBs, agent frameworks, or similar - as an engineer, technical PM, DevRel, or through serious personal projects. You don't need to code daily today, but you need to have done it.
- You can read a changelog, a docs page, or a GitHub repo and understand what actually changed and why it matters - without needing someone to translate it for you first.
- You can explain technical concepts accurately to a technical audience. No hand-waving, no "AI-powered" filler, no getting the mechanism wrong.
- You know the current landscape well enough to have opinions: what's overhyped, what's genuinely useful, how one tool differs from another in the same category.
What you'll be writing
- Launch posts : announcing new products, features, and tools in a way that reads native, not like a press release
- Educational deep-dives : how something works, why it matters, where it fits, for an audience that can smell fluff instantly
- Product walkthroughs : hands-on, show-don't-tell posts that help developers actually use a tool
All of it lives on Reddit — so it also needs to respect each subreddit's rules and culture and earn attention rather than buy it.
Added advantage (not required, but valued)
- You're an active Redditor who already knows why r/programming and r/LocalLLaMA react differently, and what gets a post buried vs. upvoted
- A track record of posts that performed well (karma isn't everything, but it's a signal)
- Experience in developer marketing or DevRel
- You understand the line between authentic community participation and astroturfing, and stay on the right side of it
- Reliable with deadlines, works independently
How to apply(your application will only be considered): Email [email protected] with:
- Your resume, with technical background clearly visible (roles, projects, stack)
- Writing samples that demonstrate technical understanding: technical blog posts, docs, changelogs, or explainers you've written (this matters more than general writing samples)
- Bonus: social posts. Extra bonus: Reddit posts, with links if public
- Screening question (required): In 3–4 sentences: What does an inference engine (e.g. vLLM, TensorRT-LLM, SGLang) actually do, and why does a team's choice of inference engine matter to end users, not just infra cost? Answer in your own words.