Overview
You're an SDR at Spectro Cloud prospecting into enterprise accounts that run Kubernetes at scale. Your job is to identify companies with complex K8s deployments, find the right technical stakeholders (VP Engineering, Director of Platform, DevOps leads), and book qualified meetings for Account Executives. You're selling conversations about infrastructure management problems - multi-cluster complexity, cloud sprawl, edge deployments - not simple SaaS features.
Role Snapshot
| Aspect | Details |
|---|---|
| Role Type | Enterprise SDR (pure prospecting) |
| Sales Motion | Outbound-heavy (90%+ per post) |
| Deal Complexity | Enterprise technical sale |
| Sales Cycle | N/A for SDR (AE cycle likely 4-9 months) |
| Deal Size | N/A for SDR (likely $100K-500K+ ACV for enterprise platform) |
| Quota (est.) | 12-18 qualified meetings per month |
Company Context
Stage: Series B/C stage (276 employees suggests venture-backed growth)
Size: 276 employees
Growth: Actively expanding SDR team, hiring for enterprise motion
Market Position: Challenger in Kubernetes management space - competing against larger platforms and DIY approaches. They're selling to orgs already using K8s who are drowning in complexity.
GTM Reality
Pipeline Sources:
- 5-10% Inbound - limited; mostly from technical content, maybe some webinars or open-source downloads
- 90%+ Outbound - cold calling, sequenced emails, LinkedIn targeting
- Some partner referrals possible (cloud providers, consulting firms)
SDR/AE Structure: Dedicated SDRs feeding meetings to enterprise AEs. You book it, hand it off, track if it goes to opportunity.
SE Support: AEs will have SE support for demos/technical discovery, but you're doing initial outreach solo.
Competitive Landscape
Main Competitors:
- Rancher (SUSE) - established K8s management player
- Red Hat OpenShift - enterprise standard
- VMware Tanzu - for VMware shops
- DIY approaches (building in-house with open-source tools)
How They Differentiate: Palette focuses on giving flexibility to build custom K8s stacks while managing complexity - "choice without risk" positioning. Not opinionated like OpenShift.
Common Objections:
- "We're already managing K8s with [other tool]"
- "We built our own solution"
- "Too early in our K8s journey"
- Budget locked in existing contracts
Win Themes: Multi-cloud/hybrid complexity, edge use cases, wanting flexibility without managing everything manually.
What You'll Actually Do
Time Breakdown
Prospecting (70%) | Meeting Prep/Research (15%) | Internal (15%)
Key Activities
- Cold Calling Technical Buyers: 50-70 calls per day to VPs of Engineering, Platform Engineering Directors, DevOps leads. Most screen to voicemail. You're leaving messages that reference their tech stack ("saw you're running K8s on AWS and Azure...").
- Email Sequencing: Writing and sending personalized emails about infrastructure complexity. You'll research their company's tech stack (job postings, conference talks, GitHub) to make it relevant.
- Account Research: Identifying which companies are good fits - need to be running Kubernetes at meaningful scale (multi-cluster, multi-cloud, or edge), typically 500+ employees or high-growth tech companies.
- Qualifying Conversations: When someone picks up and engages, you're asking technical qualification questions - how many clusters? Which clouds? Who manages it? What's painful? You need enough detail to pass a real opportunity to the AE.
The Honest Reality
What's Hard
- Low Connect Rates: Enterprise technical buyers don't answer their phones. You'll dial 60-80 times to have 5-8 real conversations. Persistence is the job.
- Technical Credibility Required: You can't sound like a typical SDR. You need to understand Kubernetes basics, cloud providers, infrastructure problems well enough to have a real conversation with a Director of Platform Engineering. There's ramp time.
- Long Feedback Loops: You book a meeting today, it happens in 2 weeks, then you wait 30-60 days to see if it becomes an opportunity. Hard to know what's actually working.
- Gatekeepers and Org Complexity: Enterprise accounts have layers. Finding the right person who owns K8s strategy (not just a DevOps IC) takes work. You'll talk to a lot of wrong people first.
What Success Looks Like
- Booking 12-18 qualified meetings per month that AEs accept (not junk meetings)
- 30-40% of your meetings progress to discovery/opportunity stage
- Building a pipeline of target accounts you're warming over time (not one-and-done)
Who You're Selling To
Primary Buyers:
- VP Engineering / CTO (economic buyer, often final sign-off)
- Director of Platform Engineering / Infrastructure (technical champion)
- Head of DevOps / SRE (user/influencer)
What They Care About:
- Reducing operational overhead of managing multiple K8s clusters across environments
- Maintaining flexibility to choose their stack (not locked into opinionated platform)
- Governance and consistency across teams/clouds without slowing developers down
- Edge and hybrid cloud use cases where centralized management matters
- Cost and complexity of current DIY approach
Requirements
- 2+ years of enterprise SDR/BDR experience, or 1-2 years as SMB AE selling technical B2B software
- Comfortable with technical concepts - you need to learn K8s, containers, cloud infrastructure quickly
- High activity tolerance - this is 60-80 touches per day, mostly calls and emails
- Resilience with rejection and low response rates
- Ability to research accounts and personalize outreach (not just blasting templates)
- Coachable and process-oriented - you'll be doing a lot of activities that don't work until you refine approach