Atlassian State of Developer Experience 2024 and 2025 (Filed under DevEx)
Atlassian State of Developer Experience 2024 and 2025 (Rubric #DevEx)
I used to. told Atlassian State of Developer Experience 2025"but this report they are." publish 2024 yearIt is interesting to see the trends and what has changed over the years.
🤖 AI and time saving In 2024 The majority of developers did not feel significant benefits from AI: 62The percentage of respondents said that artificial intelligence tools do not improve or only slightly improve their productivity. But even then, executives had high hopes for AI, considering it the key to improving productivity, but developers remained skeptical. In the report, 2025 In the past year, the situation has changed radically. Almost everyone. (99%) Developers now note that AI saves them time. 68Percentage of developers save more 10 A few hours a week thanks to AI tools. The wording of the questions has changed: 2024Respondents were asked broadly about the impact of AI on productivity. 2025We measured the specific hours saved. Free time developers in 2025 During the year, they are sent to more valuable work – improving the quality of the code, developing new features and writing documentation.
📉 Loss of time due to inefficiency Both reports capture an alarming amount of time lost by developers due to friction and inefficient processes. In 2024 It turns out that most engineers lose about a day a week to interference. 69Percentage of developers report loss 8 hours or more each week due to inefficiencies. This “lost day” included downtime, waiting for answers, dealing with code debts, searching for information, and other unproductive activities. In 2025 Despite saving time with AI, the picture worsened: 90Percentage of developers lose minimum 6 hours per week on organizational obstacles, with half of the (50%) lose 10 hours or more.
🧐 Productivity metrics and focus of effort Both studies emphasize that developer productivity is not limited to the amount of code written. In 2024 In the year, the authors noted that companies often measure performance through output – the number of tasks, commits, etc. – without tracking hidden losses due to inefficiencies. In fact, as the survey showed, the main barriers to productivity lie outside of direct code writing: bureaucracy, communication failures, documentation debt and infrastructure complexity. Leaders recognized the importance of the Developer Experience, but efforts to improve it were unsystematic and did not always hit the target. Report. 2025 I even more clearly showed this problem: directly coding developers spend only ~16% of their working time, the rest goes to meetings, search for information, setting up the environment, waiting and other related tasks.
❤️🔥 The gap between leaders and developers Both versions of the report point to an insecure gap between how leaders and rank-and-file engineers perceive the challenges of the Developer Experience. In 2024 year 44Percentage of developers believe that managers understand problems that reduce their effectiveness (technical debt, outdated processes, overloads)They interfere with productive work. Leaders themselves often underestimated the scale of the losses: for example, nearly half of tech executives believed that hiring could solve the problem. This reflects a divergence in perceptions of the root of the problems: developers pointed to the quality of processes, and managers to resources. In 2025 yearly 63Percentage of developers said that leaders do not understand their current challenges. Atlassian explained this by the fact that the management rushed to “monetize” the benefits of AI. (i.e. expected to accelerate development due to the time saved by AI)without removing old sources of friction. In the end, the leaders could decide that as developers began to work faster with AI, the problems were solved – while the developers themselves continued to stall in unsolved bottlenecks.
#AI #ML #PlatformEngineering #Software #Architecture #Processes #DevEx #Devops