El proceso duró 1 día. Acudí a una entrevista en NetApp (Pittsburgh, PA) en ene 2007
Entrevista
The phone screen was right out of joelonsoftware.com, which was fine with me. Not because it was easy (it was), but because it makes sense. I was (and still am) impressed by the technical people at NetApp.
A few days after the phone screen, they called me in for a day of interviews. I met with the HR person, maybe 5 engineers (for 1-on-1 interviews, including a lunch interview), and two managers. Everyone's questions were reasonable and relevant. If you know your stuff, have some applicable experience, and are smart enough not to put stuff on your resume that you don't really know, then you've got a good chance of getting hired at NetApp.
Preguntas de entrevista [1]
Pregunta 1
I don't remember any questions that stood out as difficult or unexpected.
Solicité el puesto por otro medio. El proceso duró 4 días. Acudí a una entrevista en NetApp (Bengaluru)
Entrevista
I got into 3 rounds and all of them were virtual
1) assesment which has a duration of about 1 hr 45 minutes where I got 30 MCQs and 3 Coding questions
2) it was an one-on-one interview where the interviewer asked about my resume and asked me to solve about 3 coding questions regarding strings
3) the final round was managerial round , he asked a lot about my resume and the projects I have done so far.
Preguntas de entrevista [1]
Pregunta 1
Solving 3 coding questions in one on one interview.
Solicité el puesto a través de un captador. Acudí a una entrevista en NetApp (Bengaluru) en abr 2025
Entrevista
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.
Preguntas de entrevista [3]
Pregunta 1
write a program to develop a navigation bar in React.js.
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