Medallia interview questions

I was contacted by a recruiter to interview. After we set up a Zoom call, there were a few emails back and forth to ensure everything was good. The recruiter was kind, encouraging, and straightforward about what the company needed. He seemed excited to push me through to the second phase with a practical project; however, I never heard back from the hiring manager or the recruiter.

After applying for the position, I was reached out to by a recruiter who discussed the typical introductory points of why am I looking for something new, what am I seeking, how much am I seeking in compensation, and about Medallia. The recruiter really rushed the conversation and really did not give me time to ask questions. In the next interview, I was asked a few technical questions pertaining to object oriented programming, but most of the time was spent in a coding exercise. I was asked to create something that would be used to track key-value pairs. As I began coding, the interviewer would ask me questions on how I would handle new features to my existing implementation. Overall, it was pretty easy and I aced it. In the immediate interview, I was asked a number of technical questions, and then I was given a coding exercise. In this case, I was asked to implement content into a React component. Because of my Angular background, I answered these questions from that perspective. There was only question I did not do well in, and that was because the interviewer did not word it well. I suppose his poor wording cast me into a light of not knowing what I was doing. Lastly, I met with a director, where we talked about my experience and more architecture related questions. This was pretty relaxed and easy, so I aced that one. In conclusion, I did pretty well, but the one question that the interviewer asked in the second interview cost me the job. While I was told coming from an Angular background would not matter, apparently it did. The interview process was in depth but pretty easy.