Skip to content
YC Root AccessYC Root Access

How Olivier Pomel Built Datadog By Refusing Every Shortcut

In this fireside at Startup School Paris, Datadog CEO Olivier Pomel reflects on the journey and challenges of building one of the defining companies of the cloud era. Apply to Y Combinator: https://www.ycombinator.com/apply Work at a startup: https://www.ycombinator.com/jobs Chapters: 00:00 — Intro 00:57 — A Chip on Your Shoulder 01:52 — From France to New York 03:29 — How Olivier Met Alexis 05:06 — The Secret to a 15-Year Co-founder Marriage 07:33 — Building in the Early Cloud 10:44 — How Olivier Still Runs the Company 13:39 — When to Ask for Approval (and When Not To) 15:14 — How Datadog Decides What to Build Next 17:53 — 25 Products, 8,000 People 18:51 — Surviving the Pandemic Lockup 20:19 — Winning the AI Wave 23:21 — The Dream of the Machine That Fixes Itself 24:10 — AI Inside Datadog 26:25 — Advice to 2010 Olivier 27:40 — Hire Slow, Stay Sane

Garry TanhostOlivier Pomelguest
Aug 20, 202629mWatch on YouTube ↗

EVERY SPOKEN WORD

  1. 0:000:57

    Intro

    1. GT

      [upbeat music] Today, I welcome Olivier Pomel, the co-founder and CEO of Datadog. He created Datadog with Alexis back in 2010 just to help engineers figure out what was happening in their cloud. Now he's built that company into defining company of the cloud era. Welcome, Olivier.

    2. OP

      Great to be here.

    3. GT

      Great to have you. Uh, so we were chatting before about your first YC experience actually, was not today, was back in 2010. Tell me what happened then.

    4. OP

      Y- yes, so we, we, we actually applied to YC in 2010. Uh, we got an interview, and we got rejected.

    5. GT

      [laughs] I'm sorry to learn that.

    6. OP

      So I s- I still have, you know, the, uh, the email from PG at the time, and, uh, you know, it turns out... So he was saying at the time that we were building a platform, but the platform was only as successful as its first product.

    7. GT

      Mm-hmm.

    8. OP

      And, uh, you know, our little revenge on life has been that we did make the platform successful in the end. [laughs]

    9. GT

      [laughs]

  2. 0:571:52

    A Chip on Your Shoulder

    1. GT

      Do you think it actually helped you in some way to, to show, uh, us, to show him, uh, wrong?

    2. OP

      I, I think... So first of all, I think many people who start companies, uh, go through a lot of rejection initially.

    3. GT

      Mm-hmm.

    4. OP

      And I think that's normal. Um, I think it's good, you know, to give you reasons to prove people wrong and-

    5. GT

      True

    6. OP

      ... you know, put a, a chip on your shoulder. And, and also, you know, I think the, the fear to, uh, f- fail-

    7. GT

      Mm-hmm

    8. OP

      ... that you feel initially, I think, at least in our case, it helped really build up the culture of the company, you know, making sure we buil- we were so obsessed about building something that was valuable. We were so obsessed about building a, a good business-

    9. GT

      Mm-hmm

    10. OP

      ... a business that could be self-sustainable in case we couldn't raise money. Um, and so all of that, I think, to this day remains the culture of the company, and we owe that to the, the difficulties early on.

    11. GT

      I'm so happy to learn that, uh, we actually helped you [laughs] in the end. That's awesome. Uh, let's go back to the early days, uh, because you were born in France.

  3. 1:523:29

    From France to New York

    1. OP

      Yeah.

    2. GT

      And then you moved to the US after... Was that after college?

    3. OP

      Yes, so I had a, had an internship at the end-

    4. GT

      Mm-hmm

    5. OP

      ... of college in New York in, uh, in research-

    6. GT

      Mm-hmm

    7. OP

      ... at IBM at the time. And, uh, I, I thought I would say, stay for six months, and I ended up, you know, I'm still there.

    8. GT

      You're still there. [laughs]

    9. OP

      Yes.

    10. GT

      How long have you been living there?

    11. OP

      So it's been, like, 26 years now.

    12. GT

      Wow, okay.

    13. OP

      Uh, it's been a while. Um-

    14. GT

      So you pretty much moved there just at the time of the bubble, the dot-com.

    15. OP

      Yes.

    16. GT

      Okay.

    17. OP

      So I lived through the, the, uh, the end of the dot-com boom, and I actually worked in startup during the dot-com boom, which was-

    18. GT

      Was an experience.

    19. OP

      Yeah, it was, it was super ex- it was weird, you know, because you could tell that things were happening that, you know, didn't make complete business sense.

    20. GT

      Mm-hmm.

    21. OP

      You know, so for example, the, the CFO of one of our, of the startups, uh, every day went to the most expensive pastry shop in town and bought pastries for the engineers.

    22. GT

      [laughs]

    23. OP

      Um, I think that was a, that was a red flag maybe, thinking about it.

    24. GT

      Maybe. [laughs] I guess you don't do that today.

    25. OP

      Yeah, you don't, we don't, we don't do that, no.

    26. GT

      That's not the thing you, you learned from them.

    27. OP

      Yes, but so I think the world was full of promise then. Then, of course, the, uh, the, the dot-com, you know, boom turned into a dot-com crash. We've been through all of that. There were a few years after that where it didn't look like technology would be worth anything ever again.

    28. GT

      Mm-hmm.

    29. OP

      Uh, so I, I stayed in New York, and my, my co-founder for Datadog, Alexis, also stayed in New York.

    30. GT

      But I guess you worked elsewhere at the time.

  4. 3:295:06

    How Olivier Met Alexis

    1. OP

      No, we-

    2. GT

      ... or you knew him from before?

    3. OP

      Oh, we, we met actually in briefly in school in France.

    4. GT

      Okay.

    5. OP

      And the, the funny story here is, um, uh, I was part of the team that ran the campus network.

    6. GT

      Okay.

    7. OP

      And Alexis was caught hacking on the campus network, and so he was court-martialed by the student body, and he was sentenced to disconnection, and I carried out the sentence.

    8. GT

      [laughs] That's a great way to get to know someone.

    9. OP

      Yes, so I... And we didn't really interact all that much. You know, I thought he was this black hat guy, you know? Uh, and then we ended up finding each other again at that IBM, uh, internship basically. So he was there, too. Uh-

    10. GT

      And then you worked again together the next time, the next company you joined.

    11. OP

      Yes, and then we worked together in a total of four or five companies, you know? So-

    12. GT

      So you never worked in any place without him.

    13. OP

      Yeah, basically. I mean, we, we always bring the other. Like, you know, maybe one of us would go somewhere, and then two or three months later, we'd bring the other here. So-

    14. GT

      So that's a strong relationship.

    15. OP

      Yeah, yes.

    16. GT

      And then, and then you co-founded Datadog together.

    17. OP

      Yes.

    18. GT

      And you're still working together there.

    19. OP

      Yes.

    20. GT

      Any secret of keeping that kind of marriage [laughs] lasting like that?

    21. OP

      Yeah. Well, I mean, look, it's a... I think it takes, it takes effort. For one thing, before we started a company, because starting a company is pretty hard.

    22. GT

      Mm-hmm.

    23. OP

      Uh, before we started a company, we had known each other and worked together for more than 10 years, and so we had tested a lot of the, you know, different ways the, the relationship can go. You know, and we're also good friends, um, so, and, and that helped quite a bit. Um, after that, I think as, uh, as we've grown Datadog, like, we've made sure we kept a lot of space for, uh, talking to each other.

    24. GT

      Mm-hmm.

    25. OP

      You know, so we have these regular lunches and things like that where the, the whole point is just to talk. Um, and

  5. 5:067:33

    The Secret to a 15-Year Co-founder Marriage

    1. OP

      I think-

    2. GT

      Like no agenda.

    3. OP

      No.

    4. GT

      Just open-ended conversation.

    5. OP

      Yes, and, and there's one extra thing which is very important, which is anytime there's a big decision to make, so for example, sell or not sell. Like, you know-

    6. GT

      Right

    7. OP

      ... as you grow a company, um, you're going to have folks, you know, every now and then that will try and buy you out. Um, and these are big decisions, and-

    8. GT

      And did you decide after getting a real offer, or did you decide to not even open the conversation?

    9. OP

      We, we, we had those conversation where we, when we had offers or when, when folks were pretty serious with us. And it's very important in those cases to make sure that you're on the same page, you know, because that's what could get, can cause companies to blow up is when, uh, one of the founders, uh, kind of wanted to sell and the other one didn't. But, you know, one maybe didn't really tell the other or, you know, they told them what they thought they wanted to hear. But then, you know, it turns into a problem later on. Like, so it's very important to spend a lot of time talking on those point to make sure you really understand what each other want, you know?

    10. GT

      You bet. It's very easy, uh, in hindsight now to, to say yes, of course, that was the right decision not to sell. But I guess at that time it's a lot of money you leave on the table, uh- And there is no guarantee that your company's going to be successful.

    11. OP

      Yes. And you know, when I, when I started Datadog, I remember seeing, um, like companies that didn't sell for, you know, refuse an offer for 200 million, and I thought, "Wait, what kind of a, of a, you know-

    12. GT

      [laughs]

    13. OP

      ... who, who refuses 200 million?" Um, and then, you know, we refused that, and then we refused 10 times that, and then, you know, refused, you know, more than that even. Uh, I think the question is always-

    14. GT

      When, when you became public, what was the first, uh, uh, cap of the company?

    15. OP

      So we, we went public at, so the, the, the go public price was around seven and a half billion.

    16. GT

      Okay.

    17. OP

      And we very quickly traded at 10, 12, uh, up from that.

    18. GT

      And then a rollercoaster to a-

    19. OP

      And then, and then rollercoaster

    20. GT

      ... to kind of like much more today.

    21. OP

      Yes. Today we're around 80.

    22. GT

      Mm-hmm.

    23. OP

      Um, but at the time it was, uh, it was around that. And we, you know, we've refused lo- large offers along the way, and again, the, the thinking there is always, um, what's the upside? How do we, how do we think about the business? Are we, are we done with what we wanted to do? Is there, you know, 5X, 10X more we can do? Can we see? Do we believe in it? Do we want to do it? You know, is it exciting enough for us?

    24. GT

      Yeah.

    25. OP

      And that's what, what drives the decision.

    26. GT

      What are you going to do with your life after? [laughs]

    27. OP

      Yes. Yes.

    28. GT

      Do you retire?

    29. OP

      Yes. Yes.

    30. GT

      It's kind of like a-

  6. 7:3310:44

    Building in the Early Cloud

    1. GT

      but before being that successful, uh, I mean, the early days were not that easy, right?

    2. OP

      I know.

    3. GT

      'Cause when you started, it was nearly pre-cl- the very early days of the cloud, right?

    4. OP

      Yes. Yes.

    5. GT

      How did you approach that?

    6. OP

      Yeah, so it was, it was, uh, so it was very hard from a, a understand the market perspective. So we, Alexis and I didn't come from systems management, so most of the people who started companies in our space used to work for a vendor that made software, you know-

    7. GT

      Mm-hmm

    8. OP

      ... that sold software for that. We didn't have that. We also didn't come from a hyperscaler, so we didn't come from Google or, you know, one of the places that was operating at super large scale, and maybe, you know, folks had some glimpse of the technology that, that-

    9. GT

      Mm-hmm

    10. OP

      ... you know, can, can, can, can, uh, run that or the technology that's coming for the rest of the world. So because of that, it was very, very difficult for us to convince investors initially, so, and we mentioned YC, but, you know, uh, pretty much every single other VC also passed on us at the time. Um, so it was a very humbling experience.

    11. GT

      A lot of people will regret today, I guess. [laughs]

    12. OP

      Well, I mean-

    13. GT

      But some of them-

    14. OP

      Some of them, some of them invested later, right?

    15. GT

      Okay.

    16. OP

      You know, so that's, uh, that's the thing with, uh, with investors. There's always a next round. You know, maybe not for YC, but you know, for everybody else-

    17. GT

      Yes

    18. OP

      ... there's always a next round. Um, and um, the, the other part of it though is because we didn't come from the, um, the, the space, uh, we, we sort of saw things a little bit differently. Uh, our starting point was not, "Hey, let's take that existing product category and make it better." Our sta- our starting point was, "Hey, there's this huge problem. Like Dev and Ops don't talk to each other, and they fight all the time, and can we bring them into, uh, into, uh, under one roof and into one platform?"

    19. GT

      Mm-hmm.

    20. OP

      Um, so we saw that in a way that I don't think the rest was seeing it because we were living it on the user side. Um, we... What we didn't really fully understand was the importance of the cloud and the fact that, um, what we were doing was right at the center of it. You know, so disintermediating, bringing Dev and Ops together, actually that's big part of the cloud adoption. And of course we, at the time in 2010, you know, Amazon was a, was a, or AWS was the only game in town.

    21. GT

      Yeah.

    22. OP

      And it was a toy. Um, and companies, real companies would, were telling you that they were, were never going to use that.

    23. GT

      Yeah. Nobody was ever going to move to the cloud, right?

    24. OP

      Yes, exactly. And, and of course-

    25. GT

      And then it happens. [laughs]

    26. OP

      Yeah. Which it happens. It was extremely broad, extremely deep. Um, and uh, so that was a big part of our success.

    27. GT

      It took a, it took a... When I compare that to how fast people are adopting AI, for example, I mean, cloud, it took 10 years to get to full adoption.

    28. OP

      Yes.

    29. GT

      And, uh, in a way you were lucky. I mean, lucky. Uh, you are smart, but like you kind of like, uh, ended up at the center of that, uh, revolution.

    30. OP

      Yeah.

  7. 10:4413:39

    How Olivier Still Runs the Company

    1. GT

      Yeah. So, uh, one thing that came back often when I was, uh, discussing with, uh, ex-Datadog, uh, we have quite a few founders-

    2. OP

      Mm-hmm

    3. GT

      ... who came from Datadog or got acquired by you-

    4. OP

      Mm-hmm

    5. GT

      ... were on the other side of the M&A after, um, uh, mentioned h- the culture and how you as the founder are still very much heavily involved in like some product decision and like that you don't... Yeah, you are not at the strategic whatever power point level-

    6. OP

      Mm-hmm

    7. GT

      ... at all. Can you tell us a little more about how you see that and how you make these decisions?

    8. OP

      Y- yes, so there, there's something that's very important is that I and the rest of the management team-

    9. GT

      Mm-hmm

    10. OP

      ... um, have to, uh, understand what really happens on the ground.

    11. GT

      Mm-hmm.

    12. OP

      Like, you know, the problem you have as the company grows is that you develop these, uh, these beautiful stories. You know, people tend to manage up. Um, they want to be able to, uh, tell good news to management, you know? Um, and that's, that's human.

    13. GT

      Yes.

    14. OP

      That's just the way people are wired, right? Um, and so everything, uh, I do there in terms of the systems we put in place is to force people to look down instead of up, so to look at what's actually happening, what's happening with the customers, what's happening with the product, what's happening with the technology, what's working and not working.

    15. GT

      And concretely, what does that, uh, what does it mean day to day?

    16. OP

      So day to day, what I do is I, I sample a lot of the stuff.

    17. GT

      Mm-hmm.

    18. OP

      So I sample... I, I'm going to read, um, support requests.

    19. GT

      Mm-hmm.

    20. OP

      I'm going to read sales conversations. I'm going to read, um, actually I read all of the product briefs, like all of the product releases-

    21. GT

      Mm-hmm

    22. OP

      ... and everything we do to make sure we're understanding where exa- exactly what's going on there. And what I will do is, uh, occasionally I will reply, and I will ask question like, you know, "Hey, what's going on there?" Or, you know, "I don't understand this part." Or... And You know, very often, like, the first thing that happens after-

    23. GT

      Yeah

    24. OP

      ... that is the person who wrote that email or, you know, uh, put in that conversation in the system says, "Why, why, why is he looking at that?" [laughs] Um, and, and what it does is, is it kind of it jolts people a little bit, and also forces the local management chain to look down and fear, and people ask themselves, "I better understand what's going on there because I may be asked about it."

    25. GT

      Right.

    26. OP

      And on an ongoing basis, it forces people to, uh, to understand exactly the reality under them as opposed to, uh, you know, just weaving a beautiful message. You know, on my end, you know, it sort of trains the machine. You know? Like, that, uh, uh, I, I get a sense of reality-

    27. GT

      Yeah

    28. OP

      ... a simple reality, and then I can also figure out what agrees and doesn't agree with the stories I see at the higher level, you know.

    29. GT

      That's your own training data.

    30. OP

      Yes. Yes.

  8. 13:3915:14

    When to Ask for Approval (and When Not To)

    1. OP

      so we try to set up in a way that, that, you know, where feedback or executive feedback in particular is, uh, is possible-

    2. GT

      Mm-hmm

    3. OP

      ... but not required. So things are going to move along anyway.

    4. GT

      Okay.

    5. OP

      And they're going to move along with a number of communication points where, you know, you see what's happening, you see what's going to be released, or you see what has been released. Uh, and feedback can happen at any point there, but people don't wait for it. There's a few specific, you know, hard changes. For example, when you change the pricing and packaging of some products or things that can have a large impact and that, that are hard to back out of, um-

    6. GT

      Yeah

    7. OP

      ... that, you know, you have some pre-approvals. But for pretty much everything we build, people just push it up, um, and maybe there's feedback, maybe there's no feedback.

    8. GT

      So if it's, uh, life-sustaining for the company, of course you have-

    9. OP

      Yes

    10. GT

      ... like, you are like a filter. Uh, but if it's like relatively low-stake decisions-

    11. OP

      Yeah

    12. GT

      ... nobody's waiting for anyone.

    13. OP

      Or, you know, high stakes, but, you know, you can, you can reverse them easily.

    14. GT

      Mm-hmm.

    15. OP

      Or... You know, it's very easy, like, in, in, um, uh, when in B2B, it's very easy also to test some products-

    16. GT

      Yeah

    17. OP

      ... with some customers, make some changes for some customers, see how it works in the... And, and that's, that's actually how we build in general. Like, we see at a small, small scale with some customers how it works, you know, whether it, it improves things for them or not. Um, and then we, we roll that out more broadly.

    18. GT

      So you started with, uh, just, uh, infra monitoring.

    19. OP

      Mm-hmm.

    20. GT

      Like, uh, I think you were not even calling that observability yet, and then you expanded to many other, like, aspects of, uh, observability as a, as a high-level term. Like, how do you decide to build a new product? Um, like, what's your process

  9. 15:1417:53

    How Datadog Decides What to Build Next

    1. GT

      here?

    2. OP

      Yeah. So I mean, mostly we, we see what our customers do with our product.

    3. GT

      Mm-hmm.

    4. OP

      Uh, we see what kind of situation they put us in, and what kind of extensions and scripting and other things they build around us, and that gives us an idea of the problems they have and also where, where they think we belong. And so that, uh, for example, when we expanded from infrastructure monitoring at the time to, uh, APM, you know, tracing applications basically-

    5. GT

      Yeah

    6. OP

      ... we were seeing our customers build, you know, simple versions of that themselves on top of our platform, and so it was pretty clear, you know, they wanted us to do that.

    7. GT

      Yeah, you had to do it yourself. [laughs]

    8. OP

      Yes. And we see the same-- We saw the same thing when we, uh, we saw customers, uh, doing security automation with us, like instrumenting, uh, their security posture and doing security automation with us, so that was pretty clear that we, there was something we could do for them, uh, in that area. So that's really what drives most of the, the new, uh, um, entry points, yeah.

    9. GT

      Does that come from the teams, like, uh, who are seeing that day-to-day once they interact with customers?

    10. OP

      Yeah.

    11. GT

      Or is that some top-down-

    12. OP

      Yeah

    13. GT

      ... approach here?

    14. OP

      So there's, there's actually three parts. Uh, there's one part which is customer feedback.

    15. GT

      Okay.

    16. OP

      And customer feedback is, uh, I mean, I would say the majority of the changes we make.

    17. GT

      Mm-hmm.

    18. OP

      Uh, the good thing about customer feedback is that you're generally right. Like, you have enough customers, you have, you know, feedback, and usually it's right. The bad thing about customer feedback is that it's often very incremental.

    19. GT

      Mm.

    20. OP

      You know, so, you know, "I want, fix that button, please," or, "I need another integration," or, you know, um-

    21. GT

      "We want the faster horses."

    22. OP

      Yes, yes. And that's great, but you do all of that. But in addition to that, there's the more top-down, uh, you know, which I, uh, begrudgingly call strategic, uh, which-

    23. GT

      [laughs] It's not a word you like to use

    24. OP

      ... I, I, I hate that word. Um, but basically, hey, we know we're going to new areas that are a little bit different. There's less direct feedback from customers about it, but we know it's going to be important, and we see we have proof points that it will be relevant for us.

    25. GT

      Yes.

    26. OP

      So you do some of that. Um, you're wrong more often when you do that-

    27. GT

      Mm-hmm

    28. OP

      ... um, but you need to do it. And then the last part is complete bottom-up, and complete bottom-up is the engineering teams or the product teams, uh, solved a problem that they just, they thought needed solving, and we're building products out of that. And-

    29. GT

      Oh, it could be an internal need or it could be anything.

    30. OP

      Yeah. Could be we built an internal platform for something and we want to productize it. Could be-

  10. 17:5318:51

    25 Products, 8,000 People

    1. OP

      innovation.

    2. GT

      And so how many, uh, how many products do you have today?

    3. OP

      Uh, we have, like, 25 that we charge for.

    4. GT

      25 Products publicly released-

    5. OP

      Yes

    6. GT

      ... you can buy. Okay.

    7. OP

      Yes, yes, yes.

    8. GT

      And, uh, and what, how many compa- how many employees?

    9. OP

      We have 8,000 employees.

    10. GT

      8,000.

    11. OP

      Yeah.

    12. GT

      Okay. So that's kind of like a complex organization to get right here.

    13. OP

      Yes.

    14. GT

      Okay.

    15. OP

      But, but, you know, the, the way the products are adopted is, is somewhat similar to, um, what you might see, you know, at a cloud provider like an AWS or, you know, so the-

    16. GT

      Hopefully, hopefully better.

    17. OP

      Yes. Well, that's, that's the whole point, but the, the, the point here is you don't, you know- You don't have 25 different sales processes and sales teams and everything, so that's much simpler from that perspective.

    18. GT

      Uh, that makes sense. Um, and then, uh, and then there was that AI kind of like a complete disruption of the business and the market, right? Uh, how did you go through that? I guess, uh, were you taken by surprise? Did that affect you? It feels like, uh, the markets, once you are public, of course, markets is more volatile.

    19. OP

      Yeah.

    20. GT

      How did it

  11. 18:5120:19

    Surviving the Pandemic Lockup

    1. GT

      react?

    2. OP

      Yeah. I mean, market volatility, I think we're kind of used to.

    3. GT

      Yeah.

    4. OP

      You know, so we, uh, we-- So we went public in t- uh, 2019.

    5. GT

      Mm-hmm.

    6. OP

      And our-

    7. GT

      Pre-pandemic.

    8. OP

      Yeah, pre-pandemic.

    9. GT

      You probably went through up and downs and-

    10. OP

      Yeah

    11. GT

      ... up and downs there.

    12. OP

      Yeah, I mean, our lockup expired the day of the lockdowns. Uh, so ma- huge market crash at the same day or the, the same day our lockup expired. Uh, the stock was down like crazy. Uh, everybody was watching in horror at the time. Also, I mean, it was-- the world was pretty scary too at the time, if you remember.

    13. GT

      Yeah. Nobody would-- knew what would, uh-

    14. OP

      Yes

    15. GT

      ... what, uh, would come next.

    16. OP

      Um, and it probably ended up being worse than what we thought at the time too, like in terms of how long it lasted. Um, but-

    17. GT

      But maybe business-wise, it wasn't as bad as you expected.

    18. OP

      No, business-wise, it was, it was actually a seesaw. You know, the market crashed, and the market went, went back up very quickly. And, and then we've seen more gyrations like that over time. So markets going up and down, I think we, we're used to.

    19. GT

      Mm-hmm.

    20. OP

      We actually educate the company quite a bit on that. So every quarter, you know, we have a, an all-hands where we go through all of the results.

    21. GT

      Mm-hmm.

    22. OP

      Um, and we always end up with a slide that says, you know, the, uh, in the short term, the, uh, the markets, the st- the stock market is a voting machine. Uh, in the long term, uh, it's a weighing machine.

    23. GT

      Mm.

    24. OP

      And so, hey, what happens today doesn't matter. What ha- what really matters is we build enough of the right things, we find enough of the right customers for it, we deliver the right service, and then, you know, everything will be fine.

    25. GT

      Oh, okay. Okay, makes sense. How about the AI impact? Like, uh, I guess the market reacted to you being the incumbent. Like-

    26. OP

      Yeah

    27. GT

      ... early on you were kind of like the disruptor.

    28. OP

      Yeah.

    29. GT

      But

  12. 20:1923:21

    Winning the AI Wave

    1. GT

      by now you are the incumbent yourself.

    2. OP

      Yeah. So I mean, the two things. One is we're-- So yes, we technically we lead the observability market.

    3. GT

      Mm-hmm.

    4. OP

      But we only have 13% of it according to the measures.

    5. GT

      Okay.

    6. OP

      And that market is growing fast, so the bulk of the opportunity is, is still ahead of us there. Um, on the, on the AI side, I think it's difficult for public investors to understand, you know, who's winning and who's losing in the long run because it is fairly disruptive. It's changing a lot of the product needs. It's changing, you know, qui-quite a few things. Uh, it's also disrupting business models. In our case, it doesn't really matter. Like in our case, we are usage-based, you know, but many companies that are seat-based, for example, have to rethink, uh, how their businesses are going to be structured. So we-- on our end, so we were actually quite busy building products both for, uh, the, the, the AI, uh, builders, I would say.

    7. GT

      Okay.

    8. OP

      And also-

    9. GT

      Like AI as customers.

    10. OP

      Yes.

    11. GT

      AI companies as customers.

    12. OP

      Yes. And also for the, uh, the, the all the other companies that were starting to consume AI. And then in addition to that, you know, we're also building AI into our own product for automation. So, you know, we have these two big initiatives, and initially we call them Datadog for AI and AI for Datadog. Uh-

    13. GT

      In a way, like from kind of a maybe a scare of the market because you were the incumbent that was going to be disrupted by AI, you became a winner of the AI changes, like because that's more customers-

    14. OP

      Yeah

    15. GT

      ... bigger customers, new products.

    16. OP

      Well, on the-- on one end, you know, there's, there's so much more demand. Like, you know, there's more software, more infrastructure, more everything, and that's-- and it's getting-

    17. GT

      How much of your business now is AI companies?

    18. OP

      Um, so we-- I think we, we stopped disclosing it, you know, so I can't-

    19. GT

      Okay. So you don't have to say a number.

    20. OP

      Because we, uh, we, you know, we, we choose, uh, which metrics we disclose. But we, like we serve like the, the top 10 AI companies in the world.

    21. GT

      Okay.

    22. OP

      Um, and they're growing fast. And but we also serve all of the other, uh, startups, or not all, but a, a good fraction of the, uh, of the startups that are building and scaling fast, you know. So, uh, the-- on one end you have the-

    23. GT

      So did you, did you re-accelerate then?

    24. OP

      Yes.

    25. GT

      Is that-

    26. OP

      So we saw substantial re-acceleration of the business and, and you know, if you zoom out, if you look at the just the sheer amount of complexity there is in terms of the-

    27. GT

      Mm-hmm

    28. OP

      ... you know, the build out, the GPUs, the models. The models themselves are really hard to, uh, manage and monitor and secure and everything else. Um, the-- and in addition to that, the crazy amount of code that is being produced with coding agents, the fact that now, um, the code when it's written, you actually don't-

    29. GT

      Mm

    30. OP

      ... don't know it. You don't understand it. Like you-

  13. 23:2124:10

    The Dream of the Machine That Fixes Itself

    1. GT

      You bet. And I, I guess, but that's probably, uh, very exciting to have a new, complete new space of potential products to build.

    2. OP

      Yes. And, and look, the, the, the whole space has been, um, chasing AI automation like since-

    3. GT

      Mm-hmm

    4. OP

      ... like ever since the first, uh, you know, uh, infrastructure monitoring product came out, like I think there was maybe something about AI in it, you know, like even twenty years ago, thirty years ago. Uh, it never quite worked, right?

    5. GT

      Yes.

    6. OP

      Uh, today-

    7. GT

      At last

    8. OP

      ... there, there's actually a lot we can, you can do that can work. You know, so the dream of, uh, instead of waking you up at two AM so you can fix your software, uh, having the machine-

    9. GT

      Doing that.

    10. OP

      Doing that.

    11. GT

      The machine gets wake up-

    12. OP

      Yeah

    13. GT

      ... woken up.

    14. OP

      And then the following day it tells you, "Hey, by the way, I fixed it. You wanna check it out?" That's a much better experience.

    15. GT

      Yeah.

    16. OP

      And that's, that's actually within reach now, so that's pretty

  14. 24:1026:25

    AI Inside Datadog

    1. OP

      cool.

    2. GT

      How about, uh, your own internal use of AI? Like, uh, did you transform the company?

    3. OP

      Yes. I-

    4. GT

      And like what can you share, like, uh, how do you work today?

    5. OP

      Yeah. I mean, look, the biggest, the biggest impact is on the development side. Like I think most, uh, software companies-

    6. GT

      Everyone is using CloudCode or-

    7. OP

      Yes. Yes. I mean-

    8. GT

      Or coding agents

    9. OP

      ... everybody across the company is using it, and it's, uh, it's helping every single s- side of the business. But There's much more upside on the engineering side right now than there is, for example, on the sales side.

    10. GT

      Mm-hmm.

    11. OP

      Like, you know, you, you... Yes, you can improve productivity a little bit, but you're not going to multiply productivity by, you know, two, three, four, ten. You know, like, maybe you can, at least in some parts of engineering.

    12. GT

      At least we are not there yet, but-

    13. OP

      Yes

    14. GT

      ... who knows?

    15. OP

      Yes. Uh, but the, I think the killer apps have been invented for engineering. They haven't been invented yet for some other areas. And so my co-founder actually stood in front of the whole team a couple of months ago saying that, you know, within two quarters we mostly don't write code anymore, and-

    16. GT

      Was that two quarters ago approximately?

    17. OP

      He was-- Well, it was a few months ago, so.

    18. GT

      A few months ago.

    19. OP

      You, you know, we, w- I think we're on the, on the same schedule as most companies, you know-

    20. GT

      Okay

    21. OP

      ... like all most, uh, uh, tech companies, where we had an epiphany in December. Uh-

    22. GT

      [laughs] New models, capabilities-

    23. OP

      Yes

    24. GT

      ... kind of like step change.

    25. OP

      Exactly. New models, and also maybe a little bit of, uh, free time for some people to experiment. Um-

    26. GT

      Like it's, uh, it was the, the Christmas holidays. Like-

    27. OP

      Yes. Yeah

    28. GT

      ... and, uh, and then, uh, and then everyone could tinker-

    29. OP

      Yes

    30. GT

      ... discovered how powerful the models have become.

  15. 26:2527:40

    Advice to 2010 Olivier

    1. OP

      you know. Mm-hmm.

    2. GT

      What would you tell 2010 Olivier when you were just starting? What kind of advice could you give yourself?

    3. OP

      Yes. I would, I would tell 2010 Olivier that, uh, it's, it's gonna be tough, but it's okay. [laughs]

    4. GT

      [laughs] Okay.

    5. OP

      And actually, I, I believe strongly that all of the hardships we've had, um, they've, they've really helped us, uh, survive, get stronger, you know. So we, whether that's the rejections initially-

    6. GT

      Yes

    7. OP

      ... um, and a lot of the culture came from that, or, you know, we, like, uh, I think 10 years ago we had a serious security incident also.

    8. GT

      Mm-hmm.

    9. OP

      And that also completely transformed our approach to security and our approach-

    10. GT

      You're probably much better today because of that incident.

    11. OP

      Y-yes, exactly. Exactly. So everything that was very traumatic-

    12. GT

      Mm

    13. OP

      ... uh, I think in the end had a positive, uh, impact on the company, so that's good. That being said, um, I think, uh, m-moving faster, always, always decide faster. I think the advice-

    14. GT

      Yes

    15. OP

      ... I would give myself is decide faster. Yeah.

    16. GT

      Decide faster on, on what? On product? On people? On-

    17. OP

      Product, people. Usually people. P-product, I think you, uh, you get better at deciding fast over time.

    18. GT

      Yeah.

    19. OP

      People, it's really hard to, uh-

    20. GT

      The hardest part, right?

    21. OP

      Yes. You know, and that's always, like, you know, h-hiring, firing. That-

    22. GT

      Mm

    23. OP

      ... there are two things that you, in general, you should be faster. You-

    24. GT

      Should be-

    25. OP

      Whatever your instinct is, it's too slow.

    26. GT

      Um,

  16. 27:4029:06

    Hire Slow, Stay Sane

    1. GT

      did you hire enough people, or do you think you hired... It took your time to hire? And I'm thinking about team size because, like-

    2. OP

      Yeah

    3. GT

      ... one advice we always give is to, like, don't hire anyone pretty much before product market fit.

    4. OP

      Yeah.

    5. GT

      Do you feel you should have hired faster there?

    6. OP

      We-- I think we were always on the slower side.

    7. GT

      Okay.

    8. OP

      Um, so we, you know, even when we were growing like crazy on the business side, like we were not doing more than doubling the size of the engineering team-

    9. GT

      Okay

    10. OP

      ... every year, for example, things like that.

    11. GT

      So you are very conservative-

    12. OP

      Yeah

    13. GT

      ... compared to your cost.

    14. OP

      Y-yes, and, and mostly we, we wanted, didn't want to break everything. Like we, we saw some, some companies, m-many of them are our customers, that, um, had pretty dysfunctional, um, engineering teams because they 10X'd the size of the team over 18 months.

    15. GT

      Yes.

    16. OP

      And we thought it's not helping anyone because it's... What you do when you do that is you, um, so first of all, you, you lose all short-term productivity because all you're doing is, uh, hiring and, and ramping up new people. Uh, and then you have a huge risk that things are gonna blow up and, you know, then you'll be set back for another year or two after that. So we thought, "Hey, maybe we'll leave a little bit of business on the table because we'll be undermanned, but we're going to, uh, cap the, the growth rate of the engineering team."

    17. GT

      It's probably even more true today. Like you can do so much more with the same team-

    18. OP

      Yes

    19. GT

      ... in engineering. Awesome. Olivier, thank you so much for joining us today. It was awesome to have you.

    20. OP

      Well, thank you for having me.

    21. GT

      Thank you.

Episode duration: 29:08

Install uListen for AI-powered chat & search across the full episode — Get Full Transcript

Transcript of episode zcUoVg8Xvrk

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.