How I Built This with Guy Raz - Figma: Dylan Field

Episode Date: June 16, 2025

The dashboard in your car – the interface on your Zoom screen … many of the products we interact with every day were created with the collaborative software Figma. Figma is a kind of Google Docs for design, created by Dylan Field and Evan Wallace after they won a Thiel fellowship in 2012. Dylan was just 20 when he became CEO. The only other job he’d had before that….? was college intern. He eventually figured out how to manage his team, and grew the company enough to attract a 20 billion dollar acquisition bid from Adobe. The deal fell through, but Figma continued to grow, and recently filed for an IPO.This episode was researched and produced by Kerry Thompson with music composed by Ramtin Arablouei. It was edited by Neva Grant. Our engineers were Patrick Murray and Jimmy Keeley.You can follow HIBT on X & Instagram, and email us at [e-mail]. Sign up for Guy’s free newsletter at guyraz.com or on Substack.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

This podcast is brought to you by Squarespace. I talk to entrepreneurs all the time who are looking for a way to upgrade their digital footprint. Well, whether you're just starting out or you're scaling your business, Squarespace is the easiest way to build a great website that stands out. It's an all-in-one website platform that gives you everything you need to claim your domain, showcase your products, and get paid. Anyone can use Squarespace's cutting-edge design tools to build an online presence that truly reflects what makes your business special.

There are templates, intuitive drag-and-drop editing, and even an AI-enhanced website builder. Then, Squarespace's built-in analytics tools help you make smarter business decisions. Review website traffic, learn where to focus engagement, and track revenue all in one place. Looking to grow your business, Squarespace even offers fast, easy business financing

through Squarespace capital. Go to Squarespace.com slash built for a free trial. And when you're ready to launch, use offer code built to save 10% off your first purchase of a website or domain. Loans issued by Celtic Bank and serviced by Stripe, all loans subject to credit approval. This show is in partnership with Airbnb. This past summer, I took my family to Vienna, and it was incredible. We spent our days wandering the old streets, stopping for coffee and pastries, visiting museums, and just soaking up the history of one of the most beautiful cities in the world. And one of the things that made the trip so special was the home we booked on Airbnb. It had tall windows, beautiful old details, and plenty of space for all of us. And being in that home on Airbnb, right in the middle of Vienna,

walking distance from so much of the city, made it feel less like a visit and more like we were actually living there. Plus, taking a trip is the perfect time to host your space on Airbnb. your place with all of its personal touches and its amazing location could make someone else's vacation even better your home might be worth more than you think find out how much at arbb.ca.ca They were just going, Dylan, you've got to be more commercial. I'm like, what does that mean? They're like, you've got to be more commercial. And I'm like, do you mean, do I have to like say more sales terminology and stuff like that?

Like, what are you getting at? And I think what they meant was price the product. And when this design leader came and said, we can't use it unless you price the product. I was like, oh, everyone, we got to go charge for the product as fast as we can. So I was a little dense on it, but it got there eventually. Welcome to How I Built This, a show about innovators, entrepreneurs, idealists, and the stories behind the movements they built. I'm Guy Raz, and on the show today, how Dylan Field left.

college to figure out a better way for designers to collaborate and built a company called Figma, now worth billions. If you've ever booked a trip on Airbnb, watched something on Netflix, or joined a Zoom call, you've interacted with a product that was designed using Figma. Figma is the platform behind the platforms, a tool that lets teams of designers collaborate in real time from anywhere in the world. And while that might sound obvious today, back in 2012, it was a pretty radical idea. At the time, real-time design collaboration was clunky and slow. Most people still emailed files back and forth.

Even designers were skeptical that something like Figma could work. But Dylan Field and his college friend Evan Wallace believed there was a better way. So much so that Dylan left Brown University at 19 after landing a Teal Fellowship to give the idea a shock. He had never managed a team, never built a company, and had never launched a product. It took four years of development before Figma officially launched, and even then, adoption didn't happen overnight. But eventually, it clicked. And in 2022, Adobe, one of Figma's biggest competitors, offered $20 billion to acquire it. But as you will hear, the deal was blocked by government regulators.

Today, Figma is used by some of the most recognizable companies in the world to design the apps and interfaces we use every day. But this story isn't just about software. It's about a young founder learning to build, lead, and grow up without a whole lot of experience to guide him. Dylan Field grew up in the late 1990s and early 2000s in Sonoma County, California. He was into math and computers from an early age, but also he did a lot of acting. even some paying gigs. You know, at five, five and a half, whatever I was, like, I could read, I could sit still. And I think in comparison to how I am now, I was actually a very, that was a cute kid.

You know, that's changed to puberty. We can get to that later. But as a kid, you know, was cute. And so I guess someone referred me to an agent and no major roles or anything, but lots of auditions and some commercial work, a little bit of TV work. So you were really, I mean, you were on this kind of path to becoming a child actor. I mean, I know you said that you didn't really land any major roles, but I read that you were, I mean, which is kind of crazy, you were in like a Windows XP commercial as a kid. Yeah. That was a funny one because there is a performance of Tommy the Who that the original actor who was going to play young Tommy felt through for because she refused to shave her head or cut her hair or other. they needed someone else

and so I got pulled in and this is a performance where where was the where was it? It was at SRJC San Jose Junior College Santa Rosa Junior College okay yep and then after that I got to be Michael and Peter Pan

also there at Santa Rosa and also at Santa Rosa Junior College but during their summer program which is really cool it's actually my most embarrassing moment in acting as a kid was during that production because I fell asleep on stage in that scene where in Peter Pan where all the kids are asleep and Wendy is talking to Peter.

And the actress playing Peter Pan gave him my cue and I was still asleep and she gave me my cue again, still asleep. And then she gave me a kick. And then I leapt up and gave my line. But yeah, I was like Dylan didn't get up. Anyway, but due to that production, I had the experience with stunt flying. and then that was what they're looking for for the XP commercial.

So it was kind of a fun chain of events that led to that one. So how did it, I mean, so you're doing all this community theater. What happened? Why am I not talking to an adult actor today? I mean, first of all, I was very thankful that, you know,

my parents, especially my mom, who was the one who was driving me all these places, was willing to do that, but also that she was never pushing me to do it. And I think at some point, the combination of like becoming a teenager, acne, braces, awkwardness in general, plus, you know, game mortars and math computers. Yeah. It's like, okay.

And then, hey, math and computers is pretty fun. So I started diving on that instead. Jill, and there's an article that was written about you, and we're going to talk about why later on in 2012 in the local paper, the Santa Rosa Press Democrat, which I still read. I still subscribe to, just if anyone's listening from the Santa Rosa Press Democrat. And your dad, Andy, is quoted in it. And it was on the occasion of you winning an award, which we're going to talk about later. And he said, you know, when Dylan was six, he was already solving algebra problems. And, you know, by the time he was in middle school, he was hanging out with a janitor who was kind of a math savant helping him learn more advanced mathematics.

