Technical BDR

Firecrawl

Where
San Francisco, CA
Pay
$130K to $190K a year
Type
Full time

Posted 3 months ago· Checked live at Firecrawl 2 hours ago

Stale: open 107 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 2 hours ago.
What is the job?
You'll open Firecrawl's outbound motion: finding, engaging, and qualifying the engineers, data scientists, and AI/ML leads who need to turn messy web data into structured, LLM-ready output. This isn't a volume BDR seat. You'll combine real technical fluency with relentless outbound execution to open doors that only someone who speaks the buyer's language can open.
What does it pay?
$130K to $190K a year, as the posting states.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

You'll open Firecrawl's outbound motion: finding, engaging, and qualifying the engineers, data scientists, and AI/ML leads who need to turn messy web data into structured, LLM-ready output. This isn't a volume BDR seat. You'll combine real technical fluency with relentless outbound execution to open doors that only someone who speaks the buyer's language can open.

Salary Range: $130,000–$190,000 USD/year OTE

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

Location: San Francisco, CA (SF HQ). On-site, five days a week.

Job Type: Full-Time

Experience: 3+ years in a technical role (engineering, developer relations, solutions, or technical founding) with a pull toward the commercial side

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 outbound pipeline: Research and target engineering teams, AI startups, and data-heavy orgs that need web extraction at scale. Build sequences that land because they're technically relevant, not generic
  • Speak their language: Engage prospects on their terms. Reference their stack, understand their scraping pain, and articulate how Firecrawl's API solves problems they've been duct-taping around
  • Qualify with depth: Run discovery calls that go beyond BANT. Understand the technical use case, map the decision-making process, and hand off deals to AEs with context that accelerates close
  • Run live technical intros: Demo the product on first calls when it makes sense. You don't need to be a solutions architect, but you should be able to show a prospect how a simple API call turns a URL into clean data
  • Feed product intelligence: Surface patterns from the field (what prospects are building, what's blocking adoption, what competitors are doing) and relay it to Product and Engineering
  • Iterate relentlessly: Test messaging, channels, sequences, and personas. Treat outbound like a product: measure, learn, ship improvements

What we're looking for

  • Engineer-first, BDR-second. We can teach you sales. We can't fast-track deep technical intuition. You've spent at least a few years in a technical seat (shipping code, supporting developers, building a product, or running your own outbound as a technical founder) and you're drawn to the commercial side of technology
  • Technically fluent. You can read code, use APIs, talk about web scraping, and understand what LLM-ready data means. You've built things, even if they're small
  • Urgency is your default setting. You don't wait for permission, process, or perfect information. You move. You follow up. You close the loop same-day
  • Bias for action over analysis. You'd rather send 10 imperfect outbounds and learn than spend a week crafting the perfect email. Speed compounds
  • Thrives in complexity and ambiguity. You don't need a playbook to get started. You can navigate a messy prospect landscape and figure out who to talk to, what to say, and when to say it
  • Curious and relentless. You dig into a prospect's GitHub, read their blog, understand their stack. You earn the right to their time
  • Clear communicator. You write crisp emails and run tight calls. You know when to go technical and when to zoom out

Backgrounds that often do well: engineers who want to move into a commercial role. Technical founders who've done their own outbound. Developer advocates or solutions engineers looking for a more direct revenue path. Sales engineers who'd rather open the door than walk through it.

What we're not looking for

  • Volume-only dialers. If your playbook is blast 200 generic emails and hope, this isn't the role. Every touch should show you understand the prospect's world
  • Non-technical "relationship builders." Rapport matters, but you earn trust through relevance and technical credibility, not small talk
  • People who need a finished playbook. We're building the motion as we go. If you need someone to hand you a script, a list, and a cadence tool before you can start, you'll stall here

Similar open jobs

Sales development rep jobs in San Francisco (88)Jobs in San Francisco (11750)