teams contribute domain content through APIs, evals, and knowledge — the platform owns the experience. We're hiring a staff-level engineer to take ownership of major runtime surfaces and grow into a technical owner of th…
Engineering & IT · Portland, OR
DevOps Engineer jobs in Portland, OR
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.
190
Open roles today
$39–$103/hr
Typical pay range
$140k
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
6 shown of 190 · sorted by freshness
A local distribution company is seeking a fully remote Senior Azure Cloud Security Engineer to support its cloud security initiatives. This role involves securing Azure environments, automating security processes, and co…
creative, collaborative and sustainable environment where opportunities for growth, leadership and recognition abound. The Platform Engineer will be building a highly configurable, multi-tenant enterprise class SaaS solu…
$9,731.21 per month
The City of Beaverton is seeking an Assistant City Traffic Engineer (ACTE) who will play a key role in shaping the future of traffic and transportation in the city. This position is in the Public Works Transportation Eng…
hurricanes, the primaries and more. Founded by 20-year veterans of the cyber security industry, Swan Island Networks began as a software engineering lab working with the US government, focusing on R&D programs. Now our p…
Job Description Axian is seeking a Senior Full Stack Software Engineer to design, build, and modernize enterprise-grade applications and... ...discussions. ~Implement CI/CD pipelines and support DevOps automation practic…
02
What devops engineers earn in Portland
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $39–$56 | $82k–$116k |
| Mid level | $56–$79 | $116k–$165k |
| Senior | $77–$103 | $160k–$215k |
Adjusted for the Portland 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 Portland?
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.