Four technical interview rounds. They scheduled the last two on the same (working) day, two hours apart, with the final one being the coding round. So by that point, I was obviously very tired and stressed.
Then the interviewer tells me, “It’s an easy problem, there are plenty of ways to solve it.” Great. Except I checked LeetCode afterwards and discovered it was actually a Hard problem—and not just any Hard problem, but one of the weirdest ones which was also very poor written.
Honestly, I don’t understand the logic here. After three rounds of ML-related questions that I absolutely nailed, apparently the best way to evaluate me is to throw a random LeetCode Hard at me when I’m already exhausted. Because clearly that’s the perfect way to assess someone’s ML skills.
To be fair, at least all the interviewers were very nice and friendly, so I can’t complain about that part. But then I had to wait almost three weeks for feedback, and they only set up a call after I sent them three emails asking for an update.
The following metrics were computed from 1 interview experience for the Twilio Machine Learning Engineer role in Spain.
Twilio's interview process for their Machine Learning Engineer roles in Spain is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Twilio's Machine Learning Engineer interview process in Spain.