Candidates report a Palo Alto Networks security engineering process built around an HR screen, a protocol-heavy technical round, and a behavioral or HR step. Expect SSL, VPN and troubleshooting depth, and be ready for uneven recruiter communication.
$151K
Avg. Base Comp
$236K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Palo Alto Networks security engineering candidates describe technical depth in network and secure-connection fundamentals. One Security Engineer candidate reported an on-site technical round that went deep on SSL, HTTPS and VPNs, with questions that wanted an explanation of how a secure connection forms and how a VPN tunnel is established, not a textbook definition. The same candidate then faced a managerial, behavioral round about problems they had faced and solved at work, and said specific examples from their own experience were what the interviewers seemed to want.
A separate candidate, interviewing for a Cyber Security Researcher role, described three rounds: a contractor-run technical screen, a Palo Alto-run technical round, and an HR conversation about salary and notice period. The contractor screen covered tracing a packet through a network, how a TCP connection is established and IP header fields. The Palo Alto round moved into scenario-based troubleshooting, including high availability, SSL/TLS and routing at roughly CCNA/CCNP depth. That candidate reported an accepted offer.
The Security Engineer reports did not end well. One candidate was rejected after a final HR call. Another said a recruiter joined a call about fifteen minutes late, seemed unfamiliar with their resume, and then stopped responding. That is one report, so don't treat it as the norm, but it is reasonable to ask for a timeline and next steps early. For preparation, practice explaining each layer of a connection and how a failure would show up there, and prepare two or three concrete problem-solving stories.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Palo Alto Networks process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Palo Alto Networks
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| DDoS Attack Response | |
| Client Solution Pushback | |
| Azure Kubernetes Infrastructure | |
| Find Bigrams | |
| Find the Missing Number | |
| String Shift | |
| Scrambled Tickets | |
| Get Top N Frequent Words | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Prime to N | |
| Good Grades and Favorite Colors | |
| Recurring Character | |
| Friendship Timeline | |
| Permutation Palindrome | |
| Weekly Aggregation | |
| Complete Addresses | |
| Hurdles In Data Projects | |
| The Brackets Problem | |
| N-gram Dictionary | |
| Cyclic Detection | |
| Find the Index with Equal Left and Right Sum | |
| Level Of Rain Water In 2D Terrain | |
| String Subsequence | |
| Flatten N-Dimensional Array to 1D Array | |
| Longest Increasing Subsequence | |
| Nearest Common Ancestor | |
| Radix Addition | |
| Impute Median |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with an HR phone screen or recruiter call. One candidate said the recruiter was late and unprepared and then stopped responding, so it may help to ask early about next steps and timing and to keep a record of follow-ups.
One candidate for a researcher role described a contractor-run technical screen covering how a packet travels through a network, how a TCP connection is established, and what fields sit in an IP header. It may be worth rehearsing these fundamentals aloud.
A Security Engineer candidate reported an on-site technical round that went deep on SSL, HTTPS and VPNs. The researcher-role candidate reported a Palo Alto-run round that started with basics and climbed to scenario-based troubleshooting, including high availability, SSL/TLS and routing.
One Security Engineer candidate reported a managerial round asking how they handled past problems and what problems they had solved at their company. They prepared specific examples from their own work, which seemed to be what interviewers wanted.
Candidates report ending with an HR call. One Security Engineer candidate received a rejection on that call. The researcher-role candidate discussed salary and notice period and later accepted an offer, so it is sensible to have compensation expectations and a start date ready.
