Technical Bdr positions focus on delivering results in their domain. This page aggregates open Technical Bdr roles and what employers typically expect.
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: $140,000-$185,000/year OTE Equity Range: Competitive equity — details shared during the process. Location: San Francisco, CA (Hybrid, on-site required) Job Type: Full-Time Experience: 3+ years or equivalent shipped systems Visa: Must be legally authorized to work in the United States. We're not able to sponsor visas right now, though that may change down the line. ABOUT FIRECRAWL Firecrawl is the easiest way to turn the web into data AI agents can use. One API call converts any URL into clean, LLM-ready markdown or structured data - the boring-hard problem everyone building with LLMs eventually hits, solved. We hit 8 figures in ARR in year one and more than doubled it in year two. We have 150k+ GitHub stars, and developers, agents, and category-defining AI companies build on us every day. Growth like this is rare, and we're just getting started. We're a small team punching far above our weight. Everyone here owns a real piece of the product and company, end to end, and runs it themselves - no hiding behind process or headcount. This is a place for people who want to work at the frontier: an AI company building the infrastructure other AI companies run on, not one bolting AI onto an existing product. We move fast, go deep, and are building the tools superintelligence will rely on to gather data from the web. 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…