J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Twilio en nov. 2020
Entretien
5 rounds of interaction - easy DSA and very stupid system design question. I talked to 5 different people in 5 different locations (3 countries). The interviewers themselves were not at all experienced. They would have been my peers at best. They were themselves a bit intimated by me TBH.
They are in India with a very low budget and they want candidates who memorize things. That said, all interviews were positive but I think they had a budget constraint and decided not to hire. There was a "bar raiser" which is like an HR interview here - the guy seemed to be in a very bad mood right from the start as if the India center is going to snatch their jobs away (he was somewhere in EU). Felt almost a bit racist the way he talked.
Overall, they have assessed India to be very cheap. So I advise them to increase recalibrate their budget.
Questions d'entretien [1]
Question 1
DSA - Graph - DFS/BFS
JS - use fetch / promise
System design - load distribution
J'ai postulé en ligne. J'ai passé un entretien chez Twilio
Entretien
Three-stage process: recruiter screening, a test task and on-site interview. Both test task and the on-site were simple and straightforward, with focus on practical skills. On-site included the prospective team lead, VP and a team lead from another team in the same location.
Questions d'entretien [1]
Question 1
- What data structure would you use for variable-length phone number prefixes?
J'ai postulé en ligne. J'ai passé un entretien chez Twilio en janv. 2025
Entretien
Interviewed for the L2 role on the Channels team. I did the online assessment (~3 hours), passed it, then was notified saying they filled the role and were no longer considering me. No referral to another role either. Long story short, don't let this awful company waste your time.
2 algo problems (listed below), 1 easy SQL problem, 1 easy API data retrieval problem, and 2 trivial multiple choice problems.
Questions d'entretien [2]
Question 1
Similar to LC1664 - Ways to Make a Fair Array except you don't need to count the number of ways to make it fair, you just have to find the 1 index to remove to make it fair.
If you google Hackerrank Approximate Matching you can find some material on it. Involves calculating a text score for substrings of a word based on a given prefix and suffix.