Technical BDR

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 more direct revenue path.

What We're NOT Looking ForVolume-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.

Clock-watchers. We move fast because the window for what we're building won't stay open forever. If urgency stresses you out rather than energizes you, this probably isn't the fit.

A Note On PaceWe operate at an absurd level of urgency because the window for what we're building won't stay open forever. If that excites you, keep reading. If it doesn't, no hard feelings — but this role probably isn't for you.