Screaming in the Cloud - A Conversation with AWS’ Sandy Carter, One of the Busiest Women in Tech

Starting point is 00:00:00 Hello and welcome to Screaming in the Cloud with your host, cloud economist Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud. And this is important to me. No billing surprises. With simple, predictable pricing that's flat across 12 global data center regions and a UX developers around the world love, you can control your cloud infrastructure costs and have more time for your team to focus on growing your business.

Starting point is 00:00:59 See what businesses are building on DigitalOcean and get started for free at do.co slash screaming. That's do.co slash screaming. And my thanks to DigitalOcean for their continuing support of this ridiculous podcast. This episode is sponsored by the Observe 2020 virtual conference happening on April 6th. Are you looking for a germ-free way to learn all about observability and possibly the new OpenTelemetry project? If you visit snark.cloud slash observe, you can be part of this one-day virtual conference happening on April 6th, with talks and workshops packed tighter than a multi-stage flattened nano-based

Starting point is 00:01:46 Docker image. $50 per person, but group rates are available for distributed teams too. Ticket purchases go towards providing free learning for folks experiencing economic hardship and underrepresented communities in tech. Visit snark.cloud slash observe to join them on April 6th. That's snark.cloud slash observe. Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by AWS's VP of Partners and Programs, Sandy Carter. Sandy, welcome to the show. Thank you, Corey. I've been so excited about joining the show, so I appreciate you having me on. Of course. So when we first started speaking, you were effectively running AWS's Windows operations. And then when your bio came through, it said that, oh, you're now the VP of public sector partners and programs, which, okay, I

Starting point is 00:02:41 guess that might be Windows-oriented, sort of, if you squint hard enough. But what's the story behind that? Yeah. So I came into AWS about three years ago to run enterprise workloads. And so I focused on our Windows business, because obviously lots of enterprise workloads run Windows, as well as VMware Cloud on AWS. A lot of our enterprise clients today run VMware, SAP, as well as Salesforce, and now IBM slash Red Hat. So I really honed and focused on

Starting point is 00:03:16 those workloads. And then I was asked to come over and broaden the perspective. So not just those five workloads, but what could we focus on globally from a partner perspective? And so we're now looking at public sector in not just the government, but state and local education, healthcare. A lot of healthcare is a non-profit. Outside the US, a lot of telecommunications,

Starting point is 00:03:43 a lot of transportations. And then in several regions of the world, like the Middle East and some in Asia, the entire country essentially is public sector. And a lot of that growth and a lot of that scale will come through our partners. So I am super excited to take that Microsoft role, VMware, SAP, et cetera, and expand it out and about across the globe. What's fascinating about your background to me is you come from pretty much the exact opposite of everything I've ever done in my career, for lack of a better term. You come from extremely large companies, big E enterprise style of approaches. And I come from a small business

Starting point is 00:04:23 world where to my mind, a big company has 200 people. So I assume that's roughly how big AWS is. So it's, oh, you work at AWS. Do you know Jordan? And the answer is always no. It turns out you folks do have more than a couple hundred people working there. Who knew? It's just a different mindset and it's really its own skill. Unfortunately, it seems to be one that I lack more often than not. How have you found that, I guess, transitioning from some of the largest companies in the world to, I guess, AWS and its, I guess, practically small team mentality is really, I guess, what's that been like? Has it been a change? Has it been more or less same, same?

Starting point is 00:05:01 Well, here's the way I would think about it. So I was at IBM and I was actually running our partner ecosystem for the cloud, IoT, and machine learning and AI. I was asked to move out to California, which I love. The Valley is just so energetic around tech and to go out there and really develop that ecosystem. When I made the decision to leave IBM, I decided I would have been working with all of these startups. And when you're in the valley, you get the startup bug. So when I left IBM, which is this huge company, I went and started my own company. We were working on some research about how a company's culture needs to match what they're doing in innovation. So, Corey, I would see all of these huge companies and countries come into

