DevOps vs DevSecOps: Skills, Mapped

A viral post listed everything recruiters ask one “DevOps engineer” to know — and pointed out that it is the whole team of five companies. Here is that list, split into the roles it really spans, with security placed where it belongs.

40+tools in the typical “one engineer” wish-list
6roles it actually spans
7security checks in a mature pipeline
1rule: security is a stage owner, not a gate at the end

DevOps is a way of working in which the people who build software also ship and run it, with automation in between. DevSecOps adds security to that loop so it happens continuously, not in a review before release. Neither is a single job. The list that recruiters copy into job posts — several languages, several clouds, containers, infrastructure-as-code, CI/CD, GitOps, observability and a long tail of security scanners — describes a platform team. Splitting it by role makes hiring realistic and shows where security responsibilities actually sit.

1 · One Wish-List, Six Roles

RoleOwnsTypical tools from the listSecurity duty
Platform engineerKubernetes, container platform, internal developer toolingKubernetes, Docker, OpenShift, Helm, Argo CD, FluxCluster hardening, admission policies, signed images only
Cloud / infrastructure engineerAccounts, networks, infrastructure-as-codeAWS, Azure, GCP, Terraform, AWS CDK, Bicep, Linux and Windows administrationLeast-privilege IAM, IaC scanning, cloud posture
CI/CD engineerBuild and release pipelinesJenkins, GitHub Actions, Azure DevOpsPipeline secrets, runner isolation, branch protection, artefact signing
SRE / observabilityReliability, monitoring, incident responsePrometheus, Grafana, ELK, Datadog, SplunkSecurity logging, alert routing to the SOC, runbooks
Automation developerTooling and glue codeGo, Python, Bash, PowerShellSecure coding in the tooling itself; no secrets in scripts
DevSecOps / product securitySecurity checks across the pipelineSonarQube, Trivy and the “twenty other DevSecOps tools”Choose, tune and own the checks; triage findings with developers

▸ One strong engineer can be deep in one or two of these roles and conversant in the rest. That is a realistic hire. Asking for depth in all six is how roles stay open for months.

2 · Where Each Security Check Sits

Plan→Code→Build→Test→Release→Deploy→Operate
StageCheckExample toolsOwner
PlanThreat modelling for new featuresWhiteboard, OWASP guidanceProduct security with the team
CodeSecret scanning; static analysis (SAST)Gitleaks, SonarQube, SemgrepDevelopers, tuned by DevSecOps
BuildDependency scanning (SCA) and SBOMTrivy, OWASP Dependency-CheckCI/CD engineer
BuildContainer image and IaC scanningTrivy, CheckovPlatform and cloud engineers
TestDynamic testing (DAST) against stagingOWASP ZAP, NucleiDevSecOps
ReleaseSigned artefacts and provenanceSigstore / cosign, SLSA practicesCI/CD engineer
Deploy & operateAdmission policy, runtime detection, cloud postureKyverno or OPA Gatekeeper, Falco, cloud-native posture toolsPlatform engineer and SRE

The free tools in this pipeline are covered in Open-Source Security Stack. Fail builds only on high-confidence, fixable findings; everything else becomes a ticket, or developers learn to ignore the pipeline.

3 · A Realistic Learning Path

  1. Foundations — Linux, networking, Git, and one scripting language (Python or Bash) properly.
  2. One cloud, deeply — identity and access, networking and the core services of AWS, Azure or GCP; the others then map across.
  3. Infrastructure as code — Terraform plus that cloud’s own tool.
  4. Containers and Kubernetes — build images, run a cluster, understand its security model.
  5. One CI/CD system end to end, with secrets handled correctly.
  6. Observability — metrics, logs and traces with one stack.
  7. Security in the loop — add the checks above to your own project and fix what they find.

4 · Writing a Job Description One Person Can Fill

Instead of…Write…
A list of forty toolsThe two roles from the table you need most, and the outcomes you expect in the first six months
“Expert in AWS, Azure and GCP”“Deep in the cloud we run; able to learn others”
“Knows twenty DevSecOps tools”“Has added security checks to a pipeline and worked findings to closure with developers”
“Owns everything in production”The on-call rotation, team size and what is already automated

The offensive and defensive security careers that sit next to these roles are in Red, Blue & Purple Teams.

Bottom line

  • The wish-list is a team — platform, cloud, CI/CD, SRE, automation and security.
  • Hire for depth in one or two roles and breadth across the rest.
  • Security belongs at every stage, owned by the people who run that stage.
  • Fail builds on what is real and fixable; ticket the rest.
  • Learn one cloud and one pipeline deeply before collecting tools.

Sources & method. Tool names from the widely shared “Dear recruiters” post and common job advertisements; capabilities from each project’s documentation. Role split, pipeline placement and guidance are the author’s analysis, consistent with OWASP DevSecOps guidance and SLSA. Tools are examples, not endorsements. Original analysis; no third-party graphics or text reproduced.

← Back to Cyber security