Technical Writer

Youll own how Firecrawl explains itself to developers and how developers find us in the first place. That spans docs API reference SDK guides quickstarts 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 at all. Youll own the writing end to end and youll treat search and LLM discoverability as part of the craft not an afterthought you hand to someone else.

Youll 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 whats possible.

Salary Range: $160000 to $200000/year (Range shown is for U.S.-based employees in San Francisco CA. Compensation outside the U.S. is adjusted fairly based on your countrys cost of living. You can explore how we calculate this here: 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

About Firecrawl

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 just a year weve hit 8 figures in ARR and 135k GitHub stars by building the fastest way for developers to get LLM-ready data.

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

What Youll Do

• Own the docs end to end: API reference SDK guides quickstarts 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 youre 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 changelogs and the docs updates that ride alongside new features.

• Triage and respond to docs feedback from GitHub Discord and support. The docs are a product. They get bugs. You fix them.

What Were Looking For

A writer who can actually code. You dont 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 dont run neither does the documentation.

Experience writing for developers. Youve 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. Youve 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 2000-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 whats 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 Were NOT Looking For

• Writers who cant read code or who outsource every example to an engineer.

• Pure content marketers without the technical depth to write real docs.

• SEO specialists who optimize content they cant write themselves.

• Anyone who needs a full editorial calendar handed to them before they can produce.

• Writers who think developer content means listicles and thought leadership.

A Note On Pace

Were a small team doing a lot. Roles here are loosely defined on purpose. Youll own things that dont have a clear owner yet and thats a feature not a bug. If you need your scope fully defined before you can move this probably isnt the right fit. If you want to write the docs and content behind one of the fastest-growing developer tools on the internet lets talk.

Benefits & Perks

Available to all employees

Salary that makes sense $160000$200000/year (SF U.S.-based) based on impact not tenure

Own a piece Up to 0.05% equity in what youre helping build

Generous PTO 15 days mandatory anything after 24 days just ask (holidays excluded); take the time you need to recharge

Parental leave 12 weeks fully paid for moms and dads

Wellness stipend $100/month for the gym therapy massages or whatever keeps you human

Learning & Development Expense up to $1000/year toward anything that helps you grow professionally

Team offsites A change of scenery minus the trust falls

Sabbatical 3 paid months off after 4 years do something fun and new

Available to US-based full-time employees

Full coverage no red tape Medical dental and vision (100% for employees 50% for spouse/kids) no weird loopholes just care that works

Life & Disability insurance Employer-paid short-term disability long-term disability and life insurance coverage for lifes curveballs

Supplemental options Optional accident critical illness hospital indemnity and voluntary life insurance for extra peace of mind

Doctegrity telehealth Talk to a doctor from your couch

401(k) plan Retirement might be a ways off but future-you will thank you

Pre-tax benefits Access to FSAs and commuter benefits (US-only) to help your wallet out a bit

Pet insurance Because fur babies are family too

Available to SF-based employees

SF HQ perks Snacks drinks team lunches intense ping pong and peak startup energy

E-Bike transportation A loaner electric bike to get you around the city on us

Interview Process

Application Review Send us your work: links to docs tutorials or technical content youve written. A short note on what youd want to understand about Firecrawls current docs before you started.

Intro Chat (20 min) Quick alignment call. Well talk about what youve written how you work with engineers and what youd prioritize first.

Writing Sample (take-home) Pick a real Firecrawl feature read the existing docs and rewrite one page. Were looking at how you read the product how you structure information and whether your examples actually run.

Deep Dive Chat (60 min) Walk us through a piece of writing youre proud of and one youd redo. Then a live scenario: how would you approach the first 30 days of docs and content work at Firecrawl

Founder Chat (30 min) Culture pace ownership and how you like to work. Time for your questions too.

Decision We move fast.

If you want to write the docs and content behind one of the fastest-growing developer tools on the internet this is your shot.

Apply now.