The interview process started with a technical discussion around low-level systems concepts including memory allocation, fragmentation, alignment, lock-free programming, mmap/malloc internals, and allocator design. However, the interview quickly became extremely adversarial and unbalanced. The interviewer continuously interrupted answers with repetitive “why?” follow-up questions without giving enough time to think or complete explanations. Instead of evaluating problem-solving ability collaboratively, the interaction felt more like an interrogation intended to expose gaps at every possible level. Although this was supposed to be a coding interview, almost the entire session was spent on deep theoretical grilling. The actual coding portion was pushed to the last 10–15 minutes, which was not enough time for a fair coding evaluation. The overall experience felt disrespectful, unnecessarily stressful, and poorly managed. A challenging interview is understandable, but candidates should still be treated professionally and given adequate time to think and code. Unfortunately, this experience gave a very negative impression of the engineering culture and interviewer behavior.