Just wrapped a Twilio EM interview loop for a senior engineering manager role (San Francisco, remote-flex). Five rounds total. Here's what each one was actually testing.
Recruiter screen (30 min). Straightforward. They want to know your team size history, what domains you've owned, and whether you've scaled a team through hypergrowth. Twilio went through their own scaling chaos so they care about that. Have a crisp answer for "biggest team you've built and how you did it."
Hiring manager intro (45 min). This is them assessing culture fit more than anything. They want to see genuine excitement about communications infra, not just a good story. If you haven't used Twilio products, poke around the developer docs beforehand. They notice.
Engineering deep dive (60 min). One of their senior ICs asks you about a system you built. Not whiteboard coding, but a real technical discussion. They'll go deep on your choices. Why that architecture, what failed, what would you build differently. I talked through a microservices refactor I led and they pushed hard on observability decisions. Know your systems.
People leadership round (60 min). Two behavioral questions back to back with a cross-functional director. Both were basically "tell me about a time you had to make a call with incomplete information and the team disagreed." STAR format, but they want to hear the disagreement part specifically. Don't skip the conflict.
Executive presentation (45 min). You give a short (10-15 min) talk on how you'd approach leading a team in their space, then Q&A. They told me to keep it concise and they meant it. One candidate reportedly went over and it hurt them.
Total cycle was about 3.5 weeks. Debrief happened fast, within 2 business days. They move when they want someone.
Leveling: I was told the role mapped to their L5 EM band. Comp offer was base in the $230-250k range, RSUs vesting over 4 years, standard benefits. Not FAANG top-of-band but competitive for the role scope.
Biggest takeaway: they want operators, not theorists. If your answers are too abstract you'll get filtered at the deep dive round.