Technical BDR

Technical BDR TECHNICAL BDR You'll be the tip of the spear for Firecrawl's outbound motion — identifying, engaging, and qualifying technical buyers (engineers, data scientists, AI/ML leads) who need to turn messy web data into structured, LLM-ready output. This isn't a dial-and-smile BDR seat. You'll combine technical fluency with relentless outbound execution to open doors that only someone who speaks the buyer's language can open. Salary Range: $120,000–$220,000/year OTE (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living. You can explore how we calculate this here: https://www.firecrawl.dev/careers/compensation.) Equity Range: Up to 0.10% Location: Remote (Americas, UTC-3 to UTC-10) Job Type: Full-Time or Contract Experience: 3+ years or equivalent shipped systems Visa: N/A (Remote) ABOUT FIRECRAWL Firecrawl is the easiest way to extract data from the web. Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call. In just a year, we've hit 8 figures in ARR and 90k+ GitHub stars by building the fastest way for developers to get LLM-ready data. We're a small, fast-moving, technical team building essential infrastructure super-intelligence will use to gather data on the web. We ship fast and deep. 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. The ideal candidate has a technical background — maybe you've shipped code, built side projects, contributed to open source, or studied CS/engineering — 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. CS students who've done hackathons and side projects. Technical founders who've done their own outbound. Developer advocates looking for a ... (truncated, view full listing at source)