First of all, were your parents kind of doing math problems with you as a kid? Were they mathematicians? Was that something that they were kind of exposing you to? Or how did you come to just become really fascinated with math? My mom was an elementary school teacher. And so I would press her for while we're waiting for things. I'd press her for, hey, give me more problems to solve. Who was the, I mean, apparently,

In middle school, there was a janitor. It sounds like, I mean, it sounds like Goodwill Hunting, almost. Yeah. So he was really cool. Yeah, he was very cerebral, very into math and physics. And I think the reason he took the janitor job was very much to just kind of think about stuff all day long and be in his head. And so I try to always cultivate friendships with people who are older than. than me. I think now that I'm sometimes the older one, it's like, okay, you're straight

at college. Like, there's a lot I could probably learn from you, you know? And he would tell me about different ideas and concepts that he was learning about and studying himself. And at some point, he said, well, look, the really cool stuff is improves. You should really learn a little bit of set theory. And so, but he was super sweet. I know that, I know that you also got really into computers when you were a kid. And then when it came time to go to college, you went to Brown in Rhode Island to study computer science

and I believe mathematics. And tell me a little bit about, you know, your time there because from what I read, you went through a bunch of different, like you were interested in computer science, but you were actually more interested in, like, art history classes. And I think you even explore, like, political science,

maybe thinking at a certain point, maybe law school, you know, which is great, right? That's like what college is for. But did you start to kind of, I don't know, get more interested in other things and less interested in computer science or computer programming? Yeah. I've always been curious about most everything. And at Brown, one of the best parts is there's no formal requirements for the school. Right. Than technically a writing requirement. You need to make sure that you can write. And yeah, I kept getting pulled back. to sort of Silicon Valley startups as something that I felt very engaged with.

Yeah, as you say, you kept getting pulled back because I think the first summer of your freshman year, you go and work for LinkedIn. You do a summer internship there back in California. Yeah, I met DJ Patil, who later on became the chief data science officer of America under the Obama administration. And DJ contacted me pretty early in my freshman year and said, hey, what are you doing this summer. You know, it was pretty informal at the time. That was kind of the process. And, yeah, DJ was great. You know, the start of the internship, he said, hey, you know, everyone at LinkedIn on this

team, you know, they all do something the first three months. They do something that's like really incredible and foundational. So you got to figure out that is for you. And I was like, oh, okay. And, you know, In the back of my head, I'm kind of searching for that challenge as well. And there was an end day, which is kind of like a hack day. And I kind of noticed that people were really excited about this idea of LinkedIn for good. Like, see if we can harness the power of LinkedIn to do good, whatever that means. Exactly. So that was kind of the idea is there a nonprofit aspect that we can explore, et cetera.

At the meantime, I saw a lecture from someone who was talking about. the work he had done to translate text messages for victims of the Haiti earthquake. But the issue was they didn't have enough Creole speakers. So they couldn't translate to the emergency responders. The text messages of people that were stuck in rubble, it was horrible. And I'm sitting there and going, my gosh, we've got all the data to know who the speakers of Crail are. And so it kind of spawned this idea of, okay, maybe there's some

way to connect people to nonprofits based on skills. So you ended up working on this project, LinkedIn for Good, which basically aggregated all of the, all of these skills that were available on the site. I guess it even caught the attention of the CEO of Jeff Weiner. Yeah, the real effort started after, to develop it started after I left my internship. Jeff Weiner certainly, you know, came out to me after I presented about the project, budgeted all hands. And yeah, after the all hands, he goes, hey, so like, you know, do you want to

keep going on LinkedIn? I said, well, I think I want to go back to school. Thank you, though. And he started thinking about starting something someday. I said, maybe. I said, well, if you do, call me, at least it's my recollection. His recollection is slightly better, which is, or a better story. His recollection is saying, hey, Dylan, are you going to start something someday? Maybe, I don't know. Well, if you do, I'll fund it. And I got to say, I like his version better, but I don't remember it quite that way. And foreshadding a little bit, we'll get to it. But a few years later, he did become one of your earliest investors in Figma. Yeah. He has been an incredible advisor and mentor and investor and investor in Figma and supporter from day one. Wow. All right. So you go back to Providence, Rhode Island and start your sophomore year and really getting more into design, right? Because you had done a lot of, you know, you'd been interested in web design, but you were a programmer, but you were getting more into design. And I guess the summer after your second year, you go work for this company called Flipboard, which I think they're still around. Yeah, they are. Yeah. And they basically created this.

way to look at at the internet, the web, look at a web page, but like you were flipping through a magazine. Yeah, so Flipboard was one of the first iPad apps that really took advantage of the iPad surface to explore what was possible. Yeah, it was so good. It looked so, so good. Yeah. And you ended up going to work there. They were also in California in the Bay Area. Yeah, they were in Palo. And, you know, it was a very buzzy company at the time. And it was a very buzzy company at the time. And it was, it was. It's just an absolutely gorgeous product. And, yeah, I just started to get to hang out with the designers. And I'd always been a really interesting design. And, you know, one thing that I got to learn at Flipboard was just really more about the history of typography, of layout. And I'd always been surrounded by magazines growing up.

my dad found some ways to like get crazy discounts in magazines through some coupon codes online or something like that. And so there's always just like endless magazines around the house. Yeah. And I guess the next year you go back to Flipboard to work there again for a while, I think this time in design. And then in your third year, Brown, you decide to apply for the Teal Fellowship, which is this fellowship or the winner again. It's a couple hundred thousand dollars to basically drop out of college and start a business. So did you have an idea in your mind of what you might want to do or even like who you might want to do it with? Well, I thought to myself, okay, there's no way I'm going to, you know, go start something if I'm not doing it with someone that I think is amazing.

And I thought, okay, the only person I'd start a company with and whatever way it goes, I'll learn from them. And it'll be an amazing experience because just being with them will be, you know, a gift into itself is Evan Wallace. Evan Wallace, who's a year older than you at Brown and just somebody you really respected and admired. Yeah. Evan was my TA for a computer vision class at the time. I said, hey, do you want to get dinner? We got dinner and I said, you know, you're about to graduate next semester. What are you going to do? and he goes, well, I've got offers from, you know, he lists all the places he had interned, Microsoft, Pixar. And he goes, you know, I just think that, like, I'll be probably not as challenged in those environments.

But, you know, it could be cool. We'll see. And by the way, Evan's not like a super cocky guy. Like, he is as humble as humble gets. But also, he was very clearly the most genius person I'd ever met. His nickname was CJ, computer Jesus, because Evan was basically on the computer every chance he got. And it turns out, if you spend 10, 12 hours a day programming from a young age, every single day, you are a really good programmer. Yeah. But yeah, Evan and I got dinner and we started talking about, okay, well, would you ever start a company with me? And he goes, yeah, I consider that that might be more fun than joining a bigger company.

