priority — our systems are designed to meet strict uptime targets, including no downtime during market hours. As a Senior Software Engineer, you will build and improve core infrastructure used by many engineering teams,…
DevOps Engineer jobs in Seattle, WA
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 541 · sorted by freshness
, differentiated, and personalized experiences that drive loyalty and traveler satisfaction. The Senior Software Development Engineer – ML Platform role is a part of the ML Platform team. We build Expedia Group's ML Plat…
and thrive as part of an inclusive global community that's redefining the future of commerce. About the Role: As a Senior DevOps Engineer on our Platform Engineering team, you'll bring deep, hands-on expertise to solve i…
2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at What You'll Do: The Systems Engineering team owns the host software stack that turns a freshly provisioned bare-metal machine i…
customers and business teams, powering experiences across commerce, personalization, inventory, and customer service. As Senior Engineer, you are a lead individual contributor responsible for the quality of a team’s work…
Senior Software Engineer, AI/ML Platforms and Infrastructure – Brain Health Accelerator The mission of the AllenInstitute is to understand the principles that govern life and to advance health. Our creative and multi-dim…
, and end to end test suites Manage test execution cycles, defect identification, tracking, and closure using SAP/ALM / Azure DevOps / QTest tools Formularize the automation scripts to be executed in different environmen…
produces events, the data team that owns the lakehouse you feed, infrastructure/operations who run the managed log and broker, and the engineers building the agent and CV workflows that consume your platform. ROLE RESPON…
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…
DevOps Engineer IIIThe mission of the AllenInstitute is to understand the principles that govern life and to advance health. Our creative and multi-dimensional teams focus on answering some of the biggest questions in bi…
Job Description Job Description This is a great opportunity to put both your engineering & cloud operations skillset to use. We are currently looking for a DevOps Engineer to deeply embed within our engineering team to g…
What devops engineers earn in Seattle
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 Seattle 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 Seattle?
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.