Hannah Olson

Business Development Representative (BDR)

MuleSoft

BDROutbound HeavyConsultativeOn-site📍 San Francisco, CA
Posted by Hannah Olson•

Overview

You're a BDR at MuleSoft (owned by Salesforce since 2018) selling API integration and connectivity software to enterprise IT organizations. Your job is to cold prospect into accounts, qualify their integration needs, and book discovery calls for AEs. You're not closing deals—you're getting meetings with directors and VPs who are dealing with legacy systems, data silos, or digital transformation projects.


Role Snapshot

AspectDetails
Role TypeOutbound BDR (meeting setter)
Sales MotionOutbound-heavy with some inbound lead follow-up
Deal ComplexityN/A - you're qualifying, not closing
Sales CycleN/A - your metric is meetings booked
Deal SizeN/A - AEs handle pricing
Quota (est.)15-20 qualified meetings/month

Company Context

Stage: Public (acquired by Salesforce in 2018 for $6.5B)

Size: ~1,400 employees (part of Salesforce's larger org)

Growth: Mature product with established enterprise customer base; hiring BDRs suggests continued expansion

Market Position: Leader in enterprise integration/API management space, competing against legacy players and newer platforms


GTM Reality

Pipeline Sources:

  • 70% Outbound - you're building lists, cold calling, and running email sequences into target accounts
  • 20% Inbound - some marketing-generated leads from events, content downloads, website forms
  • 10% Internal referrals - existing Salesforce customer cross-sell opportunities

SDR/AE Structure: Dedicated BDR team feeding a pool of AEs. You book meetings, AEs run them. Clear handoff process.

SE Support: AEs work with Sales Engineers for technical demos—you won't be doing technical selling, just qualifying technical pain points.


Competitive Landscape

Main Competitors: Dell Boomi, Informatica, Workato, Jitterbit, Tibco, custom-built integrations

How They Differentiate: Anypoint Platform positioning (design, build, manage APIs in one place), Salesforce ecosystem connection, strong brand in enterprise IT

Common Objections:

  • "We already have an integration tool"
  • "We're building this internally"
  • "Too expensive for our needs"
  • "We're in the middle of another IT project"

Win Themes: Faster time to market, unified platform vs point solutions, scales with enterprise complexity, Salesforce integration if they're already a customer


What You'll Actually Do

Time Breakdown

Cold Calling (35%) | Email/LinkedIn (25%) | Research (15%) | Meetings/Admin (15%) | Coaching/Training (10%)

Key Activities

  • Cold Calling: 50-70 dials per day to IT leaders (CIOs, VPs of Engineering, Directors of IT, Integration Architects). Most don't answer. You're trying to catch them at their desk and have a 2-minute conversation about integration challenges.
  • Email Sequences: Running multi-touch cadences (6-8 touches over 2-3 weeks) using Outreach or SalesLoft. You're A/B testing subject lines and personalizing based on recent company news or tech stack research.
  • Account Research: Looking up companies on LinkedIn, checking their tech stack on BuiltWith or similar tools, finding integration pain points in job postings or press releases. You're building context so your outreach doesn't sound generic.
  • Qualification Calls: When someone responds, you run a 10-15 minute discovery to understand their integration landscape, current tools, pain points, and timeline. You're looking for BANT (Budget, Authority, Need, Timeline) indicators to pass to an AE.
  • CRM Hygiene: Logging everything in Salesforce. Your manager tracks your activity metrics closely (calls, emails, meetings set, show rates).
  • Internal Syncs: Daily standup with your BDR team, weekly 1-on-1s with your manager, regular feedback sessions with AEs on lead quality.

The Honest Reality

What's Hard

  • Rejection Volume: You get rejected constantly. Most calls go to voicemail. Most emails get ignored. You need thick skin and short memory.
  • Technical Learning Curve: You're talking about APIs, microservices, legacy systems, cloud migrations. You don't need to be an engineer, but you need to sound credible when asking about their integration stack.
  • Gatekeeper Battles: Getting past EAs and front desks to reach decision-makers. You'll hear "send me an email" or "we're not interested" dozens of times per day.
  • Meeting Show Rates: Not everyone you book actually shows up. Probably 70-75% attendance. AEs will push back if you're booking unqualified meetings just to hit numbers.
  • Quota Pressure: You're tracked on daily activity and monthly meeting quotas. If you're not hitting your number, you'll get coached hard or put on a performance plan.
  • Repetitive Work: Same conversations, same objections, same pitch, different person. It can feel like Groundhog Day.

What Success Looks Like

  • Consistently booking 15-20 qualified meetings per month (meetings where the AE agrees it was worth their time)
  • 70%+ meeting show rate (prospects actually attend)
  • Getting promoted to AE in 12-18 months if you perform well
  • Building a foundation of B2B sales skills—research, cold calling, objection handling, qualification

Who You're Selling To

Primary Buyers:

  • VP of Engineering / CTO at mid-market and enterprise companies (500-5000+ employees)
  • Director of IT / IT Managers dealing with system integration projects
  • Integration Architects / Technical Leads evaluating tools
  • Digital Transformation executives running modernization initiatives

What They Care About:

  • Reducing time spent on custom integration work (developer productivity)
  • Connecting legacy systems to modern cloud apps without rip-and-replace
  • Standardizing how APIs are built and managed across the org
  • Scalability and governance as integration complexity grows
  • ROI and speed to value (they've been burned by long implementation projects)

Requirements

  • Bachelor's degree (they'll enforce this at Salesforce)
  • 0-2 years of experience (this is an entry-level sales role)
  • Willingness to cold call 50+ times per day without getting discouraged
  • Some technical curiosity—you don't need to code, but you should be comfortable learning basic IT/software concepts
  • Coachability—you'll get a lot of feedback on your pitch, tonality, and messaging
  • Ability to work in-office in San Francisco (this is not a remote role based on the posting)
  • Comfort with high-activity metrics and being measured on numbers daily