DevSecOps Engineer Resume: Complete 2026 Guide

From the author

Emmanuel Gendre, ex-Google recruiter

My experience with DevSecOps Engineer resumes

Twelve years recruiting in tech, with a long run inside Google, and the DevOps Engineer resume is the one where I most often see strong production work read as flat plumbing on the page. The actual job sits at the seam between developers and prod: the pipelines, the IaC, the platform that lets every service team ship safely. The resumes I get hand it to me as a tool list.

What hiring teams in 2026 want is the delivery story behind that tool list, and a DevSecOps Engineer resume reading as "Kubernetes, Terraform, Argo CD" without a deploy lead time cut, a change-failure rate held down, or an SLO defended through a real incident never makes it to a screening call.

Closing that gap is what this guide is for. We walk the 5 sections that decide a DevOps screen, with one outcome in mind: screening calls landing in your inbox again, market softness or not.

Want it written for you? My Tech Resume Writing Service rebuilds it from a blank page. Already have a draft? Send it in for a free review; the notes come back from me.

Let's put your DevSecOps Engineer resume back on recruiters' desks. Ready?

What the DevSecOps Engineer resume guide covers

How I rewrite a DevSecOps Engineer resume

DevSecOps Engineer drafts hit my resume writing service intake most weeks, and I rework each line until the shift-left work shows clearly to a recruiter who has never read a CVE report. The bit nobody says out loud: only a small handful of sections actually decide whether the screening call lands. Doing the rewrite solo? Sort these 5 first. The rest of the page barely moves the dial, so we keep that part brief.

We walk each one below, in order. Treat it as a checklist, run top to bottom, and the resume that comes out the other side is far stronger. Here's the structure:

Want to see the full method? My step-by-step tech resume rewrite process covers everything else.

Step 1 · DevSecOps Engineer Resume Format

The format to use for a
DevSecOps Engineer resume

Easy first step: a layout an ATS handles cleanly without crashing on it.

Nothing complicated at this stage, whatever the internet keeps trying to sell you. The aim: the software hands your content and structure back out to the reviewer in the same shape you typed them in.

Keyword work happens later, in the filtering step (Technical Skills, Step 5). Right now: when the parser fails on the file, you're already eliminated from 95% of openings before any reviewer touches the page.

Just 3 rules at this step:

Use a text editor (Word, Google Docs)

ATS systems read text, not the rendered picture of it. Put the resume through Canva, Figma, or any other design tool, and the words leave the file as a flat image. The parser sees nothing where your security stack should sit, and the application that reaches the recruiter shows up blank.

Single column, plain layout

Skip two-column templates outright. Sidebars, tables, and icons fall into the same bucket. Even in 2026, parsers still mangle every one of them, and it's the single biggest reason resumes fail the scan, on the order of one in three drafts that hit my desk. Move to a clean one-column layout flowing top to bottom, and most of the failures vanish.

Simple section titles

Label them Profile Summary, Technical Skills, Work Experience, Education. Not "Security Posture", not "Compliance Track". ATS parsers and human readers both look for those exact standard names; a creative rename pulls you straight out of the running. Fold any fuzzy headings into the same buckets: "Core Competencies" goes under Profile Summary or Technical Skills, and "Selected Projects" under Work Experience.

Want to see how yours fares? Drop it into the ATS resume checker and read what the parser hands back. If the output comes back garbled, the layout broke the read, not the words you typed, which is the whole story behind how ATS systems really work.

Starting from a blank file and want clean parsing on save one? Begin from the DevSecOps Engineer resume template.

Step 2 · DevSecOps Engineer Profile Summary

Writing a profile summary
for a DevSecOps Engineer

Plenty of DevSecOps Engineers skip past the Profile Summary as filler. It runs the other way: this is the first block a recruiter lands on the page.

If yours is thin or missing entirely, fixing it is the fastest gain you can put on the page today.

I broke the mechanics down in how recruiters screen resumes. Short version: a two-pass read. Pass one drops anyone who doesn't register as a match for the role; pass two builds the shortlist out of whoever survives.

That first pass is the recruiter ripping through the stack at seconds per resume, which is where the "10-second screen" phrase comes from.

The Profile Summary is your one window to land the exact details a recruiter screens for inside those seconds, which is what earns the page a deeper read.