Starting point is 00:05:56 Silicon Valley. They would spend six months to a year, and they would learn everything about how all the top innovative companies there did business. And then they would take it and they try to take it back to their country or their company, and it would literally fail. So what I worked on as my startup is I worked on the ability to do kind of a Myers-Briggs for a company and match innovation tactics. So needless to say, it was very small. So I went from big, big, big IBM to really small, my own company. And that actually eased the transition into Amazon. So once I had built my MVP, I had done some work with Carnegie Mellon Silicon Valley on

Starting point is 00:06:35 a piece of research. I was able to sell those assets off because I only had done an MVP, so I can't even say product. I was presented with an opportunity to come to Amazon. And so when I came, I had kind of already transitioned to being my own assistant, doing my own slides and narratives and documents and thinking differently, being very scrappy. And I think that that transition really helped me a lot as I came into Amazon. Because as you know, Amazon is a bunch of two pizza teams.

Starting point is 00:07:05 So you are working in a startup when you enter AWS. That's always been the sense I've gotten. I've never been the type of person that would ever fit in any large company. But of any large company that I've ever spoken to, it seemed that AWS was the closest to the startup mentality that I tend to deal with without some of the problematic parts that generally startup culture in San Francisco is best known for. Yeah, I would say, I'll just give you one quick example. When I started,

Starting point is 00:07:33 an intern that worked for me came up with this idea. He did a six-page narrative, which of course we do at AWS. He brought it in to me. I was like, this is a magnificent idea. We had, of course, a team of people sitting, reading the document in silence and then evaluating it. And so I went to my boss and I said, this is a great idea. How do we get this going? And he's like, well, you go. Just take your team and you just do it, which was very different from every other company

Starting point is 00:08:00 I'd worked at. And so we did it. And it's grown to be a sizable business, an idea that came out of an intern, which is typically a story that you would hear at a startup in the Valley. And I have many stories like that from Amazon. So it's quite a fun place and a very innovative place and a very much of a small feel. I really love it. Changing gears slightly, something that's been very interesting is watching, I guess, almost a transition in what AWS has been focusing on and speaking on at reInvent last year. One of the things that was very notable throughout the course of the keynotes

Starting point is 00:08:37 and the releases was an emphasis on the idea of hybrid. There's always been some options, Direct Connect or the Snowball Edge with the compute variant as well. But this was the first time that we really saw more or less the entire theme of the conversation revolving around hybrid. Things like VMware Cloud for AWS, Outpost being released. It really felt like it was a change in tone. Is that an accurate assessment? Or is that just for where I sit, I'm just starting to notice things I didn't used to notice before? Well, I would say this, you know, I came in with VMware Cloud on AWS being one of my big missions and that is hybrid cloud. So we've been speaking

Starting point is 00:09:17 a hybrid, if you would, for quite some time, but kind of with different motions. And what we were doing is as we looked at our VMware Cloud on AWS offering, great offering, by the way, if you are a VMware shop today, you want to get to the cloud, it really helps you quickly migrate, you know, integrates networking, both NSX-T with Direct Connect or vSAN storage with our EBS. It's a great solution, a great way for customers to kind of get to the cloud, but in a hybrid way. And also, many of our customers love the fact that they can vMotion applications back and forth as well. As we started understanding that solution, we started listening to a lot of our customer feedback, which is what we're known for, right? Working backwards from the customer. So I think what AWS has done on hybrid cloud is really amped up the messaging, amped up the product portfolio. I mean, Outpost is an amazing

Starting point is 00:10:18 offering that gives you not something like AWS, but gives you AWS on-prem and has that ability to enable customers to now leverage hybrid in a way that you haven't been able to before. Same with Wavelength or our Far Zone concept. It's just an incredible way to take this to the next level. So I would say we've been talking about hybrid computing for different segments of customers. I think what Amazon released and Andy talked about a lot at reInvent was really fulfilling more promises working backwards from our customers. That's one of the things that always struck me as being a truism about AWS and Amazon in a larger context, and that people like to say, oh, it's a corporate talking point. And I'll be perfectly honest, I used to think the same thing. But increasingly, every time I would wind up having a conversation

