During the recruiter stage, the recruiter was well-prepared and asked thoughtful questions tailored to my experience with datacenters and hypervisors. My background seemed to align closely with their expectations.
In contrast, the technical interviewer seemed nervous and unprepared, with no clear set of questions. The role itself feels more like a Private Cloud Software Architect position rather than one focused on infrastructure. The interviewer asked about my experience with Kubernetes (K8s), and although I provided an example, no follow-up questions were asked.
Throughout the discussion, he repeatedly emphasized that this wasn’t a ‘typical’ private cloud role, as if he were trying to invent new industry terminology for the position. In reality, it didn’t seem to differ meaningfully from existing concepts.
The call included two participants, neither of whom introduced themselves. One individual, Radha, remained silent throughout. Overall, this was one of the most peculiar and disjointed interactions I’ve encountered in a hiring process.
It seems they are attempting to develop an internal application for needs already addressed by existing software solutions. Based on this experience, the company appears highly disorganized, and I would hesitate to join a team lacking such basic structure and clarity.
