Team

The people behind Social Fetch

We write the docs, answer the support threads, and keep the fetch layer up. This is the team you will actually hear from.

Team
7 people
Focus
Docs, support, fetch
Location
Remote, worldwide
Hiring
Slowly, deliberately

People

Who you'll hear from

  • Luke Askew

    Social data APIs

    • Social data APIs
    • Reliability
    • API design
    • TypeScript

    Founder of Social Fetch. Writes about social-data APIs, reliability, and the production incidents that forced better timeouts, envelopes, and billing.

    Posts
  • Jade

    Developer onboarding

    • Developer onboarding
    • API operations
    • Usage and billing
    • Support operations

    Operations at Social Fetch. Jade writes about developer onboarding, usage, and the stretch between a first API key and a production job that stays up.

    Posts
  • Sarah

    Customer support

    • Customer support
    • Request IDs
    • Billing and credits
    • Integrations

    Customer support at Social Fetch. Sarah lives in email threads and `meta.requestId` — billing, credits, 429s, and the failed call an hour before a demo. She writes the replies developers can act on: a corrected curl, the right doc section, or an honest "it's on us."

    Posts
  • Michael

    Incident communication

    • Incident communication
    • Platform drift
    • Support escalations
    • Retry strategy

    Customer support at Social Fetch. Michael writes about platform drift, failed jobs, and the incident notes customers can actually use — request IDs, sample URLs, and a retry path that works.

    Posts
  • Emily

    SEO content

    • SEO content
    • Technical tutorials
    • Developer education
    • Use cases

    SEO content at Social Fetch. Emily writes integration guides and tutorials with working curl examples and real endpoint names — the pages developers finish, not just skim.

    Posts
  • David

    Web scraping

    • Web scraping
    • Schema drift
    • Anti-bot
    • Fetch reliability

    Web scraping specialist at Social Fetch. David writes about schema drift, empty parses, and the Instagram or TikTok change that breaks a fetch overnight.

    Posts
  • Jessica

    SEO content

    • SEO content
    • Commercial comparison
    • Platform coverage
    • Product accuracy

    SEO content at Social Fetch. Jessica writes comparison pages and platform guides — which endpoint to hit, what a live API actually returns, and how Social Fetch stacks up against tools like Apify.

    Posts

Publishing

Company byline

Some posts are published under the Social Fetch organisation rather than an individual. That byline is used for product updates, shipping notes, and anything that speaks for the whole team.

The Social Fetch team publishes shipping notes, API design essays, and production post-mortems for developers who need live social and web data without running scrapers.

Hiring

Want to work with this team?

We hire slowly and deliberately. Open roles are listed on the careers page — or email us if you think you should be here.

support@socialfetch.dev

What we look for

  • People who write clearly — docs are the product surface
  • Comfort owning a problem end to end
  • Genuine interest in the data we work with