,weretrusted to deliver transparency, cost savings, and peace of mind. WhatWereLooking For VPL is looking for a hands-on DevOps Engineer to helpoperateand improve our Azure cloud environments and container-based applicat…
DevOps Engineer jobs in Columbus, OH
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
3 shown of 1,116 · sorted by freshness
Job Title: Azure DevOps Engineer Location: Princeton, NJ, Newark, NJ, New York City, NY, Boston, MA, Hartford, CT. Looking for W2 candidates. No C2C Job Summary: Seeking an Azure DevOps Engineer with experience managing…
Job Summary: The DevOps Cloud Engineer is a technical expert responsible for designing, implementing, and supporting cloud-based IT solutions primarily on Microsoft Azure and AWS platforms. This advanced role involves bu…
What devops engineers earn in Columbus
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$48 | $71k–$100k |
| Mid level | $48–$68 | $100k–$142k |
| Senior | $66–$89 | $138k–$185k |
Adjusted for the Columbus market from national ranges.
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 Columbus?
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.