Skip to content
Nasuni

Senior DevOps Engineer, Release Engineering

Boston, Massachusetts, United States; Marlborough, Massachusetts, United States; Boston; MarlboroughUnited States
Senior · Core Engineering
POSTED 15 SEPTVERIFIED 28M AGO
Apply Ask
Role
57 days opentrue age
Past the 49d median close
Posted 15 Sept · n=12
Pay
$154k–$180kno pay posted
Market p25–p75
$154k–$180k
Boston · n=17 · 365d to 10 Nov
CompanyNasuni →
28open roles
Opened · 30d
+3
Closed · 30d
−7
10d of snapshots · 30d window
Market
1,726open · Senior DevOps / SRE / Infra
Opened · 7d
+1106% of open
All devops / sre / infra
7,031open
All tracked boards · live 11 Nov · n=1,726
Visa
1H-1B LCAs · FY26
LCAs FY26 · n=1 · to 2026-04-09
PythonKubernetesDockerTerraform

Senior DevOps Engineer – Release Engineering

Location: Boston / Marlborough, MA — Hybrid, 3 days per week

Role Overview

This role is for an engineer who has both sides of release engineering: rewrite the product build, and run the DevOps infrastructure that builds, tests and ships it.

Nasuni is looking for a hands-on Senior DevOps Engineer – Release Engineering who is able to reshape how our product is built (Makefiles, bash, Python) and own the Linux-based CI/CD and build infrastructure it runs on (Jenkins, GitHub Actions, Packer/Terraform/Ansible, Artifactory), while creating dynamic agents in the cloud.

This role is for you if you have rewritten or optimized a product build system and built the infrastructure around your CI/CD. It is not the right fit if your experience is strong on only one side: pipelines and infrastructure without hands-on build code or build scripts without the DevOps tooling. We both need the same person.

You will work independently, partner directly with developers to remove bottlenecks, and improve delivery speed, reliability and release quality across multiple engineering teams. This is a hands-on engineering role, not a release-coordination or operations-support position.

What You'll Do

Build engineering (the code side)

  • Read, rewrite and optimize product build scripts and Makefile-based builds; make them faster, repeatable and easier for developers to work with.
  • Partner with development teams to find and remove build bottlenecks, flaky builds and slow dependency or packaging steps.
  • Write and maintain automation in bash and Python (and Groovy for Jenkins) across a Linux-based environment.
  • Define build and release requirements for complex product changes and flag release, dependency and infrastructure risks early.

DevOps and release infrastructure

  • Build and run distributed CI/CD on Jenkins (Groovy pipelines, distributed agents) and GitHub Actions, including automated branch validation and release-readiness checks for patch, release and code-freeze workflows.
  • Own build agent templates and environments using Packer, Terraform and Ansible (or Docker-based alternatives), with hands-on Docker and Kubernetes.
  • Manage artifact and package workflows in Artifactory: RPM lifecycle, repository organization, traceability and promotion.
  • Design and evolve branching, versioning and release models across multiple repositories.
  • Strengthen monitoring, alerting and visibility across build infrastructure using Zabbix, plus Grafana or Prometheus.

Troubleshooting, ownership and collaboration

  • Diagnose complex pipeline and distributed-infrastructure failures and implement durable fixes, not workarounds.
  • Automate repetitive work, and lead cross-team technical initiatives with Engineering and QA.
  • Mentor other engineers in build and release practices.
  • Use AI-assisted tools for log analysis, code generation, troubleshooting and workflow automation, and validate the output for correctness, security and production readiness.

Must-Have Qualifications

Candidates need both the build-engineering and DevOps items below. Strength in only one side will not be enough. All experience should be recent, within the last 2–3 years.

Build engineering

  • Hands-on experience reading, rewriting, troubleshooting and optimizing product build scripts and build tooling, including Makefile-based builds. You should be able to describe a build system you rewrote.
  • Strong bash and Python scripting.

DevOps and infrastructure

  • Advanced Jenkins pipeline development (Groovy, distributed agents) and distributed CI/CD experience.
  • Experience designing and running the infrastructure behind CI/CD, such as build agents, templates and environments, supporting multiple engineers or teams.
  • Hands-on Docker and Kubernetes.
  • Strong Linux administration, troubleshooting and networking fundamentals. Our environment is almost entirely Linux.

Release and troubleshooting

  • Experience with branching models, release workflows, source control and versioning across multiple repositories.
  • Ability to independently diagnose complex distributed-system or pipeline failures and implement durable fixes, with recent examples.
Source · NasuniFirst seen 2 Nov2 editsOriginal ↗