And I always said, great, well, let's meet up some more and see if there's any ideas we like. And so what did you guys start to bat around? What kind of ideas? Kind of everything. So the question that we were trying to answer was, why now? like what is the change that's happening in the world that would make a idea interesting you know i had a huge list you know as did he and kind of merged them and then started striking him out and at the end we got we had two that we thought were kind of interesting one was one that

I was more bullish and excited about one was something that he was more excited about but we're both kind of interesting the other one too and the two were drones and webGL webGL which is basically a way to do 2D and 3D graphics in a web page, right? Mm-hmm. And so this just made it, this is going to factor into what he would eventually create

because this was a revolutionary change. WebGL introduced frictionless, this frictionless ability to see like 3D renderings in a web page, which today we take for granted. But in 2011, that was still quite radical, revolutionary.

So yeah, so one of the directions, WebGL, which Evan was way ahead of everybody else on. And I was also a fan of too. I thought that there's so much you could do with it, but I also had some concerns. And the other one was drones. I looked at the world in late 2011 and said, okay, still need to figure out the use cases,

but I'm pretty sure that quadcopters and sort of what will come out of that will be huge. and I think we were both right. I want to go back to what made you compelled you to apply to this fellowship in the fall of in 2011. I mean, because they want you to drop out of school. But why did you decide to do this when you were absolutely convinced that you were going to graduate from college? Well, it wasn't necessarily like a dropout situation. You can always go back.

Right. Yeah. And plenty of people take leave of absence. So I think that was my mindset, first of all. Like, even if the startup flames out, I learn a lot from Evan, had some savings from the acting days. And at the same time, I thought that the probability of this happening was very low. Well, I get the TL Fellowship, almost certainly not. Well, Evan decided to do this with me.

Who knows? But it'll be fun to explore. And, you know, I'll put an application in just in case. So you get the application in just, you know, an hour or two before the deadline. You submit, they have all these questions about you. They want to know what publications you've been in. So, of course, you were written about in the Brown student newspaper a couple of times. So you were also in an NPR story in 2011, which was about one of your mentors, DJ Patil. And he, in this article, he's quoted as saying, oh, this kid is just phenomenal. I've known him since he was 16. And so that's a pretty great endorsement to have that guy saying in this article. But the other thing that I noticed about your application, because there are 500 people applied for this that year. There's a question that they ask, which is something like, you know, tell us something counterintuitive, like what the world strongly believes in that most people, you know, that most people think is true, but that you just disagree with. It's just something that you completely think is wrong.

Your answer is, I'm going to just read a little bit of it, is it says, tell us what you think is true, but that most people think is not true. and you write, chocolate is repulsive. And then you go into a whole essay about why you hate chocolate, you think it's horrible, you can't stand the smell of it, and then you include the fact

that apparently 2% of the population doesn't like chocolate, and then Nestle did research into this, and they found that maybe there's... Small end, but yes. Maybe there's an imbalance of gut bacteria that's... Because to most people, you're thinking,

chocolate is repulsive? It's insane. Who thinks that? Everybody knows chocolate is delicious. But this is truly a counterintuitive idea. And I have to think that that really caught their eye because all of a sudden it's just like a left turn. Totally not connected to technology. You know, it's funny.

I was really proud of that essay. And I had a lot of fun writing it because I really don't like chocolate. And people have always thought that was the weirdest thing ever. So I thought I was answering the question, the purest way possible. and maybe even being a bit metacentrarian. But I think that they want counterintuitive thinkers. And I mean, you're competing against, you know, 500 of the smartest, you know, kids in the country under 20. And I guess your parents initially were not psyched about you really pursuing this because they wanted you to finish school.

Your mom and dad wanted you to finish college. Yeah, they had, they were, you know, savers and I had my own savings as well. But they were not rich. They had solid, you know, middle-class careers. And they had put a ton of resources to my education. So the idea of, you know, potentially squandering that is like, what are you doing? And with Evan, we would talk every weekend, even as this process was ongoing and just kind of keep moving forward, talking about ideas to prototype. and the thing we were exploring then was using WebGL,

but it was, again, that's the hammer and everything was a nail. So basically, we were exploring how do you take a photograph and convert it into a 3D scene? And so we thought maybe there's a way to go and explore many different tools that will let people do the sort of things that you can accomplish in high-end programs such as Photoshop or 3D tools, but do them in a way that anyone can access and really democratize that. All right.

So you guys are batting around ideas and you really kind of land on this idea of using WebGL to create something that will give, that will sort of empower people to be designers somehow. You're not really sure what it's going to be. And then you become a finalist for this fellowship. You get to the final round, 40 people under 20. And you get it. You're picked. You present. You're sent to San Francisco. You fly to San Francisco. You present. And my parents came. Your parents came. And they're getting more excited now.

And they got bought in because they met all these other finalists and went, oh. Or as my dad put it, he goes, I always thought you were weird, but these people are weird too. That's right. And so you find out at the end of your junior year, May of 2012, that you get the fellowship. Evan is about to graduate and he's going to join you. You're going to move to California back home and you're going to start working on this. So you took technically, I think you took a leave of absence. You did not drop out of Brown, right? Yeah. Yeah. I mean, there's a and, you know, these fellowships get so much attention because it's such a big deal. I mean, you know, Peter Thiel is encouraging people under 20 who have great ideas to pursue them. Yeah. I was excited about the fellowship and also the other people that were taking the fellow. ship were, or applying, were just so cool. And the chance just to have this community around of people that like literally knew what I was going through and spent time with them, it was just socially very helpful and also very inspiring. People would push you and say, hey, like, why are you thinking small? Think bigger. And that actually, I think, was a big input to why we got to where we eventually headed for FICMA.

All right. So you, in an article, an article written about that time, I think the press Democrat wrote a piece about you. You were still, I don't want to say vague, but you were still like working out what this is going to be because you're starting to work on this. And it was described at the time as like Photoshop in a browser, you know, journalists, and I say this as somebody who was a journalist, I think for well-intentioned reasons, like to simplify things so people can understand, right, so they can visualize what it is. And that was kind of initially how people described it. And I guess that summer, it was just you and Evan kind of working together. And what were you, tell me what you guys were literally doing every day. Well, so first of all, we didn't start until August because Evan wanted to graduate, of course. And we got started a bit later than when we received the fellowship. And

