← Twilio
Twilio role-play cheat sheet
For the mock cold call at the end of most SDR interviews.
What they sell, in one line
Twilio provides tools that let businesses add texting, calls, email and customer messaging to their apps and services.
Who you'd be calling
Developers, engineering managers, product leaders and customer-experience heads at companies of all sizes.
Your opener
“Hi [Name], this is [You] from Twilio. I know I'm catching you at a random time, so can I take 30 seconds to say why I called and let you decide if it's worth continuing?”
Problems you solve for them
- Building calling and texting features from scratch is slow and complicated
- Customers expect fast, personal messages on their favorite channels
- Messages and calls must be reliable and reach people worldwide
Discovery questions to ask
- How do you talk to your customers today: text, email, calls, chat?
- Do you build those communication features in-house or use a vendor?
- What breaks or frustrates customers about those messages today?
Objections they'll throw at you
“I'm busy right now.”
→ Totally understand. I'll be brief: how you message your customers is my only topic. Can we find 10 minutes later this week?
“We're not interested.”
→ Fair enough. Can I ask how you send things like order updates or verification codes today?
“We already have a provider.”
→ That's good to hear. How is it working for reliability and cost, and would you be open to comparing?
“Just send me an email.”
→ Sure. To make it relevant, which channel matters most to you: text, voice or email?
Competitors worth knowing
Vonage, Sinch, Bandwidth
Interview tips for this company
- Learn what an API is in one friendly sentence, like 'a way for one app to ask another app to do something'.
- Practice asking about both technical buyers (developers) and business buyers (customer experience), since Twilio sells to both.
Written from public information about Twilio to help you practice. Ask an insider what their role play looked like; it's the best prep there is.