Each bullet has one job. Below: the order I work through, what each bullet carries, and a worked example for a DevSecOps Engineer profile summary.

Target job title, overall experience & security scope

Bullet 1 sets the marker: the role you're aiming at, your seniority, plus the security posture you own (CI/CD shift-left, secrets, supply chain, compliance). Drop in the regulatory frame (SOC 2, ISO 27001, FedRAMP, PCI) and a known employer if either lifts weight. Read this sentence as the page's top headline: a recruiter clocks it before anything else, and on rushed days it is sometimes the only line they reach.

Info for recruiters Target job title Years of experience Security scope Compliance frame

Example DevSecOps Engineer 8 years Shift-left across 60 services on SOC 2

Domain expertise

Bullet 2 covers your domain expertise: the slots that make up the DevSecOps role profile (laid out in Step 3, DevSecOps Engineer Work Experience). For this role those slots are CI/CD security integration, secrets management and key rotation, container and supply-chain security, infrastructure and cloud security, and policy-as-code and compliance automation. A non-technical screener walks that scorecard line by line and ticks off your entries. Treat this bullet as your own scorecard and leave no row empty.

Info for recruiters CI/CD security Secrets & PKI Supply chain IaC & cloud security Policy as code

Example SAST/SCA in CI Vault secrets program Cosign & SBOM Checkov on IaC OPA admission

Your tech stack

Bullet 3 names your daily stack: the scanners, the secrets manager, the policy engine, and the cloud-security tooling you actually run. The full inventory lands further down under "Technical Skills" (covered in Step 5, DevSecOps Engineer Technical Skills); up here you only call out the daily drivers. For a DevSecOps Engineer that means: SAST/SCA scanners, secrets layer, container and supply-chain tooling, IaC scanners, and the policy-as-code engine that backs admission.

Info for recruiters Scanners Secrets Supply chain IaC scanning Policy

Example Snyk, Semgrep, Trivy Vault, AWS Secrets Manager Cosign, Syft, in-toto Checkov, tfsec OPA, Kyverno

Collaboration

Bullet 4 covers your cross-functional partnership. DevSecOps work sits between Platform Engineering, Application Engineering, SecOps, and Compliance; the controls you wire in are what every service team ships through, so the threat model, the security review, the audit evidence, and the developer-friction feedback loop all live across those handoffs. A hiring manager checks you carry the security side cleanly without slowing down delivery, so call out the partner teams and what they get from your program.

Info for recruiters Partner teams Security contracts Audit support

Example Platform Engineering App Engineering SecOps Compliance SOC 2 evidence

Leadership

Bullet 5 surfaces your technical leadership. Even pure-IC DevSecOps Engineers have a line worth showing here. Leadership runs through the security program and the people: chairing threat-modeling sessions, owning the secrets and policy standard, running secure-code office hours, and coaching engineers new to shift-left practices.

Info for recruiters Standards you define Engineers you coach Reviews you chair

Example Threat-modeling reviews Secrets & policy standard Secure-code office hours

DevSecOps Engineer Profile Summary Example

Senior, shift-left across 60 services on SOC 2

Profile Summary

DevSecOps Engineer with 8 years running shift-left security across 60 services on SOC 2 Type II across fintech and B2B SaaS.
Strong on CI/CD Security Integration, Secrets Management, Container & Supply-Chain Security, Cloud & IaC Security, and Policy-as-Code & Compliance Automation.
Day-to-day across Scanners (Snyk, Semgrep, Trivy), Secrets (Vault), Supply chain (Cosign, Syft), IaC scanning (Checkov, tfsec), and Policy (OPA, Kyverno).
Cross-functional partner working daily with Platform Engineering, App Engineering, and Compliance, taking a service from a developer's commit to a production deploy through gated scanners and signed artifacts.
Leads through threat-modeling reviews and a secrets and policy standard, runs secure-code office hours, owns the audit evidence pipeline, and coaches engineers new to shift-left.

Want more depth? My fuller writeup on how to write a killer profile summary walks the same idea line by line.

Want a recruiter's read on your DevSecOps Engineer resume?

Months in the queue with zero interviews, zero feedback.
No employer owes you the reason, leaving you to guess what's off about the draft. Keep guessing, or hand it to someone who screened thousands of DevSecOps and security-engineering resumes at Google.

Pass it over and I'll take it apart.

