Technical BDR
- Market p25–p75
- $90k–$200k
- Firecrawl p25–p75
- $159k–$291kn=6
- Opened · 30d
- +0
- Closed · 30d
- −0
- Opened · 7d
- +41,17610% of open
- All other
- 623,046open
Technical BDR
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. You'll report to our VP of Deployment, and you're measured on qualified pipeline created, not emails sent.
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.
About Firecrawl
Firecrawl helps AI agents get the data they need through Alexandria (its library of official data providers), its own indexes, and the live web. Developers first turned to us because getting clean data from the web is harder than it looks. Today, Firecrawl has 200k+ stars on GitHub, and more than 1.5 million people build with it, including teams at 67 of the Fortune 100.
The open web is only part of what agents need. Much of the most useful knowledge, like company data, financial records and research, sits behind paywalls and private APIs. Firecrawl Alexandria brings that into the same API, and we pay the providers whose data agents use. We believe people who share what they know should be compensated.
Our Values
Bias to action: We move fast, ship hard, and don’t wait to be told.
Realistic about AI: We’re clear-eyed about what AI can and can’t do, and we keep pushing to use it where it actually works.
All in: The next few years matter a lot, and we’re all in for them.
Human connection: As intelligence gets cheaper, relationships with customers, partners, and each other matter more.
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