content
Posted 3 weeks agoIn-House Technical Writer
at Firecrawl
San Francisco, United StatesHybrid
Requirements
- IN-HOUSE TECHNICAL WRITER You'll own how Firecrawl explains itself to developers — across docs, API reference, SDK guides, quickstarts, tutorials, cookbooks, and the technical content that lives between marketing and engineering.
- This role sits at the intersection of product and growth: the docs are the product surface developers hit first, and the technical content is how they discover us in the first place.
- In just a year, we've hit 8 figures in ARR and 120k+ GitHub stars by building the fastest way for developers to get LLM-ready data.
- WHAT YOU'LL 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. - 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 the things 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. - Partner with the growth team on technical content that compounds: SEO-relevant tutorials, comparison guides, and the cookbook entries that show up when someone searches for the problem we solve. - Triage and respond to docs feedback from GitHub, Discord, and support.
- The docs are a product. They get bugs. You fix them.
- 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.
- Experience writing for developers.
- You know what good docs look like (Stripe, Twilio, Vercel, Supabase) and you know why those docs work.
- 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.
- If you want to write the docs and content behind one of the fastest-growing developer tools on the internet, let's talk.
- benefits — Access to FSAs and commuter
- A short note on what you'd want to understand about Firecrawl's current docs before you started.
- Writing Sample (take-home) — Pick a real Firecrawl feature, read the existing docs, and rewrite one page.
- 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.
- 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.
Benefits
- 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.) 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 ABOUT FIRECRAWL Firecrawl is the easiest way to extract data from the web.
- BENEFITS & PERKS AVAILABLE TO ALL EMPLOYEES Salary that makes sense — $160,000–$200,000/year (SF, U.S.-based), based on impact, not tenure Own a piece — Up to 0.05% equity in what you're 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
- 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 you've written.
Additional details
- You'll work closely with the growth marketing 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 show developers what's actually possible.
- Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call.
- We're a small, fast-moving, technical team building essential infrastructure superintelligence will use to gather data on the web.
- If your code examples don't run, neither does the documentation.
- You write for the developer who wants to skim, find the snippet, and ship.
- You notice when an example is technically correct but practically useless.
- You push back when a feature ships with a confusing name.
- Comfortable working without a content brief for every piece.
- 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.