The people you work with will be your best asset. Working in the Midwest, the people become like family and really care about each other. I can speak for other geos. Pay is good and benefits are great.
Leadership has no appreciation for talent. Teams are pitted against each other.
The "culture" is constantly talked about, but at the end of the day, leadership will sell their own grandparent for shareholders. Take note: they are no less slimy and elitist than any other publicly traded company; they just like to talk about the "culture" because they feel it keeps employees distracted from what is really going on.
Layoffs are a constant and very real fear.
Recognize talent. Admit that ONtap is so far behind the market and is out of touch. Learn how to successfully integrate new acquisitions. Finally, admit the culture and great place to work is just smoke and mirrors to distract from the layoffs.
I had two rounds of interviews via phone calls. The first round was with the campus manager. It was basically a review of my CV and a brief discussion about the company. The second round was with the manager and an engineer, focusing on technical as
I spoke with NetApp briefly at my college's career fair, which led to a couple of phone interviews. The first was a standard HR call. The second and third were light technical interviews, primarily discussing C/C++, OOP, and my development history.
I met their engineers at a campus career fair. After several minutes of chatting about my internship project, which is highly related to their products, I had totally forgotten about this conversation. Then, after maybe one to two months, HR called m
I had two rounds of interviews via phone calls. The first round was with the campus manager. It was basically a review of my CV and a brief discussion about the company. The second round was with the manager and an engineer, focusing on technical as
I spoke with NetApp briefly at my college's career fair, which led to a couple of phone interviews. The first was a standard HR call. The second and third were light technical interviews, primarily discussing C/C++, OOP, and my development history.
I met their engineers at a campus career fair. After several minutes of chatting about my internship project, which is highly related to their products, I had totally forgotten about this conversation. Then, after maybe one to two months, HR called m