Inside Amazon's AI video generator | Kabir Bedi

24 Jun 2025 · 49 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Podcast Notes: Dev Interrupted - Episode: Inside Amazon's AI Video Generator with Kabir Bedi

Episode Overview In this episode, hosts Andrew Zigler and Ben Lloyd Pearson interview Kabir Bedi, Head of Product for Image and Video Generation at Amazon Ads. They discuss the advancements in generative AI specifically for video advertising, Amazon's culture of innovation, and the implications for businesses of all sizes.

Key Themes and Discussions

  1. Democratization of Video Advertising
  2. Concept: Amazon's Video Generator aims to make video advertising accessible to all businesses, from small mom-and-pop shops to large enterprises.
  3. Functionality: The tool simplifies video creation, enabling users to turn a single click into professional video content.
  1. Engineering Culture and Customer Obsession
  2. Customer Feedback: Kabir emphasizes the significance of having engineering and science teams engage directly with customers to gather feedback. This practice has informed product development and improvements.
  3. Iterative Development: The team adopts a culture of experimentation, testing new models rapidly to enhance the product continuously.
  1. Innovations in Video Generation
  2. Product Use Cases: The Video Generator allows brands to showcase products in realistic lifestyle settings, moving beyond simple product displays to multi-scene advertisements.
  3. Key Features: New capabilities include uploading images and videos to create ads, allowing for a more comprehensive presentation of products.
  1. Challenges in AI Development
  2. Rapid Innovation: The fast-paced nature of AI technology requires teams to stay agile and adapt quickly to new advancements.
  3. User Experience: The tool is designed to require minimal input from the user, which is crucial for brands inexperienced with video advertising.
  1. Skill Development for Engineers
  2. Learn and Be Curious: Kabir highlights the importance of fostering a culture of continuous learning among engineering teams, encouraging them to dive into AI tools and share insights.
  3. Collaborative Environment: Kabir suggests that involving all team members in customer conversations and experimentation can enhance morale and innovation.
  1. Future of AI in Software Development
  2. Insight on Industry Trends: The podcast discusses broader themes in AI adoption across organizations, including the importance of reducing barriers to entry for users and ensuring the technology serves real-world needs.

Key Takeaways

  • Customer-Centric Innovation: Bringing engineering teams closer to customer interactions leads to better product development and satisfaction.
  • Emphasis on Experimentation: A culture that encourages regular experimentation fosters innovation and adaptability in rapidly changing tech landscapes.
  • Simplifying User Interaction: Building tools that minimize user input can enhance accessibility, especially for small businesses that may lack technical expertise.
  • Continuous Learning: Encouraging a growth mindset within engineering teams is essential for navigating the evolving landscape of AI and software development.

