real interview stories, told over a cup of tea ♡
Palo Alto Networks Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
10 results
- Debugging Exercise, LeetCode, System Design and AI QuestionsPalo Alto Networks · Software Engineer · Technical Screen · Oct 2026Offer
To get ready, I worked through a well-known list of 150 LeetCode problems, the lessons from an online system design course, that course's drills for debugging and refactoring code that already exists, and a few YouTube walkthroughs of classic system design questions. In system design I mostly picked simpler problems and read up on fundamentals such as APIs, caching, databases and concurrency. I a…
- Account Executive interview at Palo Alto Networks: cut-off Zoom callPalo Alto Networks · Account Executive · Jul 2026
What began as a normal Zoom interview stopped abruptly after about forty minutes. I tried to reconnect and followed up repeatedly, but heard nothing for roughly a week. When someone finally responded, it was simply to say they were no longer considering candidates. The early cutoff and lack of closure left me confused about whether the interview had ended properly on their side or whether I was s…
- Palo Alto Networks Software Engineer interview experience: missed interview follow-upPalo Alto Networks · Software Engineer · Jul 2026No response
The technical content was not what defined this process for me. Recruiter contact started well, then communication stopped. My emails and phone outreach went unanswered, and even an interview that had been scheduled did not happen as expected. There was a no-show situation where I was left waiting without follow-up. That missed interview felt secondary to the larger problem: I never received any…
- Palo Alto Networks Software Engineer interview: project decisions and AIPalo Alto Networks · Software Engineer · HR Screen · Jul 2026
After applying, I had a recruiter phone screen about my experience and the technologies I had used. Soon afterward, the technical discussion focused on how I had built real projects: one project in depth, the design decisions I made, and the trade-offs behind them. That conversation also included how I had considered adopting AI in my current work. Coding-related exchanges were woven into the pro…
- Software Engineer interview at Palo Alto Networks: interview experiencePalo Alto Networks · Software Engineer · Online Assessment · Jul 2026
I started with an online assessment and then had three virtual technical rounds. The first was a system-design-and-coding-style prompt where I implemented a solution. It soon turned into debugging existing code to fix a bug, with the focus on making the code work under constraints rather than on theory. In the final round, I had to modify the code again in an object-oriented way, changing both it…
- Palo Alto Networks Software Engineer interview: three-hour mixed evaluationPalo Alto Networks · Software Engineer · Online Assessment · Jun 2026
I began with an online HackerRank completed on my own. Next came behavioral questions on HireVue, without video recording. A recruiter call followed with the usual request to walk through myself and similar basics, meant to confirm fit and direction before the deeper stages. The next step was the largest one. The recruiter said it would take around three hours, and that was how it played out: rou…
- Five Onsite Rounds, Rejected via Candidate PortalPalo Alto Networks · Software Engineer · Onsite · Feb 2026Rejected
I interviewed with them at the end of last month. First I talked with the HM, and a week later I went onsite at the company. There were five rounds total, 45 minutes each. Every round started with questions about past projects, then a lot of content around k8s, networking, and cloud. Coding included typical LeetCode-style problems, plus one simple BFS. Design included a scheduler and metrics moni…
- Sloppy Scheduling, No Lunch, and a Surprisingly Easy OnsitePalo Alto Networks · Software Engineer · Onsite · Jan 2026
First, let me vent about the interview experience here — it was very unprofessional. From start to finish I never received a single HR email; it was always unscheduled phone calls, and I never got any prep doc either. Contact was basically one-way. After the HR call in January, almost a month went by with no movement, and I figured it was dead. Then suddenly they reached out to schedule the hirin…
- An Algorithm Question That Turned Into System DesignPalo Alto Networks · Software Engineer · Onsite · Sep 2025
Interview Process Introduced ourselves to each other Asked about resume details (the interviewer was pretty funny — he saw on my resume that I mentioned how much revenue my project had contributed, and he actually asked whether the company had actually paid me that money) Algorithm question / system design Questions for the interviewer Algorithm Question / System Design This part was interesting.…
- Architecture Walkthrough Then Build on Top of ItPalo Alto Networks · Software Engineer · Onsite · Sep 2025
Interview process Introduced ourselves to each other Asked about resume details A simple algorithm warm-up question System design based on the team's existing architecture Q&A for the interviewer Algorithm question: 226. Invert Binary Tree Wrote it on the whiteboard and did a dry run. System design This team is similar to an ML Infra team — the ML team provides a bunch of models, wraps them into…