Skip to main content

Ten Great DevOps Job Opportunities

DevOps.com is now providing a weekly DevOps jobs report through which opportunities for DevOps professionals will be highlighted as part of an effort to better serve our audience.

Our goal in these challenging economic times is to make it just that much easier for DevOps professionals to advance their careers.

Of course, the pool of available DevOps talent is still relatively constrained, so when one DevOps professional takes on a new role, it tends to create opportunities for others.

The ten job postings shared this week are selected based on the company looking to hire, the vertical industry segment and naturally, the pay scale being offered.

We’re also committed to providing additional insights into the state of the DevOps job market. In the meantime, for your consideration.

Greenhouse

Inflection AI
Palo Alto, CA
Senior DevOps Engineer (AI & Cloud Infrastructure)
$175,000 to $250,000

NABIS
Remote, US
Senior DevOps Engineer
$145,000 to $165,000

Trovo Health
New York, NY
Lead DevOps Engineer
$220,000 to $250,000

Skylight
Remote, US
Senior/Staff DevOps Engineer
$150,000 to $203,000

SIXGEN
Columbia, MD
Senior DevOps Engineer
$180,000 to $220,000

Gallup
San Francisco, CA
Site Reliability Engineer
$150,000 to $200,000

Campminder
Remote, US
Senior DevOps Engineer
$175,000 to $215,000

NMI
Remote, US
Staff DevOps Infrastructure Engineer
$155,000 to $165,000

Ashby

Wealth.com
New York, NY
Senior Software Engineer, DevOps
$195,000 to $220,000

Homebot
Denver, CO
Senior DevOps Engineer
$145,000 to $170,000



from DevOps.com https://ift.tt/PdKLrtc

Comments

Popular posts from this blog

Shift Left to the Developer’s Machine: Building Local Git Security Gates 

A developer pushes one file. It contains an AWS access key left in a configuration block. Five minutes later, CI catches it. By then, the secret is in the remote repository, cached by mirrors and potentially forked. The developer rotates the key, scrubs the commit history and spends the rest of the afternoon on incident response. The real question isn’t how to clean up faster — it’s why the secret left the developer’s machine in the first place.   The Five-Minute Gap   Most engineering teams have invested in CI-based secret scanning . Tools such as GitHub Advanced Security, GitGuardian and TruffleHog’s CI integration catch leaked credentials in pull requests and pushed branches. This is good, but it’s also too late.   The GitGuardian 2026 State of Secrets Sprawl report found that 29 million secrets were detected on GitHub in 2025 alone — a 34% year-over-year increase and the largest single-year jump ever recorded. Worse, 64% of secrets leaked back in 202...

Cloudbees Is A Launch Partner For Google Cloud Run As Product Goes Ga

Industry Leaders Collaborate to Offer Streamlined Deployment of Containerized Applications, Better Access to CloudBees Solutions on Google Cloud Platform Marketplace   GOOGLE CLOUD NEXT, LONDON AND SAN JOSE, CA. – November 20, 2019 – CloudBees, the enterprise DevOps leader powering the continuous economy, today announced an extension of its partnership with Google. As a Google […] The post Cloudbees Is A Launch Partner For Google Cloud Run As Product Goes Ga appeared first on DevOps.com . from DevOps.com https://ift.tt/2XuFTxc

Carbon-Aware DevOps: Turning CI/CD Pipelines Into Emissions-Controlled Workloads 

Turning continuous integration and continuous delivery (CI/CD) pipelines into emissions‑controlled workloads is a strategy businesses adopt to reduce the carbon footprint of their pipelines. This article examines how a Carbon-Aware DevOps strategy can help optimize CI/CD pipelines for sustainability by reducing their carbon footprint while also decreasing costs and meeting the increasing demand for innovative, eco-friendly solutions.   Understanding the Problem   Today’s organizations take advantage of CI/CD pipelines to streamline and accelerate their software delivery. However, these CI/CD pipelines can become a hindrance to sustainability because of the resources required to create, build, test and ultimately deploy software into production.   Typically, CI/CD pipelines run tens of thousands of automated builds, tests and deployments daily, thereby consuming significant compute and energy resources. If you don’t take the steps necessary to reduce the emissions generated by these ...