One phone interview included a short coding problem over the internet.
The second onsite interview was a four-hour coding project on a laptop.
The third interview was another onsite meeting with the hiring manager to discuss compensation.
It took some days to make arrangements with the company recruiter.
Once started, the entire interview process was pretty smooth and fast.
The coding interview style was fair and effective.
However, I felt there wasn't much face-to-face communication to check other aspects of a candidate, for instance, to check if I was a culture fit, etc.
The phone screen asked me to write a string manipulation function in Java. I don't remember the exact problem, but it wasn't hard. The coding required me to show familiarity with coding (need to code fast), the programming language, and some corner case handling.
My onsite interview was a project with a story that required me to implement a series of command-line driven functions. These involved, among other things, JSON (de)serialization to and from files.
The following metrics were computed from 1 interview experience for the Twilio Senior Software Engineer role in Mountain View, California.
Twilio's interview process for their Senior Software Engineer roles in Mountain View, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Twilio's Senior Software Engineer interview process in Mountain View, California.