Starting point is 00:11:15 with someone at AWS about something, it doesn't matter how ridiculous my ask was or what I wanted to do. Even if it was part of the setup for one of my ridiculous ideas like using Route 53 as a database, the answer is always the same. Interesting, can you tell me more about your use case? And sometimes that use case was ridiculous and other times it was, oh, well, you might not think of it that way. What about if you used another service or offering? But I've never yet been made to feel dumb when talking to someone from AWS, despite the fact that oftentimes I was being extraordinarily dumb. that. Corey, I talked to 141 customers myself, got all kinds of use cases, and no question or comment was dumb. In fact, it all played into, you know, working backwards for the customer. You know, we always say 90% of what AWS builds is what AWS customers ask for. The other 10%, of course,

Starting point is 00:12:22 is strategic interpretation of that need. I think that that is really where the power is, is listening to customers, having builders talk to builders and really understanding. In fact, I kicked off one of my sessions once with a quote from Stacey King. I don't know if you like basketball, but I'm a big basketball fan. And Stacey King was a rookie and he played with Michael Jordan, who in my mind was the best all-time basketball player ever. And he said, I'll always remember this day as the day that Michael Jordan and I combined to score 70 points and Stacey King scored one point. Whenever I see us announce something, I always give credit back to the customers. I say, I scored the one point because I engineered and did the product management on it.

Starting point is 00:13:11 But you customers, you did that 69 points because you gave us the ideas. You gave us the nuances. You gave us the use cases that enabled us to build something new and something that works for you. And that's why we have such fast adoption. In fact, that service I told you about was License Manager, which is now used by thousands and thousands of customers and was only announced less than a year ago. And the reason the adoption is so fast is because we do listen to our customers. This episode is sponsored by ExtraHop.

Starting point is 00:13:48 ExtraHop provides threat detection and response for the enterprise, not the starship. On-prem security doesn't translate well to cloud or multi-cloud environments, and that's not even counting IoT. ExtraHop automatically discovers everything inside the perimeter, including your cloud workloads and IoT devices,

Starting point is 00:14:08 detects these threats up to 35% faster, and helps you act immediately. Ask for a free trial of detection and response for AWS today at extrahop.com slash trial. So let's pick a fight for a minute. I had the privilege of seeing you speak at a couple of summits last year. And one of the things you said both times, and I figure if you say it on stage in front of the world, it's a fair thing to ask questions about. And what you said was that AWS was the best platform for Windows workloads.

Starting point is 00:14:39 Fair enough. I'm not going to dispute it, but I will ask why. Well, first of all, AWS has run Windows for over a decade. We host nearly two times as many Windows server instances in the cloud as does Microsoft. So you're like, okay, so what? Well, if you have all that experience, you know, the Andy Jassy quote that says, there is no compression algorithm for experience. It's really true.

Starting point is 00:15:08 Our experience running Windows workloads has earned us our customers' trust. We have tens of thousands, hundreds of thousands of customers bringing their workloads over. Autodesk, who's been running Windows on AWS for 10 years, or Salesforce, who has over 10,000 Windows instances, they run it on us. So the question then is why, right? Why is that the case? And I would tell you, there are, I think, three or four core reasons. One is we continue to innovate. So whether it's, you know, Windows Server with things like License Manager I just talked to you about, which enables you to manage your licenses, or SQL Server being able to innovate with insights for SQL using machine learning, we can help you debug SQL application bugs on AWS faster, or.NET support. We were some of the very first to support Lambda

Starting point is 00:16:09 for.NET and use of machine learning with.NET or application modernization. We just innovate faster and have that agility that enables our customers to move quickly. It could also be an innovation and optimization. So right now, the performance of running SQL Server on AWS is two to three times faster than running SQL Server on Azure. And that's because we've taken the time to optimize our networking and our storage to make that happen. The second big reason is reliability. And some people are like, ah, but reliability matters. A lot of the Windows workloads are mission critical. And reliability really begins with our global infrastructure,

