Home
/
Podcast
/
You can’t blame AI for the code you ship | Freshworks’ Murali Swaminathan

You can’t blame AI for the code you ship | Freshworks’ Murali Swaminathan

By Murali Swaminathan
|
Blog_Comprehensive_DORA_Guide_2400x1256_5_b6d982aa4c

AI can write the code, but a human still answers for it once it ships. Freshworks CTO Murali Swaminathan built his engineering org’s approach around that idea after opening the gates to AI tools brought a wave of duplicate code, often 100 lines where 10 would do. This week on Dev Interrupted, he joins Andrew to explain how an AI product development life cycle brought discipline back, and why engineers now own their work end to end like product builders. Murali also shares why trust in AI features has to be earned through outcomes, like one customer deflecting at least 30% of its tickets after rolling out Freshworks AI agents.

Show Notes

  • Freshworks: freshworks.com Murali’s company, which makes AI-powered service software for IT, customer service and CRM.
  • Freshservice: Freshservice The Freshworks product that customers like Seagate moved their IT service management onto.
  • Freddy AI: Freddy AI The Freshworks AI agents built into its products.
  • Seagate’s 3-month, 30,000-person IT overhaul: Customer story The migration Murali describes, where AI agents now deflect more than 30% of tickets.
  • Freshworks Engineering Blog: Medium Posts from Freshworks engineers on architecture, infrastructure, AI and operating at scale.
  • Freshworks Developer Platform: developers.freshworks.com APIs and developer toolkits for building on Freshworks.
  • Connect with Murali: LinkedIn

Transcript 

(Disclaimer: may contain unintentionally confusing, inaccurate and/or amusing transcription errors)

[00:00:00] Andrew Zigler: Welcome to Dev Interrupted, brought to you by LinearB. I'm your host, Andrew Zigler, and if you've been listening to this show, then you know that we've been pulling back the, the hood on how to understand how agents are transforming enterprises, large companies, and, and actual teams that are using agents day to day to deliver work not only with, with engineers, but also to non-engineers as well.

[00:00:24] Andrew Zigler: Uh, there's a huge opportunity to make agentic interactions a more commonplace part of how everyone does their job and share the successes that we've seen many agentic companies, uh, see transform them- itself internally this year. There's opportunities to distribute that more broadly to folks, and I'm so excited to talk about this with today's guest, because joining me is Murali Swaminathan, and he's the CTO at Freshworks, and he's a member of the Forbes Technology Council.

[00:00:53] Andrew Zigler: Murali has a really impressive background at some of the largest and most recognizable companies, and, uh, he makes, uh, at [00:01:00] Freshworks, the customer service, IT experience, CRM software that thousands of companies run their front lines on. And it's all made possible by Freddy AI agents and innovations on their team, which we're gonna dive into today.

[00:01:14] Andrew Zigler: And here on the show, we've had some amazing opportunities to look at huge companies and how they've made these really bold bets on agentic assistance and, uh, providing these, uh, really premier customer experiences, and we're gonna look at how it's transformed Freshworks. And so Murali runs the global engineering and architecture teams behind all of this.

[00:01:33] Andrew Zigler: And, uh, Murali, we're really excited to have you here, so welcome to Dev Interrupted.

[00:01:38] Murali Swaminathan: Thank you, Andrew. That was a great introduction. Uh, I just wanna, uh, add a little more color to everything that you said.

[00:01:44] Murali Swaminathan: So it's a great time to be here, and great time, to be in the middle of all this technology disruption. Uh, another technology disruption, uh, as I would say it. I've spent 30-plus years in the industry building enterprise software, [00:02:00] uh, scalable, that's being used by many customers around the world. Prior to service, uh, prior to Freshworks, I spent some time with ServiceNow, uh, uh, running engineering for many of their products, and then, uh, came into Freshworks because I felt the opportunity here is, is much multi-fold because we are the AI-powered unified service operations platform, used by 75,000 customers and counting, uh, which is fast to deploy, intuitive to use, then enables every employee to be more productive. everything that we do, uh, offers powerful governance and scale without the, uh, the operational drag of legacy platforms. And then we have customers like Databricks, TaylorMade, McLaren, uh, who we are a partner of, uh, trust Freshservice to deliver quality employee service and then manage their technology operations efficiently.

[00:02:58] Murali Swaminathan: So I'm really, [00:03:00] uh, glad to be on your podcast. Thank you for inviting me over.

