Real, anonymous reports from people who interviewed for Software Engineer at Palo Alto Networks, newest first and distilled into what to expect across the loop.
Get your personalized Palo Alto Networks Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My process began after a recruiter screen, and then the rest of the interview chain happened virtually over a few technical rounds. The first technical round felt like a fairly standard system-design-flavored coding question, then I moved straight into fixing a bug in code. By the time I reached the last round, it had shifted again into something more object-oriented in spirit—modifying an existing codebase rather than starting from scratch.
Even before the coding, I had one earlier interview that was more project-focused than technical drills. I walked through a project in depth and we discussed specific design decisions and trade-offs, plus how I was adopting AI in the kind of work I’d been doing. The conversation included coding-adjacent discussion, so it didn’t feel like pure behavioral interview questions.
3 months ago
Average Negative United States
My experience wasn’t just about the technical work—it was also shaped by communication issues that threw off the whole timeline. I went through early stages with recruiters, and the process initially started positively. Then, suddenly, the updates stopped completely: no replies to emails, no answers to phone calls, and no clear next step.
At one point, I even scheduled an interview and then the interviewer didn’t show up. That compounded the frustration because it made the silence feel even more unprofessional. The technical parts never really got a fair chance to play out once I was stuck waiting without feedback.
4 months ago
Average Positive Santa Clara, CA
After an online HackerRank-style assessment, I went through a pretty long set of stages that combined behavioral prompts with technical work. I answer…
4 months ago
Difficult Neutral Santa Clara, CA
I knew it was going to be a LeetCode-and-system-design style process, but I was honestly unsure what to expect at the start. The recruiting team gave …
4 months ago
Average Positive Tel Aviv-Yafo
I went through a fairly test-heavy path before I ever got to a live conversation. The first stage was a 90-minute set of three questions. One was abou…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically starts with a recruiter screen, followed by a mix of online assessments and multiple back-to-back technical rounds that include both coding and behavioral questions. Candidates noted that the timeline can feel rushed, with some experiencing communication issues that added to the stress.
Candidates can expect a variety of technical assessments, including online coding challenges that resemble LeetCode problems, followed by live coding interviews that require problem-solving and debugging on the spot. The difficulty of these assessments varies, but many found them to be average to challenging, with some noting a focus on algorithms and data structures.
LeetCode-styleCoding challengesAlgorithms
System Design & Object-Oriented Questions
Interviews often include system design questions and object-oriented programming tasks, where candidates may need to modify existing code or discuss design trade-offs. This aspect is crucial for demonstrating both technical knowledge and the ability to adapt to changing requirements during the interview.
System designObject-oriented programmingAdaptability
Behavioral & Fit Interviews
Behavioral interviews are integrated into the process, focusing on candidates' past experiences, project discussions, and how they handle challenges. Interviewers seem to prioritize cultural fit and communication skills, assessing how candidates would operate within the team.
The overall difficulty of the interview process is often described as average, but candidates report feeling mentally drained due to the intensity and pace of the rounds. Some candidates experienced unprofessional interactions that negatively impacted their perception of the process.
Average difficultyMental drainProfessionalism
Feedback & Communication
Candidates frequently expressed frustration with the lack of timely feedback and clear communication throughout the process, which contributed to feelings of uncertainty and stress. This aspect can significantly affect the overall candidate experience.