SDR (Sales Development Representative)

Overview

You're prospecting into mid-market and enterprise companies to book qualified meetings for Account Executives. You're reaching out to engineering managers, DevOps leads, site reliability engineers, and security teams who currently use observability/logging tools like Splunk, Datadog, Elastic, or New Relic. Your pitch centers on data cost reduction and routing flexibility - essentially "we help you manage your log/telemetry data better and cut your observability bill."

Role Snapshot

Company Context

Stage: Growth stage (1,134 employees, expanding SDR team)

Size: 1,134 employees

Growth: Actively hiring 5+ SDRs, team is scaling

Market Position: Category player in data observability/pipeline space - competing against legacy observability vendors and newer data routing tools

GTM Reality

Pipeline Sources:

• 30-40% Inbound - MQLs from content downloads, free trial signups, demo requests (technical audience researching data management solutions)
• 60-70% Outbound - Cold calling and email sequences into target accounts, LinkedIn outreach to technical personas
• Small % from event follow-up and partner referrals

SDR/AE Structure: Dedicated SDR team (you're one of a growing org) feeding qualified meetings to AEs

SE Support: Not directly relevant to SDR role, but SEs support later-stage demos

Competitive Landscape

Main Competitors: Direct: Vector, Logstash, Fluentd (open source alternatives). Indirect: Observability platforms themselves (Splunk, Datadog, Elastic) that bundle data routing

How They Differentiate: Vendor-agnostic data pipeline layer - lets you route data to multiple destinations, transform it in-flight, and reduce volume/costs before it hits expensive tools

Common Objections: "Why not just use our current tool's built-in routing?", "Open source alternatives are free", "This adds another layer of complexity", "We're locked into our current vendor"

Win Themes: Cost reduction (especially for Splunk customers bleeding money), flexibility to use multiple tools, data volume reduction, avoiding vendor lock-in

What You'll Actually Do

Time Breakdown

Prospecting (60%) | Inbound Follow-up (25%) | Admin/Internal (15%)

Key Activities

• Cold calling technical personas: 50-70 dials/day to engineering managers, SREs, DevOps leads, security engineers. You're interrupting their day to talk about log management - most calls go to voicemail or get a quick "not interested." You're looking for anyone who mentions pain around observability costs or data management.
• Multi-channel outbound sequences: Building lists in your sales engagement platform (likely Outreach or Salesloft), sending personalized emails, LinkedIn touches, and follow-up calls. You're researching what tools prospects currently use (check their job postings, tech stack data) to personalize your message.
• Qualifying inbound MQLs: When someone downloads a whitepaper or requests a demo, you call within minutes to qualify whether they're a real opportunity or just tire-kicking. You're asking about current tooling, data volumes, team size, and budget authority.
• Discovery for handoff: When you get someone interested, you run a 15-20 min discovery call to understand their current state (what observability tools they use, approximate data volumes, pain points around cost or complexity), then hand off to an AE with good notes.

The Honest Reality

What's Hard

• Technical gatekeeping: You're calling engineers who don't want to talk to salespeople. They'll ask technical questions you may not be able to answer early on ("How does this integrate with our Kubernetes setup?" or "What's the performance overhead?"). You have to know enough to sound credible but not so much that you try to run the demo yourself.
• Abstract value prop: "Data pipeline optimization" is not as sexy as "close more deals" or "automate your marketing." It takes multiple touches to get someone to care about a problem they may not know they have.
• Long qualification cycles: Even when someone's interested, they need to loop in multiple stakeholders (engineering, DevOps, sometimes security and procurement). A "yes, let's meet" today might turn into "let's reconnect in 3 weeks when our architect is back."
• Lots of rejection: Most cold calls end in "we're happy with our current setup" or "not a priority right now." You'll hear a lot of "just send me some info" (which usually means no).

What Success Looks Like

• 15-20 qualified meetings booked per month that actually show up and advance to next stage with the AE
• 40-50% show rate on booked meetings (better than average means you're qualifying well)
• Converting 20-25% of interested responses into actual qualified meetings (not just calendar holds that cancel)

Who You're Selling To

Primary Buyers:

• Engineering Managers / Directors of Engineering (own the observability budget, feel the cost pain)
• Site Reliability Engineers / SRE Leads (deal with data management day-to-day)
• DevOps Leads / Platform Engineering teams (looking for better tooling and efficiency)
• Security Engineers / SOC teams (secondary - care about log retention and compliance)

What They Care About:

• Cost reduction: Observability bills (especially Splunk) are massive and growing. If you can show a path to cutting that 30-40%, you have their attention.
• Flexibility: Not being locked into one vendor; being able to route data to multiple destinations (e.g., Splunk for security, Datadog for APM, S3 for long-term storage).
• Data volume management: Reducing noise, filtering out useless logs before they hit expensive tools, transforming data to optimize storage.
• Ease of implementation: They're busy. If this requires ripping out their entire stack, they're not interested. They want something that fits into current workflows.

Requirements

• Comfort with technical concepts: You don't need to be a DevOps engineer, but you need to learn what Kubernetes is, what log aggregation means, what observability tools do. You'll be talking to technical people who can smell BS.
• High activity tolerance: This is a volume game. 50+ calls/day, 100+ emails/week. You need to be okay with repetitive outreach and lots of "no."
• Coachability: This is likely your first SDR role or early in your SDR career. You'll need to take feedback on messaging, call structure, and qualification criteria.
• Persistence without being annoying: Technical buyers ignore generic outreach. You need to follow up multiple times with relevant, personalized touches - but know when someone's genuinely not interested vs. just busy.
• Curiosity about the product: You'll ramp faster if you actually care about learning how Cribl works and why customers use it. The best SDRs can have semi-technical conversations and sound like they understand the problem.