$150k - $230k
industry , committed to making a positive impact on its customers, employees, and communities. The Role As a Principal DevOps Engineer for a new product within Veeva, you will be a founding member of a team building our…
Engineering & IT · Kansas City, MO
DevOps Engineer jobs in Kansas City, MO
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.
259
Open roles today
$34–$88/hr
Typical pay range
$120k
Median, full-time
3
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
5 shown of 259 · sorted by freshness
React. Work closely with product owners, architects, and QA engineers to clarify requirements and deliver high-quality solutions.... ...Contribute to CI/CD pipelines, deployment automation, and DevOps practices to improv…
Kforce is looking for a Senior Software Engineer in Kansas City, MO. Responsibilities: ~ Use appropriate tools, programming languages... ...pipelines, quality gates, and deployment processes using Azure DevOps ~ Ensure p…
verifiable Microsoft certification aligned to D365 F&O or Azure required. ~ Hands-on experience with D365 F&O, X++, Visual Studio, Azure DevOps, LCS, DMF, integrations/APIs, and enterprise ERP support. ~ Experience suppo…
$110 - $120 per hour
Collaborate with client stakeholders, technical leads, cloud engineers, and project teams to support secure application operations in... ....NET, JavaScript/TypeScript, REST API integrations, and Azure DevOps. ~ Experien…
02
What devops engineers earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$48 | $70k–$99k |
| Mid level | $48–$68 | $99k–$141k |
| Senior | $65–$88 | $136k–$183k |
Adjusted for the Kansas City 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 Kansas City?
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.