The Database & DevOps Engineer is responsible for the performance, reliability, and overall health of Microsoft SQL Server databases supporting PathGroup's critical transactional applications. This is a hands-on, databas…
DevOps Engineer jobs in Nashville, TN
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.
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.
Open devops engineer roles
12 shown of 219 · sorted by freshness
Position: Senior Data Engineer Location: Nashville, TN preferred. Remote considered for candidates who work Central time hours... ...Dimensional modeling (star and snowflake schemas). ~ Azure DevOps and CI/CD for data en…
Job Title: Sr. Specialist Software Engineer Job Code: 46461 Job Location: Nashville TN Job Schedule: 9/80 employees work 9 out... ...to identify and apply design patterns as appropriate Azure DevOps source control (GIT)…
will troubleshoot build release and manage issues across the development lifecycle while applying secure engineering practices following the direction of Sr DevOps team member to strengthen delivery consistency platform…
Description Overview OCI Resource Query Service is seeking a Senior Platform Engineer to help evolve a critical cloud resource-discovery service into a richer resource analytics platform. The role combines hands-on engin…
Oracle Cloud Infrastructure (OCI) delivers cloud infrastructure services for a wide range of customer workloads. OCI Kubernetes Engine (OKE) is OCIs managed Kubernetes service helping customers deploy and operate contain…
Job Title: Specialist Software Engineering Job Code: 46235 Job Location: Nashville TN Job Schedule: 9/80employees work 9 out of... ...Basic understanding of UML (Unified Modeling Language) Azure DevOps source control (GI…
performance, capacity, and operability through resilience patterns, monitoring, logging, and automation. Collaborate with OCI engineers, review designs and code, and guide adoption of platform capabilities. Create techni…
want to be part of an inclusive, adaptable, and forward-thinking organization, apply now. We are currently seeking a Sr. DevOps / Cloud Engineer to join our team in either Plano, TX or Nashville, TN. Please note that thi…
in software design reviews, code reviews, technical discussions, and cross-functional collaboration. Mentor interns and junior engineers on day-to-day engineering practices. Continuously improve engineering practices, to…
operational readiness for Tier-0 systems. Define technical direction and lead complex initiatives spanning multiple services and engineering teams. Architect identity capabilities for AI agents, machine identities, servi…
Description Ingram Marine Group is hiring for a Sr. Platform Engineer in Nashville, TN . This role will be responsible for the... ...models and cost allocation methods Platform Engineering, DevOps & SRE Practices ~ Incid…
What devops engineers earn in Nashville
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $36–$50 | $75k–$105k |
| Mid level | $50–$72 | $105k–$150k |
| Senior | $70–$94 | $145k–$195k |
National ranges — pay in Nashville typically tracks these.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For devops engineers specifically — generic advice costs you here
Lead with measurable operational wins: deploy frequency, mean time to recovery, uptime, or cloud cost reductions.
Name your infrastructure stack precisely — 'Kubernetes on EKS with Terraform and GitHub Actions' beats 'cloud technologies'.
Certifications (AWS, CKA) still move the needle in this field; list current ones near the top.
Describe scale: number of services, clusters, or engineers your platform supported.
Mention incident and on-call experience — teams hiring DevOps are usually buying calm under pressure.
Where this role goes
Typical progression
Applying for devops engineer jobs in Nashville?
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.