The start coincided with media that the fellowship had kind of offered up. And so, you know, the actual like first or second day of doing the fellowship starting to work with Evan, I flew out to New York with my mom to be on the Today Show. And I had no idea what we're doing yet because we hadn't barely started. And they probably were like, and today we're going to introduce you to a whiz kid genius, Dylan Field. Welcome to the Today Show, and they were saying, and tell us what are you going to do? How are you going to change the world? Yeah, I gave them a very vague answer because we really didn't know. When we come back in just a moment, Dylan and Evan launch a tool that will change how designers work,

only to learn that a lot of designers don't really want to change how they work. Stay with us. I'm Guy Raz, and you're listening to How I Built This. Hey, welcome back to How I Built This. I'm Guy Raz. So it's the summer of 2012 and Dylan and his partner Evan are gearing up for the Teal Fellowship, working on an idea that has something to do with design. The first thing we looked at was 2D face swapping. So basically, you know, I got your face, they got my face, how can I take your face and swap it onto my face? Kind of a cool party trick.

But with something called Busan blending, which Evan found a way to do very, fast in real time in the browser with some graphics wizardry. We were able to make it so that we had an amazing demo in just like a week. So wait, just to interrupt for a sec, you weren't necessarily like playing around with these ideas. Sounds like you weren't going for like the serious designer crowd, maybe like more like people who wanted to make memes. Yeah, I mean, it was that first one, yes. I think we were also looking at more consumer cases that were not as meme-oriented as well. At some point, later on, we literally create a meme creator.

That was the darkest week of Figma. You know, I was pitching Evan saying, look, I've done the research. I've looked at the data. This meme thing, you know, we're just used to it because it's internet culture and we see it online all the time and we share them with our friends. But like, most people haven't discovered it yet. Like, it's a very early part of an exponential trend around memes. memes are going to be way bigger than we could ever possibly imagine. We should make a meme creator. And Evan's like, are you serious? And so he kind of humored me for a week or so, like five days.

We made a meme generator. And, you know, it was a very good meme generator. And, you know, at the end of the week, we just kind of looked each other. And I'm like going, man, I dropped out of Brown for this. And Evan's going, I think I'm going to quit. And it was a good sign of like, we're going to work on some more serious stuff. So you guys are working on this. And just so I can understand this, you know, today, oftentimes Figma is kind of described in shorthand as Google Docs, but for images, for graphics, for design. When did that idea start to converge?

Was it in 2013 when the two of you thought, well, what if we build a collaboration tool like Google Docs, but for design, for, for, for, for, for, for, for, for, for, was it? graphics or images. Yeah, so I think that that experience of working at Flipboard, working with the designers there, it'd always been my mind as something that was amazing to be part of this design process,

and Flipboard was way ahead of its time. And the collaboration didn't exist. It was emailing files or at best you put them in a Dropbox folder, but you know. And oftentimes, if you were a designer working collaboratively, you might start to work on something that was emailed to you, fix it up,

but then only to realize that this is like already two days old and people already moved on. Yeah, people already done other stuff with it. And I, you know, Evan and I both grew up using Google Docs, you know, playing multiplayer games. And so the nature of real-time collaboration, that was native to us. And just kind of like obviously the way that things should work, that said, we weren't sure about the market size for design. You know, I looked at the Bureau of Labor Statistics, and it said there is something like 200,000 designers in the United States, or web designers it is.

And so that's obviously like a pretty small number. Yeah. And at the same time, we felt like there's something there. We felt like maybe this is a starting point. We go broader afterwards into other areas, but let's try it out. And just to just to clarify, You looked at the Bureau of Labor Statistics numbers and saw that in 2013, there were only 200,000 web designers in the U.S., which is kind of hard to believe. Because that's a small market, if that's who your target audience was, but you had a hunch that given the tools that were available, which are clunky and there were plugins, and they weren't really, they didn't make collaboration easy, you felt like there was a real opportunity here.

Did you get, I mean, and this is still, you're still miles away from having a product ready to go. But did you hear that from people? Did you have an opportunity to interview designers or to talk to them and ask them what they wanted? Yeah. So both I had been working as a designer at Flipboard or design intern. I went and talked with other designers that I knew. I also started talking and researching and learning about how companies were growing their design teams. and there's something that seemed very off because these companies were investing a lot in design.

You know, Facebook was acquiring entire design agencies to try to make their design team bigger. And it was like, wait, how is it the case that all this hiring is going on, and yet there's only a few hundred thousand web designers in the United States? Like, either the number is wrong or it's growing so fast, that it doesn't matter. In either way, we can go into other areas later, so I think let's go. Let's go do this. And at first, we were very focused on

what are the things that we can just do so much better from the tool standpoint, not the collaborative standpoint, but as an individual user, what are the breakthroughs we can introduce? Can we make a better way to create grids and guides? Also, how do we honestly build a project of this magnitude on the web? That was something that, you know, we had a lot of technical work to do to figure out what was possible. All right.

So you have, so you guys are really focusing, doubling down on this idea. And because of the TL Fellowship, I'm sure there are a lot of people who are interested in, you know, maybe even blindly investing in whatever you're. I'm sure there are people who are like, I'm just going to put, you know, half a million dollars down on every single one of these people. You had already had a relationship with Jeff Wiener, the CEO of LinkedIn. And he had told you like two years before, hey, if you ever start something, get in touch with me. And in fact, you guys went to him and a group of other people to raise some money for seed funding, which you did. He raised almost $4 million since June of 2013. So about a year after you got the T.O Fellowship, what did you, what was the, I mean, at that point, was it a fully formed idea?

Was it, were you able to articulate what this was going to be? You know, not yet. You know, I honestly, I've looked back to that pitch. And I don't know if I would invest in myself if I saw it, you know, back in 2013, it was, it was very vague. It was not clear yet like what we were going to do exactly, and exactly the strategy was. I think that came very shortly afterwards. But we raised just a bit ahead of being concrete on our direction. There was one guy.

You really wanted to be involved with this. And this was a guy named John Lilly, who was, he had been the CEO of Mozilla and was now partner Greylock. And I imagine you wanted him involved because of his experience with Mozilla, you know, running a browser business. But he did not, he decided he was not going to invest at the seed level. That he didn't feel like you guys really knew what you were going to do. And normally, not normally, oftentimes people just move on. And they're like, okay, he doesn't want to do it. But you were really, you wanted him.

involved, right? And I guess you felt like you had to figure out a way to get him to convince him that this was going to be something. Tell me a little bit about that relationship. Well, I mean, John is just an excellent human. And immediately I was just so

impressed. Like, not only was he super high integrity, it was just very clear and principled, but he was also his belief, his care about design. It was off the chart and then said, hey, I'm down to keep in touch. I like you guys. Let's just keep

