I recently interviewed for a Technical Support Engineer position at Twilio, and after almost three weeks of interviews, tests, and preparations, I’m left deeply disappointed. Here’s a detailed breakdown of the process and why I wouldn’t recommend it: 1. HackerRank Flex Test: The first step was a HackerRank Flex test, but it wasn’t your typical coding challenge. Instead, it consisted of a couple of questions designed to evaluate how I would respond to technical support emails. One question asked me to review a customer's issue and provide a solution via email, and another involved using Twilio’s own tool where I had to read documentation and build a workflow. This part of the process felt relevant, but not particularly challenging. 2. Phone Screen: After the test, I had a phone interview with a recruiter. It was a fairly standard conversation covering my background, the role, and why I wanted to join Twilio. Everything seemed fine, and I received positive feedback from the recruiter. 3. Technical Interview: Next, I went through technical interviews where I had to answer questions related to Node.js, React.js, and network-related issues. This round wasn't challenging but in line with my expertise, and I felt like I performed well. 4. Behavioral Interviews: Several rounds of behavioral interviews followed, where I shared examples from my previous experience using the STAR method. I felt confident in my responses and was given no indication that anything was amiss at this stage. The problem arose during the final interview with a senior manager. The tone of the conversation shifted after I was asked a completely irrelevant question about where I was based. From that point on, the manager’s focus moved to my previous salary, which seemed inappropriate given I told him that I was uncomfortable sharing it and modern hiring practices. The interaction became uncomfortable and unprofessional, completely derailing what had been a constructive interview process until then. After three weeks of back-and-forth, I was ultimately rejected, with vague feedback that my behavioral responses weren’t up to their standard. This reasoning felt hollow, given that there were no concerns raised in earlier rounds. I couldn’t help but feel that the real reason for the rejection was unrelated to my actual skills and experience. For a company that emphasizes diversity and inclusion, my experience reflected the opposite. If you’re considering applying to Twilio, be prepared for a long, drawn-out process that may not be worth the time and effort, especially if you end up being judged on irrelevant factors.