Palo Alto Networks Software Engineer candidates report coding assessments and live problem solving alongside debugging, system design, project discussion, behavioral questions, and, in one report, deep Linux and C++ topics.
$145K
Avg. Base Comp
$215K
Avg. Total Comp
3 rounds
Typical Rounds
3-5 weeks
Process Length
Palo Alto Networks Software Engineer interviews reported here are broader than a single LeetCode screen. Candidates described HackerRank or other coding assessments, recruiter conversations, live coding, debugging, system-design discussion, and behavioral questions. One candidate explicitly reported three interviews; another described a final morning of three back-to-back sessions after earlier steps. The overall number of rounds is therefore not consistently reported.
For coding, prepare to explain an approach before implementing it and to adapt when requirements change. Reported prompts included bracket matching, sliding-window logic, cycle detection, folder-tree traversal, string and interval work, anagram grouping, merge sort, and array/string fundamentals. One onsite-style report required a folder-tree solution written on paper, while another candidate said a live coding interviewer added constraints after a working implementation.
Systems preparation deserves attention alongside coding. One candidate faced detailed questions on Linux processes versus threads, IPC, signals, C++ static features, and smart pointers, plus debugging and modifying object-oriented code. Other candidates encountered architecture or system-design discussions about scaling, overload handling around a firewall, or a project they had built. Prepare a concise project walkthrough that covers design choices, tradeoffs, and how you would scale it.
Behavioral discussion also appeared in recruiter and later interviews, including initiative, collaboration, creative thinking, and past work. Evidence is thin for a single universal sequence, so use the reported topics to prepare flexibly rather than expecting every interview to follow the same format.
Synthesized from 11 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.
The technical bar felt very systems-oriented. I started with a HackerRank online assessment, then spoke with a recruiter about my background and past experience. That conversation also included a few STAR-style behavioral questions, including an example of a time I had to think outside the box. The remaining interviews were virtual. In one team panel, I worked through two coding questions: an easy stack problem based on matching brackets and a medium sliding-window problem.
The technical rounds went beyond standard coding. I was asked to discuss my projects, work through a basic system-design coding question, debug an existing piece of code, and make changes to code with an object-oriented focus. Another longer interview had two interviewers and lasted about an hour and a half. They were pleasant overall, but the questions were deep on Linux internals: threads versus processes, IPC, and signals. There were also C++ questions around static features and smart pointers, followed by a design question and discussion of my prior work.
I found the process demanding mostly because it combined practical debugging and code modification with systems knowledge rather than relying on algorithms alone. The interviewers were professional, though at times the pace felt hurried. I did not receive an offer. My main advice is to be ready to explain Linux processes, threads, IPC, and signals clearly, and to practice debugging and modifying existing object-oriented code in addition to preparing a bracket-stack problem and a sliding-window problem.
Prep tip from this candidate
Focus on Linux internals—especially processes, threads, IPC, and signals—and be prepared to debug and modify existing object-oriented code. Also practice a bracket-matching stack question, a medium sliding-window question, and discussing a scalable system design.
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 | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Prime to N | |
| Upsell Transactions | |
| Download Facts | |
| First Touch Attribution | |
| Job Recommendation | |
| Find the Missing Number | |
| Daily Retention Summary | |
| Recurring Character | |
| Scrambled Tickets | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report HackerRank or other coding assessments. One report described three questions in 90 minutes across string, interval, and anagram-grouping problems; another described easy-to-medium problems in an onsite-style assessment.
Candidates report recruiter conversations about background, recent work, and resume projects. Behavioral prompts mentioned thinking creatively, taking initiative, collaboration, and how the candidate handled a mistake.
Technical interviews may combine coding with practical changes to existing code. Reported examples include bracket matching, sliding-window logic, cycle detection, folder-tree traversal, debugging, and adapting an implementation to new requirements.
Candidates report system-design or architecture conversations, while one candidate described a deeper systems round on processes, threads, IPC, signals, C++, and smart pointers. Project scaling and design choices also appeared.