talking. You know, at some point, maybe a year and a half or so later, John said, you know, if you're ever thinking about raising another round, let me know. Right. So it would be another year and a half before he would factor in again financially. But during that year and a half, you had almost $4 million to work with, which is a pretty good, pretty good runway. And now you begin to build something, right? In your mind, when did you expect to have a product ready for, at least for some people to play with? Oh, I was totally unrealistic. I'd have to check the deck.

But I think we probably expected it to be like, you know, a year or so, maybe a year and a half. but yeah, we thought it would be a pretty straight shot. It was not. It took a while. So just to kind of put this in context, I'm going to dig into this, it would take about two years before you had something that you could let designers play with. And you had a team, I think around 10 people that you were able to bring on to help you and Evan build this thing. Now, you're the CEO, right?

Evan was the CTO technically or officially? Yes. Okay. And both of you are like, I mean, he's a little bit older, but you're, what, I don't know, 21 maybe by this point? 20. And your only experience, only, you had experience, but it was as an intern, basically, a paid intern. You had been an intern for a bunch of companies, and now you're 20 and you are a very nice guy, but zero experience as a leader or a manager,

understandably, what 20-year-olds have that experience. You weren't even a camp counselor, right? I've been a RA, but yeah. Okay, you've been a resident advisor on your dorm, right? But now you're running a business of 10 people, probably a bunch of them older than you, if not all of them. And I think everyone was older than me at some point.

And you were also building this product. So tell me a little bit about being a manager, and running a team. How did you, how did that work out? Well, I think that we had a very clear product roadmap and we all felt that there was something here. But I could have done a better job of helping people see it through like conversations with customers and whatnot. I was having those conversations. You know, I'd kind of come back, share all my notes. But what I found is that if employees are not talking with user directly, they just don't see it the same.

same way. And they don't understand the pain that people have unless they can actually interact with folks and hear about it firsthand. And I think, you know, there's plenty of things that get done on the manager's side to be better. But I think it was, it didn't really, like, blow up per se until a little later. And what was the blow up about? Because at some point, everybody on the team, like 10 people that confronted you. And they were. were like, I don't know, what did they say to you? Yeah, so at that point, we had raised our A round from John Lilly. In December of 2015, okay, yep.

Yep, and moved to Stimberstow. And, you know, also I was, like, definitely going through a hard time personally. You know, my dad had been diagnosed with cancer, and I certainly was not an experienced manager. I was still kind of getting the mechanics right around how do you just, set goals and motivate people and we still haven't shipped anything, you know, and now people are kind of looking at the clock and going, is this ever going to ship? Is this just like endless? What would you, Dylan, what would you do? Because I don't think you were yelling at people or you were mistreating people. Were you micromanaging? Were you slowing the process down?

Tell me what you were doing that was causing frustration among your team. Micromanaging is a good way to describe it. perhaps even a mild way. I think I had for quite a while thought about every aspect of the product experience we wanted to build. And I, you know, felt a lot of pressure to get something out there. And so I would just kind of come in and say, hey, this is the way we're going to do it. Turns out when you hire smart people, they have ideas too. And also turns out that sometimes Those ideas are like really, really excellent. But I think the time urgency combined with like having thought about it a lot made me lean into, you know, we just got to do it this way, let's go.

And that was not a fun environment to be in, I think. When you say people are getting frustrated because a product wasn't ready to be shipped, was that because of you? You kept saying it's just not ready, it's not good enough yet? Well, we validated that. So we went out and found all these kinds. companies in Silicon Valley in San Francisco especially. And we talked with, you know, I don't know, it must have been dozens of companies. We showed them Figma.

And just kind of like a flat response. They were not too interested. They're just kind of like, oh, cool. So you were basically trying, I mean, you had tested this and people were based, the feedback wasn't great. So you couldn't put it out there. yet. And when your team came to you, I mean, what did they say? Did they say, Dylan, you know, you're not managing well? Like, how do they confront you? Yeah, I mean, people were clearly not happy. They felt like I needed help. They were right. I actually did need help. I needed someone to help on the management side. We were not going to build a scale fast enough without bringing someone else on to help. To help. run a part of the company. I just kind of like felt offended though, I think, because, you know,

I obviously parted my heart and soul into this. And yeah, I felt bad because I at some point, it not me, I did raise my voice. I mean, just just in response to one of the kindest guys in our team who was saying something that was actually quite constructive. And probably you were under a lot of pressure because you had now raised money and there's real money on the table and you probably felt like personally, you know, this was on you to make something. How did you start to take in that feedback and criticism and I don't know, maybe change the way you operated? Well, I first called John Lilly, we talked about it and said, hey, something happened and, you know, I'm taking a few days away from the office.

I got to clear my head. And John's like, whoa, okay. And, you know, he knew I had been going through stuff with my dad and that things were getting pretty tough medically. And, you know, he went into the office and, you know, talk with folks. And I think his sort of sense was, okay, like, this is knowledgeable. don't raise your voice. But like, we just got to get this thing shipped and we can get this back on track.

And I guess fortunately, right, right, right around this time, you were able to hire someone, a lead engineer named Shokulamoto, who was a guy who worked at a lot of other companies like Adobe. And he was identified as somebody who could, I guess, kind of help steady the ship about. bit? Well, he was identified as someone who had just like really unique experience that was relevant to what we're doing. And yeah, I think he came in and week one was like, man, what company I just joined? This is some weird, weird stuff going on here. But very quickly, he kind of got a sense of where people are at and said, Dylan, we got to ship this thing. Let's figure out what it is. It's wrong. Why people are not resonating with it. But, you know, my sense is there's

only a few features missing. We already know that we need to redesign it visually. And he did a presentation to the team end of week, first week, about like kind of rallying cry of, you know, we've all been working so hard, so long, we're really close. Here's what's going to take. Here's the gap. And we rallied. We got it out. This is in December of 2015, just to clarify, you say you got it out, but this is in, this is closed. It was just for beta users, right? Yeah. We made sure that we had a really great early blog post, formed a press strategy, created a launch date, got out there. And it was controversial, honestly.

It was not universally well received. It was very mixed reviews. Very mixed. So I think, and again, it was closed. So it's not like everyone's using it and giving it mixed reviews. It was mixed reviews to the perception of what it could be. And, you know, there are some people that immediately got it, but a lot of people went, why would I want to design collaboratively? Right. Because it was seen as a very kind of solitary thing. Like, this is my vision. I'm going to design it.

You can maybe make some improvements, but this is my thing. Yeah, a lot of designers at that point were coming from an agency culture where, you know, you go explore, you come up with a few solutions for the client. You present, you know, three solutions. And then you have a grand reveal of like, here is the big, amazing thing that you should obviously do. And that's just not the way that product development should work on a team internally. Instead, you know, there's a wide range of things you consider.

You collaboratively need to work through them. But people, you know, we're so used to that agency method of working that, you know, some of the initial comments in the launch were stuff like, if this is the future of design, I'm changing careers. I mean, people, a lot of the early comments were like, and this is interesting because This is 2015. People, I mean,

