Palo Alto Networks · Primly Community

Palo Alto Networks onsite / final round, how it really goes: my detailed notes from 2026

mobile_mara · 6 replies

Just finished the PANW onsite for a senior security engineer role (AppSec-adjacent). This was a virtual onsite across four 55-minute sessions on a Thursday. Writing it up in detail because I found fragmented info when prepping and wanted to give someone the full picture.

Round 1: Coding Graph problem, medium difficulty. Cycle detection variant. I coded in Python. Interviewer was an SWE from the Cortex team, didn't have deep security background himself, was focused purely on code quality and communication.

Round 2: System Design Design a distributed rate-limiting service for an API gateway that might be protecting against DDoS-style abuse. Security context baked in. Talked through token bucket vs. leaky bucket, how to keep rate limit state consistent across nodes, Redis as a fast in-memory layer with Postgres fallback for auditing. They pushed on: what if Redis goes down? What if your network partition splits the rate-limit state?

Round 3: Behavioral / Values One interviewer, felt more like a conversation than an interrogation. Questions: tell me about a conflict with a teammate, tell me about a security incident you were involved in and what you learned, and one 'where do you want to be in three years.' Roughly 30 min behavioral, 20 min for my questions to them.

Round 4: Hiring Manager Was the actual hiring manager for the team. This round felt the most like a mutual evaluation. She asked about my preferred working style, how I handle unclear requirements, and we spent probably 15 min talking about the team's current roadmap. Read the PANW blog and their recent product announcements before this round. She noticed I'd done homework.

Logistics: All Zoom. No whiteboard, CoderPad for coding, Excalidraw link shared for system design. Debrief took 6 business days. Offer came on day 7.

Happy to answer questions.

6 replies

ml_mike

Six days for debrief is actually pretty normal. Did they give any signal during the rounds, or total poker faces?

sec_sasha

Round 1 interviewer smiled a lot and gave me a hint, which felt good. Round 3 was more neutral. I genuinely couldn't tell until I got the call. Don't read too much into interviewer body language.

de_derek

The Redis-goes-down question is evergreen. They ask some version of it at basically every distributed systems design round everywhere. You need a canned answer for single-node-of-failure scenarios.

brand_ben

The HM round being the last round is actually a good sign. It means you've cleared the technical bar by that point and the conversation is more about fit and mutual interest. Treat it accordingly, ask real questions.

firsttime_mgr

Is the onsite the same for new grad / entry level, or different format entirely?

sec_sasha

From what I know, new grad onsite drops the system design round or replaces it with a second coding round. Behavioral is still there. Check with your recruiter to confirm the exact format for your req.