Business Development Representative (BDR)

Overview

You're prospecting into mid-market and enterprise companies to book discovery meetings for AEs who sell Databricks' unified data and AI platform. Your targets are data engineers, analytics directors, and CDOs at companies spending money on data warehouses, ETL tools, and ML platforms. You're explaining why they should consolidate onto Databricks instead of using Snowflake, AWS Glue, or a patchwork of point solutions.

Role Snapshot

Company Context

Stage: Late-stage private (Series I, $43B valuation, likely pre-IPO)

Size: 14,777 employees

Growth: Rapidly scaling - hiring across all GTM roles, expanding into AI/ML use cases beyond traditional data engineering

Market Position: Leader in lakehouse category (they essentially created it), but Snowflake is the main competitor everyone knows. Also competing against cloud-native solutions (AWS, Azure, GCP data tools) and legacy players (Teradata, Oracle).

GTM Reality

Pipeline Sources:

• 30-40% Inbound - leads from website, product-led growth (free community edition trials), conference booth scans, webinar attendees. Quality varies widely - some are tire-kickers wanting free Spark, others are legitimately evaluating.
• 50-60% Outbound - you build lists in ZoomInfo/LinkedIn Sales Nav, run multi-touch sequences (calls, emails, LinkedIn). Targeting companies with data engineering headcount or known Snowflake/AWS spend.
• 10% Partners/Referrals - cloud marketplaces (AWS, Azure, GCP) generate some co-sell opportunities

SDR/AE Structure: Dedicated BDRs feed meetings to territory-based AEs. You'll support 2-3 AEs typically.

SE Support: AEs have dedicated Sales Engineers for demos - you don't run technical calls, just book the first meeting.

Competitive Landscape

Main Competitors:

• Snowflake (data warehouse, main comparison point)
• AWS suite (Glue, Redshift, SageMaker)
• Microsoft Azure (Synapse, Fabric)
• Google BigQuery

How They Differentiate: "Lakehouse" architecture (open-source Delta Lake) vs proprietary data warehouse. Unified platform for data engineering AND data science vs point solutions. Apache Spark performance vs SQL-only warehouses.

Common Objections:

• "We're happy with Snowflake" (this is 40% of your calls)
• "We already use AWS/Azure/GCP tools"
• "Too expensive" (it is - but you're not pricing, just booking meetings)
• "Not ready to evaluate, just did a migration"

Win Themes: Orgs tired of managing 5+ tools, teams doing ML/AI (not just BI), companies with massive data scale (petabytes), open-source preference over vendor lock-in.

What You'll Actually Do

Time Breakdown

Cold Outreach (50%) | Inbound Follow-up (25%) | Admin/Meetings (25%)

Key Activities

• Cold Calling: 50-70 dials/day to data engineers, analytics managers, and IT directors. Most don't answer. When they do, you have 30 seconds to explain why Databricks before they hang up. You're not demoing - just trying to get 15 minutes on their calendar.
• Email Sequences: Writing personalized emails referencing their tech stack (you can see if they're hiring Spark engineers, posting about Snowflake costs on LinkedIn, etc.). A/B testing subject lines. Most emails get ignored.
• Inbound Lead Qualification: Calling website form fills and trial signups within 5 minutes. Half are students or consultants, not real buyers. The real ones often need education on what Databricks even is.
• Meeting Coordination: Scheduling discovery calls between prospects and AEs, prepping handoff notes, joining first 5 minutes to intro the AE. Tracking which meetings turn into opportunities (your conversion metric).

The Honest Reality

What's Hard

• High rejection rate: Data engineers don't want to talk to salespeople. You'll get a lot of "send me an email" and ghosting. It takes 8-12 touches on average to get a response.
• Technical product: You need to understand lakehouse vs warehouse, Delta Lake, Apache Spark, ML workflows - enough to sound credible to engineers. They'll sniff out if you're faking it.
• Crowded market: Everyone knows Snowflake. Databricks requires more education ("what's a lakehouse?"), which makes cold calls harder. You're often the underdog in competitive evals.
• Long feedback loop: You book a meeting, but won't know for 6-12 months if it becomes revenue. Your success is measured on meeting volume, not closed deals, which can feel disconnected.

What Success Looks Like

• Hitting 15-20 qualified meetings per month consistently (qualified = right persona, active project, budget/authority)
• 30-40% of your meetings convert to opportunities (AE accepts it as real pipeline)
• Becoming the go-to BDR for a territory - AEs request you specifically because your meetings are high-quality

Who You're Selling To

Primary Buyers:

• Director/VP of Data Engineering (owns the platform decision)
• Head of Analytics/Chief Data Officer (cares about consolidation and cost)
• ML Engineering Leaders (need unified data + ML platform)

What They Care About:

• Performance at scale: Can it handle petabyte-scale data without falling over?
• Unified platform: Tired of integrating Fivetran + Snowflake + Sagemaker + DBT
• Open source: Don't want vendor lock-in, want Delta Lake's openness
• TCO: Snowflake bills are getting out of control, looking for alternatives

Requirements

• 0-2 years in sales/BDR role (or new grad with strong technical curiosity)
• Comfortable cold calling technical personas who don't want to talk to you
• Ability to learn technical concepts (you don't need to be an engineer, but you'll study up on data architectures)
• Resilience with rejection - this is high-volume outbound to skeptical buyers
• Chicago-based (hybrid role, expect 2-3 days/week in office)