Palo Alto Networks runs a fairly conventional big-tech engineering loop for its India campus and off-campus hires: an online assessment gates candidates with DSA plus aptitude/MCQs, followed by two or three live technical interviews mixing coding (trees, arrays, hash tables), a bit of high-level design and DBMS/SQL, and often a final conversation with a director or hiring manager about past projects and PANW's problem space. Candidates without a formal CS background report being probed hard on core CS fundamentals (networking, operating systems) alongside code, which is a notable failure mode. For non-engineering roles (Unit 42 red-team, sales engineering), applicants describe long, sometimes stalled recruiter-led screens before any technical evaluation.
These 3 writeups cover software engineering, security research, sales engineering roles, India campus + APAC security roles. All of them were posted under a forum handle, so we could not verify the authors’ identities.
1Online AssessmentOnline assessmentMCQs on DSA topics plus two basic DSA coding questions on the OA platform.Covered: Data structures & algorithms, MCQ
2Technical Interview 1TechnicalTwo live coding problems: find the median of two sorted arrays, and compute the bottom view of a binary tree. Standard mid-tier DSA on shared editor.Covered: Arrays & strings, Trees
3Technical Interview 2TechnicalImplement a hash table from scratch without inbuilt maps, plus discussion of DBMS/backend concepts including JWT-based authentication flow and REST semantics.Covered: Hash tables, DBMS, SQL, API design
4Core CS + fitTechnicalDeep-dive on core computer science subjects. Candidate (non-CS background) was probed on computer networks and OS and was told at the verdict that a gap here drove the rejection.Covered: Networking, Operating systems
1Online AssessmentOnline assessmentTwo easy/medium coding questions plus about thirty aptitude MCQs on the OA platform.Covered: Data structures & algorithms, Aptitude
2Technical 1 (HLD + coding + backend)TechnicalOpened with a high-level design of a social media site, then a straightforward string-manipulation coding question, and finally a discussion of DBMS and REST-heavy backend concepts.Covered: System design, Arrays & strings, DBMS, API design
3Technical 2 (coding + SQL + resume)TechnicalOne medium coding problem built around a hashmap, several SQL queries, and questions about the candidate's prior internships.Covered: Hash tables, SQL, Past projects
4Director of EngineeringHiring managerTwo open-ended discussions about ongoing PANW engineering problems and how the candidate would approach them, mixed with more depth on past internship work.Covered: Past projects, Behavioral
Unit 42 red teamer
Outcome not shared
Experienced. 1 round. Shared by u/thehunter699 on reddit, 2023-12-20
1Recruiter screen (never held)Phone screenApplicant for a Sydney-based Unit 42 red team role was contacted by an India-based PAN recruiter roughly a month after applying. The recruiter proposed a time-alignment call to check that role interests matched, but scheduling collapsed over the AU-vs-IST time gap and the recruiter went silent. No technical rounds occurred.Covered: Domain knowledge, Behavioral
What Palo Alto Networks is hiring for now
1,348 open roles in our index. Advertised pay floors run $145k to $206k (median $172k, from 537 postings that state pay).
What is the interview process like at Palo Alto Networks?
Palo Alto Networks runs a fairly conventional big-tech engineering loop for its India campus and off-campus hires: an online assessment gates candidates with DSA plus aptitude/MCQs, followed by two or three live technical interviews mixing coding (trees, arrays, hash tables), a bit of high-level design and DBMS/SQL, and often a final conversation with a director or hiring manager about past projects and PANW's problem space. Candidates without a formal CS background report being probed hard on core CS fundamentals (networking, operating systems) alongside code, which is a notable failure mode. For non-engineering roles (Unit 42 red-team, sales engineering), applicants describe long, sometimes stalled recruiter-led screens before any technical evaluation.
What topics does Palo Alto Networks test in interviews?
Commonly reported topics include Data structures & algorithms, Arrays & strings, Trees, Hash tables, System design, DBMS.
These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.