[00:03:03] Andrew Zigler: Thank you for providing all that, that extra context there too, because this is really what I'm trying, the, the nut I really wanna crack into today, because you face a really, a really big engineering challenge. You create the engineering world that is approachable by so many other businesses that, you know, they, they don't, they aren't a tech company.

[00:03:24] Andrew Zigler: They're a company that does something, and they have to plug into the rest of the world. They have to be able to leverage modern technology. That way they can have the, you know, the, the same kind of, um, edge on their competition that we're always seeking to leverage just as engineers with AI itself. And so you have this, like, dual mandate, and it's a double challenge we're gonna talk about today, where you're under this immense pressure to use AI internally to transform how Freshworks does Freshworks.

[00:03:52] Andrew Zigler: But then you also have to imagine the art of the possible, of how are all of these industries we serve and all of these types [00:04:00] of, uh, clients and very unique businesses which are completely different from each other, how do we create a platform that's unified, that's secure, that meets them where they need, and is ultimately, like, composable in their hands, flexible so that it meets them, uh, on demand, but then also, uh, backed by all of the engineering prowess and technology that Freshworks is bringing to make it stable and something you can build your business on?

[00:04:28] Andrew Zigler: That's a really, that's a really hard double challenge, uh, to kind of juggle. And when we've talked with leaders on the show that have been in that position, like, we've learned a lot of really interesting, uh, ways that they even think about, um, AI adoption and impact within their orgs. And one of the first things I would really love to, like, just, like, to get a sense of maybe the engineering org that you're a part of at Freshworks and how it operates and how it's changed this year, like so many engineering orgs, you know, [00:05:00] have.

[00:05:00] Murali Swaminathan: Yes, you are, uh, Andrew, you have absolutely, uh, cracked it there. I think, uh, that's exactly the chal- uh, challenge that we are in right now. It's great to have sort of 1,000 customers and counting and more. That means we have the responsibility to support those customers with their business needs and solve their business problems, also innovate in parallel, and then leverage the power of AI to deliver more f- to them so that they can run their businesses efficiently. so, uh, so from an engineering problem perspective, yes, our core engineering foundation is key. Like, what are we doing? We have to do it better. And then we have to leverage AI in many ways, the way we are building it, the way we are, deploying our, uh, our features, the way we are enabling our customers through features.

[00:05:46] Murali Swaminathan: We don't want it to be a bolt-on, so we want it to be where customers are seeing it as part of their business flows, and it's implicit in many ways, right? It doesn't have to be explicit. Um, so that's why it's important for us to not just [00:06:00] bring technology into the product, but find a way to bring it into their business process and make it easy for them to adapt it. and so that's one thing that we have to think from a product engineering perspective, uh, when we are trying to solve this problem for our customers.

[00:06:15] Andrew Zigler: Yeah, absolutely. Because, you know, your customers, they, they're not just gonna take AI as, like, a bludgeon to everything. It... Y- I like how you said, it's, like, implicit and explicit in so many of the interactions that they then start to do. Uh, because that's really the new normal that we have to settle those kinds of customers into.

[00:06:32] Andrew Zigler: Uh, this is the way that we'd work now, this is the way you're gonna get the most out of our platform, out of what you're doing. This is what your competitors are doing. Getting, getting other people in this mindset, just even outside of the tech world, is a challenge in and of itself. And, you know, all of that's made possible by having really clear, I think, language, an internal process about how you think about, like, from beginning to end within your SDLC, how you leverage the tools you do, what, um, AI agents that you [00:07:00] use, you know, how you run your, your code.

[00:07:01] Andrew Zigler: H- uh, what are your bottlenecks that pop up now in this new world? And then critically, how do you as an engineering leader rise to that challenge to fix that bottleneck? So, like, a big obvious bottleneck that's, like, slammed a lot of teams this year, are bottlenecks around, like, review, right? It can also be things for teams around having the right kinds of boundaries and places for agents to get the right context.

[00:07:27] Andrew Zigler: And I'm curious, like, with the s- the scope that, that... For the things that y'all are building at Freshworks, like, what emerged as early bottlenecks, and what were some ways that y'all as a team started to get past them so you could continue to deliver value?

[00:07:40] Murali Swaminathan: This was easy, right? When the, when the whole, we got an influx of all these coding tools and, uh, uh, AI, uh, ways of working, uh, it was easy to just pick up any tool and work with it. But then, uh, it's... Then we had this, plethora of tools that everybody was using. Everybody was using it, everybody was using white coding and generating code, and generating a lot of [00:08:00] code. uh, two people writing a similar, uh, code that, that, that, that... Lot of duplicacy there. Lots of code. Anything could have been done in 10 lines is now being done in 100 lines because the,

