SEO Content Writer

About the role

Developers find us through search — "TikTok profile API", "YouTube transcript API", "Social Fetch vs Apify" — and decide whether to sign up based on what they read. You'll own that content: integration guides, platform tutorials, comparison pages, use-case landing pages, and blog posts. Content lives in MDX in our monorepo (apps/web/content/guides/, compare pages, use-case pages). You'll work from rough outlines, internal notes, or recorded walkthroughs and turn them into publish-ready articles. Engineers review for technical accuracy; you own structure, clarity, and whether a reader can copy the curl example and get a 200 back. The API changes — new endpoints, renamed fields, pricing updates — and content has to keep up. Stale docs hurt us more than no docs, because developers trust us with production jobs.

Team & how we work

You'll work with engineers who built the endpoints you write about and support who know repeat questions. No separate editorial team — you are the editorial function. Remote, async, flexible hours. Output is written work in GitHub or Google Docs, not slide decks in standups. Flag when a draft doesn't make technical sense rather than guessing. Occasional sync calls to plan calendars or walk through a feature; default is write, get feedback, ship.

Responsibilities

• Plan and write SEO content: blog posts, long-form guides (often 2,000–5,000 words), 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; 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 deep.
• Track what's ranking and what's stale; propose updates based on traffic and support themes.

Requirements

• Portfolio of technical or B2B SaaS writing — developer-facing content strongly preferred.
• Solid SEO fundamentals: search intent, heading hierarchy, metadata, internal linking — not keyword stuffing or AI-slop listicles.
• You can explain REST APIs, authentication, pagination, and error handling to someone who's competent but hasn't used our product.
• Clean, direct English. You edit your own work and cut fluff.
• Comfortable pinging engineers on Slack with specific questions ("does this endpoint return cursor or nextPageToken?").
• Self-directed remote work habits — you manage a content backlog without someone standing over you.

Nice to have

• Experience writing for developer tools, data APIs, or social/marketing tech.
• Familiarity with MDX, Markdown, or Git-based publishing workflows.
• Basic understanding of social platforms and scraping (you won't write scrapers, but you should know what a rate limit is).
• Experience with comparison or alternative pages in competitive SEO.

Benefits

• Flexible hours — Async-first. Ship your work; we don't track screen time or mandate overlap windows unless a role specifically needs it.
• Unlimited PTO — Take the time you need. Give the team a heads-up for longer breaks so support and on-call handoffs stay covered.
• Equipment stipend — Home office setup — desk, monitor, chair, whatever actually makes you productive.
• Learning budget — Courses, books, and conferences tied to your role. Scraping conferences, writing workshops, support tooling — all fair game.
• Health benefits — Health coverage for full-time team members. Details and eligibility depend on location; we walk through it during hiring.