Starting point is 00:16:51 of which underpins all of those Microsoft services. We have 61 availability zones, 20 geographic regions around the world. And the latest, it's only from 2018, but they published it. It said that the next largest cloud provider had seven times more downtime hours than us. So we get a lot of customers coming to us saying, hey, I tried running my Windows workloads on Azure. It's just not reliable enough. I can't count on it. So I need something better. And I would say the third big reason is security. Our security,

Starting point is 00:17:27 you know, as Andy likes to say, is our priority zero because it's so important that we prioritize it above everything else. And just one example is if you look at FedRAMP, which is really important, not just for the government, but for regulated industries. We have over 90 solutions today that are FedRAMP authorized, and that is four times more than Google and Microsoft combined. So we take this stuff very seriously, and it's because of our innovation and our reliability, our performance, our security, that people are choosing us. And it's in the numbers. It's not a debatable thing. It's definitely in the numbers, Corey. There's a lot in there to unpack. And I'm sure that some people are going to be sitting up there

Starting point is 00:18:14 taking angry issue with almost everything you said, in which case, cool, email you, not me. But one thing I have noticed is that Microsoft's cloud offering is one of the, to my understanding, the only major cloud provider that offers an SLA around individual instances, which first is terrifying about what it says about those workloads. Windows workloads have a tendency to be, shall we say, tetchy. But it does speak to the idea that this single pet of an instance can't die. And that is something that I know that I've spoken with customers where that idea resonates. As much as we love talking about the idea of, oh, there should be no single points of failure in your environment. Well, here in the real world, we're often nowhere near lucky enough. That is true. And I would say that, you know, as you look at our customers, there are different use cases for each customer as they're deploying.

Starting point is 00:19:05 And based on what their needs are, we really try to make sure that they've got the right level of security, reliability, performance. So, for example, one of the things that we announced most recently is FSX for Windows, which is a fully managed native compatibility with Windows, the SMB protocol, the industry standard. And a lot of people were like, well, why are you doing that? It's Windows native, it's built on Windows Server, but who's going to really use it? We had such uptick in the use of that, even though it was really about performance and cost, primarily, we thought, in the media industry. But then we had customers like Neiman Marcus, Ancestry, Cube Research, really take advantage of using this feature that drives wicked fast performance with lower TCO. So I think that, you know, you can find a use case or something that fits

Starting point is 00:20:07 every different customer scenario. And that's one of the things that Amazon is so good at, is trying to figure out what does each customer need? What is the level of security? What is the level of performance? What are they really looking for and trying to fill that need? There's definitely a value in meeting customers where they are. Back when EFS and then its Windows equivalents came out, I was fairly harsh to the idea because from my perspective, if you're building something net new Greenfield, you don't necessarily want to use a shared file system in a cloud environment, more or less the effective way of doing these things with object stores, et cetera, et cetera. And I sat here in my ivory architecture tower and I wound up getting some feedback from the GM of that product. Hi,

Starting point is 00:20:49 Wayne. And the entire point was, okay, you can take that position if you'd like, but understand that not everyone has the option of throwing everything that they've built away and starting over from scratch. That seems like it is the, from my perspective, the San Francisco startup disease of anything older than 18 months is ready to be thrown away. But that's just not how the business works. It's not how the world works. And if you've got to run NFS or the SMB slash CIFS equivalent in a cloud environment, there's no better way to do it. And I started digging into the services and realized, yeah, I really should have had a more informed take on that when it first came out. There's something to be said from learning from our

Starting point is 00:21:27 customers. Absolutely. And can I pick up on another point, Corey, that you said that, you know, you can't throw everything out and start over. I mean, those are the customers that I've been working with for the last three years. They're enterprise customers, so they don't have the luxury of being, you know, a cloud native startup, which has advantage because they're beginning with native cloud services on Linux. And that's also why I'm so excited about another announcement that we made, which was BYOL on dedicated host and making that more cloud-like, right? Because we have so many customers today who are still running Windows Server, and they need a way to get that to the cloud. And instead of telling them they have to just