[00:08:11] Andrew Zigler: Right

[00:08:12] Murali Swaminathan: is much... The code that the AI tools generate is much more than what a human would write. And then it gets into the next stage of, oh, who's gonna review all that code, and who's gonna test all that code? Um, so we went through the same cy- uh, same cycle where, uh, when we introduced it, I would say like more than 12 months back, it was all like, "Oh, everybody go use it. Let's try it." And we... That's how we opened the gates. But then a few months we realized that everybody was using it, but then it, it was so hard for us to say, yeah, just because you produce a lot of code doesn't mean it's the right code that's helping us ship products faster or whatnot. So we had to streamline it, and so we came up with this whole AIPDLC, AI product development life cycle, to streamline how we do things. How do I build a little more discipline into how you build code? Because just because [00:09:00] you're using AI tools doesn't change the way you're building things. You still have to follow a certain software development life cycle, because you are accountable to your customers the software that you ship.

[00:09:09] Murali Swaminathan: I cannot blame AI for the software, the code that was shipped, right? End of the day, the human is responsible, the company is responsible. So we had to put those practices in place. So we did a lot of stress into how we build, what we build. So it's not just the code. Code is just a piece of the thing. I think it's all about the thinking that goes into building that code, and then after the code is built, do you have the right, uh, automation in place to test the code, validate the code, um, review the code, and then deploy the code.

[00:09:38] Murali Swaminathan: So, uh, it is definitely a journey we are in. We are still working through all the kinks, but that's been fascinating to see how we are transforming from just generating code to, to building code that really works.

[00:09:49] Andrew Zigler: Yeah. You're describing the journey so, the, the landmarks so vividly and clearly, and they, they line up so, so well to what we hear from other leaders as well [00:10:00] about how first it's about, like, get a lot of tools. Let's, let's try everything. Let's just get at the stick. Let's see what's gonna work for us. And then you get to this stage of code pro- proliferation, of we're getting this verbosity that we weren't doing, uh, before.

[00:10:13] Andrew Zigler: We're getting code that's harder to maintain. Then you get runaway costs. As an industry, we went through the whole tokenmaxxing and token minimizing and, and everything in between. And, and, and, and really it's just been about trying to understand the ROI. You know, we, we may all made this bold bet a year ago to, like, pick up these tools and change the way we work, and for many teams it's paying off.

[00:10:35] Andrew Zigler: And like, teams are just doing so much more, um, and achieving really amazing stuff. And because of that, now we have to look at, like, how do we optimize that for the future? What are the new ways that we, like, you know, think about our process? Y'all approach this in a, in a very, like, distinct way of, acknowledging that the SDLC and the product development world and, you know, code and [00:11:00] owning code and owning product, like, these ideas smashed together.

[00:11:04] Andrew Zigler: And maybe y'all experience that, but what I've learned from talking with a lot of, like, product leaders on the show is that they're more engineering-driven than ever. They're driving more tickets, more stuff across the line, and they're, uh, team- people who would typically operate in, like, a team of three with, like, an engineering lead and a dev, like, they're, they're now encapsulated almost as one.

[00:11:25] Andrew Zigler: And it's not that there's less people there, but then maybe the o- those other two people are also specialized. They can all three come up with a product. They can all three, uh, get the stuff, you know, developed and then out the door, and then they can all three turn around the marketing and explain what they need to do with it.

[00:11:40] Andrew Zigler: So you get this, like, really change in skills. Um, what have been, like, skill... What has skill growth been like at, at, at, at Freshworks for your team? Like, what have been, like, the new, uh, norms for engineers day to day as, like, they work in this new kind of agentic world?

[00:11:55] Murali Swaminathan: Yes, I think it's definitely all of this that you mentioned is exactly the, what's [00:12:00] going on in our minds as well, uh, while we are building this stuff. And then the naturally it's the, uh, we are no longer expecting the engineering to just code, right? We are expecting them to do design thinking, architecture.

[00:12:11] Murali Swaminathan: We are as- expecting them to do a lot more experimentation. We are experimenting to build a lot more prototypes. We are expecting them to think about, think like a product manager, think like a designer, because all of that can be done, right? It's no longer that I'm a backend engineer or a frontend engineer or a, or I only am an architect, right?

[00:12:27] Murali Swaminathan: Those, those lines are blurring up right now.

[00:12:30] Andrew Zigler: Right

[00:12:30] Murali Swaminathan: longer... So the, an engineer who knows the product should be able to do a lot more because coding should not be the bottleneck anymore, because they can apply the knowledge of the product to build better products. Uh, that means that they can double up as a product manager, because if they know the domain, they know the product, they know as good as the product manager.

