Jobs at Firecrawl

What Firecrawl's application asks

Across the one application form Otto has filled at Firecrawl: 11 distinct questions, 10 of them usually required. A single application works out at about 11 minutes once you have your details to hand. It runs on Ashby.

6 are Firecrawl’s own, not boxes every form has:

• describe a design or scope call you made on a library or primitive that you weren't 100% sure about going in…
• we already know why firecrawl matters. tell us why it matters to you.
• tell us about a repo you've maintained or made a significant contribution to. what did you actually own —…
• tell us about the worst version of your self-host or "getting started" experience you've shipped, and how you…
• linkedln
• this role requires in-person in sf. are you in the bay area or willing to move to the bay area? (if not, you…

Read off the forms themselves, last checked 2026-09-06, because Otto fills them in and has to read them first. Roles differ, so the estimate is per application rather than for the list above: each question counts for its cost times how often this employer actually requires it. A written answer is 2½ minutes, a dropdown 12 seconds, a yes/no 5 seconds, attaching a file 45 seconds. The list leaves out name-and-email boxes and anything Ashby puts on every employer’s form.