Careers
Join us as we scale Social Fetch.
We're hiring a small, remote team to keep our social data API reliable, documented, and easy to integrate.
We're a small company (you'll know everyone by name within your first week). Engineering, support, and content overlap more than they would at a 200-person SaaS shop. That means less process theatre and more direct impact — but it also means you'll sometimes do work outside a narrow job description when something urgent lands.
Open roles
Web Scraping Specialist
Own scraper reliability across 20+ social platforms: anti-bot challenges, schema drift, rate limits, and the weird edge cases that break production jobs at 2am.
Remote — worldwideFull-time£55,000 – £85,000SEO Content Writer
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.
Remote — worldwideFull-time£35,000 – £55,000Customer Support Agent
Handle email support for a social data API — triage errors with requestIds, answer billing and integration questions, and escalate real bugs to engineering with enough context to fix them.
Remote — worldwideFull-time£28,000 – £42,000
How we work
Fully remote, worldwide. No office to commute to and no expectation that you're online 9–5 in a particular timezone. We communicate in writing — Slack for day-to-day, Linear for engineering work, email for customer-facing threads. Meetings are rare and usually recorded so people in other timezones can catch up async.
We hire adults and treat them that way. Flexible hours are the default, not a perk you have to ask for. What we care about is whether the scrapers stay up, the docs stay accurate, and customers get unblocked — not whether your Slack status was green at 10am.
Honest caveat: we're not a big-company remote operation with dedicated people ops and a formal career ladder. You'll have real ownership, but you'll also figure some things out as you go. If you need heavy structure and a manager in the same city, we're probably not the right fit.
Why join
Small team, real ownership
You won't disappear into an org chart. The scraper fix you ship on Tuesday is in production by Wednesday. The guide you publish shows up in search results next month. Support replies you write become the template everyone else uses.
Developer-first product
We sell to engineers. Docs, error codes, `meta.requestId` on every response, and API stability aren't marketing copy — they're what customers pay for. If you've been frustrated by API vendors who treat docs as an afterthought, you'll fit in here.
Hard problems, clear scope
Social platforms change without warning. Schema drift, bot detection, partial JSON blobs buried in HTML — the work is messy and never finished. If you like figuring out why a fetch broke and making it stay fixed, there's plenty to do.
Remote by default
Distributed across timezones, hired for skill not postcode. We overlap where it helps (support leans US/EU; engineering is mostly async) but nobody's counting your hours on a timesheet.
Questions before you apply? Email jobs@socialfetch.dev—we read every message.