[00:12:49] Murali Swaminathan: They shouldn't have to wait for a product manager. So that's exactly what we are trying to, encourage our engineers to be a lot more, uh, I would say, um, have that product builder mindset, uh, [00:13:00] where they're thinking about, uh, building the product end to end. It doesn't mean they're taking the, the entire product end to end, but whatever they own, own it end to end,

[00:13:08] Andrew Zigler: Yeah

[00:13:09] Murali Swaminathan: don't rely on a tester to, to test your product. Don't rely on a security person to s- to, to make sure that your product, your code is secure. A lot of the stuff you can do it yourself, and we're putting those checks in place. That's why we have, we have, we have created skills and, um, and reusable things for, for our engineers to be guided while they're building, and then we're putting those checks in place as part of review and all of that.

[00:13:33] Murali Swaminathan: That way, if they miss something, the reviewer kind of points it out, uh, right? And if it's, if it misses some of that stuff, there's a check somewhere. So there's always a check in the system at some point, uh, for them to catch those things and, and learn from that experience and do it better next time. It's not like they, we want, don't want to repeat the same mistakes over and over again. So we are giving

[00:13:54] Andrew Zigler: Yes

[00:13:54] Murali Swaminathan: guidance to make sure that, yeah, do it right the next time, that way, and then get it [00:14:00] better and make it better.

[00:14:01] Andrew Zigler: Yeah, iterate on the system. That becomes... Everyone has to become a systems thinker. Those become like the ones, the leaders, the, the, the most productive folks that stand out are the systems thinkers who can take the problem, break it down into pieces, compose them into loops, find the collaborators, the other DRIs, the people that need to be a part of it, but also too identifying the domain experts within their company who, who, who would make...

[00:14:26] Andrew Zigler: I can set up this loop, but who's gonna make this loop perfect? Who's gonna iterate with it and catch every problem and really make this something that we can carry forward? Because that's what then s- sets the difference between a disposable practice and a durable one. Because otherwise you end up in this phenomenon which you so, so, so succinctly hit on that I loved, is that You know, it's been over a year of, like, teams adopting these tools and using them, and what you have are a bunch of individually highly agentic folks that are scattered around or maybe it's, like, one person on a team and then [00:15:00] their team is super agentic.

[00:15:01] Andrew Zigler: Or, someone is... There's, like, a few pockets of people, and they've all three or four redeveloped, rebuilt basically the same way of working or have created a complete unique castle, right? About, like, how they do their everything, and because of that it's like, you know, wasted work, it's duplicity. There's not an interoperability, but then it, it wasn't designed in a team uplifting way, in a way that's gonna make it as, like, a durable, um, process we have to carry forward.

[00:15:28] Andrew Zigler: So it's also, too, about, like, identifying when those pockets happen of, like, okay, what can we learn to make the whole team, the whole process, um, more agentic? And then bit by bit it becomes a durable part of your SDLC, your, your AIPDLC, however you want to envision how something comes from idea to, uh, to execution.

[00:15:50] Andrew Zigler: And, you know, this has been a, like, a really great view into how, like, your own engineering org has transformed during this really, like, rapid time of, like, innovation. And during that [00:16:00] same time, and, you know, we talked about this at the beginning of, of our chat here. It, like, this transformation is also coming for all of these other industries, is also heavily impacting all of them right now.

[00:16:11] Andrew Zigler: So from your perspective when you're creating tools in a platform that's consumed by users who are not engineers, you know, let's talk about how you think about adoption, how you think about getting them, um, in the right mindset to, like, be successful in a agentic world and build pro- products that are useful for them.

[00:16:29] Andrew Zigler: So, like, I, I'm curious about, like, how you get trust and keep trust, and how you think about trust, because I think trust is completely different when you build products for a non-tech world. us techies are, are a little more forgiving and, uh, you know, to each other and to our out- status pages and whatnot, but when, uh, you know, a, a major, like, uh, provider for, like, how a, a business stays open is impacted by something or dramatically changes, these pains are real.

[00:16:57] Andrew Zigler: And so, you know, having trust is so important. I, [00:17:00] I'm, I'm curious to know how you think about that.

[00:17:02] Murali Swaminathan: Yeah, that's a great point. Uh, I think just because, yeah, engineers definitely are more forgiving and you wanna, you wanna, you wanna be and stay on top of technology and, uh, uh, and leverage the best technology and

