Role: DevOps Engineer (Kubernetes & OpenShift) Location: Charlotte, NC (Onsite) Job Summary We are looking for a DevOps Engineer with strong experience in Kubernetes and Red Hat OpenShift (OCP). The ideal candidate will…
Engineering & IT · Charlotte, NC
DevOps Engineer jobs in Charlotte, NC
DevOps engineers build the pipelines, infrastructure, and automation that let teams ship software quickly and safely. The work centers on CI/CD, cloud infrastructure, and reliability.
488
Open roles today
$36–$92/hr
Typical pay range
$125k
Median, full-time
6
Fresh in this list
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
01
Open devops engineer roles
12 shown of 488 · sorted by freshness
and infrastructure teams to deliver reliable cloud solutions. Required Skills & Qualifications ~7+ years of experience in DevOps Engineering, Cloud Engineering, Platform Engineering, or Site Reliability Engineering (SRE)…
Job Title: Sr. Application Support / DevOps Engineer (.NET) Location: Charlotte, NC only 3X a week . Final round in person , so ideally locals only Target profile This is primarily an Application Support/DevOps role supp…
API-based integrations. ~ Familiarity with Git, GitHub, Azure DevOps, and modern CI/CD practices. ~ Excellent problem-solving,... ...Bachelor's degree in Computer Science, Information Technology, Engineering, or a relate…
architecture integrity is maintained Mentors other software engineers and coach team on Continuous Integration and Continuous Development... ...Strategy Development Architecture Business Acumen DevOps Practices Result Or…
technology team operates at the intersection of enterprise data engineering and application development, with an emphasis on scalable... ...~ Experience with Azure Functions, Azure Service Bus, Azure DevOps, Azure Repos,…
Integrate security scanning and compliance checks into the software delivery lifecycle. We are seeking an experienced DevOps Engineer with strong expertise in cloud platforms, automation, CI/CD, containerization, infrast…
Description We are seeking a Senior DevOps Engineerwith expertise in CI/CD pipelines, GitHub Actions, and cloud security. You will balance high-level architectural improvements with daily monitoring and collaborate with…
across the enterprise. The environment brings together experienced engineers and financial technology professionals working across the... ...Experience with Git, Jenkins, CI/CD processes, and the broader DevOps lifecycle…
Job Description Job Description Description: Hybrid 3 on in Charlotte, NC Our client seeks a senior MLOps / DevOps Engineer focused on platform and infrastructure. The role emphasizes building and operating reliable, sca…
Job Description : Set up CI/CD pipelines and Helm charts for deployments. Implement GitOps for declarative infrastructure. Integrate observability tools for logs, metrics, and traces. Skills: Infrastructure: OpenShift/Ku…
knowledge of several technical competencies. Senior CI/CD Devops Lead who can work within the Credit space on, On-Prem and Cloud... ...Salesforce/AWS) applications in the capacity of CI/CD, DevSecOps Engineer Responsibil…
02
What devops engineers earn in Charlotte
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $36–$50 | $74k–$103k |
| Mid level | $50–$71 | $103k–$147k |
| Senior | $68–$92 | $142k–$191k |
Adjusted for the Charlotte market from national ranges.
03
What employers ask for
The skills these listings keep naming
AWS, GCP, or AzureKubernetes and DockerTerraform or other IaCCI/CD pipelinesLinux and shell scriptingPython or GoMonitoring (Prometheus, Grafana)Incident responseCost optimization
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through a CI/CD pipeline you built or improved.
Cover the stages, what you automated, and the measurable result — faster deploys, fewer failed releases. Numbers make this answer.
A deploy just took production down. What do you do?
Roll back first, diagnose second, communicate throughout. Then talk about prevention: canaries, health checks, smaller changes.
How do you manage infrastructure as code, and why does it matter?
Explain reproducibility, review, and drift prevention with a tool like Terraform. Mention how you handle state and secrets — that is where real experience shows.
How would you reduce a team's cloud bill?
Start with visibility (tagging, cost reports), then rightsizing, reserved capacity, and killing orphaned resources. A real example with a dollar figure is ideal.
How do you decide what to monitor and alert on?
Alert on symptoms users feel, not every metric. Talk about SLOs and reducing alert fatigue — mature answers focus on fewer, better alerts.
How do you roll out a risky infrastructure change?
Describe staging environments, incremental rollout, rollback plans, and communicating with affected teams before you touch anything.
How do you handle secrets in pipelines and applications?
Name a secrets manager, rotation, and least privilege, and the anti-pattern you are avoiding: credentials in code or CI variables sprayed everywhere.
05
Resume tips that move the needle
For devops engineers specifically — generic advice costs you here
01
Lead with measurable operational wins: deploy frequency, mean time to recovery, uptime, or cloud cost reductions.
02
Name your infrastructure stack precisely — 'Kubernetes on EKS with Terraform and GitHub Actions' beats 'cloud technologies'.
03
Certifications (AWS, CKA) still move the needle in this field; list current ones near the top.
04
Describe scale: number of services, clusters, or engineers your platform supported.
05
Mention incident and on-call experience — teams hiring DevOps are usually buying calm under pressure.
06
Where this role goes
Typical progression
01
Junior DevOps Engineer
02
DevOps Engineer
03
Senior DevOps Engineer
04
Platform Engineering Lead
Ten quiet minutes a day
Applying for devops engineer jobs in Charlotte?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.