Network Engineer

Role & responsibilities

G3 Network Security Engineer Required Skills

Experience:

• 5–8 years of relevant experience in Network Security.

• Minimum 3+ years of hands-on experience with Palo Alto Firewalls in a production environment.

Mandatory Technical Skills:

• Strong administration and troubleshooting of Palo Alto Firewalls.

• Hands-on experience with Panorama (device groups, templates, template stacks, policy deployment, troubleshooting).

• Strong understanding of:

  - Security Policies

  - NAT

  - App-ID

  - User-ID

  - Security Profiles (IPS, Antivirus, Anti-Spyware, URL Filtering, WildFire)

• Routing knowledge:

  - BGP

  - OSPF

  - Static Routing

• High Availability (HA) deployment and troubleshooting.

• Packet capture analysis and traffic flow troubleshooting.

• Log analysis using CLI, Monitor, ACC, or SIEM tools (Splunk preferred).

• PAN-OS upgrades, content updates, and rollback planning.

• VPN troubleshooting (Site-to-Site IPsec).

Cloud Knowledge (Preferred):

• Palo Alto VM-Series on AWS and Azure.

• Basic cloud networking concepts (VPC/VNet, Security Groups, Route Tables, Load Balancers).

Additional Technologies (Preferred):

• F5 LTM (basic administration and troubleshooting).

• Azure Networking.

• AWS Networking.

• Basic understanding of WAF, DNS, and Load Balancing.

Operational Skills:

• Production incident handling (P1/P2/P3).

• Root Cause Analysis (RCA).

• Change implementation and rollback planning.

• Working in ITIL environments using ServiceNow or equivalent.

• Monitoring and troubleshooting using enterprise monitoring tools.

Troubleshooting Expectations.

Candidate should independently troubleshoot:

• Traffic drops.

• NAT issues.

• VPN failures.

• Routing problems.

• HA failovers.

• Policy matching issues.

• Performance-related incidents.

• Certificate-related issues.

Communication Skills:

• Strong verbal and written communication.

• Ability to independently handle customer bridge calls.

• Ability to explain technical issues clearly to customers and leadership.

• Professional stakeholder management during incidents.

• Clear and structured incident updates without excessive prompting.

What I Look for During Interviews:

• Real production experience rather than theoretical knowledge.

• Strong troubleshooting methodology.

• Ability to explain why a solution works, not just what command to run.

• Confidence in handling customer-facing situations.

• Good ownership, analytical thinking, and problem-solving skills.

• Clear, concise communication throughout the interview. This skill set aligns well with a G3/L2–L3 engineer who is expected to work independently, troubleshoot complex production issues, participate in customer bridge calls, and handle implementation and operational activities with minimal supervision.

Preferred candidate profile