[00:17:13] Andrew Zigler: It could be my platform that goes down tomorrow. I can't, I can't blow it up like every wor- or it could be me, you know, we, we all are a little traumatized by the nines, right? And so, uh, other, other, other businesses are not, they're not

[00:17:26] Murali Swaminathan: Exactly. And then developers have this, "It works on my system," right? It's always that, that phrase you see is, "Oh, it works for me." Right? When you, but when you push your code into the git and when you test it and deploy it with other code, you realize that it breaks in integration. When you, when you test with complex use cases, it breaks.

[00:17:41] Murali Swaminathan: So that's where the trust is important, is like you're, you're measuring it based on the outcomes you're delivering. is it, uh, the customer use case, right? Our customers, we serve a lot of industries, some tech, non-tech, right? So, and the users of our system are, again, different kinds of employees.

[00:17:56] Murali Swaminathan: Some, some technology for some in other [00:18:00] departments who are using technology, but they're not the most technology savvy. So you, you are delivering, uh, functionality for them to use the product, and you trust if, if the system is helping them get their job done, they're gonna trust you. If the system is not help with their jobs, gonna start saying, "Okay, I'm not gonna use this product."

[00:18:21] Murali Swaminathan: Right? They'll find reasons to not use the product. So that's why it's important f- for us to gain that trust and, and it has to be earned, right? It cannot be just granted and said, "Okay, I'm going to, uh, we want to let you trust the system." They have to tell you, and it's up to the, the customer satisfaction, our employee experience scores, I think that's where determines whether the system is working or not working. And, uh, and that's how we have to, uh, when you s- build software, you have to think about, uh, is it, um, incorporating AI into the workflow, it's not that it's... Just, just putting AI is not gonna help them trust the system. They have to look at, okay, is the [00:19:00] outcome that they're trying to get out of leveraging AI, is it, are they getting the same outcome or a better outcome? And that's how the trust is gonna build.

[00:19:08] Andrew Zigler: Exactly. And bringing them to the table, keeping them at the table is a completely different operation when it, in terms of trust. You know, you are talking about a very different audience, and I, I think also, too, something that's different is how they, um, the stickiness and the adoption of tools.

[00:19:24] Andrew Zigler: Because really realistically, like if a business owner can, can get their business scaffolded and built up on top of a system that they can rely on, they didn't go into business of opening whatever store or doing what they're doing so that they could sit on top of their tech all day and make it perfect.

[00:19:40] Andrew Zigler: Maybe, maybe a really nerdy one did, but the most of them don't. They wanna set it and forget it. So there's like a little bit of like a push and a pull where you wanna put the most innovative and the most like exciting, the newest stuff right at their fingertips, but you also have to make sure that like what they're used to and what they're expecting is still delivered.

[00:19:59] Andrew Zigler: And this [00:20:00] requires, I think, stepping customers, especially in the last year, through a lot of little steps of adoption changes. Let's like slightly, you know, wiggle you this way, wiggle you that way until we- we're all kind of like, uh, you're... The customers are, are, are understanding what the tools are sort of using for, and they have the intuition to adopt them and be sticky with them.

[00:20:19] Andrew Zigler: And you're able to get that really good feedback now about the tools they are using and be able to make them better and more effective. And I'm, I'm curious, like in that journey, like what about adoption in the AI world and, and adding AI features to your platform has surprised you in, you know, in a, in, in any kind of direction?

[00:20:39] Andrew Zigler: Like, uh, is there, uh, things or, or parts of it that really stood out as part of like that transformation?

[00:20:45] Murali Swaminathan: Definitely yes. Uh, uh, just because we built a feature in the product doesn't mean that a customer is gonna adopt it, right?

[00:20:51] Andrew Zigler: Right

[00:20:52] Murali Swaminathan: and then, we have to ask the reasons for why is the customer trying to use that feature? Because they are trying to deliver outcomes. Uh, it's, and, [00:21:00] and it's all about... So there is adoption, there's impact, and outcomes, right?

[00:21:04] Murali Swaminathan: So, uh, adoption, something that we all measure to make sure that, okay, yes, uh, are they using the product and making sure that they're able to discover the product? Are they able to... We look at, uh, usage, we look at some of those metrics, uh, we look at token usage, all of that. But end of the day, a customer doesn't care about any of those.

[00:21:21] Murali Swaminathan: The customer care about outcomes that they want. Do they want... Is it helping them do their work faster? Is it better quality? Is it reliable? Is it trustworthy? Right? So, so, uh, let me give you an example of one customer, of ours, uh, Seagate. Seagate is in the whole, disk drive business, and they became a customer, uh, what, a year or so back, and they migrated 30,000 employees from their existing system to our Freshworks Freshservice product 3 months.

