Plivo Technical Support Engineer Interview Questions
& Process

The interview process was good. They started with basic tech theory questions, then moved on to APIs and some programming questions. If you had a prior coding test, you'd also be asked to explain your code.

The interview process includes a short 10-minute screening call, followed by a 30-minute managerial round, and a 30-minute technical round. The overall process can be quite slow, potentially extending for over three weeks. Expect behavioral questions during the first two stages.

I applied and then connected with the hiring manager on LinkedIn. We went back and forth on LinkedIn Messenger trying to schedule a phone conversation. The first time we had something scheduled, they followed up the next day apologizing for missing our time slot because a meeting ran over. After the initial phone conversation, I was given a technical take-home assignment to build a web app using the Plivo APIs. There was no timeframe or deadline mentioned in the assignment, but I completed it a week and a half later. After I sent back the project, I got a curt reply that the role had been closed. I'm happy that it didn't progress further. I don't usually take the time to write a review for such a brief interview, but I hope to save someone else from wasting their time without clear guidance. I would have expected clear instructions on when to return a substantial assignment, and a courtesy email not to bother completing it if they knew the role was closed.