Starting point is 00:22:12 throw it out and get rid of it, we took a different approach. And the approach we took was, you want to continue to bring those licenses to AWS, but dedicated host is kind of a non-cloud-like experience, right? You have to have a dedicated machine to run that application on. So how could we take away, you know, that physical server that's dedicated to the single use of the customer and make it appear or seem like it was running EC2, an EC2 instance? So that's what we did. You know, we enabled our customers to be able to create a BYOL instance, just like they do any other instance. They can do that in the command line. They can do that in the GUI.

Starting point is 00:22:55 Um, to me, this was one of the most exciting announcements. Again, leveraging what you, what you were just talking about. I can't throw away everything away. How do I get that to the cloud and get that to that cloud so I can start my experiments? It's always easy to sit here and tear things down that are existing.

Starting point is 00:23:13 What are you doing with that ancient piece of crap? Oh, about $8 billion a year in revenue. Why do you ask? It feels like there's an aversion intact to anything legacy, by which we mean it makes money. There's a lot of pushback in from the quote unquote thought leaders of the world who are, oh, this is now the way to do it, the way and

Starting point is 00:23:33 the light. And here's our beautiful whiteboard architecture. I've never yet seen one of those. It was a realistic representation. Production, the real world, it's always messy. There's no way around that. And my biggest concern now is when people, well, one of them, there are many concerns, is that when people see these things on a stage somewhere at a conference, they're convinced rightly or wrongly that, oh, this company has it all figured out, whereas ours is garbage.

Starting point is 00:23:57 But I've been sitting in conference halls where someone from a company is talking about their migration or their beautiful architecture. And I turned to the person next to me and said, I'd love to work someplace like that. And the person next to me says, yeah, I would too. And they work at the speaker's company. It's conference wear for lack of a better term. We all tell stories that get to a point, but nothing is perfect. Nothing is idealized and the world is messy. And I think accepting that's important.

Starting point is 00:24:29 I agree with you. I love that conference wear, you know, and these are the companies that, like I said, I've been working with for the last three years, great companies, great IT shops that are looking to, you know, mix that legacy with the new world. And so I am, I was just so excited to work with them, not just because they're, they're big companies, you know, like Capital One, but because they have this need, and they really want to get to the new world. And, you know, they're developing training programs and, and education to get there. And I would tell you another, you know, another great idea that came up from one of those companies was single sign-on. So, you know, most of our, most companies overall, not just most of our companies, they use Active Directory. And so one of the things they kept

Starting point is 00:25:19 asking us is, look, you launch single sign-on and we can work with our existing AD on-prem, but because we use AD, we need to also be able to interface with Active Directory on Azure because every Office 365 needs that. So how can you help us? So one of my other favorite announcements, again, came from this need of leveraging that legacy. We provide support for Azure Active Directory. And you can do that through standard protocols. So you don't have to get locked into anybody. It gives you more flexibility in your overall cloud. But we also added in flexibility and multi-factor authentication. So you could use Google Authenticator or Microsoft Authenticator. And then we integrated it into the command line to make it easier for someone to sign in and stay in securely without having to change and with an

Starting point is 00:26:12 automated short-term credentials to eliminate that hassle of staying secure and freeing up that time for the developer, yada, yada, yada, all those great things. So this is one of the reasons I really love my job because my job was to help those legacy companies and even more so now help those companies figure out how to move and get there. And they want to get there and we're seeing them get there. And I think that's probably one of the most exciting things, other than seeing the CEO of Goldman Sachs DJ at reInvent last year. Yeah, that was definitely something. I heard the story. I knew that he effectively did that in his spare time. I did not expect to see him doing it on stage, and that was fantastic. I will ask you about the reInvent keynote, though. One of my recurring jokes has been that the head of Amazon's product strategy

