Palo Alto Networks·Software Engineer·Onsite - System Design / Architecture
- 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.”
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
“This is one of those problems where you think you know it and then five minutes in you're drowning in edge cases.”
“They asked me this in the Power Day and then again word for word in the fourth interview.”
“This was the meat of the whole conversation.”
“This is a meaty one and I underestimated how much ground it covers.”
“I fumbled a bit here because I wanted to sound competent but also honest.”
“This took up most of the interview.”
“This is the question I always feel like I nail in my head beforehand and then ramble through in the actual call.”
“I always over-prepare this and then ramble anyway.”
“This question is basically a full system design exam crammed into one prompt.”
“Got the base case working with a stack, tracking sign and handling operator precedence by pushing/popping for * and /.”