Palo Alto Networks Interview Questions

An unpleasant experience. unprofessional. A recruiter called to coordinate: a minute of conversation and said that someone else would call. After a day she called and in a short conversation scheduled an interview with a team leader for an hour and a half. I asked more info' about the interview, requirements and the job itself - she promised that they would get back to me. They didn't come back. At the very beginning of the interview: it was said that it was scheduled for an hour (even though I cleared an hour and a half). I was asked if they explained the position to me: I said they promised to get back to me and did not. There are *13 minutes* left to apply a technical question. I began to think under pressure about a solution and began to implement (in parallel). I said it was not applicable to the time given. Even on a solution I was barely able to think that I was up to it with a stopwatch. Really disrespectful! After a few days I got an automatic email + second email to be filled out anonymously so that they can improve in future interviews.

There was a recruiter call, manager interview where i described a system i worked on previously, pair programming session and then 3 more technical - 2 coding and 1 system design. The interviewers were relatively nice except for one who barely made eye contact and was not really interested in what i had to say from the beginning.

Long interview process, recruiter is also a bird brain who can’t keep track of candidates for her life. Hiring freeze and made me waste my time. I’ll be sending an invoice for the hours they’ve wasted

Process took 3+ months – screening interview with recruiter, call with hiring manager, 1st panel interview with 2 leaders, another panel interview with 3 individuals, and a call with the HRBP. The process was dragged out and the final decision process took over 3 weeks. For anyone interviewing for Prisma Cloud roles: The Prisma Cloud team has a lot of attrition, executive departures, and had low quota attainment over the past 12 months. the overlay teams are very different cultures than the roles on the core sales team. Highly recommend doing your due diligence on the role and surrounding team

Recruiter call, followed by Basic linux questions and general questions from team lead and at home test containing python and linux challenge followed by panel interview . Scenario based questions as well as technical questions regarding tech support and customer success

Tested only the skills that are actually relevant to do the job (instead of pure leetcode and general CS fundamentals). Everyone was very humble and open, even distinguished engineer and people from higher ups.

Great interview; the questions were suitable for the position and the interviewer didn't rush me. When I got the decline email, the interviewer gave me a feedback that helped me to be more accurate with my answers in my next interviews.

Phone call with the company recruiter to hear about the job description and describe my technology stack. Technical phone call for 30 minutes with the team lead. Technical zoom interview for 1.5 hours. Present one maim project, answer technical questions.

Two interviews, 1:1 + 4 panel. Very fair, well rounded questions. They'll make you feel very comfortable, but the process could take months. Overall not a bad experience. Video is required if remote.

Sporadic place with zero humanity. They approached me, I was not looking. They sent out an email explaining why I am not the right fit. Disgusting as I never even thought about moving to such a bad company. Recruiting processes that are simply ugly.