this idea that design being a collaborative thing was not a thing necessarily. Like one comment was, was a camel is a horse designed by committee. Yep. Essentially saying like, right, if,

if you design things by committee, it's going to be, it's going to suck. Yeah, I mean, I think that that was maybe the mainstream view of the design culture then, but there were also a lot of people

have signed up for the wait list. And then we started to, to every week, let more people off the wait list into the product. And we saw right away that people were using it, even without everything we knew that they needed. And then every time we added additional functionality to the product, we saw that conversion of people going from, okay, you're off the wait list to you're actually using it. It would go up. So early customers like Koda, Notion, Microsoft, Uber, mindbody. You know, there was a bunch that started to really use the platform.

Did you find that people were starting to use this in ways that you didn't anticipate? Because initially it was for, right, web design, software design. But eventually, you know, people would use it. Designers and agencies would use it for, like, restaurant menus or, like, even the interface on a screen on an airplane. Did you anticipate that or did that happen organically by users? So much happened organically. It was kind of like anything visual that could be created, you know, ended up being created at some point in Figma. All right. Dylan, that year, I just want to ask you, because we're talking about you professionally focused on this, trying to put this out there. But this is a tough year. I mean, your dad is very sick.

How are you balancing this really intensive? development, but also going back and forth to see him. Yeah, I mean, I was doing everything good to try to be there for him. And also at the same time, I mean, he did really want me to be, you know, progressing Figma. He was really excited for what we're doing. Yeah, it was definitely back and forth. There were days where things were really dark and I would just not be in the office and I'd go up and see him. It was unclear sort of like how long he had.

He was in just such immense pain, but his body was, you know, he was, he was an athlete his entire life. So he's a strong dude. And even with the immense amounts of pain that comes with cancer spread everywhere, including bone, he was, his body was just holding on. And yeah, so that launch happened, you know, he was very proud. see it. But yeah, he passed quite soon after. He was able to see the beginnings of what you would go on to become very well known for, which is amazing. Meantime, you guys are building this thing. You launch it to general use in October of 2016, and it was free, right? Initially, it was free. And you really wanted, I think, you guys.

guys wanted to keep it free as long as you could. You knew eventually you had to have some business model, right? Because you were, you know, you raised money. You had a series A. You raised $14 million in that series A in December of 2015. But eventually you had to figure out a plan. What, I mean, did you, is that, was that thinking that, okay, we're going to make this free for as long as we can, but we will eventually have to charge for it? Or was that not the plan? We definitely were planning to charge. But knowing what to charge, how to charge, you know, we wanted to kind of watch people use the product first. And also, I personally, after all this time of being told it's not ready by a lot of people, I was not yet in the mindset of like, it's working.

Right. I just had in my head, there's so much more we got to build. When we come back in just a moment, Figma gains more trouble. then loses an acquisition worth $20 billion. Stay with us. I'm Guy Raz, and you're listening to How I Built This. Hey, welcome back to How I Built This. I'm Guy Raz. So it's October 2016, and Dylan and Evan have finally released Figma to the general public. They're not charging for it yet, but they soon discover that they probably should.

You found out that Microsoft, they had a... designers there who were really using it. But I guess corporate said, hey, you can't keep using this product because it's a free product. And it's not reliable enough. If you really, we can't trust it. It's not, who knows what's going to happen to it. But the idea was that because it was free, it was somehow not fully baked. And that was sort of a kick in your butt, right?

You thought, well, we better start charging for it. We're going to lose Microsoft. Yeah. Microsoft was actually really cool about. the way they did this. One of their design leaders came to our office and spent some real time with me. And he, I think, was sussing out, like, is, are they serious or not? And at the end, he goes, you know, your tool is free. I said, I know, we got to make some improvements, I think, before we pay. He goes, well, we're going to have to probably rip it out at Microsoft if you

don't charge us soon because we've got to make sure you stay in business. So crazy. Yeah. And, you know, at that point, um, I just had a conversation with our board where they took me out to lunch. It was like a pretty hard conversation, I think, for them. And they were just going, Dylan, you got to be more commercial. I'm like, what does that mean? And they're like, you got to be more commercial. And I'm like, do you mean, do I have to like say more sales terminology and stuff like that?

Like, what are you getting at? And I think what they meant was price the product. And then, you know, that didn't really break through. But when this design leader came and said, we can't use it unless. you priced the product. I was like, oh, everyone, we got to go charge for the product as fast as we can. So I was a little dense on it, but it got there eventually. So you start charging for this. And meantime, you guys are presumably working on ways to make it better. You start in August of 2012 and you're shipping something out in December of 2015. So it's a long time. Just for a moment,

During that time, that three-year period, when you didn't have anything yet to show for, were you feeling anxious? Were you feeling like, did you have a lot of sleepless nights? I think the sleepless nights were more because I was just so excited about what was possible to build. At least once we got on the track of what would become Figma, I think between when we started and when we got to, we're going to go build a design tool. That period, I had it sleepless nights because we were. We didn't know what we were doing. Yeah. But once we were on that track and we had it validated and I had talked to people and I knew what they needed,

no, I mean, like the, it was more just my head was spinning about there's so much that's possible. Weren't you getting impatient? Oh, yeah, for sure, impatient. I mean, I'm always been impatient about like how fast can we build this thing. That's just my default state. But anxious is the wrong word. I was, you know, very confident in our approach. No one else was doing it the way we were doing it.

it was just like how do we get this to market? How do we get this in front of people? And how do we build a great product? I mean, it's not, I don't think it's an exaggeration to say that from the time you've released it to general availability, it was a hit. I mean, people really adopted it. Designers really began to adopt it. I mean, the parallel I can think of, it's not the best parallel. It's a little bit, it's a little bit as Instagram or Snap.

I mean, not obviously the same kind of virality because that appears. to just a mass consumer audience. But for designers, and your intuition about companies hiring more designers was true. It proved correct. So were you, I mean, when people start to adopt this pretty quickly in large numbers, were you like, yep, I knew it? Well, it's more about, like, what's the next thing to go do? How do we go and make sure that we, you know, there's still, even as people, adopting. There was a lot of things that they told us they needed. And those were the same things

that would cause people not to adopt. And then separately, we started to see that our assumptions about the ways teams work were maybe correct for small teams, but not as correct for large teams. Larger teams needed different ways to organize their work. They needed different security things. And so we need to meet the needs of these larger teams as well. meantime, as you started to really explode in growth and usage, and I mean, we're going to can't talk about every funding round, but you do another, I mean, 2015 was the last round, and then there was a series B in 2018 and then a series C in 2019, which valued the company at half a billion dollars.