[00:21:52] Andrew Zigler: Wow

[00:21:52] Murali Swaminathan: so they took a big, uh, bet on us to get it done. But the whole intent was, how is it gonna [00:22:00] be better than the system they had, and is it, are they able to, improve the satisfaction for their employees, right? And, and what we are seeing is, uh, once they started deploying our AI agents, we see that at least 30% of the tickets are being deflected. Their first contact resolution has improved. and that's the kind of operational metrics that we want our customers to start measuring to say, "Oh, I did change the tool. I, I put a lot of effort into changing my tool set and re-educating my employees to work with the new tool." But if it doesn't deliver impact, the change, the cost of change is not, is not going to be justifiable, right?

[00:22:39] Murali Swaminathan: So that's why I think we need, uh, the adoption is important, but then bigger than that, the impact is the most important one that people have to look at when you're, when you're rolling out software.

[00:22:50] Andrew Zigler: Yeah, you have people to illustrate it, m- make it, make it really obvious and, and, and also to just make it self-instructive. Like, the... But [00:23:00] also I really, what I love about the story with Seagate is that that's a huge shift. That's a large amount of seats, and w- that is a really big bet on where the problems are and what can make it better.

[00:23:12] Andrew Zigler: And ultimately, it's like having the right kinds of systems that can support those big bets and be able to be that, like, landing place where a company can make that change and then experience the transformation that internal transformation that they're trying to get. It's like, I, I think teams are willing to make big bets right now, especially, uh, with agentically enabled tools, to out-transform, um, their competitors, and that becomes like the real engineering challenge is, is bringing those people to the table.

[00:23:43] Andrew Zigler: And, you know, as I, as I listen to you talk about it and, it, what I really think is must be the truth is like, with so much of your world that you build must rise out of user stories and getting super close to how all of these different industries and, and companies use your [00:24:00] product, hearing their pain, live on calls, surfacing them up, turning them into real things that can then be creative.

[00:24:06] Andrew Zigler: There's a true potential in how the tools exist and how you get feedback from your so many different customers to truly create a unified platform that can meet their needs. But in order for that to happen, they have to be using the tools. Because you can't just build the tool. You have to get everyone enabled, everyone excited about it.

[00:24:25] Andrew Zigler: Maybe this w- person is g- has it behind a feature flag, and don't even get me started on how feature flags make all of this way more complicated. And so, and it's like then you start thinking about how you market that, and really what happens is your, your user base and how you talk about your product becomes a whole bunch of different segments of like these are the really, really AI-enabled, the super agentically enabled cohort of our customers.

[00:24:48] Andrew Zigler: And, and you'd be able to like learn new things, uh, from them versus maybe how like, uh, newcomers are starting to adopt things. But even they have their valuable user stories you dig out to make your experience [00:25:00] better. And I, I'm, I'm curious like how you think about your role as a CTO and overseeing that kind of technology transformation.

[00:25:08] Andrew Zigler: What things have changed for you in the last year in your perspective? And, you know, do you have any other advice for, for folks in your same kind of position?

[00:25:17] Murali Swaminathan: Yeah, definitely our jobs have become a lot more challenging. I think, uh, uh, again, it's no longer steady state anymore, right? So every day there is some other company that's disrupting, uh, what you're trying to do, and then the technology is getting better. Uh, the, the barrier to entry is becoming lower, so naturally you have to continuously innovate, differentiate, uh, keep up the custom- keep up with the customers.

[00:25:38] Murali Swaminathan: That's become a bigger thing for us. So it's not that, okay, yeah, it's uh, I'm just not focusing just on technology, right? So we are thinking about how do we bring everybody along? How do we bring our, uh, the, the change the ways of working? How do we bring our engineers along? How do we bring our customers along? Um, so a lot of these things are, uh, it's shifting [00:26:00] to the, the cultural shift that needs to happen on how we build software, how we

[00:26:04] Andrew Zigler: Yeah

[00:26:05] Murali Swaminathan: uh, how fast we ship. There used to be a time we all used to say, "I'm gonna ship it in three months." And now everybody's like, "Okay, what can you push, uh, at the end of the week?"

[00:26:13] Murali Swaminathan: Right? So

[00:26:14] Andrew Zigler: Yeah.

[00:26:15] Murali Swaminathan: the, the, the appetite for, for new things is, is a lot more, right? People are expecting change to happen much quickly, right? Nobody's waiting for a yearly cycle to push software. So a lot of the expectations have changed so much, right? So it's all about, how do we... It's not about deploying more AI or s- or deploying the best technology there, but what technology will make the organization meaningfully better?

