staging-devopsy.kinsta.cloud 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 five 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.
Announced at the AWS re:Invent 2025 conference, Harness is now integrating the Model Context Protocol (MCP) server it added to its continuous integration/continuous delivery (CI/CD) platform with the Kiro AI coding tool developed by AWS.
At the same time, Harness is now making its entire DevOps platform available on the AWS cloud.
Bala Venkatrao, senior vice president and general manager for platform at Harness, said that integration will make it possible for the AI agents that are being embedded into Kiro to invoke AI agents that Harness has developed to automate workflows using a Harness Software Delivery Knowledge Graph that helps ensure more accurate outputs are generated.
That approach will enable developers to invoke, for example, security scans as they code, with DevOps teams then relying on Harness to automate workflows after code is checked in.
Longer term, Harness expects to develop similar relationships with other providers of AI coding tools, noted Venkatrao. The Harness CI/CD platform will, in time, become the vehicle for integrating and observing DevOps workflows spanning multiple cloud computing environments, he added.
Mitch Ashley, vice president and practice lead for software lifecycle engineering for The Futurum Group, said the Harness integration with AWS demonstrates how AI-generated code and delivery systems can operate as one workflow. Kiro gains direct access to the delivery context, and Harness brings the intelligence needed to validate, secure, and move that code through pipelines without slowing teams down. Developers stay inside their environment while agents see the full picture of build health, policy checks, and production readiness, he added.
As a result, Harness is positioning delivery as an adaptive system that learns from every build and release, and AWS provides the platform where that automation can run at scale. As this approach takes hold, AI software development will shift from being a set of disconnected stages to a continuous operational loop that improves with each change, noted Ashley.
Neha Goswami, director of engineering for Amazon Q Developer at AWS, said the overall goal is to reduce the level of friction software engineering teams currently experience between when code is checked in and when an application is deployed in a production environment. AWS does not have any ambitions toward building its own CI/CD platform or code repository, but there is an opportunity to leverage AI agents to streamline DevOps workflows.
In fact, as more code is generated using AI coding tools it will soon become apparent that every organization that builds software will need a CI/CD platform to manage those workflows, noted Goswami.
It’s still too early to say how best DevOps practices will evolve in the age of AI but the one thing that is certain is AI agents will make it simpler for application developers to invoke a range of backend services that should improve the quality of the code being created before it finds its way into a build.
When I first landed in Las Vegas for re:Invent and saw the keynote previews, it looked like AWS was putting all its chips on one square: Agentic AI. Every sign, every teaser, every whisper pointed in the same direction. And yes, after the keynotes, that impression held up. AWS is clearly betting big on agents, new model families, specialized hardware and everything needed to power the next generation of AI workloads.
But that’s only the surface story.
After spending real time on the floor, walking the expo, talking with attendees, asking vendors what they were hearing and watching the sessions closely, a very different picture emerged. DevOps, cloud native and platform engineering were not pushed to the sidelines. They were present, energetic and in many cases central to the conversations happening away from the big stage lights.
In other words, the foundations of modern tech are not quietly fading into the background. They are very much alive here. And they are thriving.
The Headlines Say “AI,” but the Work Still Says “DevOps”
There is no escaping the fact that this re:Invent leaned harder into AI than any I have attended. Frontier agents, expanded Nova 2 models, new silicon, AI orchestration systems and “AI Factory” concepts all took center stage. AWS wanted the world to know it is serious about leading the next phase of AI adoption.
What surprised me, though, was how often DevOps showed up once you looked past the main stage.
New automation capabilities appeared throughout the announcements. AWS previewed workflow and coordination enhancements for building reliable, long-running, multi-step processes. That is classic DevOps territory. The new AWS DevOps Agent landed as one of the most practical reveals at the show. A managed CI/CD runner that eliminates the need for teams to maintain their own build systems is not about hype. It is about helping organizations ship software safely and repeatedly.
And look across the expo floor. The overwhelming majority of DevOps vendors came in with force. Budgets might be tight, but the booths were busy, the conversations were serious and customers still wanted to talk pipelines, testing, automation, security, observability and tooling integration. Everyone I spoke to said the same thing: the AI wave is real, but software still has to get built. Enterprises still need to deliver reliable services. DevOps continues to be the engine that makes that possible.
Cloud Native: The Modernization Path Is Still the Preferred Route
The cloud native story is just as strong here. AWS quietly reinforced the importance of containers, serverless functions, orchestration layers and managed services across a wide range of sessions. No matter how futuristic the AI narrative becomes, modernization and digital transformation still rely on cloud-native principles.
That was the underlying rhythm of the show. Not loud, but steady and constant. You could feel it in the types of sessions that filled up. You could see it in the partner announcements. You could hear it in the way customers described their real challenges. Moving to modern architectures remains the path forward and AWS knows it.
AI may open doors to new possibilities, but those possibilities won’t materialize without the scalability, resilience and operational discipline that cloud native brings.
Platform Engineering Steps Into Its Maturity
Another encouraging sign this year is how Platform Engineering has settled into its rightful place. A few years ago, it was still treated like an emerging trend or a niche approach practiced by the avant-garde of tech organizations. That era is over.
Today Platform Engineering is accepted, well understood and viewed as an essential function for any company that wants to move with speed and safety. I had dozens of conversations with platform teams building internal developer platforms, unified self-service systems and automation layers that support both traditional workloads and the new AI-driven ones.
Organizations have realized something important. AI is not going to simplify their infrastructure. It is going to make it more complex. And that complexity needs structure. It needs guardrails. It needs consistency. All of that points straight to Platform Engineering.
This re:Invent made that truth visible. Platform Engineering was no sideshow. It was woven through the customer stories, vendor discussions and architectural sessions. It is now part of the fabric of how enterprises operate in the cloud.
Shimmy’s Take: AI Is the Future, but DevOps, Cloud Native and Platform Engineering Are the Present
Let me be clear. AI deserved the spotlight it received. The momentum is real and the innovations are coming fast. Agents, new models, new chips and new abstractions will reshape the industry.
But none of this will work in a vacuum.
AI depends on everything we have built over the past decade. It runs inside pipelines, containers, clusters and platforms. It needs observability. It needs automation. It needs governance and testing and security. It needs reliable deployment practices and scalable infrastructure. It relies on all the methods and systems that DevOps and cloud native introduced and refined.
And those systems don’t just magically appear. They are built and maintained by people who understand how to make large, complex environments operate at scale. Platform engineers, SREs, DevOps teams and cloud architects remain the backbone of modern IT.
If anything, AI makes them more important, not less.
So while the headlines shout AI, the real story happening in the halls and expo floor is this: the foundational disciplines of modern technology are still leading the way. They are the enablers. They are the stabilizers. They are the folks who make the magic possible.
It was good to see DevOps, cloud native and platform engineering so well represented at re:Invent this year. It tells me that the industry hasn’t forgotten the fundamentals. It tells me that the future we are rushing toward will still be grounded in the hard-won lessons of the past decade. And it tells me that the people doing the real work are still moving the ball forward.
AI may be hot, but the foundations are solid. And solid foundations win every time.
Amazon Web Services (AWS) today at its re:Invent 2025 conference extended its Kiro artificial intelligence (AI) tool to provide access to a set of agents that have been trained to trigger specific actions as they observe the way code is being created.
Adnan Ijaz, director of project management for Kiro at AWS, said these specialized agents, dubbed Kiro Powers, enable developers to invoke steering files that are extensions to the specifications-based approach that AWS has adopted to improve the quality of the code generated by an AI tool by narrowing the scope of the tasks that AI agents are allowed to perform.
The overall goal is to make AI agents more efficient by reducing the amount of “context rot” in a way that serves to better fine tune the outputs generated, he added. That approach ensures the AI agent doesn’t become unduly influenced by data that is outside the scope of the task it has been assigned that could result in a hallucination, he added.
AWS earlier this week also extended its AI portfolio to include a set of AI agents for optimizing DevOps workflows. AWS is now previewing an AI agent within its Kiro AI coding tool that autonomously works in the background to optimize tasks such as pull requests and provide feedback to developers. Additionally, AWS previewed an AWS Security Agent to review and test code, including conducting penetration testing, and an AWS DevOps Agent that will always be on call to help manage IT incidents.
The AI agents added to the Kiro AI coding tool are also designed to only load when needed to minimize costs. Trained using best practices developed by AWS, those agents are able to access hooks and Model Context Protocol (MCP) servers to trigger specific actions, including invoking third-party services from Datadog, Dynatrace, Postman and others, as code is being developed, said Ijaz.
For example, an AI agent might automatically invoke the Datadog monitoring service to identify an infrastructure issue that is adversely impacting the ability of the code generated by Kiro to be optimally run, he added.
In time, more specialized AI agents will be added to the AWS portfolio that will independently perform tasks in the background in real time as application developers build their code, noted Ijaz. Those capabilities in time will substantially reduce the amount of friction that software development teams currently encounter as they invoke multiple tools, he added.
Mitch Ashley, vice president and practice lead for software lifecycle engineering at Futurum Group, said AWS is providing agents the hooks they need to operate as real contributors to the development of software. When an agent can reason using telemetry data provided by, for example, Dynatrace or validate application programming interfaces (APIs) created using Postman tools, it can more fully participate in development workflows, he added.
Ultimately, AWS plans to expand the ecosystem of providers of DevOps platforms and tools that can be invoked by its AI agents. The only issue that remains to be seen now is how the role of the DevOps engineer will evolve as more of the capabilities provided by those tools are shifted further left across the software development lifecycle (SDLC).
Stack Overflow today made generally available an artificial intelligence (AI) tool that makes it possible to use natural language to search its repositories for code.
Company CTO and chief product officer Jody Bailey said AI Assist provides developers with a conversational search and discovery tool that enables them to more easily find relevant online content stored on the Stack Overflow and Stack Exchange sites.
After a summary is generated based on Stack Overflow’s ranking system, an AI agent embedded within AI Assist will also re-rank any answer provided for correctness and comprehensiveness to ensure verified code is surfaced with clear attributions, added Bailey.
Finally, if the search itself fails to yield any relevant community content, the AI agent is then instructed to answer the question using examples of code it finds outside of the Stack Overflow sites by invoking third-party large language models (LLMs). That hybrid approach, while prioritizing Stack Overflow content, ensures that a relevant answer to a question is always provided, said Bailey.
Many developers are, of course, relying on AI tools from OpenAI, Microsoft, Google and Anthropic to discover code they can reuse. The AI Assist tool created by Stack Overflow provides an alternative that generates more reliable content, including its original source, that makes use of the Stack Overflow ranking system to minimize any chance a hallucination will surface a snippet of code that actually doesn’t work or is deeply flawed, noted Bailey.
Going forward, Stack Overflow plans to integrate AI Assist via a Model Context Protocol (MCP) server with other Stack Overflow features and offerings, including its chat function and coding challenges, before adding extensions to integrated development environments (IDEs) and Discord servers. Longer term, AI Assist will also enable Stack Overflow to add additional education programs for developers, noted Bailey.
Since making AI Assist available in beta, Stack Overflow claims more than a quarter million IT professionals have already employed it.
It’s not clear how many developers are relying on AI to find and generate code, but as usage increases DevOps teams are starting to encounter more code that for one reason or another needs to be rejected. In some cases, it’s because a known vulnerability is discovered but just as often DevOps engineers are realizing that the overly verbose code generated by AI tools increases the amount of infrastructure required to run it. Over time, the code created by the AI tool will eventually significantly increase the total cost of IT.
The AI Assist tool developed by Stack Overflow helps minimize those issues by providing developers with examples of code that have already been vetted by their peers, noted Bailey.
There is little doubt that AI tools are making application developers more productive than ever. However, without the appropriate safeguards it’s also apparent that AI coding tools quickly become too much of a good thing. The challenge and the opportunity now is to find ways to apply much-needed guardrails to AI coding as early as possible in the software development lifecycle (SDLC).
Raj Sethi, senior vice president and go-to-market leader for software development lifecycle (SDLC) at GlobalLogic, pushes back on the narrative that generative AI will eliminate the need for junior developers. He argues that while AI can generate boilerplate code, tests and scaffolding, modern software delivery still depends on human judgment, critical thinking and a deep understanding of how systems are designed, built and evolved over time.
Sethi notes that recent layoffs and hiring slowdowns are less about AI replacing humans and more about organizations recalibrating after over-hiring and then scrambling to understand how AI actually fits into their productivity models. Despite headlines about “60–70% of code written by GenAI,” he points out that teams still need people to design prompts, review what AI produces, validate correctness, and reason about architecture, algorithms and performance. If organizations skip that layer of human oversight—especially at the junior level—they risk creating an unsustainable wave of technical debt.
He also challenges how junior talent is being prepared and evaluated. In an era where learning resources, courses and tools are democratized, Sethi urges aspiring developers to treat education as continuous, not transactional. Degrees alone aren’t enough; portfolios, open source contributions and visible problem-solving matter more than ever. He encourages students to focus on fundamentals—math, algorithms, linguistics, systems thinking—and to use AI as a collaborator rather than a crutch.
For DevOps and software delivery teams, the future isn’t about replacing junior engineers with AI, but about elevating their role. Junior developers will spend less time on repetitive plumbing and more time reviewing AI-generated output, refining specs, improving quality and learning how to orchestrate systems. In that world, the organizations that invest in growing their next generation of engineers—not just in buying tools—will be the ones that actually benefit from AI at scale.
staging-devopsy.kinsta.cloud 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.
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 five 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.
A major expansion of the self-propagating Shai-Hulud cyberattack aimed at popular node package managers (npms) used by JavaScript application developers is creating a major headache for DevSecOps teams around the globe.
Popular projects from Zapier, ENS Domains, PostHog, and Postman were affected. According to security researchers from Wiz, 27% of cloud and code environments are affected. The attack is accelerating across roughly 1,000 new repos every 30 minutes, they added.
Security researchers at JFrog, meanwhile, said the final payload, similar to the first Shai-Hulud attack, is a self-propagating worm that steals user secrets, uploads them to a public GitHub repository, and repacks itself with malware into all of the available npm packages.
Guy Korolevski, security researcher at JFrog, said it’s not clear what the ultimate objective is, but DevSecOps teams are being advised to replace all the tokens used to access code repositories.
The GitHub repositories affected are now harder to detect because they now have randomized names. Payload deployment and execution now also occurs across two-stages. Additionally, the infection limit is 100 npm packages per execution, which makes propagation faster when users with credentialed access to large numbers of packages are compromised.
A failure to authenticate to GitHub or npm with acquired credentials triggers a wipe of the HOME directory of the user, which will cause build failures in continuous integration/continuous deployment (CI/CD) platforms.
The one thing that is almost certain is that the Second Coming of Shai-Hulud is not the last of these types of attacks against software supply chains. DevSecOps teams, as a result, will need to revisit best security practices for software development. Arguably, existing processes are simply unsustainable from an application security perspective.
Mitch Ashley, vice president and practice lead for software lifecycle engineering at the Futurum Group, said Shai-Hulud exposes how unprotected the JavaScript supply chain has become. Modern software pipelines depend on ecosystems like npm, which means trust in dependencies must be treated as a core part of engineering practice, he added.
Secure sourcing, automated credential rotation, and continuous monitoring of developer components and pipelines are essential, noted Ashley. Shai-Hulud is a warning that software security efforts must focus on the development lifecycle, not just the production environment. Software supply chain security is not optional, he said.
The challenge, of course, is that in the age of artificial intelligence (AI) the pace at which code is being developed is exponentially increasing, which increases the number of repositories that need to be secured against attacks based on self-propagating worms.
In the meantime, however, looking for indicators of Shai-Hulud compromise is likely to require a significant amount of effort. Hopefully, there will soon be tools that help automate that process but in the short term at least DevSecOps engineers have their work cut out for them.
Endor Labs has developed a static application security testing (SAST) tool that leverages agentic artificial intelligence (AI) to more accurately identify vulnerabilities and other issues in code created in more than 40 programming languages.
Amod Gupta, vice president of product and design for Endor Labs, said the AI SAST tool the company develops combines a multi-modal static analysis engine, multiple AI agents and large language models (LLMs) to create the equivalent of a security engineer that analyzes code as it is developed.
The AI agents were built using a proprietary code application programming interface (API) that builds a model of how the code works in a way that provides additional context about the organization, added Gupta.
That approach enables the AI SAST tool to filter false positives by analyzing syntax, dataflow, and intent to reduce the number of false positives that SAST tools have historically generated by 92% on average, the company claims.
SAST AI will also review code for architectural and business logic flaws, such as broken access control and insecure design, and classify findings against the OWASP Top 10 security vulnerabilities framework. The AI agents will then surface recommendations to fix code based on the context they have been able to establish.
Finally, DevSecOps teams can also use natural-language prompts to teach SAST AI about specific practices and policies.
The SAST AI tool is arriving at a time when developers are relying on AI coding tools to generate more code than ever. That challenge is that AI coding tools typically invoke a general-purpose LLM that was trained using examples of code pulled from across the web that were often deeply flawed. The end result is that many of these tools are generating vulnerabilities in code that, on average, require 15 to 30 minutes each to triage.
Unfortunately, many application developers lack the cybersecurity expertise required to identify many of the vulnerabilities being generated. It’s then left to DevSecOps engineers to discover and remediate the rest before code is added to a production environment. Despite their best efforts, however, there are a lot more application developers than there are DevSecOps engineers, so more vulnerabilities are inevitably going to find their way into production environments.
The only way to break that cycle is to rely on AI to discover and help remediate the vulnerabilities being generated by AI coding tools, said Gupta. The issue is that organizations can not rely on the same LLM that was used to create code to also analyze that code for vulnerabilities, he added.
It’s probable that application security in the age of AI will get worse before it eventually gets better. Existing tools for analyzing code are often ignored by developers simply because they generate too many false positive alerts. As AI is incorporated into SAST tools, however, the overall level of noise generated by these tools should decline. In the meantime, DevOps teams should exercise more care. After all, if more of the code being created by AI tools winds up creating more security issues, the whole point of being able to build software faster becomes self-defeating.
AI agents are moving from novelty to necessity in software delivery—and with that shift, the developer’s role is changing. Emilio Salvador, vice president of strategy and developer relations for GitLab, explores what happens when every engineer works alongside a small “team” of agents: some personal, some shared across squads, and others assigned to specific lifecycle tasks. The takeaway: DevOps will look less like a linear pipeline and more like an orchestrated system where humans set intent and policy while agents execute, verify and report.
Salvador lays out a practical model for “AI guardians”—specialist agents that continuously check security, quality and compliance as code and configs move through the system. Above them sits a layer of “meta-agents” that coordinate work, escalate issues and interact just like team members (email/Slack/tickets), while keeping humans firmly in the loop for approvals and accountability. No one’s shipping enterprise software on autopilot.
Salvador also gets real about today’s bottlenecks. Most teams fixate on AI for code generation, but the real drag lives elsewhere: brittle CI/CD, slow security checks, noisy incidents and manual release chores. The guidance is to instrument AI across the entire SDLC—pipeline optimization, policy enforcement, test generation, SCA/secret scanning, rollback logic—not just at the editor prompt. Otherwise, you’ll write code faster only to hit the same wall faster.
On governance, the risk isn’t just “shadow AI” tools; it’s fragmented models and agent sprawl. What’s needed is a single source of truth for software assets and activity, plus clear policies for which agents can do what, where, and with which data. Expect multi-model strategies, layered verification (agents auditing agents) and stronger observability for both pipelines and AI behavior.
Finally, we touch modernization: AI will help refactor legacy apps and accelerate adaptation cycles. The horizon isn’t “more software,” it’s faster evolution—with DevOps teams measured by how intelligently they balance speed, safety and scale.