← Back to Directory

Palo Alto Networks interview notes, page 2 of 4

Large Enterprises

Most of these Palo Alto Networks write-ups come from Software Engineers (28), then Product Managers (2) and Backend Engineers (1). The most reported rounds are the technical phone screen (10), the system design round (8), the onsite coding round (4) and the product sense round (4).

31 interview notes · updated Sep 2026

Palo Alto Networks·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Went through a system design round at Palo Alto Networks for a software engineering role. Just one question, but it had enough surface area to go in a lot of directions.
  • Design a job scheduler system.

“This is one of those problems where you think you know it and then five minutes in you're drowning in edge cases.”

View Post

Palo Alto Networks·Software Engineer·Onsite - Multi Round

Jun 2026
Recruited for a bachelor's-level SWE role at Palo Alto Networks, the process stretched two months and felt pretty disorganized. There was a standard recruiter screen followed by a three-interview 'Power Day,' then a surprise fourth interview that got no-showed the first time and repeated questions I'd already answered when it finally happened. Ended up waitlisted after having to chase the recruiter down for any update at all.
  • Debugging question: walk through identifying and fixing a bug in a given piece of code.
  • Behavioral question about a past experience (repeated from an earlier round).

“They asked me this in the Power Day and then again word for word in the fourth interview.”

View Post

Palo Alto Networks·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Second round at Palo Alto Networks for a Security Researcher role, paired with someone who'd joined about a year prior from a similar background. Very low-key, mostly behavioral, and we even ended up talking about the cafeteria at some point. Felt more like a conversation than an interview.
  • Walk me through how you approach research. What does your methodology look like and how do you decide where to focus?

“This was the meat of the whole conversation.”

View Post

Palo Alto Networks·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Palo for a software engineer role. The core problem was a config management system for a fleet of devices, and the follow-ups pushed pretty hard on consistency and scale. Felt like a solid 45 minutes of back-and-forth.
  • Design a system that lets roughly 1,000 admin users manage configurations for roughly 1,000 devices, where configs are updated daily. Walk through the main APIs, the storage model, the rollout workflow, and how the system behaves operationally.
  • How would you scale this system if the number of devices and admins grew significantly?
  • How would you guarantee strong consistency for configuration updates across the system?

“This is a meaty one and I underestimated how much ground it covers.”

View Post

Palo Alto Networks·Software Engineer·Hiring Manager Screen

Jun 2026
Interviewed at Palo Alto Networks, one behavioral question about handling knowledge gaps with customers. Short and straightforward, nothing too intense.
  • What did you do when a customer asked you something you didn't know the answer to?

“I fumbled a bit here because I wanted to sound competent but also honest.”

View Post

Palo Alto Networks·Software Engineer·Hiring Manager Screen

Jun 2026
First real interview for this role, directly with the team lead. Mostly a deep dive into my research background since I'm coming from a PhD. Less of a structured interview, more of a 'walk me through everything you've done and why' kind of conversation.
  • Walk me through your past research projects and the methodology behind them.
  • How do you think about research methodology when scoping a new security problem?

“This took up most of the interview.”

View Post

Palo Alto Networks·Software Engineer·Technical Phone Screen

Jun 2026
Went through what felt like a standard senior eng screen at Palo Alto Networks, covering background, project deep dives, and a production incident story. Pretty thorough for a single round but nothing that blindsided me.
  • Walk me through your background and highlight one or two projects most relevant to this role, including your specific contributions, the technical decisions you made, trade-offs involved, and what the measurable impact was.
  • Describe a difficult bug or production incident you personally owned from start to finish. What happened, how did you handle it, and what did you take away from it?
  • What are you looking for in your next team?

“This is the question I always feel like I nail in my head beforehand and then ramble through in the actual call.”

View Post

Palo Alto Networks·Software Engineer·Technical Phone Screen

Jun 2026
Went through a structured screen for a software engineer role at Palo Alto Networks. The format was pretty well-defined: intro, resume walkthrough, a decision-making question, and then flip it around and ask them stuff. Nothing too surprising but it moved fast.
  • Give a 60 to 90 second self-introduction.
  • Walk me through one or two projects from your resume where you had measurable impact. Cover your role, the key technical decisions you made, any tradeoffs, and what the outcome was.
  • Describe a challenging technical or product decision you made, and walk through how you worked with other teams to get there.
  • What questions do you have for us about the role, the team, or where the product is headed?

“I always over-prepare this and then ramble anyway.”

View Post

Palo Alto Networks·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Palo Alto Networks for a software engineering role. The whole thing was one big sprawling question about building an ML orchestration platform, and it went pretty deep across a lot of dimensions.
  • Design a platform that orchestrates multiple independent ML model services (classification, embeddings, re-ranking, etc.) into end-to-end workflows for external users. Cover request routing, data flow between models, schema validation, intermediate storage and caching, results storage, model version management, failure handling, monitoring, scaling, and multi-tenant auth with rate limiting.
  • When would you use RPC versus REST for communication between these ML services, and what are the trade-offs around latency, schema evolution, observability, and backward compatibility?

“This question is basically a full system design exam crammed into one prompt.”

View Post

Palo Alto Networks·Software Engineer·Technical Phone Screen

Jun 2026
Palo Alto Networks coding round for a Software Engineer position. One algorithmic question that seemed manageable at first but had a follow-up that pushed things further than I expected.
  • Given a string representing a basic arithmetic expression with non-negative integers and the operators +, -, *, /, evaluate it and return the result. Integer division should truncate toward zero. You cannot use any built-in eval-style functions. Follow-up: extend the solution to handle parentheses.

“Got the base case working with a stack, tracking sign and handling operator precedence by pushing/popping for * and /.”

View Post