Skip to main content

Public Cloud Network-Security Engineer

Posted today

2t consultingCarrollton (TX)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

We are seeking an experienced Public Cloud Network Security Engineer to design, build, and maintain secure, scalable, and highly available cloud network infrastructure. The ideal candidate should have strong hands-on expertise in AWS, GCP, Network Security, Terraform, Python, and Infrastructure as Code (IaC).
Key Responsibilities: Design and implement highly secure, scalable, and resilient public cloud network architectures. Build and manage cloud network security solutions across AWS and GCP. Implement network segmentation strategies using cloud-native security services. Develop automated infrastructure deployment solutions using Terraform and Infrastructure as Code. Implement CI/CD pipelines and automated testing for cloud infrastructure. Develop automation scripts and tools using Python, Golang, and cloud SDKs. Implement cloud security best practices and compliance standards. Work with Kubernetes and container security technologies. Collaborate with cloud engineering, platform, networking, and operations teams. Identify opportunities to automate processes and improve cloud service delivery. Ensure infrastructure security, auditability, availability, and compliance. Must-Have Technical Skills AWS Cloud Networking and Security Google Cloud Platform (GCP) Network Security Engineering Network Segmentation Infrastructure as Code (IaC) Terraform Python Programming Golang CI/CD Pipelines Kubernetes Container Security AWS / GCP SDKs Cloud Security Best Practices Experience Requirements 6–10 years of relevant IT experience. Strong experience in public cloud network security. Hands-on experience with AWS and GCP network security services. Proven experience with Terraform and automated infrastructure deployment. Strong programming and automation skills using Python or Golang. Experience implementing cloud security policies and compliance frameworks. Knowledge of cloud-native applications and container orchestration.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this