What the job involves
The main requirements, responsibilities and hiring steps.
Requirements
- Portfolio of technical or B2B SaaS writing, with developer-facing content strongly preferred
- Solid SEO fundamentals including search intent heading hierarchy metadata and internal linking
- Ability to explain REST APIs authentication pagination and error handling to a competent reader who has not used the product
- Clean direct English with strong self-editing and a focus on cutting fluff
- Comfortable asking engineers specific technical questions on Slack
- Self-directed remote work habits and ability to manage a content backlog independently
Nice to have
- Technical writing
- B2B SaaS writing
- Developer-facing content
- MDX familiarity
- Markdown familiarity
- Git-based publishing
- Social platform knowledge
- Competitive SEO
Day to day
- Plan and write SEO content including blog posts, long-form guides, tutorials, comparison pages, and product landing copy
- Turn rough outlines, Loom transcripts, or bullet-point briefs into polished articles with working code samples
- Research keywords and search intent, then structure headings and internal links for search without writing for bots
- Fact-check endpoint paths, parameters, response fields, and error codes with engineers before publish
- Refresh existing guides when platforms change, endpoints ship, or competitors move pricing
- Build internal links between docs, guides, free tools, compare pages, and use-case pages so readers can go deeper
- Track what is ranking and what is stale, then propose updates based on traffic and support themes
Hiring process
- Email jobs@socialfetch.dev with the role title in the subject line
- Include a short intro and relevant experience
- Link to 2–3 writing samples, ideally technical or B2B SaaS
- Optional: suggest one guide topic for Social Fetch and explain why