Job Title: Proxy Engineer (Network Security) Default Deny for Servers and Containers - hybrid
Duration: 1 year
Location: Jersey City, NJ or New York, NY (Hybrid – 3 days/week onsite)
Enable and operate default-deny internet access for servers and containers (dev, pre-prod, prod)
Design and implement server-side break-and-inspect proxy policies and path-aware policies
Route untrusted CDN domains (for example, content hosted on Fastly and Cloudflare) through the proxy
Support the firewall rule cleanup and target-state security design
Must have: hands-on enterprise proxy experience (Blue Coat/Symantec, Skyhigh or similar); strong routing and Layer 4-7 knowledge; ability to learn how proxy policies are built (Skyhigh experience is not required)
Preferred: Layer 7 experience; container or Kubernetes networking exposure; AlgoSec and SaaS/IaaS/PaaS traffic patterns; financial services background
Position Overview
The customer is moving its server environments (development, pre-production, and production) to a default-deny internet policy and extending the same controls to containers. Default deny is a broad first step, so the work goes further: using server-side break-and-inspect proxying to gain full-path visibility and build more refined, path-aware policies. This effort is focused on visibility and policy precision rather than data loss prevention. You will work alongside the customer’s proxy engineers in the UK and US, and partner with network, firewall, and application teams.
Key Responsibilities
• Enable and operate default-deny internet access for servers and containers across development, pre-production, and production environments
• Design and implement server-side break-and-inspect proxy policies to provide full-path visibility into outbound traffic
• Build path-aware policies that replace broad default-deny rules with more precise, least-privilege access
• Route untrusted CDN domains, such as content hosted on Fastly and Cloudflare, through the proxy so that traffic is inspected and controlled
• Analyze server and container outbound traffic to identify required destinations and validate policy changes before and after rollout
• Troubleshoot blocked or failing connections using Layer 4 through Layer 7 analysis, working with application and infrastructure owners to resolve issues
• Support the firewall rule cleanup effort and the target-state security design, helping align proxy and firewall controls
• Execute proxy policy and configuration changes under formal change-control processes, including testing and rollback planning
• Document policy designs, exceptions, and operational procedures, and coordinate handoffs with team members in other time zones
Required Qualifications
• Hands-on enterprise proxy experience (Blue Coat/Symantec, Skyhigh, or similar platforms)
• Strong routing knowledge and solid understanding of Layer 4 through Layer 7 traffic behavior
• Ability to learn how proxy policies are constructed and apply that knowledge to new designs (Skyhigh experience is not required)
• Experience working in a change-controlled enterprise environment
• Clear written communication and the ability to work with teams across time zones
Preferred Qualifications
• Layer 7 experience, such as application-aware inspection and policy
• Exposure to container or Kubernetes networking
• Firewall rule management experience (AlgoSec) and familiarity with SaaS, IaaS, and PaaS traffic patterns
• Financial services background
Proxy roles: Which proxy platform and version? Have they written or tuned SSL/TLS inspection (break-and-inspect) policies? Any default-deny or egress control work for servers? Any container or Kubernetes exposure?
All roles: Have they worked under formal change control in a bank or other regulated environment?
Other proxy platforms are acceptable. Strong enterprise proxy engineers on Zscaler or comparable platforms (Forcepoint, Palo Alto and similar) are in scope, not only Blue Coat/Symantec or Skyhigh.
A strong firewall or security engineer with deep Layer 4-7 knowledge may be considered for one of the seats.
The manager expects anyone who works with a proxy to be very familiar with TLS break-and-inspect, so hands-on SSL/TLS inspection experience is still a must for any candidate you submit.
Prioritizing candidates who can speak to:
Writing or tuning SSL/TLS inspection policy, including CA trust and bypass decisions
Controlling server egress or default-deny internet access
Preventing traffic from bypassing the proxy
Thank you,
Shiva Mittal
Proxy Engineer (Network Security) Default Deny for Servers and Containers - (No TP or Employer) in New York at Calance
This position is listed as full time and hybrid. It was posted yesterday.