Starting point is 00:27:07 is a Post-it note that says yes on it. And that is never more true than during the three-hour barrage of Andy standing on stage talking about new services and features. So we've long since passed the point where I can talk incredibly convincingly about services that don't really exist,

Starting point is 00:27:24 but no one at AWS would dare question it because maybe it's just not in their group. Maybe they haven't heard of it yet. So I promise not to do that, but I will ask you, what were some of your favorite releases that came out? Oh, wow. So I would tell you that one of my very favorite wasn't in my group, but the IDK for machine learning. So part of my passion, you know, when I went to college way back when I majored in computer science and math, and one of my minors was in artificial intelligence, which has changed a lot. And then I told you about my career at IBM, where I spent time developing training modules for Watson, which is IBM's AI. So this was so exciting to me that we now have SageMaker, which is essentially now a true IDK.

Starting point is 00:28:17 So I just thought that that was a neat announcement to make as a coder. One of my favorite quotes is that programming is the closest to magic that you'll ever have. And for me, that is so incredibly true because coding, you can create anything, you can really drive anything. And now, you know, with SageMaker, I'm just thinking, you know, SageMaker Studio that enables everything to be integrated for machine learning or notebooks that gives you that notebook experience with a quick start or the experiments enabling you to organize and track all of your experiments that you want to run, debugger, the model monitor, which I love because I love creating models, detecting the quality of your model and helping you to take corrective action. Really excited about that entire announcement, which I thought

Starting point is 00:29:18 was amazingly cool. And then if I switch back to my Windows hat, another, I guess Windows and Linux hat, another one of my super cool announcements that I love was Image Builder. I don't know if you caught that, but when I first started at AWS, the number one complaint my customers gave me is, I have to build a compliant Windows or Linux image for AWS. And when I do that, I have all this work, right? I have to create it. I have to manage it. I have to deploy it. I have to keep it in compliance. And so my team started working on this, really thinking about it because it is hard. So what we were able to release is Image Builder that automatically produces that new image and distributes it to AWS regions after you validate the test on it. And your test could be your test, could be some of the Amazon best practices. It helps you reduce the ability to build those compliant and up-to-date images. It's just, it was really one of my very favorite announcements. I got to do that announcement on stage. And when I did that, I think it got the most applause.

Starting point is 00:30:30 And I even had a couple of people stand up, which was super cool because we worked on it for so long. And it enables both Windows and Linux. We started building it just for Windows, but we made it for Linux as well. It enables customers to save so many different things. And I would say my last one, I know I'm really, I have a lot here, but the last one that I really loved, and I don't know how many caught it, was, again, for our Windows users, was the ability now to take Windows Server 2003 and 2008 and enable them to move up to the next version, but to encapsulate those 2003, 2008 APIs, move that up to 2006 or 2009 without refactoring.

Starting point is 00:31:24 And we do that through a program, but also through some code as well. move that up to 2006 or 2009 without refactoring. And we do that through a program, but also through some code as well. When you say a program, I assume that is not in the sense of, it's a bunch of code that compiles and we hand it to you. The program is in a organized system of people. That's right. You got it. We announced some partners who are able to perform that, like Smartronics and Accenture. But we also announced, I think it's important that it's not just a marketing program.

Starting point is 00:31:52 It's actually technology that enables you to package these legacy apps up so that it can run on new versions of Windows Server without having to refactor. That struck me as being something that is going to be transformative for an awful lot of companies because the technical debt of, sorry, the term sounds derogatory. Let's not even talk about it in that sense. The problem of having workloads that are not current or haven't been touched in a long time is the people who built them are often gone. No one knows all the edge cases of it. I mean, there's the worst programmer I ever met, heck, was myself six months ago.

Starting point is 00:32:29 When I do get blame and find out what moron wrote this and I'm said moron, it's, well, that tracks. It winds up being a terrible problem. And how do you wind up solving this if you don't have to tear an entire application apart and rebuild it just to move it? Suddenly that unlocks an awful lot of opportunity. I would further agree with you with what you say about the EC2 image builder. In hindsight, I should have seen it coming, I I was transitioning jobs every year or two because my primary employee skill set is getting fired. What is one of the first things I would always have to do when showing up in a new environment?

