AI Enablement Lead

Firecrawl

Where
Hybrid in San Francisco, CA
Pay
$235K to $260K a year
Type
Full time

Posted 45 days ago· Checked live at Firecrawl 1 hour ago

Stale: open 45 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Firecrawl asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Firecrawl's own hiring page 1 hour ago.
What is the job?
Firecrawl is looking for someone to own how we use AI internally. The thesis behind the role: a company's output used to scale with headcount, and ours scales with tokens, meaning how much compute we run and how well we turn it into shipped work. A small team that does this well operates like one several times its size, and the ceiling on that isn't budget, it's adoption.
What does it pay?
$235K to $260K a year, as the posting states.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

Firecrawl is looking for someone to own how we use AI internally. The thesis behind the role: a company's output used to scale with headcount, and ours scales with tokens, meaning how much compute we run and how well we turn it into shipped work. A small team that does this well operates like one several times its size, and the ceiling on that isn't budget, it's adoption.

Salary Range: $235,000–$260,000 USD/year

Equity Range: Competitive equity. Details shared during the process.

Location: San Francisco, CA (SF HQ). Hybrid, onsite 3+ days a week.

Job Type: Full-Time

Experience: 4+ years

Work Authorization: Open to candidates already authorized to work in the US. We also support H-1B transfers, F-1 OPT and STEM OPT, TN (Canada and Mexico), and E-3 (Australia). We’re not able to sponsor new H-1B visas for candidates outside the US.

What you'll do

  • Own the internal AI stack: the agent harnesses, configs, shared skills, and model routing every team uses. Set them up, keep them sharp, and ship changes as the tools change
  • Start with the revenue team. Learn how they actually work, find the jobs an agent should be doing, and get them running on it, then go team by team
  • Bring people who barely use agents along. Sit with them, build their first real workflow together, handle the skepticism and the "I'm faster doing it myself" honestly, and stay on it until it sticks
  • Work from our token spend data. Find who's burning tokens without output and who isn't using enough, then fix both. The second problem is usually the bigger one
  • Make cost per useful token a number we manage: model choice, routing, caching, and cutting the workflows that don't pay for themselves
  • Explain the why, over and over. Help every team understand what scaling with tokens means for their work and why it matters, in their language, not yours
  • Build what's missing in code (MCP servers, hooks, evals, internal tooling), and track what's changing in Claude Code, Cursor, Codex, and whatever's next so we're working the new way the same week

What we're looking for

  • You get why scaling with tokens matters, and you can explain it to a salesperson, a lawyer, and an engineer in words each of them would use. A team that spends more on inference and ships more is winning. A team that spends more and doesn't isn't. You know how to tell the two apart
  • You've rolled out coding agents or AI tooling across a team and can show what changed after. An adoption, not a pilot
  • EQ. You can tell the difference between someone who's resisting and someone who's scared, and you know that most "I don't have time to learn this" is the second one. You bring people along without making them feel behind
  • An engineer or a very technical operator who lives in Claude Code, Cursor, or Codex and writes code. When the harness is missing something, you build it
  • You think about cost per useful token, and you've looked at spend data and changed something because of it
  • You teach by showing. Pairing for an hour beats writing a guide nobody reads
  • AI-pilled, bias to action, all in. You believe this is how work gets done now and you're already operating that way
  • Often an ex-founder, an early startup engineer, or the person who led your last team through a tooling change nobody wanted and made it stick

What we're not looking for

  • Prompt-tips influencers. A following built on "10 prompts that will change your life" isn't a track record
  • Change-management consultants. You should be good at change management. You should not need a framework, a steering committee, or a deck to do it. We need the adoption, done by you, in the room
  • IT admins. This isn't seat provisioning and license management
  • Someone who wants to tell the team how to use AI without using it harder than anyone else here
  • Someone who thinks the hard part is the tooling. The hard part is people

Similar open jobs

Jobs in San Francisco (11750)