My interview experience at NetApp was underwhelming, to say the least. Despite presenting a polished and organized scheduling process on the surface, the underlying attitude toward candidates was far from respectful or flexible. The interviews themselves were heavily syntax-focused. In Round 1, I was asked to solve DSA problems in Python, even though I primarily code in C++. There was no interest in testing problem-solving or logical skills—only whether I could recall Python syntax. Round 2 involved coding React components, again purely checking for syntax familiarity without any depth or evaluation of architectural thinking or real-world application skills. What disappointed me more was the scheduling rigidity. Even after I communicated that I had important meetings, I was called in the morning to schedule interviews for the same afternoon. I was told bluntly that if I wasn’t available, I’d be dropped from the process. That level of inflexibility and lack of empathy felt extremely unprofessional. I ended up skipping key meetings just to accommodate their process. For a company of NetApp’s stature, I expected a more thoughtful and skills-oriented interview process, along with a basic respect for candidates’ time and commitments. Unfortunately, my experience didn’t reflect that.

Netapp had a long and difficult process of interviews at campus placements at IIT Bombay. Difficult questions around data structures, algos and OS were asked. You need to be really good at these in order to crack