Episode Links

  • [Amazon Ads Blog](https://advertising.amazon.com/resources/whats-new)
  • [About Amazon Blog](https://www.aboutamazon.com/news)
  • [Kabir Bedi LinkedIn](https://www.linkedin.com/in/kabir-s-bedi/)
  • [DevEx Guide to AI-Driven Software Development](https://linearb.io/resources/devex-guide-ai-driven-software-development)

Hosts

  • [Ben Lloyd Pearson on LinkedIn](https://www.linkedin.com/in/benlloydpearson/)
  • [Andrew Zigler on LinkedIn](https://www.linkedin.com/in/andrewzigler/)

Conclusion The discussion with Kabir Bedi sheds light on how generative AI is reshaping the landscape of video advertising and the importance of engineering culture in fostering innovation. This episode serves as a valuable resource for those interested in the intersection of AI technology and software development.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:05Welcome to Dev Interrupted. I'm your host, Andrew Ziegler. And I'm your host, Ben Lloyd Pearson. This week, we're talking about Meta making the news for business practices and privacy violations, Cursor's own hiring practices, the joy of toy software, and how API sprawl is slowing you down. Ben, what's on your mind? Well, I can't pass up the opportunity to highlight all of the horrible privacy practices over at Meta, so maybe we can just start there. okay this is the story that broke the news in the last week talking about meta attempting to approach ai engineers from companies like open ai uh and doing so with huge bonuses and paychecks and uh sign-on agreements some of them topping a hundred million dollars could you imagine a compensation package from a competitor with that kind of price tag attached to it my mind literally cannot fathom what that kind of money feels like or looks like.

1:05Yeah. So obviously, Sam Altman and Zuckerberg, they took it to the news and there's been a whole news cycle about this. And Altman proudly said that none of his employees took that offer. They all turned it down and his employees believe in OpenAI. So it obviously became a posturing conversation between the two companies. But it's really interesting to see because only a handful of companies can really play at this level. I mean,$100 million sign-on bonus to attempt to poach competitor talent. What about the rest of us? There was a really good post that I saw on LinkedIn talking about this from Mohit Malik that said, real strength is not poaching.

1:43It's in growing, retaining, and respecting the people you already have. And so that was my positive takeaway of the story of, you know, there's always opportunities to take those$100 million poach deals and invest them internally on making your own engineers the best in the field. The thing is that Mark Zuckerberg in particular, I feel like he has a well-established history of using the throw money at it strategy to try to solve problems. So on one hand, it actually would not surprise me at all if this was true. If you look at Meta, they really were like an early leader in LM research and development.

2:20And they made a lot of great advancements in open source contributions to the cause. So I think they really do deserve some respect and recognition for their contributions in the field of AI. But it really does seem like they are struggling to build AI products that people actually want to use. We've seen Zuckerberg talking about AI social media bots that interact with you and become your friend. Or Meta's out with their new chat interface for AI that some people have been using. But I just feel like there's so many more interesting problems out there to solve with AI that social media just isn't – it's not really it, you know?

3:01So I kind of imagine that Zuckerberg feels a little bit behind in all the AI hype. But when I really dig into this, it feels like something's off. Like if this is true, it is truly a ridiculous sum of money. Truly. If it's true, it feels like an attempt to disrupt a competitor rather than any sort of real investment into AI. I personally would not trust this offer unless there was like some sort of substantial compensation that in the case that like meta revokes this offer suddenly because I feel like that's a real potential here. But, you know, honestly, I just don't really take the personal drama of random tech billionaires too seriously because at the time of this recording, Zuckerberg hasn't responded to any of this.

3:41So it's just the conjecture of a single person and Altman could be playing his own games here. So, but I will say this, if I were an open AI employee and I heard that my peers are being offered this kind of money, I would start wondering, hey, Altman, am I also worth that much? You know, you might turn up your nose at the Real Housewives of Silicon Valley, but I'm definitely going to stay tuned to the gossip and we'll let our listeners know if any new developments happen. Yeah, so I mentioned the meta privacy stuff. So let's dive into that, too, because let's just keep this meta hate train going a little bit.

4:14Well, you know, it's a nuanced hate train, but the next part of it is quite interesting because I think that if Meta convey$100 million for signing bonuses, they can probably handle whatever fine they're going to get for breaking GDPR and DSA and DMA and all the other alphabet soups of privacy enforcement out in the world. because meta there was a news broke another one this week about them about how they devised an ingenious system called local host tracking that bypassed even things like android sandbox protections that protect your identity while browsing an incognito mode an incognito mode is something that we all take for granted and obviously there's always a way for your identity to be compromised through while using incognito mode but how this one worked is basically your Facebook and your Instagram apps, they would set up like a hidden kind of like a intercom basically inside of your device.

5:06It was a port that would listen. And so when you would use incognito mode and you would go to websites that had a tracking pixel, that tracking pixel would actually reach out on your local device to that open port and then use that to identify you on Meta's server. So this effectively bypassed all of what incognito mode is intended to do because incognito mode, it protects you from yourself. It doesn't save anything on your own device. It works on your own device, right? But this works by actually sourcing Meta's tracking pixel from the content you navigate to. By any other definition, you would call this like a virus or a bypass, right?

5:43It's doing something that you're not, that is not visible to you on the surface. So that was really interesting development that came out this week about how some of the underpinnings of their own software work. I'm sure there's probably going to be more conversations about this massive privacy violation. Yeah, you know, this used to be a controversial take, but I think it's becoming less and less. You know, I deleted all meta apps from my phone more than a decade ago, like long before it was even called meta. And I never looked back, to be honest. They have a very long history of just abusing and violating privacy requirements.

6:16And even if they're not breaking the law, there are still definitely many examples like this where they are doing things that are at least somewhat hostile to their user base. So my advice is honestly, just don't trust them with access to something as sensitive as your mobile devices. And I do have a bit of a hot take on this. I actually have this theory that if you just install the apps from four different companies off of all of your devices, your life will get significantly better. So Meta is at the top of that list. I put ByteDance on this list as well. I think X deserves to be there. And I've got a forth you want to take a guess andrew what that might be so just so i understand these are the four apps that you should uninstall from your phone in order to have a better life that you should install uninstall all of their apps well i have to brainstorm for a second because i'm like what's the company behind merge mansion because definitely uninstalling that one is going to give you a lot of hours back at least if you're me but hmm knowing you ben definitely read it that's another one i think you would uh you know i've gone back and forth on that one a lot actually it is currently still on my phone though so oh okay so we don't know maybe that's even the secret fifth one we haven't gotten to what is it what is it ben pdd holdings what is that so they're the the makers of timu you know it's i feel like that kind of instant gratification style app like get something instantly whether it's like social validation or a piece of clothing from china like you know there's a lot of apps out there that are like this that met is not the only the company, I guess, is what I'm trying to make.

7:49They're just one of the more egregious violators. Yeah. And after you uninstall all of those apps, then you have plenty of room to install Roblox, which I recommend being on everyone's phone. Yeah, absolutely. But more importantly, I think this is yet another example of how U.S. regulations really have not kept up with technological advancements. We have this expectation of privacy in the physical space. It's built into a lot of laws here in the U.S. and even around the world in some places. But we haven't really adapted this concept to the digital space as well. So as a result, we rely on these U.S.-based companies primarily to become like the de facto policy enforcement organization.

8:28And not just for the U.S. Like it often, like their reach extends into other parts of the world as well. And without any sort of like adequate privacy protection in place, like companies like Meta get to decide how private data should be handled. And, you know, you mentioned that there are some potentially European data regulations that Meta has violated as well as some others. I'm sure this is not the last we're going to see of this story. But, you know, I just want to say the privacy researchers who discovered this like deserve kudos for this work. Like I really love when when people uncover this type of stuff and share it with the world.

9:03So great job to them. Yeah. So, all right, Andrew, let's talk about Cursor now. Yeah, so Cursor is a hiring playbook. It was discussed a bit in the news. I think it's just worth calling out for just a brief moment because as everyone knows, Cursor has been under like a magnifying lens for the rest of the industry. Everyone's been trying to figure out how this like ARR hyper unicorn grew from 100 million to 300 million ARR in just six months, right? So everyone's looking closely at fundamentals of a company like Cursor. So in the last week, we had a closer glimpse at how they hire their engineers.

9:37And it's a good look into how an AI-first company is looking at evaluating new talent. So on day one, these candidates are onboarded within the company, the engineering orientation around how they work. They're briefed on a project they'll be working on together with a staff member and introduced to the team's workflows, tools, and goals. So effectively, you come into shadow to work when you kick off your interview process. And they actively contribute towards brainstorming solutions, attending meetings, and they effectively collaborate as a full-time member by this end of the second day. And that entire process has a feedback loop where they're constantly talking with their hiring manager, with their potential future teammates about the process and what they're working on together.

10:23So it's actually really fascinating to think that just for interviewing and for bringing in new talent, that they have such an open door on how they work and what they're working on and when they're evaluating new talents. That was something that really stood out to me. The other thing that really stood out is that at no point in this conversation is there an arbitrary take-home exam or a coding, leak code test or any other evaluations. because these engineers, they do code while they're there, but they're more focused on evaluating their communication and problem solving skills. Yeah. And I find it interesting that they don't allow AI in any of their interviews, which is the type of thing that to me really feels like it only works for companies like AnySphere, which is the company behind Cursor.

11:08You know, they don't necessarily need to test candidates on AI skills because it should naturally come out within the interview process. And what I mean by that is, Andrew, you and I, we use AI a lot here at Dev Interrupted now. It's really unlocked a lot of new workflows for us. It's accelerated a lot of routine work. It's been just a huge change to how we get things done. And as a part of that, we've adapted new language, new practices, new tooling. We've become familiar with this whole new space of operating. So if we were going to interview somebody to join this team, for example, I think it would become pretty relevant to us or pretty obvious to us pretty quickly whether or not that candidate has, you know, sort of built AI into their lives because they would either have the same understanding in the language that we use or they wouldn't.

11:57And if they didn't, then, you know, it would be it would come out pretty easily without having to, like, ask them to use AI as a part of the interview, for example. Yeah. But what I really, really love about this is there's so many stories out there about AI taking over the hiring process. It's actually like really comforting to see an interview story that is distinctly human. Like they're focused on the human side of the experience rather than like, can you produce more code with AI kind of challenges? So it's pretty cool to see. Totally. All right. What's next for us, Andrew? Yeah, so I mentioned at the top of our new segment that writing toy software is a joy.

12:38And there was an amazing article I read last week from Joshua Barreto. As someone myself who was a hobbyist dev turned engineer, like many of these joyful game dev projects he listed out were things that I certainly tried to do or worked on as part of building my problem solving skills with code and experimenting with one-off projects. And so he gives a recap in this article, some of his favorite coding projects. And he gives a list of ones that he recommends any kind of hobbyist game developer or just code writer would try. And what's great about these is there's so many parallels in them to solving high level problems and software engineering that when you look at these steps, you really do see how the evolution of someone's skills can evolve through projects.

13:19And there's a few in here that were really fun to me that I've actually done before. Like some ones I'll call out were like a regex engine. Like I've written one of those before. A physics engine who hasn't if they've ever done game development. Your own text editor, definitely hacked around with that. A rasterizer, you know, I love working with shaders in the browser. And the last one that really made me laugh was an ECS framework, which for those that don't know is an entity component system. And really, that's something that a lot of hobbyists, game devs aspire to have is a perfect version of one of those systems.

13:54So great list. Highly recommend you all check it out. Yeah, it's pretty awesome. Yeah, I really love the personal project. I am going to disagree with the author on one key point that they make. I think somewhere in this, they make a point to not use AI for these projects. And I actually have the complete opposite perspective on that. Like almost relearning how to code because I've sort of been out of the practice for a little while just with the type of work that I've been focusing on. But with all these new agentic AI tools, I felt the need to get back into it and to start not really learning from scratch, but in many ways, like starting from, you know, not square one, but like square two or three in many cases.

14:33And, you know, I think the important thing is like, yeah, when you let cursor or copilot do everything for you, you're not going to learn anything from that. But it can also be an immense help when you are actively trying to learn. So, you know, I think my next experiment is actually going to be working with like cursor rules that help make cursor more of a guide that helps me solve problems rather than it writing all the code for me. Because I have really been focusing on like the fundamentals with this because I feel like that's important when, you know, we're adopting this new technology. Yeah.

15:06So what's our last story, Andrew? There was a new report that came out recently that actually it dropped today. and I've been looking at it. And really what's fascinating about this report from Apollo GraphQL is it looks at the state of API orchestration within organizations. And there were some really profound stats that I saw this morning when it came across my desk, which is why I included it in our discussion. Things like 76 % of enterprises can't make quick changes due to rigid infrastructure. Like, come on, that's something we talk about on here all the time. I don't think that's surprising at all.

15:37Yeah, less than 30 % can test their software without cross-team coordination. That's a reality within many teams. You know, you get these disjointed workflows. And then 52 % of... It's also a commonly cited bottleneck for companies that are adopting AI, right? Like they still have these testing workflows that get bogged down. Oh yeah, absolutely. Like if you generate a lot of code, then you're just create more throughput later on in your pipeline. You have to have the means to support that. We've talked about that extensively even in our webinar we had recently. Yeah. Another one here, too, was the 52 % of organizations struggle with large scale code changes.

16:14That's a reality. You know, large companies are having trouble doing this digital or rather this like AI transformation and modernization of their software, their infrastructure to handle how technology is being built now. So I really recommend everyone checking out the state of API orchestration report. I'm going to include it in our in our newsletter. And it's something that helpful to keep in mind that as your workloads scale, you know, this kind of thinking of orchestration. It's not just helpful, it's mandatory. There's a lot of research in here that highlights how you get these performance gaps if you don't prioritize it.

16:47So I know our audience loves these kind of data deep dives. We make them all the time. We read them and cover them here all the time. So if you want to read this report, we'll include it in the newsletter. And as a final tidbit here I'll leave you with is that we're actually bringing the CTO of Apollo on to DevInterrupted in the upcoming week. So stay around for Matt DeBurgulis. He's going to be coming up later this summer. So stay tuned for that one. Yeah, it'll be really great to learn from Matt. And what I really love about this is it actually aligns with a lot of the research we've been doing here at Dev Interrupted in partnership with Linear B.

17:20You know, as I mentioned, there's lots of bottlenecks outside of code production that AI really is not unblocking yet. And I think it's really important that engineering teams just don't rush off to generate more code without fully understanding the impact of it. you know we just published this six trends and ai driven software development guide we cover a lot of the biggest bottlenecks that teams are facing when driving ai adoption across the organization and they align quite well with what we're seeing in this report so our guide is also full of some really great advice on how to address it as well so check the show notes we'll we'll share a link down there yeah so andrew tell me about who our guest is this week yeah this week i'm sitting down with Kabir Betty at Amazon Ads, and we're taking a look at what video generation can mean for mom-and-pop businesses, how AI engineering culture works at AWS, and how Kabir's team built an AI product and brought it to market, while the fundamentals constantly kept evolving around them.

18:21AI is creeping into every part of the SDLC, but how far have teams really gone? Linear B surveyed over 400 devs, many of them like yourself in the Dev Interrupted audience, and found that 67 % are already using AI to write code. But is that creating opportunities or bottlenecks? Our new DevX guide breaks it all down, including adoption patterns, pitfalls, and the AI collaboration matrix that charts your own team's journey with AI. Check out the guide and maybe even the panel I hosted about it with Atlassian, AWS, and ThoughtWorks. I'll drop the link in the show notes. We're diving into how technology is reshaping video generation and how generative AI is a huge part of the evolution.

19:07We've seen some amazing developments recently, and today we're talking with Amazon. We're joined by Kabir Bedi, the head of product for image and video generation at Amazon Ads. And we're going to understand how generative AI is being used at Amazon and what it means for the future of generation. and also how engineering teams have come together to build this new technology that's opening up a whole new door to video creation for people just like you and me. So, Kavir, thanks for being here to dive into some of the advancements coming out of your team. Thank you so much, Andrew. It's great to be here.

19:44I'm very excited for our conversation and to discuss the latest AI launch that we just had, which is an enhanced video generator for brands to create videos. You know, video generation is a really hot topic right now. Everyone is kind of tackling this topic, both with their own technology and trying to use it in a consumer space. So there's a lot to explore and to learn from. And for the folks listening to Dev Interrupted, we're going to see a lot of parallels in this conversation to things in our own world in software engineering and how tools and things available to us are changing and democratizing the way that we work.

20:21So Kabir, if you were to give us like a big overview of some of that announcement, what were some of the biggest things that stood out to you? And what role did your team play in bringing those to fruition? Absolutely. So let me take a step back and first talk to you a little bit about what's the general problem that we were working to solve. You said it very, very rightly right now. Video is everywhere. Video is super important. we interact with video on pretty much most platforms that we all are on. Same goes for video ads. But the challenge that advertisers face is that video ads are really expensive to make.

21:00They take time, energy, effort, money. And so as a result, you have so many brands that were just not able to create video ads. So we set out on a mission to democratize video advertising so that all types of brands, whether you're a mom and pop shop that's selling one product on Amazon or a large brand selling hundreds of products, are able to use video ads. We launched Video Generator in beta last November and over the last six months have been receiving really good feedback from advertisers and just now launched an enhanced version of it with a bunch of new capabilities that I'm super excited to talk about that I think will really meet the need of those advertisers that have never been able to try video advertising before because it was too costly or too time consuming.

21:56And, you know, using the power of AI to really sort of bring their products to life in a way that they've never been able to do before. Yeah, this is like a great introduction to the problem. And I like that zoom in on it being accessible to, you know, more mom and pop shops and places that didn't traditionally dive into huge scale asset creation and having the photographer come out and set up all of the stock imagery backgrounds or to, you know, to buy all of those stock images online. And there's a huge amount of effort that goes into constructing creative works for that type of business. Not to make it more accessible to them, but without sacrificing quality, it allows them to kind of open the door on how they position their own products.

22:41And right out the gate, too, you pointed out something that stood out to me as a really big parallel is just making it accessible to as many folks as possible. You see the same thing happening right now in engineers that are adopting AI tools. It makes coding, like vibe coding, as you might call it, more accessible to more folks to try out to build things for the very first time. Absolutely. And I think that, you know, we had heard that consistent feedback when we launched in beta that we love that this allows us to create a video that we've never been able to make before. And our most recent data really validates that story.

23:20You know, what I've seen is that over half of the videos that are now getting created using video generator are for products that have never been advertised using video on Amazon before. And so right off the bat, we're seeing that advertisers or brands that have not been able to advertise their products using video are using this tool right away. and with this launch, we launched a bunch of new enhancements that really has sort of gotten folks excited. One of the pieces of feedback that we heard when we launched in beta was that back then, that technology was really cutting edge, was to show how products looked in a video.

24:03But the feedback that we were getting from brands was that actually, I want to go beyond that. I want the video to show how my products will be used instead. And so that's one of the big, big pillar innovations that we've just launched, which is we've added a lot more realism that now shows products in use. A great example could be previously we could show how a watch looked on, say, a table. Now we can show how that same watch looks on a human's hand, showing how the human moves their wrist to see the time. So previously showing things on a flat surface really worked well for certain categories like kitchen or say home.

24:45But for things like apparel or electronics, brands wanted to show how their products are going to be used. And so that's that's sort of one of the pillars of innovation that I'm super excited about. The other one is also, you know, as we've invested in innovated in new technology, we've been able to create multi-scene ads. So now you don't have to have just an ad that has a single scene. Now you could have three to four scenes that makes the ad a lot more comprehensive to show you really the product from all its different angles, all its different use cases. And so you're seeing this is sort of latest, I would say greatest in technology.

25:22Similarly, plenty of other innovations like the ability for advertisers to now upload an image and convert that into a video or upload a video and have us summarize that by actually identifying the key frames in it to create a video ad that suits that brand. So a bunch of new innovations have come out and we're getting very strong feedback that I'm very happy about. That's an interesting way of tackling the problem. And it actually brings me to one of my big questions I wanted to tackle in this conversation with you. So creating this tool, you know, and really changing the level set, right, in which folks can actually approach a video asset creation.

26:00But in doing so, you're getting a whole new generation of folks who have never used this tool before. So you have to think of all of the different ways they're going to interact with it. And this one thing that you hit off the bat is really fascinating. this like multi-modality of folks being able to input like a video or input an image or input like whatever they had, right? So what kind of assumptions did you have to throw away about how maybe your traditional audience use these tools, more tech savvy audiences, in order to make it something that would be massively adopted by other folks? Yes, yes.

26:34So one of the sort of assumptions that we worked backwards from was that we have to make it easy to use, which means how can we reduce the amount of input that's really needed from the user to give them a high quality output. So that's why one of the features of this product is that it's one click, which means that all the advertiser provides is what product they want to advertise. And we handle everything behind the scenes, which means prompting, generating the video, et cetera. And I was recently on an advertiser call where they really admired that. This was an advertiser that had been playing around with, you know, generally AI and concluded that they felt that AI required a lot of high quality prompting to get a high quality output.

27:22And he told me that he loved what he loved about this tool was that he didn't have to do any of that. He said that you've made it so simple for me that I don't have to think about what should be my input prompt? What should be the guardrails and the requirements for me to get a high quality output? And so that is, I would say, one of our biggest pillars that we really sort of wanted to hold true, which is how do you make it easy? Because a lot of the brands, smaller mom and pop brands haven't, like we already discussed, haven't created video before. They also have not with AI before. And so you want to really make it simple for them by actually reducing the amount of decisions that they have to make to also reduce their cognitive effort involved.

Read the full transcript

28:06You're really driving now at like the core of what I think makes this problem solved so fascinating is it requires this whole new mindset of innovation to build a tool that's going to be used at the scale by this broad of an audience. I think there's a lot of folks that that folks can learn from how maybe you approach solving that problem. So what were some initial things about bringing this to market that maybe like go against the grain or you had to unlearn traditional mindsets to get it out the door. You're building on a technology that's so, that's innovating so rapidly. Like we've heard now all the things you've walked through that it can do and all the modalities in which you can interact with it.

28:45And it's like nothing short of impressive, right? And we're talking about video generation. So what has it been like to innovate in that category as it's almost been like speeding ahead with you as well in terms of just like every day there's something new. You know, absolutely. I think that the rate of progress is so inspiring that everyone working on this, including myself, is, you know, having so much fun in the process. But along the way, I've also felt that, yes, the way that we have to build these AI products, particularly this sort of product, has evolved over time. Two key things come to mind.

29:22The first one is, you know that when we launched in beta, what we did is that we really brought the entire engineering and the science team right in front of customers because we wanted the entire team to hear the feedback from the customers firsthand. When we are creating a video for a brand, you know, it's a high responsibility. You are showcasing their product. You are bringing their brand to life. And so it's very important for everyone on the team to be hearing about the nuances in, in, you know, the advertisers as feedback. Oh, I like the way that the video did X, or, you know, I didn't like that, that it sort of prioritized this aspect of the product rather than that aspect of the product.

30:08And actually one great example comes to mind to me. We met a baby brand, they made baby books and essentially two fathers, new fathers that didn't like the books on offer when they became fathers. So they chose to create this brand out of Ohio. And they had never created video ads before, largely because one, it was too expensive to create video ads. And two, they felt that babies didn't make for a very good model. And so in this interview with them, he really spoke about how using video generator, they had never thought that they would be able to create video ads till they use this tool. And, you know, that feedback really sort of lit up the team.

30:47everyone got excited about what we're doing. We also got some very valuable feedback of how we can improve things, you know, how they wanted to highlight certain aspects of the product. And so bringing engineers as well as scientists into the room with customers was a game changer. So that's one. And I think that permeates to all types of AI development, wherein everyone working on it must have their ear very closely to the ground. Luckily, this also matches, you know, sort of very well into one of Amazon's most important leadership principles, which is of customer obsession. The other area that I think the team culture has really evolved is around experimentation, iterative development around model improvement.

31:35You know, all of these AI models are just progressing so rapidly that the team has sort of now developed a culture where we do multiple experiments a week. We're just constantly trying either different models or we're prompting differently to see the output. And so it's an environment which is a lot more agile, a lot more iterative, and I would say dynamic. And those are the two aspects that I I felt for any team wanting to develop has been important shifts for us, which is bringing everyone on the team closer to the customer, as well as viewing the work a lot more iteratively, because such is the rate of progress in the model development itself.

32:20It's really well said. And it also echoes what a lot of leaders come on this podcast and say about their own engineering teams. Those are two things that are that really help you stand apart and to help you get ahead in this kind of environment. That impact-driven engineering where you're customer-obsessed and you're the one smashing and building things together, but you're also talking with the folks using it and understanding their pain points and where they want to go with it. It really helps developers build the best possible software, which is what we're all here to do, right? We want to build really cool stuff.

32:51We want them to be really impactful, and we want it to work for the folks that are going to use it. So like that key thing of bringing people really close to it, even like I like how you included the scientists in that, the folks who are manipulating, looking at the data, trying to understand the patterns and think of it all. They also need to be closer to those users and to how their technology is being used. Right. So yes, absolutely. Let me give you another example of that. You know, like I mentioned already, our enhanced video generator, one of the key features is that it can now show products in use.

33:25and that feedback that we got from advertiser interviews, wherein advertisers would share with us that, you know, I want to see my product, how it's used, rather than just how it looks. It's the scientists that heard that feedback firsthand and then evolved our technology. Previously, we were using outpainting technology, which was really cutting edge when we first launched with it. And they then evolved. And now we use subject-driven generation technology, which is able to show products in use. And I think that the only way that we were able to make this leap was really to help the real folks, scientists who are actually building, iterating on these models, hear that feedback firsthand that the advertisers, for example, wanted to show a shopper drinking coffee from the mug rather than just seeing the mug on the table.

34:21And so I think that, you know, bringing folks into the room has really allowed us to really unlock various levels of innovation, including just at the most fundamental model improvements as well. That's such a great story to back that up. And I love, too, that it kind of connects all the dots there. What I love, too, is that it really brings in that second point that you made, that it stands apart, really, in terms of having a culture that creates innovation, that sustains this constant experimentation, that rewards folks for trying new things and sharing in the open. That's really critical. Like my own team does that.

34:53We're trying out new workflows every week for this stuff. I know a lot of our listeners are as well. And having that culture of experimenting in the open is then what allows folks like those scientists who get close to the customer conversations to actually then try to figure out how to get to the destination ultimately. Because I'm sure that shifting that entire model flow from outpainting to something else took a huge effort and it all started with experimenting. So really goes to show how rewarding and supporting that experimentation culture is important to innovating in the space right now.

35:26And what parts of your development process have you had to bolster up to really support your team? Like you're talking about introducing a lot of new workflows and tools and constantly experimenting and change things up. What were things that you and your team did to kind of keep developer morale high, to keep the developer experience good through all of that transformation? Yes. One of the things that I learned through this process personally is that the team is also eager to hear from the end user. That is a great source of motivation and morale boost. When the team is hearing from the small brands about who could never produce videos before suddenly being able to do so, that's a huge morale boost.

36:08One of the other avenues that we've really gone deep on that, in my view, has worked really well for the team is that the entire team, as well as leadership on the team, is very deeply involved in the experimentation, which means that if we are testing a new model and there's an output from that model, I will also dive deep to really see, you know, so what is that output looking like? Where is it doing well? Where is it not doing well? It's in some way been a source of, of, you know, an equalizer that everyone on the team is quite involved into the details, regardless of, you know, what they're working on, what level they're working on, which means that the whole cycle of sort of iteration becomes a lot more robust because everyone's giving feedback and everyone is involved into the details.

36:56And that's been super fun for me as well. I love building products. And I also love sort of diving into the details of, of, you know, how are things working under the hood? Where are they doing well? Where are they not doing well? And so I've also personally really enjoyed working very closely one-on-one with scientists. And so those are the two things that I would say. Bringing folks towards their customers is very motivating. And everyone being involved in the details is also very inspiring to the folks like the engineers and the scientists so they know that you care very deeply about what they're doing.

37:30And if a software engineering leader is listening to this and they're thinking, oh, I really need to create this culture where my own engineers can get closer to my customers and can listen to how they use my software, my tools. What advice would you give to that leader to start bringing those conversations closer together in a way that doesn't disrupt? The techniques that have worked really well for us for this product launch is that we have multiple times a week folks talking to various brands. And those meetings are open to everyone on the team. Whoever can join, you know, sort of based on the calendar is sort of welcome to do so.

38:09And so a very simple way of doing it is to have a sort of recurring mechanism that constantly gives folks the option and then not have an expectation that everyone has to join every time, but that they have the option to do so. And actually, what I've noticed is that everyone finds so much value from those calls themselves that they choose to attend. That would be my feedback and advice is to have a mechanism that gives regular touch points for the entire team. Open that up to everyone. If you want certain folks to guide the conversation with your customer, that's okay, but allow everyone the opportunity to actually listen in.

38:47And the other thing that often my team does, which works really well, is just going in a little prepared for what you want to talk to the customer about. Sometimes we want to talk about the multi-scene that we just generated. Other times we may want to talk about the one-click feature and, you know, what they think about that. And so if you go in a little prepared, it allows folks to be in the right headspace of how to navigate the conversation and, you know, what they can learn out of it. Yeah, it's about treating it like another workflow, another work stream. Like, first off, you need to have the dialogue conversation.

39:21If that means that you need to start one, then that's the case. If it means that you need to include your engineers in those conversations as an optional, then that seems the way to go. But creating a regular loop that keeps those two entities close to each other, lets them communicate, and then obviously creating this culture that rewards dipping your toes into that work stream, into understanding and getting obsessed with that problem and what you're building to solve it. Because it's a real morale booster. And I know that if you make it available, folks will want to take advantage of it. So that's really good advice.

39:54And I'm wondering too, when y 'all started on your journey to build Video Generator, and it's more in the early days of building out your early beta and getting some traction on the idea, what were some of the early signals that you got from these kind of customer conversations that stood out to you? Are there any that really painted the road that brought you to where you are today? Yes, I think two pieces of feedback that we very consistently heard, you know, sort of allowed us to continue going down this path with high conviction. One was that it was fairly apparent that brands wanted a feature that was easy to use.

40:32I already gave you the example of, you know, what we heard from the advertiser to not have to do any prompting, but the idea to make it easy to use so that neither the tech nor understanding AI were a barrier for all of these mom and pop brands. And so we really held onto that principle because we heard it over and over again in our feedback. I think the other piece of feedback that we heard, which is also what I mentioned around that sort of helped us move from outpainted to subject-driven generation, was that effective videos are those that show how a product is used in its natural setting. And I think that when we heard that feedback consistently over time, it sort of reaffirmed our belief that that was the direction that we wanted to go in.

41:19And so with this launch, we've been able to hold on to both of those principles, added a bunch of new features, like I mentioned, multi-scene generation, live images, etc. and you know are very happy with the results because the other sort of data point that i've been looking at is that what is the reuse of the tool and we've seen that over a third of advertisers that are using this tool are now using it to create two or more video campaigns and so we know for a fact that really sort of making it easy for them and showing their products and use through, you know, through a multi-scene video, it's sort of actually encouraging them to use the tool more to create more video ads.

42:04So that's sort of how I would think about incorporating your beta feedback into your tool, you know, sort of our product, and then being able to measure that, have we been able to validate the hypothesis that we really set out to solve for? Yeah, and that's actually another huge parallel with agentic AI, with the engineers too that you just said, because when you see them start to use it and start to adopt it, they pick up Copilot, they're using Cursor. It goes like really quickly overnight from, oh, they just like maybe queried it once or twice or did an autocomplete to, oh, they're using it every day or every time they use their IDE, they're agentically coding or whatever the case you see in order of high adoption, right?

42:45And that's like a strong signal. That mirrors what you see with your video generator. Folks go to use it once and then it works and it gets them what they want. And so they go use it again. And I can't think of a better result to ultimately arrive at because that's how people build products that just like spread word of mouth and just really solve a problem. Exactly. And, you know, one of the joyful things about working on AI products like this generator is that the underlying tech is improving so rapidly that if you go week over week, month over month, you will see step level changes. And so that is important for folks to keep in mind, regardless of the AI application that they are trying, is that not to view it purely from the lens of where it is today, but that the underlying technology powering those, whether it's, you know, sort of coding applications, but in this case, content creation applications, the sort of underlying technology is, you know, sort of rapidly innovating.

43:41And so they'll just keep seeing that progress come out. yeah it's going to be like really interesting to continue to follow the product as it evolves because what you've done is you've laid a foundation you've created a one-for-one transfer of folks coming in with no technical knowledge wanting to get their really great assets to having the engineers and the scientists behind it to support that effortless creation on whatever modality they want to work and ultimately the folks with the most easy to adopt modalities are going to win in all of these types of adoption scenarios. Because when you get a mom-pop who uses a tool and it just works and it gets them what they want, I don't think that anything can make something stickier than that.

44:21So I'm really excited to see where it goes. But something I wanted to end our conversation on that I know is top of mind for a lot of our listeners too, is just about the skills evolution that you see for engineers, maybe those on your own team, and how it's definitely different than engineers of yesterday. Stack Overflow generation engineers, the ones that didn't get all their answers from their GitHub co-pilots. So I am curious to know from you, what do you see as things that stand out as skill sets for the engineers of tomorrow? And how are you all building those skills within your own team?

44:54Yeah. You know, for me, what I have been encouraging the team is to rely on another Amazon leadership principle, which is learn and be curious. This space is prime for all of us to be diving in and learning constantly. And so what I've been encouraging the team to do is heavy, heavy knowledge sharing when it comes to on the application layer or at the underlying model layer and trying things firsthand as a way to improve, whether that means diving into prompting yourself, seeing what the output looks like, modifying your prompts to see what the output looks like. And so a lot of, you know, sort of my ask of the team is to really roll up their sleeves, dive into the details and give things a try.

45:46That would be my advice for anyone in the software engineering science work streams working in this space is that you really only get better by doing. Everyone else is also learning with you and share information with others. learn from others, be in a sort of a growth mindset environment. That's really the message that I've been sending to the team. And I think it's also brought about an environment of where folks are quite excited to sort of learn from each other. Everyone is constantly pinging, this is what I tried, this was the output, you know, and not everything goes well, but that's part of the learning process.

46:24And you can't win by sort of being on the sidelines. You have to be playing in the field. And so you have to jump in yourself. Don't be too harsh on yourself on the things that you know today. Just have a growth mindset. That would be my only advice. Yeah, you can't win on the sidelines. I love that you have to get in. You have to go play on the field. Like what a great way to phrase it. I'm going to be saying that forever. I'm really happy that you're able to kind of paint a picture for us of how this development happened for your team, how you're able to build and ship something that has such a huge impact on top of such a rapidly evolving tool.

46:58folks you know who we talk to and it definitely this is a common sentiment in a lot of our listeners engineering orgs like there's a paralysis around even just adopting ai tools and and building them into your workflows much less turning around and building them productizing them taking them to market and having mass adoption on solving such a huge problem set for folks so i think there's a lot that we can learn from your engineering culture so i appreciate you sharing with it with us For our listeners who are curious to know more about you and Video Generator, where would you recommend they go to learn about these kinds of things?

47:32You know, you can follow me on LinkedIn, as well as get a lot more information on Video Generator's capabilities, as well as the latest launch on the About Amazon blog, as well as the advertising.amazon .com blog. we posted information in sort of all of those places as well as on my LinkedIn. Okay, fantastic. Then we'll get that shared in the show notes. So, you know, our listeners, you know where to go to check those out. Another call out for our listeners too is that if you like this conversation, made it all this way, that means you did like the conversation. Definitely give it a like, give it a share.

48:09Most importantly, come let us know on LinkedIn what you thought about it. I'm posting this episode on our Substack newsletter. So if you're not subscribed to there, you can check it out. but it's really easy to join us online. We're both on LinkedIn and we'd love to know what you thought about today's discussion topics. Maybe even see some of the stuff that you're trying out in Video Generator if you take it for a spin. So definitely let us know and we'll see you next time on Dev Interrupted.

From the publisher

What if creating a professional video for your business was as simple as a single click?

We're joined by Kabir Bedi, Head of Product for Image and Video Generation at Amazon Ads, to discuss how generative AI is making that a reality. He provides an inside look at Amazon's mission to democratize video advertising, empowering everyone from mom-and-pop shops to large enterprises with their innovative video generator that evolved from simply showing products to showcasing them in realistic, multi-scene lifestyle settings.

Kabir shares key insights into the engineering culture that powers this innovation, built on deep customer obsession and a dynamic, experimental mindset. He explains why bringing the entire team—including engineers and scientists—into direct conversations with users was a game-changer for their development process. Plus, listen as Kabir explains why a "learn and be curious" mindset is the key to thriving in this new landscape of AI-driven product development.

Check out:

Follow the hosts:

Follow today's guest(s):

Referenced in today's show:

Support the show:

Offers:

More from Dev Interrupted

All 208 episodes
Inside Amazon's AI video generatorDev Interrupted · 49 min
Listen in VO