Oracle Sep 2025 PMTS Screening Round | Poor experience

My screening round for the PMTS role at Oracle was a truly poor experience. The interview began with two behavioral questions. Following this, I was given a coding challenge: Kth Largest element in BST. I was able to complete the code along with the necessary boilerplate, but I encountered a significant issue with HackerRank's compiler. This technical glitch wasted at least 7-8 minutes, during which the interviewer remained completely unhelpful, simply watching me struggle. Frustrated, I eventually had to ask him to compile the code on his own system to verify it.

Next, I was asked to perform a complete Low-Level Design (LLD) of a multilevel parking system. At this point, only 20 minutes were left for this entire section. I clarified with the recruiter what was expected given the severe time constraint, and he mentioned that a complete design with code was required. With such limited time, I could only define the Functional Requirements (FR) and Non-Functional Requirements (NFR), sketch out a class diagram, and briefly explain my approach for reserving and freeing parking slots, along with a high-level discussion of the API design. The expectation of a complete design and code in such a short period was extremely infuriating.

I tried to reach out to the recruiter multiple times regarding the issues I faced during the interview, but he informed me that he could not provide any assistance. My overall impression of Oracle's interview process, particularly their time management and the conduct of their interviewers, was very negative. If they intend to ask LLD questions in a screening round, they should allocate sufficient time or stick exclusively to LeetCode-style problems. Their attempt to emulate Amazon's approach of including behavioral questions in all rounds, but with such poor execution, truly sucks.

Thumbs down to their pathetic code of conduct.