Information Services Division's Headquarters. Founded in 2007 by an Engineer- by-trade, Fusion Technology dedicates our valuable resources to... ...enhancements and sustainment. What you'll do: As a DevOps Engineer, you…
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.
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
11 shown of 2,512 · sorted by freshness
As a DevOps Engineer, you know how to set up cloud environments and provision computer networking, storage, and virtual networks. On the team of cloud experts, you’ll use your configuration management and provision know-…
DevOps Engineer ROLE We need an experienced DevOps Engineer to support a contract with the United States Capitol Polices (USCP) Enterprise Applications Management Division (EAMD) where the design building and maintenance…
Datawiz, a GTSC company, seeks a DevOps Engineer to support a federal government customer in Washington, DC. Several positions may be available. Location: Washington, DC Schedule: Monday through Friday business hours. Hy…
Our innovative strategies and solutions securely and rapidly transform the way our clients do business. We are hiring a DevOps Engineer to design, automate, and scale cloud-native infrastructure supporting enterprise-gra…
hatch I.T. is partnering with Expression to find a DevOps Engineer . See details below: About The Role: Expression is seeking a mid-level DevOps Engineer to support the National Telecommunications and Information Adminis…
software agents. We're the makers of Devin, the first AI software engineer. Our team is extremely talent-dense. Among our founding team... ...high-impact ownership and professional development. Federal DevOps Engineers a…
of that evolving usage. Core Responsibilities Apply modern engineering practices to improve the maintainability, reliability, and... ...infrastructure. Hands-on experience with CI/CD pipelines, DevOps practices, and syst…
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…
We are looking for DevOps Engineers to scale our clients build and deployment infrastructure as the company grows fast. You’ll join the backend platform team, working closely with the data platform and security. These ar…
Overview: Expression is seeking a mid-level DevOps Engineer to support the National Telecommunications and Information Administration (NTIA) Federal Spectrum Data Systems (FSDS) program within the U.S. Department of Comm…
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.
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 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.