3243: How Atlassian CTO Turned Developer Joy Into a Performance Metric

Tech Talks Daily

Content provided by Neil C. Hughes. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Neil C. Hughes or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

14d ago 21:27

MP3•Episode home

What does it really mean to build software with joy? At the Team 25 event in Anaheim, I had the opportunity to sit down with Rajeev Rajan, CTO of Atlassian, to explore how one of the world’s most influential engineering organizations is redefining developer experience from the ground up.

Rajeev shares how developer joy became a guiding principle for Atlassian, not as a feel-good initiative but as a core driver of performance and innovation. Rather than focusing solely on velocity or throughput, Atlassian measured how productive developers felt in their codebases. That metric has now improved from 49 percent to 75 percent, thanks to a deliberate strategy built on three pillars: better tools, stronger engineering culture, and empowered teams.

We also dive into how this cultural shift helped accelerate the delivery of Rovo, Atlassian’s most ambitious AI product to date. Built-in record time, Rovo didn’t emerge from a top-down push but from an environment where engineers were supported to move fast without cutting corners. That includes training internal teams through AI School, rolling out dev agents, and prioritizing transparency over automation for automation’s sake.

Rajeev also reflects on how India has become a global engine for AI and software development and why Atlassian invests in its global teams with the same level of trust and ownership as any other location. From ship-it hackathons to hands-on leadership and a grounded view of where AI helps and where it still falls short, this conversation highlights what it takes to build modern engineering teams that are both productive and fulfilled.

So, if you’re building AI strategies, leading engineering teams, or rethinking how to scale innovation responsibly, what would change if developer happiness were your benchmark?

2089 episodes