$161k - $221k
excellence.This is an opportunity to do career-defining work. We're all in on this mission. If you are too, let's talk.Staff DevSecOps Engineer (TS/SCI)Secure Every Identity, from AI to HumanIdentity is the key to unlock…
Engineering & IT · Washington, DC
DevOps Engineer jobs in Washington, DC
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.
1,166
Open roles today
$45–$117/hr
Typical pay range
$159k
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
7 shown of 1,166 · sorted by freshness
Cloud DevOps Engineer Location: Washington, DC - Onsite Duration: 6+ Months Role Summary Seeking a Cloud DevOps Engineer with strong experience in AWS, Terraform/Ansible, CI/CD, Windows/Linux, and PKI/Credential Manageme…
DevOps Engineer As a Junior DevOps Engineer, you will support the automation and streamlining of deployment processes within a collaborative team environment. You will work with Linux-based systems, CI/CD pipelines, Jenk…
$180k - $190k
mission to safeguard and protect our customers from increasing threats and vulnerabilities in this digital age. TDI is seeking a DevOps Engineer to support a brand-new Agile development team at the forefront of federal I…
$200k - $220k
nation’s most sensitive and critical missions. The Release Train Engineer (RTE) supports a fast‑paced Agile environment by enabling... ...feature and capability execution using metrics across Agile and DevOps teams. Brie…
GCyber is seeking a Release Train Engineer, to help support a mission-focused federal IT modernization effort that is building and integrating... ...Track feature and capability execution using useful Agile and DevOps me…
$100k - $150k
Top Secret/SCI with Full Scope Polygraph (FSP); CI Polygraph within the last 7 years - must be active prior to start The DevOps Engineer (Development Lead) provides a reliable, highly available platform that orchestrates…
02
What devops engineers earn in Washington
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $45–$63 | $94k–$131k |
| Mid level | $63–$90 | $131k–$188k |
| Senior | $87–$117 | $181k–$244k |
Adjusted for the Washington 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 Washington?
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.