Palo Alto Networks interview notes, page 1 of 4

“Spent the first few minutes just trying to nail down what kind of metrics we're talking about.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This was the whole interview basically.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went with sliding window counter because it smooths out burst traffic better than fixed window without the memory cost of a full log.” The rest of the author's notes on Backend Engineer interview at Palo Alto Networks, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to go broad and just list channels, which was probably the wrong move.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“LeetCode 88.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew it was an LRU cache the second they finished the sentence, which was both reassuring and a trap because I rushed into code before properly explaining the structure.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is where things went sideways for me.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with target audience segmentation which felt right, but I think I spent too long on that and rushed the channel strategy.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one looked manageable at first glance but the complexity stacks up fast.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is the one that tripped me up a bit.” The rest of the author's notes on Software Engineer interview at Palo Alto Networks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.