I'll run a simulated recruiter screen over your DevSecOps Engineer resume and send back a short list of what to repair. Free, inside 12 hours.

Want to read more first? See how the resume review works →

Step 3 · DevSecOps Engineer Work Experience

Work experience on a
DevSecOps Engineer resume

This is where the second pass actually plays out, the last gate before an interview hits your inbox. The recruiter slows down right here, and even then your current role still drives around 95% of the decision.

Makes sense: nothing tells a hiring team what you can run in production right now the way your current job does. To clear that "yes", this section has to walk the full DevSecOps Engineer role profile, one bullet per slot you listed in Domain Expertise above. Every bullet has to come off something you actually held in production, not a Jira card that wandered past your queue.

CI/CD Security Integration (SAST, DAST, SCA)

You catch vulnerabilities in the pull request, before they ship. Hiring managers read security built into the pipeline behind it, not "ran a scan before release", so this is where a DevSecOps hire proves out. Talk about how you used SAST and dependency scanning with blocking gates, through Semgrep and Snyk, to block CVEs at the PR and cut time-to-remediate.

Techniques Shift-left in CI Severity policy Blocking gates at PR Auto-remediation PRs

Tools Semgrep, Snyk, SonarQube OWASP ZAP, Burp Dependabot, Renovate

Metrics CVEs blocked at PR Mean time to remediate Coverage across services

Secrets Management & Key Rotation

You lock down secrets so none leak into a repo. A single hard-coded key in Git is how breaches start, so hiring managers want to see secrets you actually brought under control. Show them how you used dynamic secrets and secret scanning, with Vault and sops, to rotate on a real cadence and catch leaks at the PR.

Techniques Dynamic secrets Short-lived tokens Auto rotation Secret scanning

Tools HashiCorp Vault AWS Secrets Manager / KMS Doppler, sops

Metrics Secrets under management Rotation cadence Leaked secrets caught at PR

Container & Supply-Chain Security

You sign and scan everything you ship. Signed images at admission and blocked high-sev CVEs are checkable facts, so real numbers beat "secured the containers". Point out how you used image scanning and artifact signing, with Trivy and Cosign, to get signed images through admission and publish SBOMs.

Techniques Image & package scanning SBOM generation Artifact signing & verification SLSA / in-toto provenance

Tools Trivy, Grype, Snyk Container Syft, SPDX, CycloneDX Cosign, Sigstore, in-toto

Metrics Signed images at admission SBOMs published High-sev CVEs blocked

Infrastructure & Cloud Security

You block misconfigurations before they reach the cloud. Hiring managers look here to see whether risky infra gets stopped at the PR, or whether it lands in prod and waits for an incident. Mention how you used IaC scanning and CSPM, with Checkov and Wiz, to block misconfigs at the PR and reduce privileged access.

Techniques IaC scanning at PR CSPM & CNAPP Security baselines per account Least-privilege IAM

Tools Checkov, tfsec, Terrascan Prowler, Wiz, Orca GuardDuty, Security Hub

Metrics Findings closed Misconfigs blocked at PR Privileged access reduced

Policy-as-Code & Compliance Automation

You turn compliance into policy that runs on its own. Two things ride on it for a hiring manager: audits you pass without a last-minute scramble, and risky changes blocked automatically. Walk them through how you used policy as code and admission control, with OPA and Kyverno, to put controls under code and clear the audits.

Techniques Policy as code Admission control Evidence pipelines Continuous compliance

Tools OPA, Conftest, Kyverno Vanta, Drata AWS Audit Manager

Metrics Audits cleared Controls under code Risky changes blocked

Threat Modeling & Security Reviews

You find the design flaw before it's ever built. A flaw caught in a design review is worth more than any late patch, so hiring managers want a real risk you found and closed, not "security-minded". Lay out how you used STRIDE threat modeling and design-stage reviews, backed by OWASP ASVS, to review the risky designs and close the findings.

Techniques STRIDE / PASTA Design-stage reviews Abuse-case stories Risk-tier classification

Tools Threagile, IriusRisk OWASP ASVS Confluence, Notion

Metrics Designs reviewed Risks closed Coverage of tier-0 services

Incident Response & Detection

