A remote Content role at Firecrawl. Writers who can't read code, or who outsource every example to an engineer.
Keywords this role’s ATS scans for
Sydicom tailors your CV and cover letter to match these.
How Sydicom helps: we read this listing’s requirements and tune your CV and cover letter to the keywords its ATS (Ashby) is scanning for, for candidates in United States, then help you apply.
Original listing text, shown exactly as published by the company.
What We're Looking ForA writer who can actually code. You don't need to ship production features, but you should be able to read a Python or TypeScript SDK, run an API call, debug your own example, and write a tutorial that works on the first copy-paste. If your code examples don't run, neither does the documentation.
Experience writing for developers. You've worked on a developer tool, API, SDK, or infrastructure product. You know what good docs look like (Stripe, Twilio, Vercel, Supabase) and you know why those docs work. You write for the developer who wants to skim, find the snippet, and ship.
A real command of how developers discover tools. You've written content that ranked, and you understand the newer game of getting surfaced inside LLMs. You know keyword research and on-page structure cold, you write for search intent without writing for robots, and you can point to content that drove measurable organic discovery. This is not a side skill for this role.
Range across docs and content. You can write a tight API reference page and a 2,000-word tutorial in the same week without one bleeding into the other. You know when to be terse and when to teach.
Strong taste and a high bar. You notice when an example is technically correct but practically useless. You rewrite your own drafts. You push back when a feature ships with a confusing name.
Comfortable working without a content brief for every piece. Eric will set direction on the bigger bets. The week-to-week (what needs updating, what's missing, what would actually help a developer right now) is yours to figure out and run with.
Backgrounds that often do well: technical writers from developer tool or API companies, former developers who moved into writing, DevRel engineers who spent more time writing than speaking, technical content marketers at PLG dev tools who can genuinely write docs.
What We're NOT Looking For
A Note On PaceWe're a small team doing a lot. Roles here are loosely defined on purpose. You'll own things that don't have a clear owner yet, and that's a feature, not a bug. If you need your scope fully defined before you can move, this probably isn't the right fit. If you want to write the docs and content behind one of the fastest-growing developer tools on the internet, let's talk.
Firecrawl
YC S22Content
18 open roles on Sydicom
Firecrawl is the web context API for AI agents. Search, scrape, parse, and interact with the live web to turn any source into clean Markdown or structured data your agents can ship with. Open source, ZDR-ready, and trusted by 80,000+ teams including Apple, Shopify, Canva, Zapier, and Lovable to power production AI.
Source: Y Combinator