Senior Growth Engineer
TypeScript • Next.js • Experimentation | San Francisco / Bay Area (Hybrid) | Full-time
Compensation $225K - $290K base salary
Equity Competitive equity, with details shared during the process
Location San Francisco, CA / Bay Area, CA (hybrid)
Employment Full-time
Visa sponsorship Open to visa transfers (e.g. OPT, H1B transfers). Further sponsorship is
open to discussion for truly exceptional candidates but is not standard
practice currently
Tech stack TypeScript, Node.js, React, Next.js, Tailwind CSS, Vercel, REST APIs,
PostgreSQL, SQL, Python, LLM APIs (Anthropic Claude API), Datadog,
Mixpanel, Amplitude, PostHog
Reports to VP of Revenue and Success
Team Hiring 1-2 engineers for this role
About the Role
You'll write the code that turns developers discovering Firecrawl into developers who can't live without
it. This is a full-stack engineering role pointed entirely at growth: you'll own the signup, activation,
onboarding, and conversion experience, and you'll be measured on the funnel metrics you move, not
just the features you ship. You'll instrument, experiment, build, and iterate on the product surfaces
that drive the product-led growth motion, and you'll own real conversion outcomes from day one.
About Firecrawl
Firecrawl is the easiest way to turn the web into data AI agents can use. One API call converts any
URL into clean, LLM-ready markdown or structured data, solving the boring-hard problem everyone
building with LLMs eventually hits. Firecrawl hit 8 figures in ARR in year one and more than doubled it
in year two, with 147k+ GitHub stars and developers, agents, and category-defining AI companies
building on it every day.
It's a small team punching far above its weight. Everyone owns a real piece of the product and
company, end to end, and runs it themselves. This is an AI company building the infrastructure other
AI companies run on, not one bolting AI onto an existing product.
What You'll Do
• Own the growth surfaces end to end: signup, activation, onboarding, and conversion
Senior Growth Engineer | Candidate Reference | Page 2
• Instrument the funnel, run experiments, and ship the changes that move real metrics
• Build full-stack, from the frontend a developer first touches to the backend that powers it
• Treat conversion and activation as your number: own it, measure it, and move it
• Work close to the data, form hypotheses, test them, and iterate fast on what works
What We're Looking For
• Experience: 5-12 years as a full-stack engineer with hands-on growth work as an individual
contributor at an early- or growth-stage startup
• Ownership of outcomes: You've personally owned a conversion, activation, or funnel metric and
moved it, with PLG features (onboarding, activation, upgrade prompts) shipped end to end
• Core skills: React, TypeScript, Next.js, and Node.js
• Experimentation: You think like a scientist (hypothesis, experiment, measure, iterate) and have
run real A/B tests you can talk about, including what you learned when they didn't go as planned
• Analytics: You've analyzed funnels (event tracking, SQL, product analytics) to find growth levers
• AI-native workflow: Fluent with AI coding tools (Cursor, Copilot, Claude Code) as daily
infrastructure
• Developer products: You understand how developers adopt tools (SDKs, playgrounds, docs,
APIs)
• Tenure: A track record of staying with your work long enough to see it through
• Pace: You move fast and close the loop. You'd rather ship, measure, and iterate than perfect on
paper
Nice to Have
• In-product growth surfaces shipped at a dev-tools or SaaS company (onboarding, activation,
upgrade flows, in-product guidance)
• Conversion pages that measurably moved signup
• Experience with our stack (Next.js, React, Tailwind, TypeScript, Vercel, PostgreSQL, the
Anthropic Claude API) or LLMs in production (prompt engineering, tool use, inference pipelines)
• Internal tooling that growth or product teams adopted
What We're NOT Looking For
• A growth marketer. This is an engineering role that writes production code
• A backend engineer with no interest in the product surface or the metrics
• Someone who has only shipped features without owning an outcome
• A pattern of short stints
