I was first contacted by someone from HR. The questions asked were to gauge my interest in the company and see if my skills matched what they were looking for. After that went through, I was scheduled for a phone screen. The phone screen was very casual, and the interviewer seemed almost unprepared, as he was unsure of what to ask. After the first phone screen, I was contacted to do one more. This person seemed much better than the first, but the style of the interview was very casual and conversational as well. Finally, I was scheduled for a four-person onsite interview.

Something that Twilio needs to work on is their reimbursement policy; it's terrible. They only provide you with $600 (meaning you have to book your flight and hotel yourself), and they don't reimburse you for food. Take note that for someone flying into San Francisco, a flight is at least $300, and good luck finding a hotel for less than $150 a night. That threw me off a little bit, but whatever, it's a startup.

Their offices are quite small for the amount of employees they have, and the place seemed crowded (it's all one big open space). They do, however, have a pantry and fridge full of food, and they bring in lunches and dinners throughout the week.

The onsite interview consisted of four interviews, and the questions asked were mostly pertinent to the languages I am most comfortable with, but they seem to like Ruby quite a lot. They also asked a lot of questions about past projects and if I had used Twilio for my own projects. This is probably important to them. I would recommend studying networking, coding, and distributed computing problems.

Have you used Twilio?

Tell us about some difficult projects that you have worked on.

Distributed computing problem. I forget the exact question.

Some C questions to test your knowledge of pointer arithmetic.