DA Interview Cheat Sheet

Twilio Product Lines

Programmable Messaging

SMS, MMS, WhatsApp, RCS. Super Network: 4,800 carriers, 900+ routing data points. Queue-based, store-and-forward.

Programmable Voice

PSTN, SIP Trunking, WebRTC. TwiML control. GLL Edge (9 locations). Connection-based, real-time.

Programmable Video

WebRTC rooms, SFU architecture. P2P or routed. Bandwidth-heavy, latency-sensitive.

Twilio Verify

OTP via SMS/Voice/Email/TOTP. Cross-channel verification workflows. Fraud prevention.

Segment CDP

Customer data platform. 700+ destinations. Kafka backbone, RocksDB dedup, Centrifuge delivery.

SendGrid (Email)

Transactional & marketing email. ISP reputation management. Async, batch-oriented.

Twilio Flex

Programmable contact center. React-based UI. Omnichannel (voice, chat, SMS, WhatsApp).

Identity (Stytch)

OAuth 2.1, passwordless auth. AI agent auth via MCP protocol. Connected Apps.

Workflow Affinity Groupings

Cell Type	Services
Messaging	SMS, MMS, WhatsApp, RCS
Real-time	Voice, Video, WebRTC
Async	Email (SendGrid), Fax
Verify	Verify API, Lookup

Cell-Based Architecture

                Core Principle: Workflow-affinity cells, operationally-differentiated tiers. Co-locate services that call each other at runtime.
            

Why Cells?

Blast radius: Cell failure = 50 customers, not millions
Noisy neighbor: SMB spike can't impact Enterprise SLA
Independent scaling: Scale messaging without touching voice

Cell Tiers

Tier	Customers	SLA
Enterprise	10-50	99.99%
Mid-Market	100-500	99.95%
SMB	1,000+	99.9%

Cell Router Flow

Redis cache (95% hit, ~5ms)
DynamoDB Global Tables (~15ms)
Least-loaded assignment (~20ms)
VPC Lattice routes by service name

AWS Implementation

Cell = AWS Account + VPC (10.0.0.0/16)
Control Tower for multi-account governance
VPC Lattice enables overlapping CIDRs
EKS per cell (100-200 nodes)

Global/Shared Services

Identity & API Keys (DynamoDB Global)
Super Network (carrier connections)
Billing (async aggregation)
Cell Router (Lambda@Edge)

Technology Stack

Data Layer

Event streaming	Kafka (MSK)
Routing/Global	DynamoDB Global Tables
Transactional	Aurora PostgreSQL
Caching	Redis (ElastiCache)
Object storage	S3

Compute

Containers	EKS (Kubernetes)
Serverless	Lambda
IaC	Terraform + Terragrunt
GitOps	ArgoCD

Networking

Service mesh	VPC Lattice
API management	API Gateway
DNS	Route 53

Protocols

SMPP SIP WebRTC OAuth 2.1 MCP TwiML

Segment-Specific

RocksDB: Embedded dedup (60B keys)
Centrifuge: MySQL database-as-queue
NSQ: Local buffer before Kafka

Behavioral: STAR+ Format

Situation	Context (10%)
Task	Your responsibility
Action	What YOU did (50%)
Result	Outcome + metrics
+Reflect	What you learned

Key Questions

Drive change across teams (influence w/o authority)
Technical decision you got wrong
Said "no" to product/business
Major incident you led
Developed senior → staff engineer
Multi-year technical vision
Build vs. buy decision

Mistakes to Avoid

Too technical (lead with people/org impact)
Taking all credit (use "we" appropriately)
No concrete examples
Not quantifying impact

2-Minute Answers

Cell Architecture

"Workflow-affinity cells with operational differentiation. Services that call each other at runtime share a cell—Messaging Cell (SMS, WhatsApp), Real-time Cell (Voice, Video). Each cell is an AWS account with its own VPC. Enterprise cells: 10-50 customers, 99.99% SLA. SMB: 1000+, 99.9%. Cell Router at edge: Redis cache (95% hit), DynamoDB fallback. VPC Lattice routes by service name—overlapping CIDRs OK. Trade-off: operational overhead, but blast radius is 50 customers, not millions."

Why Twilio?

"Twilio is solving fascinating problems at the intersection of reliability and scale. The Super Network with 4,800 carrier connections, real-time voice/video, and now AI agent authentication with Stytch—these are exactly the distributed systems challenges I want to work on. My cell-based architecture experience directly applies to Twilio's multi-tenant platform."

Build vs Buy

"BUILD when: core differentiator, unique requirements, team has expertise. BUY when: commodity, time-to-market critical, maintenance burden exceeds value. Example: Build custom Cell Router (core to architecture), buy RDS for database underneath."

Technical Debt

"Classify it (deliberate vs inadvertent), quantify the cost (dev hours, incidents), make it visible (debt backlog with estimates), negotiate explicitly ('2 weeks with debt, 4 weeks clean'). Never let debt accumulate silently."

Quick Reference

Key Numbers

Super Network carriers	4,800
GLL Edge locations	9
Segment destinations	700+
Cell Router cache hit	95%
Enterprise cell customers	10-50
SMB cell customers	1,000+

Your Narrative

                "I specialize in designing fault-isolated, cloud-native platforms where architecture enables both system resilience and organizational scalability."
            

Questions to Ask Them

How do you balance platform vs product engineering?
What's the biggest reliability challenge right now?
How does the DA role influence across teams?
What does success look like in 6-12 months?

Strengths to Emphasize

Cell Architecture Fault Isolation Org Influence Multi-Region Event-Driven

Twilio Distinguished Architect - Interview Cheat Sheet