You spot an attacker before they do real damage. The org's ability to survive a breach rides on your detections, so proving they fire on real attacks tells a hiring manager they can trust you on defense. Spell out how you used detection engineering and Falco rules, wired into Splunk and Tines, to widen detection coverage and cut MTTD.

Techniques Detection engineering Sigma / Falco rules Tabletop exercises Runbook automation

Tools Splunk, Datadog Security Falco, Tetragon PagerDuty, Tines

Metrics Detection coverage MTTD / MTTR False-positive rate down

Tooling & Workflow

You make secure the default, not a gate. Companies keep the DevSecOps engineers who make secure the easy path, not the ones who just say no, so hiring managers look for it. Tell them how you used secure-by-default templates and internal runbooks, in Git with Backstage TechDocs, to speed secure onboarding and cut PR cycle time.

Techniques Secure-by-default templates Internal CLI / runbooks Inner sourcing Self-serve docs

Tools Git, GitHub Bash, Python, Go Backstage TechDocs

Metrics Templates maintained PR cycle time Secure-onboarding ramp cut

Done right, your current role can easily run to 8 or 10 lines. Perfectly fine, whatever the one-page mantra LinkedIn keeps pushing. Recruiters don't care about length; two pages of real platform work beat one bloated page outright. What a recruiter will not read is empty filler. Cutting that is what comes next.

Step 4 · DevSecOps Engineer Bullet Points

Bullet points for a
DevSecOps Engineer resume

Bullet points carry the bulk of the rewrite, so I built them their own dedicated framework: the Level System.

Nothing magic about it: it picks up where Google's XYZ formula stops and adds a few tiers tuned for technical engineering resumes. The full breakdown lives in my guide on how to write resume bullet points.

Fastest way to learn it: take a flat DevSecOps-resume bullet and walk it up. There are 5 tiers in all; each one asks a single question, and the answer you give slides in as the next fragment of the bullet.

Climb all five and a bare "built a deploy pipeline" line turns into a shipped delivery platform with real numbers attached, which is the kind of line that puts a DevOps Engineer on the shortlist.

1 Task “What did I work on?” What you did
2 + Engineering Techniques “How did I do it?” How you did it
3 + Tools “What tools did I use?” Scanners, signing, policy engines
4 + Method “What method did I follow?” Named methodology
5 + Metric “What was the result?” Quantified impact

Level 1, Just the task. Open with a security program or control that was yours to ship to the CI/CD platform. This is the opening phrase, not the finale; most resumes stop right here on the bullet, which is exactly why so many wash out at this point.

Level 1
Just the task

Shifted security left across the CI/CD platform.
Level 2, Add the techniques. Name the specific engineering practices the work used: the testing types, rendering modes, scaling tactics, design patterns. This is where the bullet starts proving you understand how the work was done, not just that it shipped.

Level 2
+ Engineering Techniques

Shifted security left across the CI/CD platform using SAST and SCA scanning with signed artifacts.
Level 3, Add the tools. Drop in the named products and versions you used: the framework, the database, the build tool. Recruiters search resumes with technology queries, so the bullet stays invisible without the named stack.

Level 3
+ Tools

Shifted security left across the CI/CD platform using SAST and SCA scanning with signed artifacts on GitHub Actions and Argo CD over Amazon EKS with Trivy, Snyk, Cosign, and OPA.
Level 4, Add the method. Name the methodology, framework, or design pattern that guided the work: TDD, DDD, BDD, GitOps, MVVM, CQRS, progressive enhancement, and so on. The hiring manager is usually the one enforcing the methodology on the team, so naming yours shows you fit how they actually operate.

Level 4
+ Method

Adopted Policy-as-Code to shift security left across the CI/CD platform using SAST and SCA scanning with signed artifacts on GitHub Actions and Argo CD over Amazon EKS with Trivy, Snyk, Cosign, and OPA.
Level 5, Add the metric. The number is the lever that pushes a bullet into top-tier territory. For DevSecOps work, reach for figures the business cares about: mean time to remediate, risky changes blocked at PR, audits cleared, signed artifacts in production. Skip the metric and the line sits flat alongside every other resume whose author stopped at "ran security scans".

Level 5
+ Metric

Adopted Policy-as-Code to shift security left across the CI/CD platform using SAST and SCA scanning with signed artifacts on GitHub Actions and Argo CD over Amazon EKS with Trivy, Snyk, Cosign, and OPA, cutting MTTR for high-sev CVEs from 38 days to 4.

