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.
I started with an online assessment and then went straight into three virtual technical rounds. The first round felt like a fairly standard system-design-and-coding style prompt where I implemented the solution, and then the next part quickly shifted into a debugging-style task—fixing a bug in the existing code. It was all focused on making the code work correctly under constraints rather than a lot of theory.
In the final round, I had to modify the code again with an object-oriented flavor, which meant adjusting behavior and structure rather than just patching one spot. The whole loop felt technical and practical, with a steady progression from build → debug → improve, and overall it landed as an average-difficulty process even though I didn’t make it to an offer. By the end, I felt like the interviewers were testing how I iterate on code when the requirements evolve.
2 months ago
Average Neutral Utah, IL
After I applied, I had a recruiter phone screen where I walked through my experience and the technologies I’d worked with. A short time later, I moved into a technical conversation that leaned heavily on how I’d built and reasoned about real projects—covering deep dives into a specific project, the design decisions I made, and the trade-offs behind them.
That technical round also pulled in how I’d thought about adopting AI in my current work, so the discussion wasn’t purely coding. I ended up having coding-related exchanges layered into the project story, which made it feel less like a standalone algorithm test and more like explaining my engineering choices out loud.
2 months ago
Average Negative United States
My experience wasn’t shaped by the technical difficulty so much as by how the process went silent. I interacted with recruiters through the process, a…
2 months ago
Average Positive Santa Clara, CA
My process started with an online HackerRank that I completed by myself, then it moved into a set of behavioral questions on HireVue with no video rec…
2 months ago
Difficult Positive United States
I went through an assessment that combined coding with an overall coding-execution style flow, followed by a short behavioral interview. Then I was pu…
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
Initial Assessment & Screening
Candidates typically start with an online coding assessment or a recruiter phone screen, which often includes discussing their background and technology experience. This initial stage sets the tone for the technical depth expected in later interviews.
The technical interviews generally consist of multiple rounds that may include coding, debugging, and system design questions, often requiring candidates to adapt their solutions based on evolving requirements. This iterative approach emphasizes practical coding skills and problem-solving under constraints.
CodingDebuggingSystem design
Behavioral Components
Interviews often blend technical questions with behavioral assessments, focusing on how candidates communicate their thought processes and decisions related to past projects. This dual focus aims to gauge both technical expertise and interpersonal skills.
Candidates have reported mixed experiences regarding communication throughout the process, with some experiencing delays or a lack of follow-up after interviews. This inconsistency can lead to frustration and uncertainty about their status.
CommunicationFollow-upFrustration
Interview Difficulty & Expectations
Overall, candidates describe the interview difficulty as average, but the experience can vary significantly based on the interviewer's approach and the clarity of expectations set during the process. Some candidates felt unprepared for the technical depth required.
Average difficultyExpectationsPreparation
Atmosphere & Professionalism
The interview atmosphere is generally described as friendly and professional, although some candidates encountered unprofessional behavior that negatively impacted their experience. A respectful environment is crucial for a positive interview experience.