I went through 5 rounds of interviews for a Sr. TPM role in the Product Security organization. While the coordination was timely, the process itself felt poorly structured and misaligned with the stated expectations of the role. The final feedback was that I lacked product security knowledge — yet not a single interviewer asked meaningful or direct questions related to product security concepts. Several interviewers seemed unsure about what to assess, which created a vague and inconsistent experience throughout. If domain expertise is critical to the role, it should be evaluated explicitly and consistently across interviews — not used retroactively as a rejection reason. I was expected to read between the lines, anticipate unspoken expectations, and tailor my answers to invisible criteria. This was disappointing, especially given the seniority of the position and the investment of time from both sides. Okta should take a hard look at how aligned their hiring panels are and whether they’re evaluating candidates based on actual conversations — not assumptions. Future candidates: If you're applying for a TPM role in security here, be prepared to drive the security discussion yourself. Don’t assume the panel will ask — or even know how to.