Twilio Senior Project Manager interview questions

TLDR: Recruiters and not aligned with hiring managers' expectations leading to mutual disappointment in later round interviews Was recruited via LinkedIn for a role that matched my title but not experience. Ignored first message for this reason but kept receiving them. Follow up messages specifically listed how experience was a good fit. Figured that a company this size would do their research and might be targeting me for a specific reason, right? Wrong. Initial discussion with recruiter "J" was fine, but he seemed very green and out of his depth, fumbled when reading the job description a few times. I mentioned my level of technicality and how it might not be a good fit, but he suggested that this was one of several roles hiring for that office and that I might be fit into those later in the process. I asked about whether Dev Ops would be a part of the role, which is rare for DX platforms, he didn't know. 2nd interview by phone with hiring manager, but was called a "phone screen" I had prepared for the technicality of the role and could speak to the platform, but since developers were the main customer, I did not prepare for client facing role plays. Manager "D" was not happy to be there that day and audibly sighed multiple times before starting the conversation. He explained his past at the company in under 30 seconds and explained the format without any enthusiasm. He asked two basic questions about my day-to-day and why I was leaving my current company then started warning me about the technicality of the position. I told him that I brought this up in the first screening but had prepared for the discussion and explained how it fit into my career path. We then went into a client role play which completely caught me off guard. 100% my fault for not preparing better, but when the first mention of the role being client-facing was within this second interview, it didn't seem as important as the technical understanding. I managed to provide answers to all questions but should have slowed down and explained my framework. No more questions were asked so none of the technical / platform prep or any other product related experience mattered. Interviewer finally seemed to open up when I asked questions to him, but not much chance to explain much about myself at that point. Overall the experience left me with a bad taste in my mouth because: 1) Recruiter did not seem to have a good grasp of whether I was a good fit for the role, could not answer technical question relevant to the 2nd interview, and did not explain the client-facing responsibilities which were key to preparing for the 2nd interview  2) Hiring manager seemed frustrated before I even spoke to him, seemed to resent the prompt / questions he had to ask, and probably should have coordinated much better with the recruiter on the importance candidate experience instead of taking it out on a candidate during an interview 3) Ultimately I feel like I wasted my time, was not well evaluated as a candidate, and would recommend that anyone working with Twilio not trust everything their recruiters say to get you into the 2nd interview. If you personally don't feel like your experience is a good fit, don't interview. It's not worth making a bad impression to just fill a recruiter's minimum interviewee quota .

I had a really bad interview experience with one of their recruiters, it almost seemed like he had made up his mind not to fire me even before he called. And if he had made up his mind, I wonder why he even called me. I don't know how this company hires people with recruiters that disqualify a candidate as if they are the hiring managers. I applied online for a Sr Product Mgr role, got an email from Recruiting Coordinator and she set up 30 min interview with a senior recruiter. My background was a almost perfect match for the position, I do exactly the same work in my current job, albeit I might have been slightly over-qualified for the position. The job was for Sr product manager role and the job description clearly stated that applicant don't need to contribute to product code (& in what company Sr PMs are writing production code?). I come from a technical background and used to be an engineer, and now I am PM. This senior recruiter first asked me to give brief about my background, and as soon as I gave my background in a minute, he tells me that it wouldn't work for this position because, as a sr PM, you are expected to contribute to product code. If that was the requirement, why did job description say you don't need to be an engineer? I recommend you don't waste your time talking to Twilio recruiters. Use a reference and talk directly to the hiring manager if possible.