My longer piece on writing resume bullet points works the rewrite tier by tier and shows how to pull figures out of work that looked like it had none. Most DevSecOps Engineers already know the numbers; they sit in Grafana, the deploy dashboard, or the cloud cost report. Nobody ever told them that deploy lead time, change-failure rate, SLO hit rate, and cloud spend belong on a resume.

Step 5 · DevSecOps Engineer Technical Skills

Technical skills for a DevSecOps Engineer resume

The Technical Skills section is where most ATS setups run their keyword filtering, so the wording here should mirror the JD you're after: scanner stack, secrets layer, supply-chain tooling, and policy engine named, not just "DevSecOps" on its own.

This is the final 10%. Cleaning it up helps the resume slip past the automated screen and the recruiter's quick skim, but the real lift still comes from your Profile Summary, Work Experience, and Bullet Points upstream.

Either way, keywords compound across the page, and knowing the exact ones a parser and a recruiter look for is worth the time. I built a full page covering every DevSecOps Engineer skill, hard and soft, with a keyword scanner you can point at any job description.

Pipeline Security & SAST/DAST/SCA

Semgrep Snyk SonarQube OWASP ZAP / Burp Dependabot / Renovate Shift-left in CI Severity policy
Secrets & PKI

HashiCorp Vault AWS Secrets Manager / KMS Doppler, sops cert-manager SPIFFE / SPIRE Dynamic credentials Secret scanning
Container & Supply Chain

Trivy / Grype Snyk Container Syft / SPDX / CycloneDX Cosign / Sigstore in-toto / SLSA Kyverno / Gatekeeper Distroless / Wolfi
Cloud & IaC Security

Checkov / tfsec / Terrascan Prowler / Wiz / Orca GuardDuty / Security Hub AWS Config / Inspector Falco / Tetragon IAM least privilege CSPM / CNAPP
Compliance & Workflow

OPA / Conftest Vanta / Drata SOC 2, ISO 27001, FedRAMP, PCI Threagile / IriusRisk Splunk / Datadog Security Python, Go, Bash Git, GitHub

Stop guessing. Ask a recruiter directly.

You now have the format, the profile summary template, the role profile, the bullet system, and the skills categories. All that's left between your draft and the interview is a set of eyes that screened thousands of DevSecOps and security-engineering resumes telling you what to fix.

That is the free review.

Drop the draft in. Back come a simulated recruiter screen, a graded checklist, plus a specific action list. Free, inside 12 hours.

Want to read more first? How the resume review works →

Frequently asked

DevSecOps Engineer resume FAQ

How long should a DevSecOps Engineer resume be?

Just into the field, hold it to one page. Once you have shifted security left on a CI/CD platform, run a secrets program, and cleared a real audit with numbers to back it, two pages start earning their keep: the second sheet gets read when the shift-left work behind it actually holds up. The blanket one-page rule misses that a senior DevSecOps career covers a long line of pipeline gates, supply-chain controls, and compliance wins worth showing. Save three pages for staff or principal DevSecOps level where that security-engineering track really fills them.

Should it be one page?

Comes down to what controls are actually running with your name on them, not a fixed rule. New to the role: one page covers it. A few years in, with pipeline scanners you wired in, a secrets program you stood up, and audits you cleared, squeezing it all onto a single sheet cuts the very numbers earning the screen. Production posture beats page count on this resume.

What is the most important section?

Your current role, by a long way. Roughly 95% of the read sits there, since that is where the recruiter checks whether you have actually defended a CI/CD platform at the scale this team operates. The profile summary lands one beat earlier, and the recruiter uses that line as the lens over everything below.

How do I get my resume past ATS?

A plain layout: one column, no graphics, no sidebars, no icons. Use the standard labels (Profile Summary, Technical Skills, Work Experience, Education); export PDF, not DOCX. Then run the file through my free ATS parser tool and check that SAST, DAST, SCA, Trivy, Snyk, Vault, Cosign, OPA, and the rest of your DevSecOps stack parse cleanly. If any of those drop out, the layout broke the read, not your keyword list.

What keywords should I include?

