DevOps Automation Engineer

Albuquerque, United States | Posted on 09/01/2026

• Salary Range (US) $95,000 - $125,000, DOE
• State/Province New Mexico
• Country United States

Securin is an AI-native cybersecurity company. Our Preemptive Exposure Management Platform turns exposure data into clear decisions — giving organizations the confidence to know which risks are exploitable, what to fix first, and how to act before attackers do.

About the role

We're hiring a Dev Ops Automation Engineer to help Securin replace manual operational processes with AI-assisted, automated ones. The focus of this role goes beyond maintaining our existing pipelines: you'll look across our build, deploy, security, and infrastructure workflows to find the repetitive, human-in-the-loop work and systematically automate it.

You'll work with in our established Dev Ops stack — Terraform, Jenkins, Sonar Qube, and AWS — and use coding agents as a primary implementation tool. We're investing in AI-assisted development because it lets a small team deliver far more, and we're looking for someone who can take advantage of that leverage while maintaining full ownership of the quality of what ships.

We're not attached to any particular tool. If there's a better option than what we run today — a different CI system, a different scanner — we're open to the conversation. What we care about is how a change like that is carried out: our developers are the users of this tooling, and any migration needs to be methodical, well‑communicated, and supportive of them at every step.

Their day‑to‑day work should keep flowing throughout the transition.

This role also serves as an important bridge to our India-based Dev Ops team. You'll partner with them regularly, align on shared standards and ownership, and help the two sides of the organization operate as one team.

We're looking for someone who is comfortable in this kind of environment and ready to contribute early. Direct experience with our specific CI and code‑quality tools is welcome but not required — if you've done this work with comparable tooling, that transfers. This is a hands‑on senior individual contributor role with a clear mandate and real autonomy.

Identify manual, repetitive, or error‑prone operational processes and replace them with automated, AI‑assisted workflows — and measure the time and toil recovered.

Build and maintain infrastructure as code in Terraform: modules, state strategy, environment promotion, drift detection, and remediation.

Own and extend Jenkins pipelines across build, test, security scan, artifact, and deploy stages, including shared libraries and reusable pipeline patterns.

Integrate and tune Sonar Qube quality gates so that code quality and security findings surface what matters without creating noise.

Use coding agents (e.g. Claude Code) as a primary implementation vehicle — decomposing problems, defining specs and guardrails, directing the work, and reviewing the results thoroughly.

Design and troubleshoot systems end to end across AWS, including compute, networking, IAM, storage, and how these services behave under failure.

Investigate and resolve production and pipeline incidents, then capture what you learned in runbooks and automation so the same issue doesn't return.

Partner with the India Dev Ops team on shared standards, on‑call practices, and clear handoffs, including attending late‑evening meetings a few times per week to maintain meaningful overlap with their working hours.

Evaluate whether our current tooling is still the right fit, and where a change is warranted, plan and execute the migration methodically — treating our developers as the users of the platform and keeping them supported and productive throughout.

Document what you build, so the automation you create is understandable and maintainable by the whole team.

A few examples of the kind of work we have in mind:

An on-demand SQL runner agent. Most of the database migrations are versioned in the code and run as part of the deployment process. In some cases, we need to make ad‑hoc changes to configuration tables. Rather than routing database changes through a…