← Macroscope
Macroscope role-play cheat sheet
For the mock cold call at the end of most SDR interviews.
What they sell, in one line
AI that reviews code changes automatically and gives teams a clear view of how their codebase is changing.
Who you'd be calling
Engineering managers, VPs of Engineering, CTOs, and tech leads at software companies of about 50 to 1,000 people.
Your opener
“Hi Sam, this is Alex from Macroscope. I know I'm calling without warning. We help engineering teams catch bugs in code changes automatically, so do you have 30 seconds for me to explain, and you can tell me if it's relevant?”
Problems you solve for them
- Code reviews are slow and pile up on senior engineers
- Bugs slip through when reviewers are rushed
- Leaders can't easily see what is changing in the codebase
Discovery questions to ask
- How long does a code change usually wait before someone reviews it?
- Who does most of the reviewing, and is it getting to be too much for them?
- Are you using AI coding tools, and if so, how do you check the code they produce?
Objections they'll throw at you
“I'm busy.”
→ I'll be quick. Could we pick a time this week for a short chat instead?
“We're not interested.”
→ No problem. Is it that reviews are running smoothly, or that you've tried AI review tools before and weren't impressed?
“We already use an AI code review tool.”
→ Good to hear. What do you like about it, and what do you wish it did better?
“Send me an email.”
→ Happy to. Who on your team handles code review tooling, so I can include them as well?
Competitors worth knowing
CodeRabbit, Greptile, Graphite
Interview tips for this company
- Learn what a pull request and a code review are. Developers will talk in those terms, and you need to follow along.
- Developers are skeptical of AI tools. Show you've done your homework on the product and ask good questions instead of overselling.
Written from public information about Macroscope to help you practice. Ask an insider what their role play looked like; it's the best prep there is.