The State of AI-Powered Software Development

Nearly all development teams now rely on AI coding assistants, and the productivity gains are real. Yet most organizations are producing AI-generated code faster than they can review, secure, or govern it. The result: time saved in code creation is subsumed into greater efforts elsewhere in testing, review, and issue management phases, often negating benefits of AI-assisted development.

We partnered with third-party research firm UserEvidence to survey 831 software engineers and DevOps professionals. The findings reveal a clear inflection point: The question is no longer if you use AI coding assistants; it's how well you manage the AI-generated code they produce and establish deliberate, automated mechanisms to scale subsequent stages across the pipeline.

Download the report now

Download the report now to learn

  • How AI is reshaping the pace, volume, and quality of software development
  • Why the productivity gains of AI development are offset by friction
  • How governance unlocks AI's full potential
  • The three security imperatives every AI-driven development team must address
The State of AI-Powered Software Development report cover

FAQ

  • What is "The State of AI-Powered Software Development"?

    It's a market research report produced by Black Duck in partnership with third-party research firm UserEvidence. In March 2026, we surveyed 831 software engineers and DevOps professionals to get a clear, data-driven picture of how AI coding assistants are reshaping development workflows—and where the real friction points lie. The result is a benchmarking resource that cuts through the hype and gives you the data your team needs to make informed decisions about AI adoption, governance, and security.

  • What does the report cover?

    The report covers four interconnected themes that define where AI-powered development stands today. You'll find data on productivity—including the fact that AI coding assistants save developers an average of eight hours per week—alongside an honest look at the bottlenecks offsetting those gains: manual review, security testing, and code rework. It also digs into the governance gap, which is one of the most critical findings: only 30% of teams have full governance in place for AI coding assistant adoption, yet those who do are 55% more likely to see a major improvement in efficiency. Security risk rounds out the picture, with 64% of teams expressing moderate or extreme concern about AI-generated code introducing vulnerabilities.

  • Who should read this report?

    If you're responsible for development velocity, application security, or engineering strategy at a medium- to large-size organization, this report is built for you. The survey respondents come from organizations with at least 500 employees—most with 2,000 or more—and more than half hold C-suite or senior leadership roles. Whether you're trying to make the case for AI governance investment, benchmark your team's adoption maturity, or understand the security implications of AI-generated code at scale, the data here speaks directly to your challenges.

  • Why does this research matter right now?

    Because the adoption curve has already moved past the question of whether to use AI coding assistants—97% of survey respondents are actively using them today. The question your organization needs to answer is how to scale that usage without creating security debt or governance oversights you can't see until it's too late. AI is generating code faster than most teams can review, secure, or govern it. This report gives you the industry data to understand exactly where that gap exists and what the organizations closing it are doing differently.

  • What will I be able to do with the findings after I download it?

    The report includes a deep profile of trending methods in AI-assisted development and concrete recommendations for building the governance and security infrastructure your AI-powered development program demands. You'll be able to benchmark your team's current AI adoption maturity against 831 of your peers, identify the specific workflow stages where AI-generated code is creating the most risk, and build a stronger internal business case for the tooling, processes, and oversight models that unlock AI's full efficiency potential—not just part of it.