[00:26:39] Murali Swaminathan: I think that, or what solutions can you bring to the problems that will make the, the companies, um, operate at a much higher efficiency is where my, my thought process is changing. And that's how all the engineering leaders are thinking about it because it's not about just building the software because that seems to be the easiest part of it. It's about how do we organize yourself and how do you make sure that [00:27:00] you are improving the efficiency of your developers, changing the perception of how do you innovate, at the same time not be reckless, but l- but be more disciplined how you, you build and ship make sure that your employees, the, the quality and the, um, I would say the, the scale and other performance metrics are not compromised.

[00:27:21] Andrew Zigler: Yeah, absolutely. You aptly called out how the pressure to ship more often and constantly has compressed and there's definitely more rapid cycles and, uh, i- in, in this whole process, like we're dealing with the bottlenecks that make those fast cycles possible, and those bottlenecks are not solved. So then we learn about the real state of production in production.

[00:27:47] Andrew Zigler: Observability becomes really important. Like the way that we think about how do we maintain this, make it durable completely changes. I loved how you also called out that like the, the timelines, uh, like shrink so [00:28:00] everyone's involvement gets a, like a lot more hands-on and engineers just have to have a lot more context about the problems that they're solving because before it was, you know, maybe they get the nice ticket, they have their sprint, they're gonna work on this part.

[00:28:14] Andrew Zigler: Eventually we're gonna add all of the pieces to this jigsaw puzzle and it's gonna be solved. But now they have a jigsaw sol- solving machine that they can just like fire on demand. But if they don't know what the picture needs to look like, they're not gonna be able to do it. And so now the challenge is cultural, uh, which you, which you pointed out and it's about getting people aligned around how do we work, what's our expectations and, uh, how do we communicate clearly?

[00:28:39] Andrew Zigler: Where is communication breaking down? Those are often creating then those bottlenecks that show up as code that doesn't need to exist or something that should have been a refactor or 1000 plus lines when it could have been 10. And so like that's where, that's where those things start to pop up from.

[00:28:57] Andrew Zigler: And so, you know, since AI makes [00:29:00] code easy to produce, that's not the problem anymore. What becomes valuable now in an engineer?

[00:29:06] Murali Swaminathan: Yeah, exactly. So I think these are all, um, are all great skills for engineers to develop because I think they need to think about, like we talked about systemic thinking, we talked

[00:29:16] Andrew Zigler: Yeah

[00:29:17] Murali Swaminathan: uh, there's no longer tribal knowledge. A lot of the knowledge now sits in the context that's built when you build new code, right?

[00:29:24] Andrew Zigler: Right

[00:29:25] Murali Swaminathan: so the boundaries are kind of, uh, are... There is not much things about, yes, there's, there's not much differentiation between a senior person and a junior. It's all about how you think. and, uh, a lot of the, the stuff is not about, uh, okay, only this person knows, or experienced people know about something.

[00:29:42] Murali Swaminathan: And so a lot of the knowledge is, is being transferred into the context that's being built while you're building new code, and we need to take advantage of all of that while, while applying, taking that context to build newer features, newer products.

[00:29:56] Andrew Zigler: Does, does Freshworks take like a, uh, like a forward [00:30:00] deployed engineering approach? Does it bring engineers right into customer conversations so they can hear and get close to customer pain? I'm curious how you, um, make sure that that context about like how to deliver that impact and those outcomes gets to the engineer since now that seems to be the true now cultural bottleneck.

[00:30:17] Murali Swaminathan: That's right. I think, so we have 75,000 customers and growing, so it's very hard for us to... And we have customers of all sizes, right? We have customers who are, who are digital customers we don't even see. They just pay through a credit card, they use the

[00:30:30] Andrew Zigler: Right

[00:30:31] Murali Swaminathan: there are these high-value customers who have, um, uh, customer service support people engaging with them, services people engaging with them. They, they have a CSM, they have an account manager. So we have variety of customers. So, uh, our ethos is all about intuitive to use, easy to deploy, all of that. So most of our stuff, there is no touch from engineers to make for that. But there are complex customers, right? The, the higher the [00:31:00] revenue they are generating for us, naturally there is, there are complex systems that need to be demystified, and we need to work with them to help them solve those problems.

