Software engineer
- Location
- San Francisco
- Type
- Full time
- Compensation
- $150k-$200k
- Posted
- 2 days ago
Join a team building useful software. Work closely with engineering and design to turn new ideas into products.
Find roles through people you trust, and message a verified founder or page admin about your interest.
Own SEO content for a developer API: long-form guides, tutorials, blog posts, and landing copy — with endpoint names and code samples that survive engineer review.
Careers
SEO Content WriterWrite the guides and comparison pages that help developers find us — and trust us enough to paste an API key.
Apply for this roleLocationRemote — worldwideTypeFull-timeSalary£35,000 – £55,000Posted19 Jun 2026LocationRemote — worldwideEmploymentFull-timeSalary£35,000 – £55,000 / yearHoursFull-time · flexible async hoursVisa sponsorshipCase-by-case — happy to discuss during hiring.Competitive for role and experience. Final offer depends on location and background.
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.
Culture
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.
Daily
Bar
Bonus
Package
Full-time team members receive:
Apply
Published articles, guides, or docs for a technical audience — especially anything with code samples or API walkthroughs.
We usually reply within a few business days. No recruiters or agencies, please.