Palo Alto Networks software engineer interviews combine recruiter contact, timed coding, technical screens and a multi-interview loop. Candidates report coding, systems, networking and behavioral questions, over roughly two to six months.
$150K
Avg. Base Comp
$200K
Avg. Total Comp
3-6 rounds
Typical Rounds
2-6 months
Process Length
Candidates who interviewed as Software Engineers at Palo Alto Networks describe a loop that is part LeetCode-style coding, part practical systems and networking, and it differs a good deal by team. Many start with a recruiter or HR conversation, and several include a timed HackerRank-style assessment. One candidate faced three questions in 90 minutes: a string problem, an intervals problem and grouping strings into anagrams.
Coding questions are mostly easy to medium: bracket matching with a stack, sliding-window logic, cycle detection, interval merging and printing a folder-tree hierarchy by hand on paper. In one live round the interviewer added new requirements after the first solution worked, so practice modifying finished code rather than stopping at a working answer.
Beyond algorithms, candidates mention pagination with in-memory caching, Linux processes, threads, IPC and signals, C++ smart pointers, debugging existing object-oriented code, JSON handling and test design, and OSI layers or routing protocols. System design reports vary. One candidate found a firewall-and-too-many-requests discussion open-ended, so talk through your reasoning and ask clarifying questions. Another loop ended with a role-play pitch of a security solution.
Timelines range from about two months to about six, and some candidates describe long silences. Outcomes are mixed: most reports here ended without an offer, one involved a headcount delay after positive recruiter feedback, and two candidates received offers, one of them after a hackathon-based process.
Synthesized from 38 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 | |
| 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 | |
| Rolling Bank Transactions | |
| String Shift | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| Download Facts | |
| First Touch Attribution | |
| Job Recommendation | |
| Daily Retention Summary | |
| Recurring Character | |
| Find the Missing Number | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe starting with a recruiter or HR conversation about their background, resume and the role, sometimes after a referral. One recruiter call opened with a tell-me-about-yourself prompt and walked through recent work, and the recruiting team explained the next steps.
Several candidates report a timed online coding test. In one case it was a HackerRank with three questions in 90 minutes covering a string problem, intervals and anagram grouping, and the candidate ran short on time for the last one. That candidate also completed an online behavioral survey with no video recording.
Screens with a team lead or hiring manager ranged from a 30-minute call about a feature the candidate built to an hour-long conversation on architecture, scalability, caching and security. Others included a short coding problem, such as a string task or bracket matching, so a clear spoken walkthrough of your own work helps.
Reports describe three 45-minute interviews in one morning, a four-round on-site, and a longer two-interviewer session. Topics include coding, debugging, modifying object-oriented code, Linux internals, JSON and test design, graph problems, system design and behavioral prompts about initiative and collaboration.
Outcomes and communication vary. Two candidates reported receiving offers, most reported no offer, and one was told headcount was unconfirmed despite positive recruiter feedback. Others described waiting weeks or months without updates, so ask about next steps and timing in writing.
