Great place to learn, but bad WLB
Great place to learn, but bad WLB
Good learnings, smart people to work with. Stable (no mass layoffs) because security in general is stable and in demand.
Bad work-life balance. Sometimes work gets too stressful.
Increasing politics. Instances of nepotism/cronyism are increasing.
Improve work-life balance and focus on the long-term quality of the products.
Additional Ratings
Was this helpful?
Palo Alto Networks Interview Questions
Palo Alto Networks Interview Experiences
Principal Software Engineer
I interviewed for a role in the DLP team. I was to come to the office for four rounds of interviews after the HM screening. I had a coding round, which was by far the worst I'd had in a long time. The question wasn't hard. The interviewer allocated
Principal Software Engineer
Very organized, but the interview process was long. The process covered: * Coding exercises * Data structures * System design * Networking * Puzzles * Debugging skills assessment It started with a phone screen, followed by an on-site coding exercis
Principal Software Engineer
A recruiter called and set up a time for a phone screen. I was interviewed via video for 45 minutes. The coding portion was very easy and I finished it in 20 minutes. The system design was more open-ended, so we kept discussing its depth.
Principal Software Engineer
Santa Clara, California, United StatesMay 1, 2025I interviewed for a role in the DLP team. I was to come to the office for four rounds of interviews after the HM screening. I had a coding round, which was by far the worst I'd had in a long time. The question wasn't hard. The interviewer allocated
Principal Software Engineer
Santa Clara, California, United StatesJune 1, 2018Very organized, but the interview process was long. The process covered: * Coding exercises * Data structures * System design * Networking * Puzzles * Debugging skills assessment It started with a phone screen, followed by an on-site coding exercis
Principal Software Engineer
United StatesDecember 3, 2021A recruiter called and set up a time for a phone screen. I was interviewed via video for 45 minutes. The coding portion was very easy and I finished it in 20 minutes. The system design was more open-ended, so we kept discussing its depth.
