Palo Alto Networks Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 917 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 917 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Palo Alto Networks.
Palo Alto Networks
Senior Mechanical Design Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Background check
Interview formats
Behavioral Technical
The recruiter was professional and responded quickly. I had a chat with the hiring manager about my background and past work. It was more about general experience and how I manage work, not super technical on the mechanical design side. They decided not to move forward, saying other candidates were a better match for what they needed right now. It was nice that the recruiter was fast, but it would have been better if the interview was more technical to really check mechanical engineering skills and give a clearer idea of what they were looking for. It was a professional process, but they could have been clearer about how they were evaluating people.
Confirmed questions2 questions
- Can you discuss your previous work experience?
- What are your methods for managing work and your responsibilities?
Palo Alto Networks
Solution Consultant
Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Presentation Panel Technical screen
Interview formats
Behavioral Presentation Technical Case
The process at Palo Alto Networks is known to be thorough and demanding, typically spanning 4-6 weeks. It usually involves four main steps: HR Screening: An initial call to check for cultural fit, motivation, and salary expectations. Hiring Manager Interview: A discussion with the direct future manager to confirm pre-sales experience and understanding of the cybersecurity market. The Panel (Critical Stage): This is the core of the process. I had to prepare a presentation on a hypothetical client case for a panel of 3-4 people (sales, engineers, managers). The goal was to show my ability to 'sell the value' of the platform, not just the tech, and to handle objections live. Final Interview (VP/Director): A final check focusing on culture fit and long-term strategic vision.
Confirmed questions1 question
- How would you convince a CISO of a major CAC40 company, who is hesitant to commit solely to Palo Alto Networks and prefers a 'Best-of-Breed' approach to avoid 'Vendor Lock-in', that adopting a unified platform ('Platformization') is the superior choice for them?
Palo Alto Networks
UX Designer
Mid Difficult Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Onsite Panel Presentation
Interview formats
Behavioral Technical Presentation
It started with a call with HR, then a 2-hour design exercise. After that, there was a 2-hour session with a panel for portfolio review and behavioral questions. The last round was a behavioral question with the Head of Design. The HR didn't seem to know what was happening in each round, which was frustrating. They put the job on hold after I finished everything, which felt like a waste of time. Communication wasn't great about why this happened. I had to follow up a lot to find out. Also, not sure why they require an NDA for each interview stage; the process wasn't that special.
Confirmed questions2 questions
- Can you describe a time you dealt with a difficult person?
- How do you prioritize when faced with competing demands?
Palo Alto Networks
Machine Learning Engineer
Mid Difficult Neutral experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design Other
So the whole thing was broken down into 3 main stages. First up was just a casual coffee chat with the recruiter, mostly just talking about my background and why I was interested in the job, not really technical. Then I had an hour with the hiring manager, where we dove a bit deeper into my technical experience and they asked me some behavioral questions. The final stage was a 'super day' with three one-hour interviews with the team I'd be working with. The first interview was about a LeetCode-style design problem, the second one involved two system design questions focused on software, and the last interview was all about machine learning concepts.
Confirmed questions1 question
- Can you design and implement a logger class that supports logging based on different verbosity levels?
Palo Alto Networks Interview Questions
Quoted word for word from Palo Alto Networks interview reports.
“Find the words plus and minus in a string and return a string with the signs +- according to their position.”
Read reports →“From a given text file, can you filter out and return only the valid numbers?”
Read reports →“What is the bandwidth of a 16-bit data bus if it operates at 50 MHz and is only utilized 25% of the time?”
Read reports →“For an unsorted array of integers, what is the largest subset of numbers that, when sorted, exhibit a constant difference between adjacent elements?”
Read reports →“Given a binary tree, how would you remove all nodes that have only one child, excluding the root node?”
Read report →“Could you provide a list containing only the unique strings from a randomly generated list?”
Read report →“Can you build a process tree given a list of process IDs and their parent IDs?”
Read report →“And for each of those links, could you then list all the links that appear on those pages too, and keep doing that until you've found all of them?”
Read report →“What could cause a system using SetInterval to update a page color to freeze when a user inputs a large BigInt, and this number grows?”
Read report →Formats, difficulty and experience
Across all 917 Palo Alto Networks interview reports.