← Back to Directory

Palo Alto Networks

Large Enterprises

Screna has 9 Palo Alto Networks interview write-ups. The most reported round is the system design round (3).

9 interview notes · updated Jun 2026

Palo Alto Networks·Software Engineer·Technical Phone Screen

Jun 2026
Palo Alto Networks coding round for a Software Engineer position. One algorithmic question with a follow-up, nothing too wild, but the follow-up caught me a little flat-footed.
  • Given a string representing a basic arithmetic expression with non-negative integers and +, -, *, / operators separated by spaces, evaluate it and return the result. Integer division should truncate toward zero. You cannot use any built-in expression evaluators like eval().
  • Follow-up: how would you extend your solution to handle parentheses, for example an expression like '2 * (3 + 4) - (1 + 2)'? Walk through how you'd adapt the stack-based approach.

“Stack-based solution, pretty classic.”

View Post

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

May 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. Pretty low-key, mostly behavioral stuff, and we even ended up chatting about the cafeteria food at some point. Felt more like a conversation than an interview.
  • Walk me through how you typically approach security research. What does your methodology look like?

“This was the meat of the whole conversation.”

View Post

Palo Alto Networks·Software Engineer·Onsite - Coding / Algorithms

May 2026
Interviewed for a software engineer role at Palo Alto Networks and had a coding round that included LeetCode 88. Pretty standard stuff, not much to report beyond that.
  • Merge two sorted arrays in-place, where the first array has enough space at the end to hold all elements from the second.

“Classic problem, I've seen it before.”

View Post

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

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

“This type of question always sounds more contained than it is.”

View Post

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

May 2026
Did a system design round at Palo Alto Networks for a software engineer role. The prompt was to design a metrics monitoring system, which sounds scoped but opens up pretty fast once you start pulling on the threads.
  • Design a metrics monitoring system.

“There's a lot hiding in this one.”

View Post

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

May 2026
Principal-level backend interview at Palo Alto Networks focused almost entirely on rate limiting, starting from a clean design and drilling progressively harder on concurrency and then distributed scale. Three connected questions, each building on the last, which I actually appreciated even though the third one got pretty hairy.
  • Design a rate limiter for an API gateway that supports per-key limits (per-user, per-IP, etc.) with a configurable N requests per T seconds window. Walk through the algorithm options and justify your choice.
  • How do you make the rate limiter thread-safe when multiple concurrent requests arrive for the same key at the same time?
  • Now scale this to very high QPS across many nodes. How do you handle distributed state, and what are the correctness trade-offs between centralized (e.g. Redis with atomic scripts) and in-process approaches with periodic sync?

“I went with sliding window counter because it avoids the burst problem at window boundaries that fixed window has, without the memory cost of storing every timestamp like sliding window log does.”

View Post

Palo Alto Networks·Software Engineer·Technical Phone Screen

May 2026
Initial screen for a Security Researcher role at Palo Alto Networks, conducted by a Principal Researcher. Similar structure to a parallel process I was running, but this one went deeper and closed with a trace analysis question I wasn't fully expecting.
  • Walk through a packet or execution trace and identify what is happening or what went wrong.

“This came at the end after what felt like a pretty conversational interview, so I wasn't mentally prepped for something that required actual focused analysis.”

View Post

Palo Alto Networks·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Did a virtual onsite coding round for a senior security researcher role at Palo Alto Networks. The whole thing got a bit chaotic because I expected to use C/C++ but was forced into Python, which I haven't touched in a while. Interviewer was decent about it and we pivoted to a discussion format, but I left genuinely unsure whether that helped or hurt me.
  • Given two programs that appear to work correctly, how would you verify the system won't have issues when actually running them?

“This is where things fell apart for me, at least on the execution side.”

View Post

Palo Alto Networks·Software Engineer·Technical Phone Screen

Apr 2026
Coding round at Palo Alto Networks for a software engineer role. The main problem was a greedy boats question, followed by some distributed systems follow-ups that I wasn't fully prepared for.
  • Given an array of people's weights and a boat weight limit where each boat holds at most two people, find the minimum number of boats needed to carry everyone.
  • How would you approach this problem if the input array is too large to fit in memory on a single machine?
  • If multiple workers are processing parts of the input at the same time, how do you ensure strong consistency in the results?

“Sorted the array and used two pointers.”

View Post