For a 2026 DevSecOps search the must-haves are SAST and SCA scanners (Semgrep, Snyk, SonarQube), a container scanner (Trivy, Grype, or Snyk Container), a secrets manager (Vault, AWS Secrets Manager, or Doppler), policy-as-code (OPA, Kyverno, or Conftest), and a supply-chain layer (Cosign, Sigstore, in-toto, or SBOM with Syft). Strong backups: DAST tooling (OWASP ZAP, Burp), IaC scanners (Checkov, tfsec, Terrascan), a CSPM tool (Prowler, Wiz, Orca), a compliance platform (Vanta, Drata, Tugboat Logic), and Bash and Python for control automation. The full list, each paired with a sample bullet, lives on the DevSecOps Engineer Resume Skills page.

Should I lead with security depth or platform-engineering depth?

Lead with whichever side the job posting emphasizes, then back it with the other. A heavy security-first posting (SOC 2, threat modeling, supply chain) wants the controls and audits up front, with the pipeline work as supporting infrastructure. A platform-first posting (shift-left, paved roads, DevSecOps-as-a-Product) wants the CI/CD and infra work up front, with the security gates layered in. A resume that splays both equally without picking a side reads as a generalist who hasn't actually owned either. Recruiters scan for the slope the JD names; pick the side and make it the spine of your bullets.

Do I need security certifications (CISSP, OSCP, CKS) to land DevSecOps Engineer roles?

Helpful, not gating. CKS (Certified Kubernetes Security Specialist) and a vendor cert on your primary cloud carry weight on a 2026 DevSecOps resume; CISSP is useful at staff level but not required earlier. Past mid-level, hiring managers care more about the controls you actually shipped: the SAST gate you wired in, the secrets program you ran, the SOC 2 audit you cleared. If you have a top-tier cert, list it; if you don't, lead with production posture. A pipeline that blocks 92% of risky changes at PR review beats a wall of badges every time.

How long should my profile summary be?

Five or six bullets, no more. A heavy paragraph forces slow reading at the moment the recruiter intends to skim, and on a DevSecOps role what they scan for is the scanner stack, the secrets program, the supply-chain controls, and the compliance scope you cover. As bullets the recruiter can match you against the role at a glance and decide whether the rest of the page is worth more time.

Who wrote this

Built by an ex-Google recruiter

Emmanuel Gendre

1,500+ tech resumes rewritten · 4.9 on Fiverr from 419 reviews

Hi there! I'm Emmanuel, a tech recruiter with 12 years of experience, including many years at Google. I founded TechieCV to help candidates pass recruiter screens and land top-paying jobs. This guide is the process I use on real client resumes.

Read my full story →

More resources

Other DevSecOps Engineer Resume Resources

Service

DevSecOps Engineer Resume:The Complete 2026 Guide

My experience with DevSecOps Engineer resumes

How I rewrite a DevSecOps Engineer resume

The format to use for aDevSecOps Engineer resume

Use a text editor (Word, Google Docs)

Single column, plain layout

Simple section titles

Writing a profile summary for a DevSecOps Engineer

Target job title, overall experience & security scope

Domain expertise

Your tech stack

Collaboration

Leadership

Profile Summary

Want a recruiter's read on your DevSecOps Engineer resume?

Work experience on aDevSecOps Engineer resume

CI/CD Security Integration (SAST, DAST, SCA)

Secrets Management & Key Rotation

Container & Supply-Chain Security

Infrastructure & Cloud Security

Policy-as-Code & Compliance Automation

Threat Modeling & Security Reviews

Incident Response & Detection

Tooling & Workflow

Bullet points for aDevSecOps Engineer resume

Technical skills for a DevSecOps Engineer resume

Pipeline Security & SAST/DAST/SCA

Secrets & PKI

Container & Supply Chain

Cloud & IaC Security

Compliance & Workflow

Stop guessing. Ask a recruiter directly.

DevSecOps Engineer resume FAQ

Built by an ex-Google recruiter

Tech Resume Writing Service

DevSecOps Engineer Resume Template

DevSecOps Engineer Resume Skills & Keywords

DevSecOps Engineer Resume Metrics

Free ATS Checker

DevSecOps Engineer Cover Letter

DevSecOps Engineer Resume:
The Complete 2026 Guide

The format to use for a
DevSecOps Engineer resume

Writing a profile summary
for a DevSecOps Engineer

Work experience on a
DevSecOps Engineer resume

Bullet points for a
DevSecOps Engineer resume