Were you, I mean, did you start to see competitors come out? I mean, you must have by that point start to attract the. attention of, you know, the Adobe's of the world. Yeah, I know. Literally, I mean, Adobe came out with Adobe X-D, which was their offering, not web-based, but a very solid and interesting desktop application. We also saw, and this is probably the one that for me felt more concerning at the time, there was a company called Envision, which had been around since we started.

Because Envision was started in 2011, and they had put out a competing product what by when? I believe it was around 2017 was when they announced it. And that to you felt like a real threat. We were pretty worried because the mind share they had was so huge.

And they made this huge announcement and said, we're coming out with InVision Studio. And, you know, I remember for our series B round, even with all the traction we were starting to get and how inevitable

it was starting to seem. There were certain VCs that, you know, they take the meeting, but then they go at the end of the meeting, you know, look, very impressed to what you've done and a great job. But I just cannot reconcile this with the work in Vision's doing. Like, I'm sorry. I mean, just to jump ahead and Vision eventually shut down in 2024, they don't exist anymore. But it is amazing, right? Because at the time, they could have been the Figma Killer, right? And that was the prediction by some people. But how did you guys, you had an advantage. You had an advantage. because you'd been working on it longer. But were you looking at what they were doing to make sure you were staying ahead of the curve? Well, I mean, yeah, we looked at, of course, their product and why people were resonating with it. But within the day, it was like, no, I think our roadmap is correct. And we just continued to push ahead to the things that we thought people really needed.

And I feel like that was the right strategy. All right. So you guys are just moving forward and you're growing at a pace. And by 2020, you raise a series D at a $2 billion valuation. Now, again, you know, you started this in 2012. So kind of, right? So this is eight years on. And by 2020, you guys have really, I mean, you're growing. Yeah. The start of 2020, about 100. employees. End of 2020, we were 23, 240. Wow. And so we were growing at pretty rapid speed. And we're also opening up presences internationally. At the start of 2020, we put into motion opening our first office outside the United States in London. We recruited a leader for that. And, you know, it kind of opened right as COVID started and everyone went home. Yeah. But the thing that happened I definitely didn't anticipate, which was because of the multiplayer aspect of being

this infinite canvas, people started to hang out in Figma. Yes. You didn't need to be in an office anymore. You could do this all, you could basically collaborate, but you didn't have to be in the same room. Yeah, it was, it was pretty wild to see this behavior emerge. And at first, it was like, across companies, people were illustrating virtual studies together to, like, have a sense of community. And then it was within teams. We started hearing about how people were brainstorming together and using it as like a hangout space or remember one day Slack went down and people were, you know, typing in text boxes in Figma for their Slack replacement comms for the day. Obviously it's not made for that. And it's kind of like we're watching all this

behavior and going, wow, we've always seen whiteboarding, diagramming, brainstorming cases in Figma, I think we need to go build like a virtual whiteboard and diagramming tool. And we started to dig into how are people using Figma. And the thing that kind of kept coming back for this use case of ideation, brainstorming in a remote way was fun. Like people wanted to have fun while they were doing it. That was the way they were drawing out the best ideas. They were, there's something about the Figma.

that was enjoyable. And that element of fun became the differentiator, you know, doing things like if you wave your cursor around a lot, it turns into a giant hand and you can high-five somebody. Or how do you make it so you can, you know, put stamps on things or have emoji reactions? COVID, of course, this was the perfect product for COVID because all of us in remote work. Because all of a sudden you could do, you had this collaborative tool that could be done remotely. And so adoption increases. You come out of COVID, you know, just a really well-placed product.

And for a brief moment, you guys had not brief, but for a moment you had considered going public but decided against it. And then September of 2022, Adobe announces they are going to acquire Figma for $20 billion. So $10 billion over your last fundraise. And that's a big deal. I mean, this was a, you know, arguably, certainly more than arguably a competitor, they were going to acquire you for $20 billion, which was, I'm sure, extremely exciting, you know, to get that kind of validation. Yeah, I mean, I think the validation was less. what we cared about.

Yeah, there's lots of validation from the world. But it was obviously like something that kind of came out of left field for a lot of people of the company that that was not what they expected us to go do. But what made us excited about this Adobe acquisition was, first of all, we have a lot of respect for Adobe. Always have. And the chance to continue our work at Figma there, while also doing a lot to help them rethink what could Creative Cloud,

you know, other traditional products look like, an age of AI in a way that, you know, really was design-centric. That was so exciting to me personally. Part of that agreement was that if for any reason it didn't happen, they would, you know, pay a billion dollars. I have to imagine that on your side, there was maybe some concern that the government would not approve it, but immediately after it was announced the Department of Justice, you know, European Commission, UK regulatory bodies announced that they were going to investigate this as an antitrust violation of antitrust law. and they begin this investigation, which would now last for over a year. Were you nervous?

I mean, we did a story about Harry's Razors a few years ago on the show, and similar thing happened. You know, they were going to be acquired by a bigger brand. There was an antitrust investigation that was launched and eventually unraveled. Did you feel like you guys would be able to withstand this? Well, first of all, obviously I never would have agreed to an acquisition. by Adobe if I thought it wouldn't go through. Yeah. So the breakup fee was something that I was advised that we should have.

So we included as part of the negotiation. But honestly, it was a pretty fast part of the negotiation. You know, we were focused much more on, you know, the amount of time I spent talking through the Adobe, how exactly, you know, will the setup work? Like, will we have figma.com emails or will we have Adobe.com emails? Yes, right. Like, that part of it was, you know, probably 100x longer, not joking. then, you know, a conversation by the breakup fee

because I just didn't think there's any reason why that would be an issue. Our lawyers said that it would almost certainly go through. And so I also felt like, you know, Figma's all about software design development and Adobe was not. So it's just, to me, it was despite, you know, some of the earlier aspects of the company

when we first started thinking about some of the creative use cases, it just felt very complimentary to me. The deal basically by mutual agreement, you guys decided to abandon this. And in December of 2023, it became clear that the government would not allow this at that time. Maybe it would be different today. Who knows it's all depends on who's running the Justice Department. And that was it.

I mean, they paid you a breakup fee. It was a billion dollars. But here's the thing I'm curious about. I mean, you know, Adobe was a competitor. All of a sudden, they were an acquirer. And I think rightly so. You were all in. You were Mr.

Team Adobe, as I would be if I was in that position. Adobe is a great company. They make great products. But they were very well aware. I mean, they'd been in your data room. They'd really looked at your product. They knew how it worked. They knew what you were doing.

Now, no longer could you join forces. So they're once again a competitor. And how does that? It's like... They're really not. I mean... They're not. Okay.

They're very focused on other aspects of their business. And that was made abundantly clear. in the antitrust process to all the regulators too. I don't know if they believed Adobe, but that was what they said, and that's how they behaved since. The regulators believed this is going to be anti-competitive. Your argument is that they're not competing against your product at all.

