Pros: Nice benefits. Fairly competitive pay. Good WLB. Tech stack is mostly up to date. Had lots of flexibility here and was mostly happy with my day-to-day work. Was never too demanding and was able to maintain a life outside of work very easily. Management was flexible with vacation time and sometimes granted extra vacay time for getting big projects out the door. Not a lot of legacy tech; it feels like we stayed up with industry standards.

Cons: Constant churn, very chaotic. No vision or direction. Unstable (layoffs frequently). Minimal R&D. Bad management. Huge communication gaps in the organization. I worked on 4 different products in the 5 years that I was at NetApp. Management was constantly ripping the rug out from under us and moving us to the hot new product. It could be really jarring at times, especially after getting comfortable with something new. Layoffs happened 3 times while I was there, and I was affected as well (severance is solid, though, fwiw). The company is surviving off legacy products and rolling the dice every 2 years or so on 10+ different product lines to see if something lands (usually with no success). Long story short, it's a good paying, easy role with solid WLB. But career growth is difficult here, and the work is really chaotic.

Pros: Good environment, talented engineers, good projects. You will definitely enjoy working here. Lots of exciting projects. One of the best storage companies.

Cons: Decent salary. Feature development takes a long time. Off late, the company is not doing well.

Pros: Work-life balance, amazing people, interesting work.

Cons: Limited $ and resources in engineering. Most employees' mentality is to just go to work as a job, and take advantage of the strong work-life balance and benefits. There's no incentive to take ownership and do more because pay is much lower (very little equity is given) compared to other tech companies, and vertical movement is very slow progress. Ramp-up speed is also very slow. Every transfer of knowledge is done by word of mouth rather than written documentation. If there is documentation, it's very outdated. Ramp-up should not be so painful. When a senior engineer leaves, the knowledge/expertise is lost.