Updated by
Hi, I'm Jack, the owner of Cybersecurity Jobs List and co-founder of Himalayas (himalayas.app) and Cavuno (cavuno.com). Across all my platforms, I work with application security daily: dependency vulnerability scanning, secure authentication, API security, and data protection across hundreds of thousands of users. My technical background is in computer science (UNSW). I studied security engineering and computer networks, and worked as a research assistant on VR experiments that were published in the Journal of Experimental Psychology. I also work with cybersecurity hiring data every day, tracking which companies are posting, what certifications actually appear in listings, how salaries differ by sub-discipline and clearance level, and where the talent gaps are widest. That combination of security practice, engineering at scale, and daily immersion in hiring data shapes the content on this site. I'm currently based in Sydney, Australia.

Cloud security jobs share a label, but the work varies. This snapshot checked four employer postings on 6 November 2026: building cloud access patterns, securing a developer platform, assessing client environments, and shipping cloud controls into production. The roles are in the United States and Auckland, New Zealand. They are examples, not a complete list, and a live posting can close at any time.
| Employer and role | Main work | Location and work mode | Stated experience or date |
|---|---|---|---|
| Netflix: Security Engineer 5, Cloud Architecture, Tooling and Security | AWS/GCP access patterns, cloud identity, security boundaries, internal tools | Remote, United States | Posted 19 October; no closing date shown |
| Vercel: Security Engineer, Cloud | Platform controls, infrastructure as code, policy enforcement, secure CI/CD | Remote in the United States; hybrid anchor days near San Francisco or New York | 8+ years in infrastructure or platform security |
| EY New Zealand: Cloud Security Consultant | Client assessments, architecture and configuration reviews, cloud governance | Hybrid, Auckland | 4–6 years; posting dated 22 October |
| PNC: Security Engineer, Cloud Security Controls | Test and deploy Azure/AWS controls through a Security as Code pipeline | Multiple U.S. locations | Posted 14 October; no closing date shown |
These summaries come from each employer’s own listing. Check the linked page for current status and exact eligibility before you apply. “Remote” here describes the employer’s stated location boundary, not permission to work from any country.
Netflix: build cloud access patterns and security boundaries
Netflix’s Cloud Architecture, Tooling and Security team focuses on AWS and GCP identity and access management. The Security Engineer 5 role designs secure access patterns and cloud boundaries, builds internal tools, and works with software engineering teams to fit security into new products and acquisitions.
This is an engineering role with a broad operating view. The posting also calls out third-party cloud access, cloud-security metrics, and the ability to drive mid-complexity work independently. Its listed background is aimed at someone who has already worked at L5 scope. The role is marked remote in the United States, and the posting says it will remain open for at least seven days and then be removed when filled.
If your strongest evidence is an identity or infrastructure project, look for a concrete example: a permission boundary you designed, how you tested it, what tradeoff you made, and how you checked that the right teams could still do their work.
Vercel: put security controls into a cloud platform
Vercel’s Security Engineer, Cloud role sits on its Cloud Security Engineering team. The work includes secure-by-default infrastructure, policy enforcement, service isolation, infrastructure as code, CI/CD controls, threat modeling, and improvements to monitoring and incident response.
The listing asks for at least eight years in infrastructure or platform security, along with AWS or GCP knowledge and tools such as Terraform, CDK, Kubernetes, and CI/CD security. The role is remote within the United States or hybrid. People within commuting distance of its San Francisco or New York offices have Monday, Tuesday, and Friday anchor days, even when the job is listed as remote.
That detail is easy to miss if you scan only the title. Check whether your location fits the employer’s stated boundary before investing time in an application. A useful work sample could show a cloud control built into a deployment path, including the policy, the failure it catches, and how an engineer gets an actionable result.
EY New Zealand: assess cloud environments for clients
EY’s Auckland Cloud Security Consultant posting describes client-facing assessment and advice. The work covers Azure and at least one of AWS or GCP, cloud configuration and architecture reviews, identity and access, network controls, encryption, logging, data protection, and Infrastructure as Code reviews using tools such as Terraform or Bicep.
The posting is dated 22 October 2026, lists Auckland, and calls the position hybrid. It describes the opportunity as suited to someone with four to six years supporting enterprise cloud environments and transformation work. Cloud certifications are described as highly desirable, not mandatory. The role also involves writing assessment reports with risk ratings and practical remediation recommendations.
For this kind of consulting work, a strong example explains how you found a risk, framed its impact for the people who owned the system, and recommended a change they could implement. Keep the client and system details confidential.
PNC: test and ship cloud security controls
PNC’s Security Engineer, Cloud Security Controls role is built around controls for Azure and AWS workloads. The posting describes working with a Security as Code pipeline to test and deploy controls, assess workloads against operational requirements, and integrate security standards into cloud software delivery.
The role is full-time and listed in multiple U.S. locations. The employer’s page displays seven locations in its header, while the detailed result shows a shorter list, so check the current application page for the location that applies to you. The listing was posted on 14 October 2026, and no closing date appeared in the material reviewed for this article.
This role is a closer fit if you enjoy making controls repeatable across many workloads. Useful evidence might be a safe example of a policy check in CI/CD, how you handled exceptions, and how you tested the control before production. Don’t include employer secrets or real credentials in a portfolio.
Choose by the work you want to do
The titles alone don’t tell you whether the job is mostly platform engineering, advisory work, or operational control testing. Read the responsibilities and look for the work product you would own:
- Cloud architecture and identity: design how teams and services receive access, set boundaries, and make that approach reusable.
- Platform security: build security into infrastructure and delivery paths so product teams can use safer defaults.
- Consulting and assessment: review different organizations’ environments, explain risk, and write practical recommendations.
- Security controls: test, automate, and maintain requirements that workloads must meet before they go live.
Location deserves its own check. A job can say “remote” and still limit applications to a country or require office days near a hub. Look for the work location in the job page and application flow. Don’t infer visa sponsorship or work eligibility when the employer hasn’t stated it.
A five-minute fit worksheet
Before you apply, write down these details for one role:
- Source and date checked: employer page URL and the day you confirmed it was open.
- Work location: country, city, remote boundary, hybrid days, and any clearance or work-authorization language stated by the employer.
- Three core responsibilities: quote the requirement in your own notes, then explain what you have done that is relevant.
- One piece of evidence: a project, system change, review, or incident exercise. Say what you owned, what you changed, and how you verified the result.
- One honest gap: name a tool or environment you haven’t used, then describe the adjacent experience that helps you learn it.
- A question for the recruiter: clarify a location or requirement that the posting leaves open.
This keeps your application specific without turning a job description into a list of keywords. It also makes it easier to compare two roles whose titles sound similar but whose daily work is different.
Browse cybersecurity jobs
You can browse current cybersecurity jobs and compare cloud security with application security roles. If you’re preparing materials, our guide to cybersecurity interview preparation can help you turn relevant work into clear examples.
The four employer pages above were visible when checked on 6 November 2026. Recheck the source before applying; availability and requirements can change.


