> Markdown version of [/jobs/ext/3767150-senior-devops-engineer](https://www.wearedevelopers.com/jobs/ext/3767150-senior-devops-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior DevOps Engineer

- **Company:** Randstad
- **Location:** Charlotte, NC, United States
- **Experience:** Expert
- **Salary:** $104,853.0 - $124,800.0
- **Contract:** Contract
- **Skills:** Continuous Integration, DevOps, OpenShift, Scrum Methodology, Ansible, Software Vulnerability Management, Bitbucket, Jenkins
- **Published:** October 16, 2026
- **Apply:** https://www.dice.com/job-detail/c97be55f-b659-45b6-9d96-1c8af0104293

## About the Role

I'm looking for someone who is hands-on and technically strong, not someone whose experience is primarily DevOps coordination or process management. They should be comfortable troubleshooting real CI/CD and OpenShift problems, working through failures, and automating solutions rather than simply escalating issues.

They do not necessarily need deep experience with every tool listed above, but their background should demonstrate solid CI/CD fundamentals, automation experience, and the ability to learn quickly in a complex enterprise environment.

My team is lean - there is no scrum master, no business analyst, no product owner.

One important point about the team environment: we are lean and operate differently from a traditional Scrum application team. We do not have a Scrum Master, Business Analyst, or Product Owner, and we use Kanban rather than Scrum. I need someone who is comfortable operating with a high degree of autonomy, picking up and driving work without a lot of ceremony, and responding quickly when troubleshooting, support, onboarding, deployment, or other requests come in. Someone who needs a heavily structured backlog or Scrum process to direct their day-to-day work is probably not the right fit.

qualifications:

I'm looking for someone who is hands-on and technically strong, not someone whose experience is primarily DevOps coordination or process management. They should be comfortable troubleshooting real CI/CD and OpenShift problems, working through failures, and automating solutions rather than simply escalating issues.

They do not necessarily need deep experience with every tool listed above, but their background should demonstrate solid CI/CD fundamentals, automation experience, and the ability to learn quickly in a complex enterprise environment.

My team is lean - there is no scrum master, no business analyst, no product owner.

One important point about the team environment: we are lean and operate differently from a traditional Scrum application team. We do not have a Scrum Master, Business Analyst, or Product Owner, and we use Kanban rather than Scrum. I need someone who is comfortable operating with a high degree of autonomy, picking up and driving work without a lot of ceremony, and responding quickly when troubleshooting, support, onboarding, deployment, or other requests come in. Someone who needs a heavily structured backlog or Scrum process to direct their day-to-day work is probably not the right fit.

skills:

Ansible,Bitbucket,CI/CD,DevOps,Jenkins,OpenShift,Vulnerability remediation,Troubleshooting,reliability,Automating,deployment support,Onboarding,investigating,Standardizing,tooling

## Description

This person will be joining my DevOps team and working across multiple EIT applications. Day-to-day responsibilities will include:

Supporting multiple application CI/CD pipelines and OpenShift workloads

Troubleshooting, investigating, and remediating CI/CD and OpenShift failures

Onboarding new services

Standardizing existing services and deployment patterns

Automating repetitive work

Vulnerability remediation and management

Performance and reliability improvements

Occasional weekend deployment support, although this will be the exception rather than the rule