[00:31:09] Murali Swaminathan: So we engage engineers in those cases. Uh, and then that's the more helping them su- be successful. And then once in a while, there's always these escalations that come up, Software bugs and stuff like that. And those are times where if a customer support, a frontline support engineer is not able to solve an issue, we, we engage a developer to work with the, the customer. And we also create these opportunities for, uh, customers to come and meet us as part of our, uh, conferences that we do. And then that way we have a dialogue with the customer. That way if customers have something that they can, they can, we can guide them, uh, through engineering, but sometimes they wanna talk to engineering because we supposedly are the truth-tellers, right?

[00:31:51] Murali Swaminathan: So it's very hard for engineers to say something that is not there, to say it's there, Uh, so customers want to talk to engineers, to get the right facts. Um, so that's how we [00:32:00] keep our engineers engaged. Uh, uh, but it's not like every, every customer gets an engineering engagement. Uh, we pick and choose which customers we engage with.

[00:32:08] Andrew Zigler: Yeah, ma- it makes perfect sense. And just like how what we've talked about in our conversation, you have to think of this really wide scope, this really wide surface area. And in addition to all of the different industries and scopes and sizes of the businesses, there's also different levels of investment in each other that is obviously gonna bring an engineer closer or further away from whatever's going on in their world.

[00:32:31] Andrew Zigler: But no matter what, there's all these different lanes by which feedback trickles back to the engineering org, by which engineers get closer to customers that are having really complex or really interesting problems, and then this becomes the new place where the engineers can provide, like, the utmost value.

[00:32:48] Andrew Zigler: This isn't something you can just pull out of an LLM or pivot to Claude and ask. You need a domain expert with a system mind who's, uh, understands how this stuff is built, a code owner [00:33:00] who maybe runs the fleet of agents and run, and reviews their code, uh, that can get closer to the problem and understand, um, how to translate that back through prompts and context into the engineering reality.

[00:33:14] Andrew Zigler: And so that expression of, of customer pain into code is just like a new dance I think that engineers are learning to do. And,

[00:33:21] Murali Swaminathan: Exactly

[00:33:22] Andrew Zigler: long as there's ways for them to get close enough to start doing it, I think they can build the muscle. So that's really exciting to hear about Freshworks, that it sounds really, um, it sounds like a really great way to, uh, keep engineers kind of, like, close to how customers are using the product.

[00:33:37] Andrew Zigler: And, I, I just am so impressed, Murali, by, the surface area by which you cover every day in your role, and it's very rare that I speak with somebody who, um, operates such at a high level engineering context, but then also has to think about how non-technical, non-engineering users at scale and at all across the world are gonna think about and [00:34:00] adopt and use the technology that your organization's driving.

[00:34:03] Andrew Zigler: And that's a really big challenge. And so it's been really fascinating to dig into your head and think about some of the more emerging topics around your own engineering org, but then also how you guide your customers through AI adoption. It's been really, really informative, and I think it really speaks to the engineering practices there.

[00:34:20] Andrew Zigler: And just for our listeners, where can they go to, you know, maybe keep up with you or learn more about what you or your engineering team is doing at Freshworks?

[00:34:28] Murali Swaminathan: Thank you for, uh, uh, kind of giving me the opportunity to be here. Uh, you can definitely find us, find more about Freshworks on freshworks.com. And if you really wanna know how our engineers build and how we think, we have a Freshworks engineering blogs on Medium. Uh, we share deep dives on our architecture, infra, AI, and operating at scale. We also have developer Freshworks, developer.freshworks.com, um, where you can find all the developer-facing tools that we share for our [00:35:00] customers' APIs and developer toolkits and all that. And you can also always find us on LinkedIn, Freshworks, or you can Google me on, uh, LinkedIn and then, uh, you'll get information about us.

[00:35:10] Andrew Zigler: Amazing. We'll, we'll be sure to include those notes or those links in the show notes, and, uh, I'll include links to your socials as well because, uh, to our listeners, you know, if you've made it this far, then you clearly loved our episode. You clearly loved what we dove into today. And so wherever you're listening to it, be sure to give us a like or a comment, but also please come find Murali and I on socials.

[00:35:31] Andrew Zigler: We're both on LinkedIn. I'm gonna be posting this episode there along with a newsletter on LinearB, and we would love to hear your thoughts about our discussion today, maybe your own perspectives. Uh, and, uh, if you have a, a bone to pick about something we brought up today, then that's the perfect place to do it.

[00:35:45] Andrew Zigler: And so we'll see you online, and thanks again for listening. Murali, thanks again for coming on Dev Interrupted. It was a pleasure to host you

[00:35:53] Murali Swaminathan: Thank you, Andrew. Thanks for the opportunity.

Your next listen