Correct. But what was good was we kept accelerating and coming out of it, you know, obviously, you know, it's a hard thing for the team to absorb that, okay, we thought it was going to be one thing, and we're going to all work at Adobe. and actually, no, we're still in hard-charging startup mode. And if anything, we've got to prove ourselves even more now. And the team, I think, just there's a really a sense of relief,

not because people weren't excited about Adobe, but because we finally had certainty. And then we just rallied. Like the launch of Debt mode came a few months later. Yeah. And this basically allows you to take designs and translate them into code. Yeah, and also make it so that you can help designers explain to developers how to go build products in the right ways. And that was a huge launch for us. It meant it so that 30% of our

users who are developers, we could provide them with a much better experience in Figma. And, you know, we really just started to invest in our platforms so that we could go build more products and also improve the stuff we have. I'm curious. I mean, you guys are, you know, you're a much bigger company, I think 1,600 employees, right? That's where now, yeah. And cities around the world. But we are entering and we're already seeing it every single day, a really just a rapid pace of sort of innovation around artificial intelligence. I mean, we're talking now, you know, here by the time this airs, who knows what's going to be available.

Just a couple weeks ago, you know, chat GPT said, oh, you can turn anything into a studio jibli. or a Simpsons thing, and, you know, everyone was doing that. And now you're seeing people animate whole, you know, Tom and Jerry cartoons based on what they're writing into an AI platform. Products like Figma, even this podcast, right, they depend on the creativity of people like me talking into a microphone. But I can tell you right now, within five years, AI generated podcasts will be, they already are pretty good. that will be so good that people will make money out for them. And my value will probably be going, doing things live or people trusting that it's really me and not an AI that just sounds like me and mimics my voice and my mannerisms and the questions I ask. I have to imagine that this is something that is also top of mind because if it requires teams of really smart designers to collaborate and put something together now, it doesn't take a huge leap of imagination, a figment of our manufacturing.

so to speak, to imagine that, you know, with a couple of sentences, people will be able to generate the things that they're generating in Figma now that take days or weeks or months. I think what becomes differentiator, the differentiator is design. It's craft. It's how it works. It's brand. And as we look at the future, that's what I believe will still be the differentiator for software. It's going to be that craft. And I think that the value of design of good design, will actually go up even more in this environment. And can you create a piece of software that has some design with a prompt? Absolutely. Can you explore the entire option space and figure out what it is that you should ship? I think that requires human judgment to go navigate that and to figure out what is the right approach.

And I think we're still very early in any level of AI being applied. to that process. So I'm actually more bullish today than I've ever been on the role of design and software process. Dylan, Evan left the company. We didn't mention this. I think shortly after the pandemic, he wanted, he was sort of wanted to just kind of move on. And understandable is a lot of, you know, it's probably a really hard work, you know, to get to where the company got to.

And are you guys still in regular touch? Yeah. Evan is still one of the people that I look up to most in the world. And that was why I was so sad to you left because he's somebody that genuinely, like, I have so much respect for. So, yeah, he's an amazing, amazing guy. And the work he's done after Figma 2 on the open source side has been incredible. No surprise. You know, I'm sure over certain various rounds you were able to take some money off the table.

and you did not grow up wealthy, but you will certainly are and certainly will be even more so. I mean, the company's last, I mean, $20 billion acquisition offer from Adobe is quite significant. And you're, you know, you're young, very young. You're, gosh, how old are you, 30? 33. 33? Yeah. Many founders, we talked to on the show, don't even start until they're 33.

You know, really get things going at 33, 40, 45. If you could, I don't know, look out into the, first of all, into the future, you know, what do you, yeah, what do you think you want to be? I mean, do you imagine in 15 years you're still going to be running this company that you started? You know, I think that the chance to work on a platform like Figma and to impact an industry like this, it's truly once in the lifetime. opportunity and the more that I get to know other companies and whether it's an investment or just friendship, watch other founders, the more I appreciate how unique this experience and opportunity is for us. And I just think about the vision that we started with. Like, I can't think of a better thing to work on. When you think about, you know, the journey you

took and where you are now. I mean, so many things happened because you sort of manifested them, but also there was a lot of really just fortunate encounters, you know, getting to LinkedIn and managing to meet the CEO and, you know, all these different things. And, and, you know, all those connections over the years would play out, you know, these characters would come back into your life, in and out of your life. And here you are, you're just 33. And overseeing a company that's, you know, multi-billion dollar valued, you know, billions of dollars

and buy and eat, by some accounts, does over $600 million in revenue a year. You know, when you think about where you got to now, how much do you attribute it to luck? How much do you attribute it to the work you put in? Oh, wow. There's a lot of luck, not just in the connect. along the way and the ways that folks have helped, and I really care to pay that forward

and tried to. But also, I think, the timing. I mean, if we had started this a few years earlier, we wouldn't have had WebGL. A few years later, maybe someone else would have already been at it. And that timing is truly lucky. The chance to interact and intersect with Evan and the fact they were the same place at the same time, I mean, that was luck for sure. Yeah. But, But also I think, yeah, I, I, you know, there's always the question you're back your mind of like, with an incredibly talented team of people, how much am I adding versus how much is this amazing group of people humans around me adding? I think, you know, I look back at the acting from childhood and whatnot and just not being

afraid of failure. And even the days where we get punched in the face, it's like, great. You get back up and you keep running at the same. thing. What do you think was the key factor in making you not afraid of failure? Looking back as a kid, I went on all these editions. There are so many that you get rejected right away. And then sometimes, you know, you get to the final edition for like a big, big part. And it's actually like two or three people in the room and they actually look just like you. Then it's kind of harder to blame them on a look. But it's like, okay, well, for

reason they had what they're looking for and I didn't at this time. But it always felt like there's another one ahead. It's about playing over a long period of time. And the more that you can keep going, the more you can win. That's Figma CEO and co-founder Dylan Field. Shortly after we did this interview, and about a year after the deal with Adobe fell through, Figma filed for an IPO. Hey, thanks so much for listening to the show this week. Please make sure to click the follow button on your podcast app so you never miss a new episode of the show. And if you're interested in insights, ideas, and lessons from some of the world's greatest entrepreneurs, please sign up for my newsletter at gairozz.com or on Substack.

This episode was produced by Carrie Thompson with music composed by Routina and Bluie. It was edited by Neva Grant with research help from Casey Herman. Our engineers were Patrick Murray and Jimmy Keely. Our production staff also includes Alex Chung, J.C. Howard, Carla Estabez, Sam Paulson, John Isabella, Andrea Bruce, and Elaine Coates. I'm Guy Raz, and you've been listening to How I Built This.