Sales Development Representative (SDR) – Bazel Support and Platform

The Bazel Sales Development Representative (SDR) plays a critical dual role:

1. Sales Prospecting & Lead Generation, and
   
2. Technical Understanding of Modern Development Workflows, especially around Bazel, build systems, CI/CD, and monorepos.
   

This is not a traditional SDR role. You will prospect into highly technical engineering leaders—Platform Engineering Directors, Staff Engineers, Build/Release teams, CTOs—and you will need to speak their language. Your ability to understand developer pain points and communicate the value of Aspect’s Bazel platform will be central to your success.

If you love talking to developers, understand software fundamentals, and are excited about build systems and developer tooling, this role is for you.

Sales Prospecting & Pipeline Generation

• Identify, research, and qualify new leads within engineering organizations.
  
• Execute outbound campaigns using email, LinkedIn, calls, and targeted messaging.
  
• Build sequences and outreach strategies tailored to platform teams, dev-tooling teams, and engineering management.
  
• Generate interest by articulating developer pain points such as slow builds, unstable CI, monorepo complexity, and scaling challenges.
  
• Maintain and grow a healthy top-of-funnel pipeline for Account Executives as measured by intro calls and demos.
  
• Track and report activity, metrics, and results in the CRM (HubSpot). 
  

Technical Engagement & Developer-Centric Discovery

• Demonstrate enough technical insight to hold meaningful conversations with software engineers and DevOps teams.
  
• Identify build-system challenges and match them to Aspect’s Bazel solutions.
  
• Understand and explain (at a high level):
  
  • Bazel concepts (caching, hermeticity, rules, dependency graphs)
    
  • Monorepo workflows
    
  • CI/CD bottlenecks
    
  • Developer productivity issues
    
• Qualify technical fit and hand off strong opportunities to Sales Engineers or AEs.
  
• Attend product trainings and self-educate to continuously deepen your understanding of Bazel, build systems, and developer infrastructure.
  

Collaboration & Feedback Loops

• Collaborate closely with Sales Engineers to prepare technical messaging, outreach templates, and qualification criteria.
  
• Provide the Product team with insights from the field—common objections, developer needs, tooling gaps.
  

Assist Marketing with content related to developer workflows, prospect personas, and technical pain points.

Required Qualifications

• 1–3 years of SDR, BDR, or technical outbound experience OR strong interest in transitioning from engineering to a sales-facing role.
  
• Understanding of modern software development (e.g., compilers, builds, CI/CD pipelines, source control, containers).
  
• Ability to discuss technical concepts with engineers; you don’t need to be an expert, but you must be fluent enough to engage.
  
• Strong written and verbal communication skills tailored to a technical audience.
  
• High curiosity, self-motivation, and ability to learn complex technical material quickly.
  
• Strong organizational skills and comfort using CRM tools.
  
• A passion for developer tools, build systems, or helping engineering teams solve problems.
  

Preferred Qualifications

• Familiarity with Bazel, Buck, Blaze, Pants, Nx, or other build systems.
  
• Exposure to cloud platforms (AWS, GCP, Azure) or distributed systems.
  
• Previous technical internship, coding bootcamp, CS coursework, or hands-on programming experience (Go, Java, Python, C++, etc.).
  
• Experience prospecting into engineering or product teams.
  
• Ability to analyze engineering org structures and identify ideal buyer personas (Platform Engineering, Developer Infrastrucuture, Dev Tools, Site Reliability Engineering, etc.).

• Work with industry leaders who helped develop Bazel and modern build systems at Google.
  
• Shape the future of developer productivity and reproducible builds for enterprise-scale software.
  
• A remote-first, engineering-led culture with strong open-source roots.
  
• Competitive compensation, meaningful equity, and flexible work arrangements.