future. We are Science Driven. We are Customer Centric. We are Better Together. What do we need Dotmatics is seeking a DevOps Engineer to join our team working on ground-breaking Scientific Software products such as Luma…
DevOps Engineer jobs in Boston, MA
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 1,021 · sorted by freshness
turning fragmented HCP/HCO, prescription, and industry data into decisions the field can act on. Our team is seeking an Associate DevOps Engineer to support our business consulting team’s AWS and Kubernetes analytics inf…
everyone design, prototype, and manufacture faster than ever before. At Formlabs, DevOps is fundamental to how we build, scale, and maintain our products and services. Our Platform Engineering team drives the tools and i…
Job Description Job Description Vertex is seeking a hands-on Azure DevOps Engineer to build automate secure and support Azure cloud platforms used by enterprise applications data solutions and AI-enabled capabilities. Th…
FieldAI is transforming how robots interact with the real world. Our growing R&D team is based in Boston, where we develop risk-aware, reliable, field-ready AI systems that tackle the hardest problems in robotics and unl…
to the customers we work with and expanding those relationships into deep, meaningful partnerships. About the Role As a DevOps Engineer at Blitzy, you will be a critical force behind the infrastructure powering our cutti…
the B2B customer relationship. The Role We’re hiring an engineer to own our infrastructure — the AWS platform, deployment... ...ship to production many times a day with confidence Attack DevOps problems with AI: use codi…
operational issues and improve feedback loops between support and engineering. Set long-term technical direction for how PathAI services... ..., and operated. Requirements ~5+ years of experience in DevOps, platform, bui…
with customers, vendors, and internal teams. Develop cloud engineering methods and solutions across compute, storage, networking, security... ...automate builds, testing, monitoring, and releases to improve DevOps or Dev…
DevOps Engineer KCC's DevOps team plays a crucial role in the development and support of our global catastrophe models and RiskInsight® platform. As a member of our DevOps team, you will be responsible for managing the s…
Seeking a highly skilled DevOps Engineer to join our applications Development team. This role focuses on automating, optimizing, and supporting the deployment and management of application infrastructure in a cloud-first…
What devops engineers earn in Boston
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $46–$64 | $96k–$134k |
| Mid level | $64–$92 | $134k–$192k |
| Senior | $89–$120 | $186k–$250k |
Adjusted for the Boston 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 Boston?
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.