Technical Writer

Technical Writer

You'll own how Firecrawl explains itself to developers, and how developers find us in the first place. That spans docs, API reference, SDK guides, quick starts, tutorials, cookbooks, and the technical content that lives between engineering and growth. Two things make this role work: the docs are the product surface developers hit first, and the technical content is how they discover us 'll own the writing end to end, and you'll treat search and LLM discoverability as part of the craft, not an afterthought you hand to someone else.

You'll work closely with the growth team, who owns growth and content strategy, while you own the writing itself: turning shipped features into clear documentation, and turning real product capabilities into tutorials and cookbooks that rank, get cited, and actually show developers what's possible.

Salary Range: $160,000 to $200,000/year (Range shown is for U.S.

-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living. You can explore how we calculate this here: https://(Use the "Apply for this Job" box below).)

Equity Range:
Up to 0.05%

Location:

San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)

Job Type: Full-Time

Experience:

4+ years writing for a technical or developer-facing product

Visa: US Citizenship/Visa required

Firecrawl is the easiest way to extract data from the web. Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call. In just a year, we've hit 8 figures in ARR and 135k+ Git Hub stars by building the fastest way for developers to get LLM-ready data.

We're a small, fast-moving, technical team building essential infrastructure superintelligence will use to gather data on the web. We ship fast and deep.

• Own the docs end to end: API reference, SDK guides, quick starts, conceptual explainers, and migration guides. When something ships, the docs ship with it.
• Write technical content that pulls developers in: tutorials, cookbooks, integration guides, and long-form pieces that show real use cases with real code.
• Own discoverability of everything you write. You understand how developers actually search now: traditional SEO and GEO (getting cited inside ChatGPT, Claude, Perplexity, and the other LLMs developers use to find tools). You write content that ranks and gets surfaced, and you can prove it moved.
• Build the content that compounds: SEO-relevant tutorials, comparison guides, and the cookbook entries that show up the moment someone searches for the problem we solve.
• Read the codebase, talk to engineers, and use the product yourself. The bar is that you understand what you're documenting well enough to catch what engineers forgot to mention.
• Maintain a consistent voice across docs and content. Clear, direct, no fluff, written for a developer who wants to ship something today.
• Partner with engineering on release notes, change logs, and the docs updates that ride alongside new features.
• Triage and respond to docs feedback from Git Hub, Discord, and support. The docs are a product. They get bugs. You fix them.

A writer who can actually code. You don't need to ship production features, but you should be able to read a Python or Type Script 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, Dev Rel engineers who spent more time writing than speaking, technical content marketers at PLG dev tools who can…