It was a long process with a few stages and it was helpful that some of the interviews were held back to back to ensure efficiency. Weird thing was that out of 5-6 interviewers/managers only 1 who would have actually worked with this role. Only 1 of them knew about what the team was doing so there were an awkward moments when they asked me to ask questions about the roles. One of the recruiters was tasked to offer mentoring prior to and in between the interviews but they did not seem to have the tools and willingness to mentor. They wanted the calls to be very efficient and moved very quickly to "is there anything else you want to ask" without allowing a detailed and thorough conversation to my questions (I started a conversation on how the interviewers would evaluate my answers and how I could make up for me being a non-native speaker). They just repeated some general information and told me to read the guideline (that was also very general) and emphasized that I have to be confident that I almost felt bad for asking multiple questions although I thought that was what mentoring was supposed to be - to help a candidate be more prepared and informed, not just to be confident. After they mentioned they did not decide to move forward with me they said because in my answers I didn't give context which I took note about but at the same time I thought it was ironic that they repeated my comment. Lastly they offered help if I wanted to approach another role and as soon as I mentioned I am interested in they simply said I needed to apply directly to the recruiter and it was not a role that they manage. I was confused.

The interview process consisted in 5 interviews: 1) Hiring Manager with some system design questions 2) Program Sense: Evaluating the ability to manage complex projects from end-to-end, including early-stage roadmap creation, problem definitions, scope and requirements gathering, project planning, problem-solving, and risk mitigation. 3) Results Agility: Evaluating the results in new or unstructured situations. Responding to tough challenges. 4) TPM System Design: Evaluating understanding of the product by clearly identifying requirements and use cases (Product Sense) and diving into the technical details (e.g. design, scaling, product enhancement, e2e system design, tradeoffs/benefits, solutions on how to scale, define MVP). 5) Product Sense: Evaluating the understanding of basic KPIs and metrics, and what it takes to launch a product; define business/performance related metrics.