1

Virtual Automation Engineer Jobs in New Mexico (NOW HIRING)

DevOps Automation Engineer

Albuquerque, NM Β· On-site

$95K - $125K/yr

A virtual developer. An agent that handles well‑understood, boilerplate implementation work end ... Security and compliance automation -- secrets management, policy as code, SOC 2 or similar audit ...

... automation, and robotics, and supports CAPEX projects to commission new production lines. Key ... IT/OT Infrastructure Support: Assist with maintaining IT/OT infrastructure (servers, virtual ...

Cloud Engineer II

Albuquerque, NM Β· Hybrid

$130K - $180K/yr

... automation tools such as Terraform, Bicep, ARM templates, PowerShell, Azure CLI, Git, Azure DevOps, or GitHub Actions * Experience administering Azure virtual machines, storage, virtual networks ...

... automation tools such as Terraform, Bicep, ARM templates, PowerShell, Azure CLI, Git, Azure DevOps, or GitHub Actions * Experience administering Azure virtual machines, storage, virtual networks ...

next page

Showing results 1-20

Virtual Automation Engineer information

What is a virtual automation engineer?

A Virtual Automation Engineer is a professional who designs, develops, and maintains automated systems and processes in a virtual or cloud-based environment. They use software tools and scripting to automate repetitive tasks, workflows, and business operations, often working with technologies like robotic process automation (RPA), cloud platforms, and virtual machines. Their goal is to improve efficiency, reduce manual effort, and ensure the reliability of digital processes across an organization. Virtual Automation Engineers often collaborate with IT, development, and operations teams to integrate automation solutions that align with business objectives.

How does a virtual automation engineer typically collaborate with cross-functional teams while working remotely?

As a Virtual Automation Engineer, effective collaboration with cross-functional teamsβ€”such as software developers, QA analysts, and IT operationsβ€”is essential. Most communication happens through digital channels like video calls, chat platforms, and project management tools. You may participate in daily stand-ups, sprint planning meetings, and code reviews to align on automation goals and troubleshoot issues in real-time. Establishing clear documentation and proactively sharing updates helps ensure everyone stays informed and projects move forward smoothly in a remote environment.

What are the key skills and qualifications needed to thrive as a virtual automation engineer, and why are they important?

To succeed as a Virtual Automation Engineer, you need strong expertise in programming, process automation, and a solid understanding of computer networks, often backed by a degree in computer science or engineering. Familiarity with automation tools like UiPath, Blue Prism, or Automation Anywhere, and relevant certifications such as Certified RPA Developer, are highly valuable. Outstanding problem-solving skills, attention to detail, and effective communication set exceptional candidates apart. These skills and qualifications are critical for designing, implementing, and maintaining efficient automated solutions that optimize digital workflows and enhance productivity.

What is the difference between Virtual Automation Engineer vs Automation Technician?

AspectVirtual Automation EngineerAutomation Technician
CredentialsBachelor's in Engineering or related field, certifications like PLC or SCADATechnical diploma or associate degree, certifications in automation systems
Work EnvironmentRemote or hybrid, project-based, software-focusedOn-site, industrial settings, hands-on equipment
Industry UsageManufacturing, software development, industrial automationManufacturing plants, maintenance, troubleshooting

The Virtual Automation Engineer primarily designs and develops automation solutions remotely, focusing on software and system integration. In contrast, the Automation Technician works directly on-site, maintaining and troubleshooting automation hardware. Both roles require technical knowledge, but their work environments and daily tasks differ significantly.

Can virtual automation engineers work remotely?

Yes, virtual automation engineers can often work remotely, especially since their tasks involve designing and maintaining automation systems that can be managed through remote access tools. Many companies in this field offer remote or hybrid work arrangements, provided the engineer has strong communication skills and proficiency with automation software and collaboration platforms.

What are the most commonly searched types of Automation Engineer jobs in New Mexico?

The most popular types of Automation Engineer jobs in New Mexico are:

What are popular job titles related to Virtual Automation Engineer jobs in New Mexico?

For Virtual Automation Engineer jobs in New Mexico, the most frequently searched job titles are:

What job categories do people searching Virtual Automation Engineer jobs in New Mexico look for?

The top searched job categories for Virtual Automation Engineer jobs in New Mexico are:

What cities in New Mexico are hiring for Virtual Automation Engineer jobs?

Cities in New Mexico with the most Virtual Automation Engineer job openings:

DevOps Automation Engineer

Albuquerque, NM β€’ On-site

Securin
Network SecurityΒ β€’Β 51 - 200 employees

$95K - $125K/yr

Other

Medical, Vision, Life

Posted 6 days ago


Job description

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

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

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 DevOps 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 within our established DevOps stack β€” Terraform, Jenkins, SonarQube, 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 DevOps 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.

What you'll do

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 SonarQube 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 DevOps 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.

What this looks like in practice

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 person, an agent validates the SQL, executes it against the appropriate cloud infrastructure, monitors the run to completion, and reports back on progress and outcome.

A virtual developer. An agent that handles well‑understood, boilerplate implementation work end to end β€” writing the change, verifying it builds and passes tests, and opening a pull request that's ready for human review.

These are illustrative rather than prescriptive. Part of the role is identifying which opportunities are worth pursuing and in what order.

Requirements

Candidates must reside in or be within commuting distance to Albuquerque, NM.

Applicants must be legally authorized to work in the United States and must not require current or future employment visa sponsorship.

Employment is contingent upon successful completion of a background check, including verification of prior employment.

Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related technical field, or equivalent practical experience.

2+ years of hands‑on AWS experience across core services (EC2, ECS/EKS, S3, IAM, VPC, RDS, CloudWatch), including a practical understanding of how they behave under failure.

Production experience with infrastructure as code, using any mainstream tool (Terraform, OpenTofu, Pulumi, CloudFormation/CDK, or similar) β€” you've designed and owned infrastructure definitions, not only worked within someone else's modules.

Experience owning CI/CD pipelines in production, with any mainstream tooling (Jenkins, GitHub Actions, GitLab CI, CircleCI, Azure DevOps, or similar) β€” the concepts matter more to us than the specific product.

Strong system design fundamentals: the ability to reason about tradeoffs, failure domains, state, idempotency, and blast radius before writing code.

Strong system troubleshooting skills: a methodical, evidence‑driven approach to debugging distributed systems and CI/CD pipelines, including under time pressure.

Strong programming principles β€” software engineering discipline (testing, version control, modularity, code review, readable code) applied to infrastructure and tooling. Proficiency in Python, Go, or a comparable language.

Experience using coding agents for substantive implementation work, along with the judgment to evaluate agent output critically and review it to the same standard as your own.

Willingness to work with a distributed team across time zones, including late‑evening meetings a few times per week with our India DevOps team.

A developer‑as‑customer mindset: the judgment to weigh a tooling change on its merits, and the discipline to migrate in careful, well‑communicated stages rather than disruptive cutovers.

Clear written communication β€” much of your work will be documented for colleagues in other time zones.

Nice to have
  • Direct experience with Terraform β€” this is what we use today, alongside Jenkins and SonarQube.
  • Direct experience with Jenkins, including shared libraries and reusable pipeline patterns.
  • Direct experience with SonarQube or comparable static analysis and code‑quality gating (Snyk, Semgrep, Checkmarx, CodeQL).
  • Containers and orchestration at production scale (Docker, Kubernetes/EKS).
  • Observability tooling (CloudWatch, Datadog, Prometheus/Grafana, OpenTelemetry) and experience building alerting that teams trust.
  • Security and compliance automation β€” secrets management, policy as code, SOC 2 or similar audit evidence collection.
  • Experience building internal developer platforms or self‑service tooling.
  • Prior experience bridging onshore and offshore engineering teams.
  • Background in security or vulnerability management products.
Medical Insurance
  • Multiple plan options with low deductibles and competitive rates for individuals and families.
  • High and low plan options with 100% coverage for preventive care.
Vision Insurance
  • Coverage for exams, glasses, and contacts with generous allowances.
Life & AD&D Insurance
  • Company‑paid basic life insurance; optional supplemental coverage for employees and dependents.
Short-Term & Long-Term Disability
  • Income protection up to 60% of earnings for qualifying disabilities.
Flexible Enrollment with Rippling
  • Easy online platform for managing benefits and life event changes.
#J-18808-Ljbffr