The first interview was with HR and left a very positive impression — it was structured around expectations for the role and included thoughtful questions about past project experience. The tone was professional, respectful, and engaging, which made me genuinely excited about the opportunity.
However, the second interview with the CPO was unfortunately quite the opposite. The call started off poorly, as he appeared distracted and was visibly responding to chats while interviewing me, though he told me to keep talking. One of the first questions asked was whether I was "obsessed with cloud," and he emphasized that this was the key requirement for the role. While I appreciate the importance of domain focus, the conversation quickly turned dismissive of my past product experience saying they have a very complex product several times. When asking for examples of releases and features, no concrete examples of the "complexity" he referred to in their cloud offering could be explained.
There were no real technical questions or a chance to engage in a meaningful exchange about cloud products, which made the interview feel more like a gatekeeping session than an open dialogue. It left me with the impression that preconceived biases might have been at play.
I'm ultimately grateful to have noticed this dynamic early in the process — it's important to find not only the right role but also a cultural and values fit. If you're not 100% passionate about cloud infrastructure, this might not be the right place to pursue further.
