DevSecOps Engineer

DEPARTMENT OF CORRECTIONS

Where
Oklahoma County
Type
Full time

Posted 9 days ago· Checked live at DEPARTMENT OF CORRECTIONS 4 days ago

Live.Open on the employer's own site.

See how you score for this job

One sentence and your resume. We score it against what DEPARTMENT OF CORRECTIONS asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on DEPARTMENT OF CORRECTIONS's own hiring page 4 days ago.
What is the job?
Job Posting Title DevSecOps Engineer
What does it pay?
The posting doesn't say.
Our verdict
Live. Open on the employer's own site.

What the job is

Job Posting Title

DevSecOps Engineer

Agency

Supervisory Organization

IS-Servers

Job Posting End Date

Refer to the date listed at the top of this posting, if available. Continuous if date is blank.

Note: Applications will be accepted until 11:59 PM on the day prior to the posting end date above.

Estimated Appointment End Date (Continuous if Blank)

Full/Part-Time

Full time

Job Type

Regular

Job Description

Compensation

Job Description

Key Responsibilities

Automation Engineering & Infrastructure as Code

  • Design, build, and maintain infrastructure as code (IaC) using tools such as Terraform, Ansible, or equivalent, replacing manual provisioning and configuration with version-controlled, repeatable automation.
  • Build self-service tooling and pipelines that let SOT staff provision, deploy, and remediate common issues without engineering intervention.
  • Continuously identify manual, repetitive operational tasks and automate them, treating toil reduction as an ongoing responsibility rather than a one-time project.

Minimum Qualifications

Requirements include 5 years of experience in DevOps, DevSecOps, SRE, or platform engineering roles, including:

  • Hands-on experience with infrastructure as code (Terraform, Ansible, Pulumi, or equivalent) and CI/CD tooling (e.g., GitHub Actions, GitLab CI, Jenkins, Azure DevOps).
  • Experience embedding security practices (SAST/DAST, secrets management, policy-as-code) directly into delivery pipelines.
  • Experience building observability with tools such as Prometheus, Grafana, Datadog, Splunk, or equivalent.
  • Strong scripting/automation ability (Python, Bash, PowerShell, or similar).
  • A demonstrated bias toward action: comfortable operating with incomplete requirements, proposing a path forward, and iterating in the open.