← Sanity
Sanity role-play cheat sheet
For the mock cold call at the end of most SDR interviews.
What they sell, in one line
A flexible content platform where teams store content once and deliver it to websites, apps and AI tools.
Who you'd be calling
Heads of Engineering, Frontend/Platform Leads, Digital Product and Content Operations leaders at mid-size and enterprise companies running websites and apps.
Your opener
“Hi [Name], this is [You] from Sanity. I know I'm interrupting your day. I'm calling because teams that publish content to a website and an app often tell us they end up managing the same content in several places. Is that something you deal with?”
Problems you solve for them
- Content stuck inside rigid page-based CMS tools
- Copy-pasting the same content across web, mobile and other channels
- Developers and editors blocked by each other's workflows
Discovery questions to ask
- Where does your content live today, and how many channels does it need to reach?
- When an editor wants a new type of content, what has to happen?
- How are you thinking about using your content with AI tools?
Objections they'll throw at you
“I'm busy right now.”
→ Understood. I'll take 20 seconds. I want to know if content that has to go to more than one place is a pain for your team. Is it worth a quick answer?
“Not interested.”
→ No problem. Most people I call aren't looking at content tooling until something breaks. Is your team happy with how fast you can ship new content types?
“We already use Contentful (or another CMS).”
→ Good, that means you already value structured content. How flexible is it when your team wants to change the content model or editing experience? That's usually where teams start comparing.
“Just send me an email.”
→ Sure thing. Who handles the content setup, you or an engineering lead? I'll send something short for the right person and check back next week.
Competitors worth knowing
Contentful, Strapi, Contentstack
Interview tips for this company
- Be able to explain 'structured content' and 'headless CMS' in plain words, like 'content stored as pieces, not as web pages.'
- Know that you're often calling developers, so keep it short and don't bluff on technical details. Say you'll bring in a specialist.
- Skim Sanity's website for its use cases and pick one to mention in the role play.
Written from public information about Sanity to help you practice. Ask an insider what their role play looked like; it's the best prep there is.