Small team, real ownership
You won't disappear into an org chart. A scraper fix ships Tuesday, it's in production Wednesday. A guide you publish shows up in search next month. Support replies you write become templates.
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 small — you'll know everyone within your first week. Engineering, support, and content overlap more than at a 200-person SaaS shop. Less process theatre, more direct impact, but sometimes work falls outside a narrow job description.
- Location
- Remote, worldwide
- Roles
- 3 open
- Replies
- Within days
- Recruiters
- No agencies
Hiring
Open roles
- Web Scraping SpecialistOwn scraper reliability across 25 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,000
- SEO Content WriterOwn 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,000
- Customer Support AgentHandle 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
Culture
How we work
Fully remote, worldwide. No office, no expectation you're online 9–5 in a fixed timezone. Slack for day-to-day, Linear for engineering, email for customer threads. Meetings are rare and usually recorded for async catch-up.
We hire adults and treat them that way. Flexible hours by default. What matters: scrapers stay up, docs stay accurate, customers get unblocked — not whether Slack was green at 10am.
We're not a big-company remote shop with dedicated people ops and a formal ladder. Real ownership, some figuring-it-out as you go. If you need heavy structure and a manager in the same city, we're probably not the fit.
Reasons
Why join
Developer-first product
We sell to engineers. Docs, error codes, meta.requestId on every response, and API stability aren't marketing — they're what customers pay for.
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.
How applying works
- Put the role title in the email subject line
- We usually reply within a few business days
- No recruiters or agencies, please