Senior Growth Engineer

What You'll Do

• Own growth projects end-to-end: Scope the work, write the frontend and backend, ship to production, and iterate based on what the data says. Move in days and weeks, not quarters.
• Build in-product growth features: Ship the onboarding, activation, retention, and expansion surfaces that turn signups into paying customers: usage dashboards, contextual upgrade prompts, feature discovery, guidance states.
• Improve the playground: Our highest-leverage conversion surface. Make it faster, smarter, and easier for a developer to go from "trying it" to "using it."
• Ship conversion landing pages: Own the pages closest to conversion: partner integrations, competitive comparisons, use cases, campaign pages. Full stack: component, copy scaffolding, data layer, and the API endpoints behind anything interactive.
• Build internal tooling: Ship the UIs the Product Growth team uses to operate: customer dashboards, outreach interfaces, manifest views, triage tools. Turn repeatable manual work into software.
• Run experiments and measure: Instrument what you build. Run real A/B tests. Know whether the thing worked before shipping the next thing.
• Improve developer experience where it touches growth: SDK ergonomics, sample code, starter templates, first-run experiences. The surfaces where activation lives or dies.

What We're Looking For

Strong full-stack engineer. You ship production code across React, TypeScript, Next.js, and Node. You're comfortable in Python and SQL too. You've owned real features end-to-end, not just frontends or just APIs.

Product-minded with taste. You can look at a flow or a page and tell what's broken before the data does. You care about the details, and you can shape what you're building without needing a spec handed to you.

Growth-oriented. You think in funnels, activation curves, and conversion rates. You want to know how your work moved the number, not just whether it shipped. You instrument everything.

AI-native. You already use AI tools daily as core work infrastructure. You've pushed Claude, Copilot, or similar tools far enough to know where they help and where they don't. You use them to ship more, faster.

Fast and scrappy. You ship working versions, not perfect plans. You know when a one-off script is better than a framework and when a quick fix is better than an abstraction. You'd rather ship four experiments this week than one polished feature next month.

Clear communicator. You can explain what you built and why to non-technical teammates. You write good PR descriptions and document what's worth documenting.

Bonus Points

• You've shipped in-product growth features at a developer-tools or SaaS company: onboarding, activation, upgrade surfaces, in-product guidance.
• You've built conversion landing pages that measurably moved signup or activation, not just static pages that shipped.
• You've built internal tools that the team you worked with actually used every day.
• You've run real A/B tests and can talk about what you learned, not just what you shipped.
• Experience with our stack: Next.js, React, Tailwind, TypeScript, Vercel, PostgreSQL, Anthropic Claude API.
• You've built with LLMs in production: prompt engineering, tool use, inference pipelines.
• You've worked on developer-facing products: SDKs, playgrounds, docs surfaces, APIs.
• You know what "scaling chaos" feels like at a company doing 5M-50M ARR.

What it Means to Join Firecrawl

• Ship the Growth Number: The surfaces you build are how Firecrawl activates, expands, and retains customers. Every feature is a lever, and the impact is visible.
• High Leverage: One well-built flow can move activation by double-digit percentages. Your work is measurable and shipped to every user.
• Autonomy: Own your work. We care about outcomes, not hours. Ship what matters, skip what doesn't.
• Growth Path: Start as the senior IC. As the team grows, you'll have the option to lead engineers or go deeper technically.
• Remote-First Culture: Collaborate from anywhere, or work out of our SF HQ.