Starting point is 00:33:11 You set up certain things like the SFTP endpoint that then copies files to S3. That came out a year ago, which I was super thrilled about. Then now you always have to set up something with Packer or equivalent, an entire build pipeline to generate the golden AMI that you're going to use to spin things up in your environment. It's the same undifferentiated work that it shouldn't require a three-day project with bringing in a whole bunch of external dependencies to do that. So that is one of those things I'm very thrilled to see come out. And for better or worse, it's a little late for me just because A, I'm not doing engineering anymore. And B, I have jumped on board the serverless train, which means that I don't have to run computers anymore, or so they tell me. But man, is that transformative for an awful lot of shops.

Starting point is 00:33:57 I have to tell you, I had so many customers come up to me and say, thank you so much. I mean, literally thanking me for doing that and up to me and say, you know, thank you so much. I mean, literally thanking me for doing that and talking to me about how many people that was going to save for them. I just think that that was it was one of my one of my very favorite announcements for sure. As we talked about it, just because it it's not sexy, right? It's not ML because that was where I started. It's not that sexy announcement, but it's a real valuable announcement because it saves customers time and then they can put that time and those people into other things that are a

Starting point is 00:34:39 little bit sexier, but it enables them to do their jobs better. And that's what really makes me happy, is that personal connection and being able to help our customers do things at the light speed, if you would. It's the sort of thing that never makes a headline and never makes the front page of the keynote, but it's always worth looking at. One last thing I wanted to ask you about. You've been a passionate supporter of women in tech projects and movements for a long time. Can you tell me a little bit about that? Yes, I would love to talk about that. So I believe that, I believe and AWS believes that, you know, we're all about innovation. And the way that you innovate is you bring in diverse ideas. And if your employees look like

Starting point is 00:35:24 your customer, you're going to be able to come out with more innovations that are right for them. So first of all, I'll just say that diversity and working with women in tech and girls in tech, it shouldn't be just a nice to do. It really needs to be viewed as the business case of diversity. There is value in your innovation. There is value in just the different ideas that are generated. I'll just give you one case in point. If you look at data that comes out around diversity, companies who have a diverse leadership team

Starting point is 00:36:02 are 45% more likely to grow their market share and 70% more likely to capture a new market. And that's directly from a McKinsey report. So the data is there to support the value of diversity. One of the reasons that I'm really passionate about it is one of my mentors, Corey, always told me, you know, when you make it and everybody makes it every day of their lives, you have to reach back and pull someone along. So part of my mission has been, how can I help women who are already in tech? How can I help them do more? How can I help girls who are exploring tech? How can I help them get really excited about the potential of technology?

Starting point is 00:36:45 So, for example, one of the things that we had looked at at our recent conference was a drone show that was led by an all-female drone team from Intel, and they were supporting girls in tech. Girls need role models, and here is an all-female drone team that did, I don't know if you saw it, but the spectacular drone show that was there at our conference. So providing not only funding and money to get them into coding school and classes, but setting that great example. So I'm really passionate, very excited about helping others to see the value in technology and the fun of it too. It's super fun, right? It really is. It's also important to be as inclusive as possible. There's no value in having people who all look and think alike in the same room trying to build products.

Starting point is 00:37:37 At that point, you wind up with hilarious misfires. The more voices, the better. And I think that there are problems in this space that are significant. We're starting to see some advancement on there, but there's so much work yet to be done. I agree. And I don't want anybody to think I'm just talking about gender diversity. I think there's diversity across the board. So one of the interesting new facts I found was that more than one in three new businesses today are started by someone over the age of 50. So, you know, it's generational, it's cultural, it's everything. In fact,

