Solicité el puesto a través de la recomendación de un empleado. El proceso duró 2 semanas. Acudí a una entrevista en Twilio (San Francisco, CA) en ago 2015
Entrevista
Consisted of an off-site meeting with my hiring manager, a technical phone screen, and a series of onsite technical interviews. Pretty standard format. All interviewers had been trained extremely well in how to conduct an interview, and all of the questions scaled well to a variety of experience levels. Overall, my interview experience at Twilio was better than any other experience I've had. Much better than Google or Facebook.
Envié una solicitud electrónica. Acudí a una entrevista en Twilio
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
- What data structure would you use for variable-length phone number prefixes?
Envié una solicitud electrónica. Acudí a una entrevista en Twilio en ene 2025
Entrevista
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.
Preguntas de entrevista [2]
Pregunta 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.