I applied online. The process took 2 weeks. I interviewed at Twilio
Interview
Applied online through Glassdoor. Was contacted by the first recruiter who discussed the interview process and provided information on the company. Was contacted again after around 2 weeks by another recruiter who asked for slots for telephonic interview, which I promptly provided. I was later informed of the date of the telephonic interview for which I promptly confirmed my availability. A day before the interview, I was informed that the interviewer is not available and was asked about other available timeslots, which I again promptly provided. I then got confirmation of the telephonic interview being rescheduled to another date based on the new timeslots I provided.
On the day of the interview, the interviewer didn't call me at the specified time and was late by around 10 minutes, as far as I remember. Though the telephonic interview went well and I answered confidently, I was informed (and that too only after I enquired about the result) that I hadn't cleared the round. As the interview had gone well and I was somewhat surprised by the outcome, I politely enquired about some additional feedback for my improvement, but there was no response or acknowledgement from the recruiter whatsoever to my query.
Though Twilio's product and tech stack seemed interesting, due to the recruiters lack of follow-up and response post my interview, the fact that the interviewer cancelled the interview once and then ended up being late for the rescheduled phone interview, overall the interview process was a disappointment.
Interview questions [1]
Question 1
-- Explain microservices architecture used in my applications,
-- How I went about identifying and designing the microservices,
-- My thought process behind usage of sql database for my microservices (instead of nosql)
How frustrating to have a call rescheduled multiple times - that should never happen. I do apologize that you did not have a great experience with us, and I plan on using this example as a training tool for the team to improve our communication skills.
Negative experience
Easy interview
Application
I applied online. The process took 3 weeks. I interviewed at Twilio (Bengaluru) in Jul 2022
Interview
Total interview process is a mess. They schedule interview with panel members who don't have enough knowledge or experience to assess candidate in the right way.
1. Round1 is a coding round. Very basic DS Algo questions on strings. Some 4-5 lines of code presented and asked above share review feedback. (Rejected for no valid reason and no feedback shared).
2. Round1 again done to screen. Architecture and design questions. Although it appears everything went really good, the result is not expected. (Rejected for no valid reason and no feedback shared. Automated mail received - At this point no feedback would be provided :)
Interview questions [1]
Question 1
1. Basic string based ds algos using recursion etc.,
2. Architecture/Design/Choice of databases.
I applied through an employee referral. The process took 2 weeks. I interviewed at Twilio (Chicago, IL) in Jun 2022
Interview
The process was smooth, and feedback was also reasonably soon. In the interest of time, I think a decent working solution should be considered acceptable. The systems design is also subjective
Interview questions [1]
Question 1
There were programming problems and a Systems Design question
I applied online. The process took 4 weeks. I interviewed at Twilio (San Francisco, CA) in Nov 2021
Interview
1) Initial recruiter intro call
2) Hiring manager interview
3) Coding / Pairing Initial Technical Interview
4) Final interview panel including Coding/Pairing interview, Behavioral interview, and System Design interview
5) Offer
Pre-interview prep material was excellent and accurate. Recruiters were helpful and prompt. Interviewers were friendly and positive.
Interview questions [1]
Question 1
Technical assessments were focused on practical pair-programming exercises and system design. I found this to be a refreshing departure from the typical LeetCode-style algorithm exercises.
