Palo Alto Networks logo

Palo Alto Networks Technical Support Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 43 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
62.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Palo Alto Networks.

Showing 3 of 43
Palo Alto Networks logo
Palo Alto Networks

Technical Support Engineer

Engineering

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Offer
Interview formats
Technical Behavioral

I got contacted by a recruiter on Linkedin for a technical support engineer role, they said no firewall experience was needed. I passed two phone screenings and then got invited for an onsite interview. The interview was 3 hours long. I met with two engineers for 45 mins, then two more engineers for another 45 mins, and finally met with two managers. The first two engineers were kind of arrogant and rude, they smirked when I didn't know an answer. The other engineers and managers were professional though. A couple days later, I got an email from a manager wanting to talk more about the job, I thought it was an offer. But it wasn't, they wanted to hire me as a contractor first and then maybe full time if a position opened up, no promises. I'm not recommending this because of the immature behavior of the first two engineers, everyone else was good.

Confirmed questions8 questions
  • Can you describe the journey of a packet when it's trying to access google.com?
  • What is the size in bytes of a TCP handshake?
  • What are the names of the OSI layers?
Palo Alto Networks logo
Palo Alto Networks

Technical Support Engineer

Engineering

Entry Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Phone screen Onsite
Interview formats
Technical Coding Behavioral

I sent in my application online. Then, a recruiter from Talent Acquisition reached out. She gave me the lowdown on the job and how things are at the company, and asked me to tell her a bit about myself. After our chat, there was a quick 15-minute coding test with multiple-choice questions on stuff like TCP/IP, routing, and MITM, all while the recruiter was still on the line. Following that, there were two more interviews. The next one was with my potential manager and a senior engineer, where they asked me a mix of technical and behavioral questions. The final interview involved two team members and went deep into technical details, mostly focusing on packet-level concepts.

Confirmed questions4 questions
  • Can you describe TCP/IP headers?
  • How does an IPSec Tunnel work?
  • Tell me about OSPF and BGP.
Palo Alto Networks logo
Palo Alto Networks

Technical Support Engineer

Engineering

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral

I went through three technical interviews. They didn't ask any good technical questions, just basic textbook TCP stuff from their inexperienced team. They didn't ask about my troubleshooting experience, which was weird since they seemed less experienced than me. The first two interviews with the hiring manager and team were fine. But the third one felt like the interviewer was just Googling basic TCP questions. I think he wasn't that experienced because when I gave a quicker solution to one question, he didn't like it and asked me to explain the packet capture output. Honestly, do they always do packet captures when customers call? Because customers calling support are usually Tier 2/3 network engineers who have already done their own troubleshooting. So, asking them to do packet captures again just wastes their time. I think Palo Alto needs more experienced people on their technical interview panel. I do like the company and use their products though.

Confirmed questions4 questions
  • All the TCP questions you'd find in a textbook.
  • Questions about packet captures.
  • You need to answer exactly as they expect, not with your own quicker methods.

Palo Alto Networks Technical Support Engineer Interview Questions

Quoted word for word from Palo Alto Networks interview reports.

When comparing security, is SSL or VPN the more secure option?

Read reports

Can you identify the source IP address when a user node requests a DHCP packet?

Read reports

Could you list all the flag fields in Wireshark for an ICMP ping?

Read report

If a firewall is situated between two devices and a TCP handshake occurs, but the firewall fails to recognize the ACK bit, what would be the consequence?

Read report

Regarding HTTP status codes, what does 404, 408, and 200 signify?

Read report

Is it possible for the DHCP server and DHCP client to be in different L2 domains?

Read report

Formats, difficulty and experience

Across all 43 Palo Alto Networks interview reports.

Interview formats

Technical 52.3%
Behavioral 39.5%
Coding 5.8%
Presentation 1.2%
System Design 1.2%

Interview difficulty

Easy 4.7%
Average 65.1%
Difficult 30.2%

Candidate experience

Positive 62.8%
Negative 20.9%
Neutral 16.3%