Starting point is 00:38:14 one of our teams, I have to tell you this story, one of our teams was not innovating as fast as possible. And if you looked at them, you're like, wow, it's culturally diverse. It's generational diverse. It's gender diverse. What's going on? And we found out that they all graduated from the same school. So their frameworks and their mental model had all been trained by one school. So diversity is really about diversity of thought, just so you can gravitate to hearing all those ideas that you talked about. That's, I think, where a lot of the work remains to be done. It's a complicated series of issues. And it's one of those things that I regretfully suspect that we're not going to solve this in

Starting point is 00:38:58 my lifetime. But I think we can definitely make strides and get far further than we have. I completely agree. And I must say, if I could just kind of add one thing too that I think is so powerful. It's another just thought about helping others, Corey. One of the things I also love about Amazon, and I know we saw some of this, we've seen it a lot, but one of the reasons why I love Amazon, Amazon Web Services, as an example, is, you know, we have this, in my new role, we have this whole nonprofit group. And yesterday, we were just reviewing some of the impact, you know, it's not just about making money, It's also about doing good. I really believe in tech for good. had never heard of, and how Amazon is using machine learning and AI to help discover patterns and trends to help hopefully one day cure this disease.

Starting point is 00:40:17 So, you know, we've talked about a lot of things today. I think the bottom line, though, is that as you're starting the new year out, you've got to think about technology as a great enabler. It does allow you to do magic, but you should share that magic, not just with your company for earning money, but get your company to support diversity, inclusion, some of these other things that are tech for good, like what I love that you did at last year's reInvent conference with the shirts. You raised how much money for St. Jude's, right? 18,000. 18,000, which is surprisingly challenging to find a charitable cause that no one is on the

Starting point is 00:40:58 other side of except complete monsters. There's always going to be someone who said, well, why this cause and not the other cause? Well, that one's a good cause, but is it good enough? But kids with cancer is one of those things where it's hard to find something more serious and it's hard to find something that everyone can get behind in quite the same way. There are options, but it's one of those slam dunk things that I personally feel passionately about. So it was one of those things that just sort of tied together across a whole variety of box checking, as well as a cause that I'm, again, profoundly passionate about. Yeah. And, you know, if we jointly, Corey, could leave one message, I know everybody listening is all about tech.

Starting point is 00:41:53 I think what I would challenge you to do, you probably already set your New Year's resolutions, but set one to do something like what you did at our conference, where you just said, hey, buy a shirt and we're going to give the money here. Or coding for America or joining one of these efforts for helping human trafficking or curing disease. It's really about giving back. So I would hope that everybody listening would also take a challenge in 2020 to do something good, to do hashtag tech for good. Thank you so much for taking the time to speak with me today, Sandy. I appreciate it.

Starting point is 00:42:17 It's always cool. I wish we had a picture though that we could both open our mouths really wide, right? Oh, we can probably make that happen one of these days. If people want to learn more about what you have to say on this and many other topics, where can they find you? Well, I would love for them to go to either Twitter. It's Sandy underscore Carter.

Starting point is 00:42:37 I'm there with Corey almost every day. LinkedIn is another great way to catch up with me. It's just Sandy Carter. I'm also on Instagram and Facebook. And I will also give my email out. It's sandyct at amazon.com. If you've got a great suggestion for something on Windows or a new partner thing or just anything, your tech for good idea, email me as well.

Starting point is 00:43:02 I'll be happy to get back with you and chat with you as well. So, and Corey, I'm really honored to be on here. Really appreciate all the great work that you're doing both on tech for good, as well as just teaching tech and educating as well. So thank you for having me. Of course. Thank you. Once again, Sandy Carter, VP of partners and programs at AWS. I'm Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on iTunes. If you've hated this podcast, please leave a five-star review on iTunes and a fun comment. This has been this week's episode of Screaming in the Cloud.

Starting point is 00:43:43 You can also find more Corey at screaminginthecloud.com or wherever Fine Snark is sold. This has been a HumblePod production. Stay humble.

Screaming in the Cloud - A Conversation with AWS’ Sandy Carter, One of the Busiest Women in Tech

There aren't comments yet for this episode. Click on any sentence in the transcript to leave a comment.