Planview interview questions

Approach this role with caution. The initial screening revealed a significant disconnect between the actual job requirements, the written job description, and the hiring manager’s expectations. The interview felt un-vetted, highly disorganized, and entirely gatekept by a hiring manager who was unprepared regarding my specific background and asked basic filtering questions that should have been reviewed beforehand. The department is clearly suffering from an identity crisis, trying to transition a legacy PPM platform into modern architectures while retreating into outdated, rigid PMO thinking.The conversation heavily focused on abstract concepts rather than practical solution architecture. The hiring manager is hunting for an unrealistic Frankenbot hybrid: someone expected to be a technical AI Solutions Consultant while simultaneously shaping corporate strategy for Fortune 100 clients, such as major airlines, rather than focusing on software implementation, tool mapping, and integration architecture. Questions regarding executive communication felt formulaic, dehumanized, and disconnected from real-world, value-driven business conversations. Expecting an architect to use rigid, scripted checklists to dictate strategy in complex industry verticals where they have no specific operational expertise is a guaranteed way to look completely incompetent in front of clients. Technical capabilities regarding the heavily advertised GenAI and API requirements were entirely ignored.