Senior Security Engineer, Network & Zero Trust
Sezzle
IndiaremotePosted 8 days ago
Skill Required
Security-EngineerNetwork-Security-EngineerZero-Trust-EngineerCloud-Security-EngineerSr.-Infrastructure-Security-EngineerSenior-Information-Security-EngineerSenior-Cybersecurity-EngineerZero-Trust-Security-EngineerPrincipal-Network-Security-EngineerSecurity EngineerNetwork EngineerCloud SecuritysecurityRustSOCIstioEngineeringKubernetesnetworkingautomationCryptographyTerraformbuildingISO 27001fintechTestNGPythondesignCloudHelmSIEMAPIsShell ScriptingAWSGitIAMFulltime
Key highlights
- Compensation: $5,000 - $9,500 USD per month
- Experience: 6+ years
- Requirement: Deep Kubernetes and AWS networking knowledge
- Requirement: Ability to write code (Go, Python, or Bash)
Role overview
Sezzle is seeking a hands-on Senior Security Engineer, Network & Zero Trust, to own the network pillar of their zero-trust program. The role involves ensuring every connection is explicitly allowed, authenticated by service identity, and attributable across Kubernetes clusters and AWS accounts. This is an engineering-heavy role reporting to the Director of Information Security. The engineer will write policies, tooling, and rollout automation, utilizing AI-assisted engineering and agentic workflows to segment a large estate and manage network configuration as reviewed code.
Responsibilities
- Own east-west segmentation across Kubernetes clusters: design the segmentation model, derive network policies from observed traffic, and keep every workload reachable only through explicitly allowed, identity-bound paths.
- Deliver identity-aware transport — design and roll out mutually authenticated, encrypted service-to-service connections (mTLS), so that authorization decisions rest on verified service identity.
- Keep a live map of the network: VPC peerings, tunnels, cross-account links, and every public entry point — built from cloud APIs and reconciled continuously.
- Own segmentation of production and the cardholder-data environment: implement and enforce the CDE and high-trust-tier boundaries, review every peering and public exposure against them, and run segmentation testing with the security team.
- Partner with IT on private access: evaluate and help deliver per-application access (ZTNA) for engineers and operators reaching production systems.
- Own network telemetry: flow logs east-west and north-south, with enough identity on both ends that "who talked to what, when" is answerable in minutes — and feed it to our SIEM for the detection team.
- Own cluster admission control and hold the line on drift: workload admission policy (pod security, image provenance, network policy), security groups and firewall rules declared in git, applied only through the IaC pipeline, with admission control at the gate and drift detected and reverted automatically.
- Contain: build the levers that let us isolate a workload or segment quickly when detection flags lateral movement, and take part in incident response when the network is in play.
- Participate in threat modeling and design reviews for anything that changes how traffic flows, and in the on-call rotation for the controls you own.
Requirements
- 6+ years of experience in security, network, platform, or infrastructure engineering, with hands-on ownership of network controls in cloud production environments.
- Deep, practical Kubernetes networking knowledge: CNI, NetworkPolicy semantics, DNS, ingress/egress — and experience rolling segmentation out on live clusters without outages.
- Strong AWS networking: VPCs, subnets, security groups, peering and Transit Gateway, PrivateLink, load balancers, flow logs.
- Hands-on experience with mTLS and service-to-service authentication (service mesh, proxies, or CNI-level encryption).
- Infrastructure as code as your default way of working — Terraform and Helm or equivalents, through merge requests and CI, across repositories you don't own.
- Ability to write real code (Go, Python, or Bash) for tooling and automation, not only configuration.
- Ability to investigate directly with packet captures, flow logs, and system-level data.
- Working knowledge of PCI DSS network requirements — segmentation, scoping of the cardholder-data environment, segmentation testing.
- Demonstrated AI-forward engineering: you actively use AI tooling (e.g., Claude Code, Codex, Cursor, or custom LLM integrations) in your work today and have opinions grounded in practice about where it helps and where it doesn't.
Nice to have
- Cilium / eBPF in production, including Hubble or equivalent flow observability.
- mTLS at fleet scale, including certificate lifecycle — service mesh (e.g., Istio, Linkerd, Cilium service mesh) and workload identity standards such as SPIFFE/SPIRE.
- You have built AI-assisted workflows that others adopted — flow analysis, policy generation, drift review.
- Experience evaluating or deploying ZTNA / identity-aware proxy products.
- Policy-as-code and admission control (OPA/Gatekeeper, Kyverno, conftest).
- Experience with network detection — IDS/IPS, anomalous-flow and lateral-movement detection — and with containment during incidents.
- Familiarity with SOC 2 and with FFIEC-style examination expectations for network security.
- Experience in fintech, payments, BNPL, or other regulated environments.
Additional details
- Salary range: $5,000 - $9,500 per month (Gross in USD) based on experience level.
- AI-assisted engineering is a standard part of how we work.
- Technology Stack: Languages (Golang, Typescript, Python), Frontend (Typescript - React and React Native), Backend (Golang), Database (MySQL, Postgres, Elasticsearch), DevOps & Cloud (AWS, Kubernetes), Version Control (Git), CI/CD (Gitlab).
- Testing focus: Developer and AI-driven, focus on automated end-to-end, integration, and unit tests.
- Open Source: Sezzle is focused on using open source, and we build what we can before buying!
- Cultural values: Preferring allow-lists over diagrams, rolling out in observe mode first, relentlessly high standards, not bound by convention, value for speed/calculated risk-taking, earning trust, backbone (disagree then commit), and delivering results.
- #Li-remote #Full-time
- Originally posted on Himalayas