← Harness
Harness role-play cheat sheet
For the mock cold call at the end of most SDR interviews.
What they sell, in one line
A platform that helps engineering teams build, test, and ship software faster, using AI to automate the process.
Who you'd be calling
VPs of Engineering, DevOps and platform engineering leads, and CTOs at mid-size to large companies.
Your opener
“Hi [Name], this is [You] from Harness. I know I'm interrupting your day. Can I take 30 seconds to explain why I called, and you can tell me if it's a fit?”
Problems you solve for them
- Slow, fragile release pipelines that delay new features
- Too many separate tools stitched together
- Risky deployments that cause outages and rollbacks
Discovery questions to ask
- How does your team get code from a developer's laptop to production today?
- How often do deployments cause problems or need a rollback?
- How many different tools does your team use to build, test, and release?
Objections they'll throw at you
“I'm busy right now.”
→ Of course. I'll be brief. Is speeding up releases something your team is working on this year? If so, when's a better time to talk?
“I'm not interested.”
→ Got it. Just so I understand, are you happy with how fast and safely your team ships today?
“We already use something for this.”
→ Sounds like you're set up already. What are you using, and what's the most annoying part of it?
“Just send me an email.”
→ Sure. Which matters more to you right now: shipping faster, cutting deployment risk, or simplifying tools?
Competitors worth knowing
GitLab, GitHub Actions, CircleCI, Jenkins
Interview tips for this company
- Understand CI/CD in simple terms: automatically building, testing, and releasing code.
- Practice asking about process, not just tools, since DevOps leaders care about speed and safety.
Written from public information about Harness to help you practice. Ask an insider what their role play looked like; it's the best prep there is.