Surviving SVB's Collapse & Outsmarting Uber | Kyte's Nick Cobb

11 Apr 2023 · 46 min

Ask about this episode

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

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

In short

Dev Interrupted Podcast Episode Summary

Episode Title

Surviving SVB's Collapse & Outsmarting Uber | Kyte's Nick Cobb

Episode Description In this episode, Nick Cobb, the VP of Engineering and Head of Product at Kyte, discusses the recent challenges posed by the Silicon Valley Bank (SVB) collapse and how it has affected startups. He shares insights on building an engineering culture with a bias toward action, the rationale behind deleting his team’s staging environment, and how Kyte aims to compete with Uber. Additionally, Nick touches upon his experiences as an angel investor and the long-term impacts of the SVB collapse on the startup ecosystem.

Key Themes and Takeaways

Impact of SVB Collapse

  • Initial Reactions: Startups faced immediate turmoil with concerns over cash flow and fundraising.
  • Long-term Considerations: Founders are reassessing financial risks and profitability strategies.
  • Geodiversity in Banking: The incident has prompted startups to diversify their banking relationships to mitigate risks.

Engineering Culture

  • Bias Toward Action: Nick emphasizes the importance of a proactive culture where the team feels empowered to address challenges without delay.
  • Goal Setting Language: Nick uses assertive language like "we will" instead of "we need to," fostering a sense of commitment and urgency within the team.

Deleting the Staging Environment

  • Real-World Testing: By eliminating the staging environment, Nick encourages the team to deploy features directly to a test market, emphasizing fast iteration and real-world feedback.

Competing with Uber

  • Kyte’s Unique Value Proposition:
  • Focus on improving the antiquated car rental experience by leveraging technology to streamline operations and enhance user experience.
  • Example Feature: Adding additional drivers seamlessly through the app, which encourages user engagement and growth.

Insights on Startups and Investment

  • Opportunities in Crisis: Nick believes that challenging economic climates can present unique opportunities for startups to innovate and attract top talent, especially from laid-off employees in larger companies.
  • Investment Focus: He is inclined to invest in post-revenue companies that demonstrate traction and the potential for iteration.

Engineering Leadership and Strategy

  • Innovation Culture: Nick discusses the importance of creating a culture of experimentation and rapid iteration, highlighting the need for engineering leaders to foster an environment where failure is seen as a learning opportunity.
  • Incident Management: Emphasizes the need for robust incident management practices to allow engineering teams to maintain focus on innovation while resolving operational issues.
  • Learning and Growth: Advocates for saying yes to opportunities that push individuals out of their comfort zones, enhancing both personal and professional growth.

Conclusion Nick Cobb's insights into the challenges and strategies for navigating the current landscape of startups provide valuable lessons for engineering leaders. His experiences underscore the importance of fostering a proactive culture, adapting rapidly to changes, and leveraging technology to enhance customer experiences.

---

Additional Resources

  • Watch the episode on [YouTube](https://www.youtube.com/watch?v=e-mRcv1vqwA)
  • Explore LinearB’s [AI productivity platform](https://linearb.io/start-free-trial?utm_source=podcast&utm_medium=referral&utm_campaign=devint-shownotes&utm_content=shownotes)

Offers

  • [Start Free Trial](https://linearb.io/start-free-trial?utm_source=podcast&utm_medium=referral&utm_campaign=devint-shownotes&utm_content=shownotes)
  • [Book a Demo](https://linearb.io/book-a-demo?utm_source=podcast&utm_medium=referral&utm_campaign=devint-shownotes&utm_content=shownotes)

Learn More About LinearB

  • [AI Code Reviews](https://linearb.io/platform/ai-code-reviews)
  • [AI & Productivity Insights](https://linearb.io/platform/software-engineering-intelligence)
  • [AI-Powered Workflow Automations](https://linearb.io/platform/workflow-automations)
  • [MCP Server](https://linearb.io/platform/mcp-server)

---

This summary encapsulates the key discussions from the episode, providing insights into the challenges faced by modern startups and strategies for thriving in a competitive environment.

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

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

Transcript

Automatic transcript. May contain errors.

0:00constantly tell the team like we will and we are okay are the phrases I want to hear and like the phrases that I'm personally using. Like when I write down goals, I don't say we need to build this. We will build this actually. And this is something that is coming for Kite. And I think, you know, using that sort of like bias towards action language, it helps create this atmosphere where folks feel like the things that they're sharing and that they're seeing our problems are actually things that we're going to work on. And they're not just kind of like stuff that we need to do in the future at some nebulous place in time.

0:29Want to reduce your team's code review time by up to 40 % without touching your budget, GitStream is the new free dev tool from LinearB that eliminates a key bottleneck in your team's workflow, pull requests and code reviews. After reviewing the work of over 2 ,000 dev teams, LinearB's engineers and data scientists found that pickup times for code reviews were lasting four to five days longer than they should be. The good news is that they found these delays could be eliminated in four key steps. First, by adding context to every pull request, such as estimated time to review. Second, automatically assigning the right reviewer and number of reviewers to pull requests.

1:09Third, having co-review automation that auto-request changes. And finally, by automating PR approvals and merges. To learn more about how GitStream works and to try it out free for your team, please visit gitstream.cm or search for GitStream in the GitHub Marketplace. Hey, everyone. Welcome to Dev Interrupted. I'm your host, Connor Bronson, and I'm delighted to be joined in New York today by Nick Cobb, head of product and engineering at Kite, an on-demand vehicle delivery startup. Nick, welcome to the show. Thanks for having me. Yeah, really excited to have you here. It's fun to kind of be in person at an event like this at Lead Dev and have this opportunity to dive into quite a bit of exciting things that are happening in the space right now.

1:49Absolutely. One of which is maybe exciting as a slow phrase for this, infamous probably at this point, the SVB bank run that just occurred recently as we're recording. I know this has been a meteor that's kind of hit the startup space and it really readjusted some of the topics we were planning to talk about. As an angel investor yourself, obviously someone who's been heavily involved in the startup space for years, both on a personal professional level. I'd love to get your take on the impacts initially from this historic event. Yeah. I mean, I think the initial impact Thursday, you know, lots of people scrambling, trying Trying to figure out, you know, what to do, whether or not they needed to move their money or, you know, play catch up with with other fundraising, things like that and do damage control.

2:36Oh, man. I think as Friday rolled around, you know, a lot of people had either made that decision or were still trying to, you know, weigh what the outcome was going to be. And I think a lot of founders, like a couple that I talked to, they're looking at that decision between having 18, 20 months of runway go down to like four to six months. Yeah. Trying to make some new decisions. So definitely had an impact on a lot of folks. And I think, you know, now that it's kind of played itself out a little bit, they're feeling a little bit safer as, you know, depositors are made whole. But I think now, you know, folks are starting to think about what are the risks in my business?

3:10How quickly can I get profitable? You know, and if they didn't hear that message already, they're doing it for sure now. So yeah, it's been funny to hear the word geodiversity in banking. That phrase has come up a lot here in the last few days. Yeah. And I don't know about you, but I wasn't hearing that often beforehand. So it's really clear this is reframed, how people are thinking about financial risk. I'll say, like, personally, I think you and I both kind of agree that it's a positive. The depositors are made whole. Otherwise, there were essentially thousands of companies that weren't going to make payroll off of this.

3:42But it's a controversial thing. Did it personally impact you at Kite? We were minimally impacted. impacted. I think we had some exposure to like partners, I think, you know, Rippling and a couple other companies that helped deal with payroll, you know, they were interfaced with, with Silicon Valley Bank in some way. And so, you know, we weren't necessarily directly impacted in, in a massive way, but we've had to kind of work with those partners to kind of navigate around the problem and, you know, kind of move things around as needed. So. Yeah. It's been interesting as a, as a B2B business, like the one I work for where Linear B looked at it and said, okay, like similar to you, we weren't expecting to have major impacts.

4:20Sure, it would have some impact on us, but the second order impacts were very scary, right? Where it's like, are other banks going to fail? Is this going to cause many of our customers to have to say, oh, we can't renew because we simply don't have the runway to go forward with us anymore. So I think that was something where the initial piece of this puzzle was concerning enough, but the second order impacts could have been so much greater. And I'm curious what you think this result of having depositors made whole, but the ecosystem kind of showing its cracks will mean for the technology space and startups in general and how folks are going to react to it.

4:59Yeah. I mean, I think there was already a trend, say like, capital's not free anymore. We're not just, you know, funding ideas and, you know, some of the crazy stuff. Can't just get a, you know, fundraise based on your background and, you know, no traction and things anymore. I mean, I think a couple of things I've seen so far, you know, in B2B space in particular, folks saying, hey, like, we're probably going to delay payments until we can kind of like create that geodiversity that you were talking about or until the situation's resolved with depositors like fully. I think a couple of others has been, hey, you know, we're only taking payments in this account now.

5:34You got to update all your accounts payable and like the place where you actually send your payment, the platform in which you're using, we're now using this other one. And so, you know, how they do their AR has changed a little bit and we've had to change a little bit of our AP and stuff like that. You know, I think like the companies that are going through this, they're job creators, they're entrepreneurs, they're doing hard stuff. You know, don't start a company unless you feel super passionate about it because you're going to deal with everything from growth challenges to employment issues to bank runs.

6:05So I think we can add this to the list of things that founders have to deal with, right? Yeah, absolutely. Do you have any advice for founders as they go through this process or face these other impactful challenges? Yeah, I mean, I think, you know, remember why you started the company. You know, a lot of times like we go through the same thing at Kite. I definitely went through this at Uber. Lots of news. There's always going to be something going around. You know, there's always going to be something to try to pull your attention in various places. Like keep your head down, keep working. If you believe in the mission, like just keep going so more generally as a someone who's been very involved in angel investing yourself i'm curious if this reframes how you think about risk for early stage companies at all whether it's like okay is are you now thinking more about is this company based in silicon valley or is it based elsewhere and how do the financial systems work around there just wondering if that's coming into play at all yeah i mean i have not really uh ever discriminated on location i think there's lots of talented people everywhere and so location is one factor maybe definitely before 2020 it was a bigger factor but i think now less so oh yeah async has just become so much more common yeah and remote work's been enabled both synchronously and asynchronously and i mean just the prevalence of zoom and slack and all these things that have really burgeoned it makes total sense you can now recruit remotely worldwide right yeah so but but risk-wise i think like i've always personally been focused right now like mostly on post-revenue companies um companies that are finding traction, but still iterating on the idea.

7:33Um, and then, you know, beyond that and later. So I think from a risk perspective, you know, that, that risk is always there. They're new companies, they're early stage. Um, but, uh, I think, you know, post-revenue companies have significant de-risking from companies that are still figuring that out and, and haven't created any revenue. So for me, I mean, I'm still looking at the same things, mostly seed and, and pre-A series A, you know, timeline. So. So this brings up an interesting point before we had this conversation, you said something that I thought was intriguing, which was, this is the perfect time to join an early stage startup.

8:06Yeah. Uh, why do you think that? Yeah. I mean, I think, I think, um, there's a couple of kind of like ideas that you could frame it as. I think number one is that, um, investing in equities or getting equity ownership in a company is a good hedge on inflation. Um, instead of putting, you know, your money in cash and having it sit and dealing with the kind of like the inflationary kind of like results of that. You can put your time and your energy into a startup that you believe in, that's performing well, that has a great founding team, that can be a big business, you know, these things, and that you find challenging and rewarding.

8:42And I think that, you know, through the next few years, it's going to be really hard. But there's a lot of challenges that, you know, if you're investing in yourself and you believe in the idea and the team that's there, you know, equity ownership in that company can really mean a lot. And I think more and more people with all the layoffs and things like that are starting to look at early stage startups and what's the opportunity in as much as there's a group of those people also looking for the safer, you know, kind of like a big tech company or something like that to kind of like, you know, ride out the storm.

9:11And so I think the builders and the entrepreneurs and the operators who are willing to take that risk are actually going to build some amazing companies. And we saw that, you know, coming out of the financial crisis in 2010, 2011. I think the talent opportunity for those founders is so much higher now, too. Obviously, it's a shame that we've seen such mass layoffs. I know it's very scary for a lot of folks, but it also means there are a lot of very talented people who maybe were paid to not do as much at a larger company and kind of rest and vest, so to speak, and now are saying, okay, I have to go find a new gig.

9:43Maybe the Metas, the Facebooks, the Microsoft, the world aren't hiring quite as much. Let me go put some time in at a startup and see this potential upside around equity, but also bring this depth of experience and knowledge I have. So that's got to be encouraging for founders, too. And I'll say just here at Linear B, we're seeing a rise in applications overall. And sure, part of that may be related to us doing well, but a lot of it, I think, is just the economic climate where things are going. And that talent quality is really rising. I mean, I think right now is probably the best time for entrepreneurs in America to get started on the hardest problems.

10:17Like, um, I think there's plenty of, plenty of, uh, venture capitalists out there who would fund what they call, you know, American dynism companies, you know, and take on a lot of things that will, that will give America, you know, advantages for the next couple of decades. We see a lot of defense startups. I think, you know, defense is like kind of a touchy subject, but, you know, onshoring a lot of manufacturing for semiconductors is a big deal. Um, bringing a lot of that technology that we've kind of like pushed away for a long time back, you know, back to the U S I think is an opportunity.

10:47And, you know, I do think about this all the time is that like the next thing I want to do is go work at one of these companies or start one of my own. So you're thinking founder next. We'll see. We'll see. All right. All right. You got a couple of years of kite here still. Yeah, there's plenty to do. Yeah. Let's talk about kite a little bit. Really fascinating company. I mentioned on demand vehicle delivery startup earlier, and I think it's interesting to talk about that based on your Uber background. Yeah. But yeah. What's kite for those listening? Yeah. So, I mean, we, we like to define Kite as, uh, you know, basically providing you a car for any trip longer than a ride share.

11:22Um, right now we're focused on the more traditional kind of like rental experience and improving on that. It's an industry that, uh, hasn't changed in decades. No, there's literally a Seinfeld episode from the late eighties about the rental car desk and getting a car, like booking a car, having a reservation there and then not getting the car that you want and like signing the paperwork and all of these other things. And I think like watching that episode, the experience really hasn't changed. So, um, you know, pre-booking, we support web and mobile. Uh, we try to have like a mobile first experience overall in the post-booking.

11:56Um, you can see in real time, the car being delivered to you. Uh, you can coordinate with the, we call them surfers, uh, who bring you the car, uh, in real time. We have direct access to chat support. You can add an additional driver without having to go to the rental counter and, you know, do any of that, you know, kind of, kind of dance song and dance. Um, we can do verification. So we identify the drivers and verify them. Um, we use like, you know, document scan and selfie and facial recognition. So we're using technology to kind of like further this, this, uh, this kind of antiquated, you know, experience for customers.

12:29And, you know, really for us, it's about unlocking freedom for everybody, right? Like, um, I think we saw it at Uber, there was a lot of underserved areas by the taxi industry. We were able to open that up using technology and kind of like remove that barrier. And I think Kite can do the same for car ownership, for the rental experience and overall like subscriptions as well. Right. So I don't own a car. I haven't owned a car in nine years. It sort of played well for me to work at Uber for seven years. Totally. Now, now I'm kind of doubling down on that with with Kite and I'm excited about it.

13:01So fantastic. What kind of metrics are you looking at to see whether Kite's being successful and how you're thinking about the future. Yeah, I mean, we look at utilization of the vehicle fleet overall. We own all the cars. We have what we call dark, you know, lots in the 14 markets that we're in today in the U.S. So we look at utilization overall. We look at a lot of the same core metrics that most startups look at, you know, LTV, CAC, you know, all of these kind of like, you know, acquisition, et cetera, et cetera. But we're really starting to look at like system performance as a metric for the business how often are customers interacting with the features that we're shipping that do kind of like wrap kites experience uniquely and then you know how do we take those those specific features and double down on them to create even more differentiation for for the customers that kites bringing but you know similar to like like i said many companies look at retention you know we look at travelers versus like locals and who's replacing a car like car ownership like I would versus somebody who's traveling regularly for business or for work or for leisure?

14:06Are they bringing their family, you know, all of these different types of customer cohorts and just like how the product gets used. Can you give us an example of one of those features that you've shipped maybe the last few months and how you're deciding on success there? I'd love to dive in there. I think it's a really informative thing for product and engineering teams to think about because it's so easy to get disconnected from, am I actually delivering value to users with this feature and say, oh, well, you know, the C-speed was happy and, you know, some people in sales really wanted this. So it's there.

14:32But is it being utilized? Is it actually realizing values? I'd love to dive into that. Yeah. I mean, the one that comes to mind in particular, if you have rented a car in the last couple of decades and, you know, halfway through that trip, you need to add your spouse or a friend. There's some reason that you're, you know, kind of like trying to open up the opportunity for someone else to kind of assist you with whatever task you have that you rented a car for. You've got to drive back to the counter. you've got to show their ID, you've got to sign some paperwork, you have like modified rental agreement.

15:01Somebody's printing that usually on a dot matrix printer, you know, and you have to sit through this whole thing. There's somebody typing into an interface for 30 minutes. We don't, we don't really know what that interface does. But point being is that, you know, we can like improve that experience and have using our additional driver feature. And so in the app, if you have an active trip, you literally tap a button, you get a share link that you can share just like you send a text message or any other link, you know, to a friend and they'll pop that open in a web browser. It'll deep link into the app.

15:29They can sign in. They can complete the verification process in under 30 seconds and they can be added to your trip automatically. And so that feature in particular, it does two things for us. It creates this differentiated experience as we've talked about and like kind of up levels the car rental experience in general, but it also creates a growth strategy for us because people are inviting their friends to trips. They see how easy it is to get a kite and invite their friends. They tend to sign up automatically when they get added to the trip and they go through verification. And then we see those folks booking two and three more trips after they've been added as an additional driver.

16:05And so it's kind of almost like a referral, but it's involving them directly in the product like from day one and getting them directly onto a trip. How did that feature come about? I think that's a really illustrative example of both where you've seen success with the product and engineering work. But I would love to kind of back out of that and say, okay, you know, what inspired it? How did you find that piece? Because I think that's something that a lot of startups look for is, okay, like what's the right way to decide on key features? And this has clearly been successful for you. Yeah. I mean, I think, you know, adoption is one, like we have a hypothesis.

16:38We go through the product discovery process and we say, you know, do we think that, you know, this particular effort will move the needle, you know, a certain amount. We look at revenue per rental day. We look at, you know, revenue per unit on a vehicle basis. And we try to determine, you know, is the feature we're adding going to create more additional value in those metrics? And then we, you know, we go back, hypothesize on what that feature might be. How do we improve on the experience that we're creating for users? And then, you know, we experiment. We ship the lowest, you know, kind of effort thing and try to iterate on it.

17:10So I tell our product team a lot, like downscope everything to the smallest degree. Great advice. And we can talk about engineering strategy as well. Love to dive in there next. Yeah, in the last year and a half. I mean, we've, we have shipped and started moving the technology stack in a direction that removes engineering and in some cases product from the iteration cycle for the operations and markets teams. And so where we have business operations, markets, or where we have growth, we want to run experiments quickly and easily. We now have the software capability to look at, you know, a million different dynamic configurations.

17:42So if we have different tax structure in New York City, in Manhattan or in Brooklyn or in Jersey City, we can actually distribute that across configurations. Software can read all of those things and the market operations team can make those modifications as needed. We can adjust prices. We can adjust, you know, the latency of the feature. We can adjust, you know, tune lots of different parameters. And we can create this globally consistent experience where everybody's experiencing the product in the same way. but it's tailored, you know, more towards the local constraints of their market. So that's, that's been one of the big things that we've shipped is dynamic configuration and an experimentation platform in the last, you know, year and a half.

18:20What led you to that kind of modular approach? Yeah. I mean, uh, there was a lot of learnings from Uber, I think, because Uber did a really good job of creating this, you know, global experience in 300, 400 plus cities during the time that I was there. And I went to India, I went to Southeast Asia and like four or five different markets and I saw that the Uber that you know I was using in San Francisco was very similar to the Uber that people are using in India and there were different you know kind of like product outcomes fine-tuned differently you could pay in cash in Southeast Asia and India right we didn't have cash payments here and the adoption of cash was much better in those those markets it fit that the market dynamic and so you know the the product and growth teams they figured out how to implement cash in a way that you know was successful in those markets and all of the constraints around cash and how to do payments and how to alter the product and both on the driver and the rider side.

19:12And those things were very modular in the product and they did a good job of scaling that. So, you know, because we have similar kind of market penetration and footprint and breadth, you know, and we'll have more and more of that, we want to create that structure early and, you know, kind of build that out in a way that can make Kite very globally consistent, but, you know, modified per market. This seems like a logical time to ask you, Do you think Uber is still succeeding in that same kind of product innovation? Because I've seen some of your tweets. I know you have feelings on this. Yeah, yeah.

19:39I mean, you know, I have a lot of friends who work there, probably some of the best engineering culture in the world. And those folks are gone. I think that the way the company has been managed lately, like the level of innovation has significantly backtracked. You know, a lot of folks talking about app redesign and stuff like that. I mean, that's been four years in the worst to create this kind of super app. And I'm not sure that that when I open the Uber app or customers open the Uber app, they think about getting every single thing through Uber. And I think it's a bet. It's you know, I think it's courageous to take that kind of bet and really look for that.

20:11But I'm not sure that that strategy wouldn't have been more effective, implemented faster to kind of like get more people thinking that way. You go into the pandemic and you really have to kind of burn a lot of the businesses and the core bets that really made Uber successful in a lot of different ways. Like if you don't take moonshots, you don't get the microwave. You don't get, you know, tinfoil, you don't get, you know, the, the tang and all these other things that came out of that, these great innovations that we have as humanity, because we're taking moonshots. And if you're not taking those, um, it does impact the culture overall and, you know, how people feel about what they're building.

20:45Um, and I think, you know, the, the business has, has just kind of like reacted to more of the market need and, and less of maybe the customer need. And I think, you know, that's an advantage startup has, you know, build for speed and focus, listen to your customers and build what they want. You're not doing that. I don't know what you're doing, right? If I put you in charge of Uber's product and engineering teams and it's like suddenly Nick, hey, you're the new head of all engineering and products at Uber. You've got this like carte blanche to reimagine how Uber's taking their approach. What would you do to try to inject more of that innovation DNA or improve what you're seeing as far as outcomes?

21:23Yeah, I mean, I think that the dog food and culture seems to have disappeared. And I think that's the big thing. We're creating that at Kite. We want everybody internally using the product as often as possible. um the first thing that i would want to fix just like personally is dispatch latency in san francisco um i know it's you're san francisco nato right i'm from memphis but i live in san francisco and i use a product and you know i i just dropped a general kind of observation on twitter and said it feels like dispatch latency is like three four minutes when i request the car i can kind of leave my phone and just go get a coffee go do something else and you know there there was a realization that we had at Uber back in the day, which was people start to demand like a better experience year over year because they get used to the wait times being lower.

22:06And so they anticipate that, you know, it's gone the other direction. Yeah. And I think it's gone the other direction. And my hypothesis is they've, they've integrated taxi into the supply and that they're doing that for, you know, core business supply constraint reasons, I think, and partnership as well. And yeah, I mean, every time I get a taxi, it's a 10-minute dispatch. It takes forever. And I'm upset with the product experience right now. So that's something I would focus on. It does feel like you have to, and this is super anecdotal, but order your Reaper farther in advance today. I'm not going to think, oh, I can get one quickly.

22:45I know I'm going to have to wait a little while. And I think that's a great sticking point to mention where it's like, okay, there's been this big focus on being coming, you know, North America's WeChat, it feels like in some ways. But it's like, we're going to have everything on here, grocery delivery, everything you want to do. And it has missed out on some of that core business, which, I mean, I hear you on the whole, like, maybe they could have gone faster on the super app and maybe that was the direction. But because it's moved so slowly in some ways, and obviously a pandemic headwinds have heard it, the core business now is, at least from a user perspective, suffering.

23:21Yeah. Yeah. I mean, there's still a lot of good people who work there. You know, I still have a lot of contacts, you know, and friends that are still there. And I think they're really doing their best. I think that business always struggled with the business side, the making money side and ride sharing. It's a hard business, right? Like it's a bits and atoms business. anytime you have atoms in the real world it's probably the hardest thing that you're going to do but yeah i agree with you i think i was thinking about the the app redesign further it's like you know we redesigned the rider app in 2016 and that was an all hands on deck you know overnight every week burn and everyone was excited and everyone was you know kind of like pitching in and trying to solve this challenge and i highly doubt anybody's staying at uber after 5 p.m these days, you know, so, and, and I mean, that's not required.

24:07It's not, it's not, you know, And it's hard with an enterprise scale company where you start to get kind of abstracted away from that core team and feeling connected. Yeah. You start to lose that, like do whatever it takes, you know, kind of mentality. And, and you stop believing in, you know, some of the product and maybe even the innovation, you know, level of the company. So, um, but yeah, I mean, you know, they're still working at it and, you know, I'm rooting for them, but, uh, you know, I'm going to give them some feedback along the way. Yeah, totally. is there an enterprise that you see today that is doing a good job with that dogfooding approach you mentioned?

Read the full transcript

24:39Because I think that was a really important point that maybe gets ignored as companies scale sometimes. Yeah. I mean, I think Airbnb is doing pretty good with dogfooding. I think that they've always had an internal kind of culture of use the product, you know, even put your own home up. At some points, I had some friends there that were like putting their home on Airbnb to test, you know, the supply side. They've always had that encouraging employees to use the app to travel to other locations and visit offices. That's a great point. The culture, I think they called it internally, was the culture of being a host.

25:10And I think that was really important, the early part of Airbnb DNA. And I know folks who are there now who really enjoy using Airbnb, you know, as customers and they dog food the product, they look at that. And I think, you know, Brian Cheksey, they rolled out this Airbnb experiences. And I think that's what I've always wanted from Airbnb, and be, you know, for a long time. So I think that they are, you know, kind of, they have come around to realizing that, you know, and adjust it to what customer needs. Are there other companies that you see having a lot of success with that, either in startups or on the enterprise side?

25:40I could probably think of a few, but don't think of too many, you know, here on the spot. I think, you know, the world that I came from, not to keep segueing for you a little bit, but the self-driving world and the dogfooding of like the cruise product that's going on right now. I I mean, they've had cruise employees taking those rides for a while. There's another company, I think Waymo. I'm not sure if Waymo's got like an internal rides program or not. I believe they do. Yeah. But you see like the app, you know, the app seems to be well built. It's a great experience in San Francisco so far. You see that, you know, they've really thought about the customer experience and how are people going to get into this car and be validated and, you know, kind of understand what to do when there's no human there to kind of like massage the experience or kind of hand hold it along.

26:20And so I think that, you know, those companies are starting to kind of like implement that heavy dog food and culture and try to get more and more people, including like VIP customers and stuff, you know, dog food and the product. So there's a little bit of a bubble with those things, because as you build that new technology, you kind of want to make sure the technology works. And, you know, the experience kind of comes with it once the technology is there. But I mean, I see that employees there seem to be using the product quite heavily. So got some friends over there. I'd love to talk about self-driving a bit more because I have to admit, I'm not quite a skeptic, but I have concerns.

26:55I'll more broadly, you know, I'll say I lean into urbanism. I love that there's this idea that we can share cars and try to limit car usage on the road because I think there's so many negative impacts on cities. I love to walk. You know, we're in New York right now. I love the opportunity to kind of walk around and not feel like I need to have a car here. And I can also have easy access through, you know, whether it's a kite or an Uber, they're another option to, you know, if I do need to take a quick trip. Yeah. But there is a potential opportunity to build self-driving cars that could really free up time and improve the experience of transportation.

27:30What is happening in the space there? I'd love to talk a bit about that. Yeah. I mean, I think the first thing that's happened is that the market has realized how hard of a problem this is. Oh, God. I think we all thought like, well, we as a broad term. I think the media started to hype up the idea that, oh, this is going to happen soon. It's like, there's a lot that has to happen to make this as effective as it needs to be. Yeah. I mean, I think there was, there was a lot of perception and reality. I think one thing I kind of applaud Travis for a little bit is that, you know, the harder you push on some ideas, the broader they become and you actually are changing the world.

28:01You're not just changing, you know, you're changing an entire industry. You're not just kind of like doing something unique as a company. And I think there was a lot of hype behind that. A lot of things, you know, kind of, I mean, I mean, if you went to Pittsburgh in 2013 and you went back in 2016, you'd be amazed at the level of change in that city. They use the strength of their robotics program at CMU. They, you know, there were multiple companies built on this technology and the things that they were doing at CMU, NREC and a bunch of other places. And Uber was kind of the first shepherd of that.

28:29Now, granted, you know, Google and Facebook and these other companies have been in Pittsburgh for a while, but you see this tech ecosystem in Pittsburgh just really blow up. And I think like the market has caught up to the reality that this is a very hard problem, that it is very difficult to map individual operational domains over the course of a city and scale the operation. They know that, you know, shipping thousands of vehicles around to a different city, like we still only have footprint in two or three major cities in the U.S. where, you know, Waymo or Cruise or somebody else has been successful in getting that deployed.

29:00And so I think the reality of the cost and the difficulty of the technology has kind of caught up so that's the first thing i see i think you know what's going on there now i think is that they're starting to bring you know that we always had this question i guess at uber atg which was like our customers really like going to accept this technology or what's the what's the level of acceptance that they will have and the only real way to do that is to get those vehicles in the real world show them the safety record show them the benefits and have them you know interact with the product and i i see that we're kind of in that phase now in certain markets you know i don't like pretend to know all the intricacies of how to scale self-driving operation.

29:38I can tell you about the infrastructure and the developer experience that I contributed to with a great team. But I think this notion of operational domains, mapping, gathering a lot of edge case data, and then trying to build through simulation, you know, I think that's probably the most scalable approach they can take right now. And using heavy compute, lots of GPUs, like all of this kind of stuff, like we see these companies doing, they'll continue to scale, hopefully, the safety record and, you know, the technology capabilities through those means and, you know, burn those things down over a long list.

30:10But, yeah, I think they still have a long way to go. It's a big challenge. Yeah. I'd love to dive a bit into that infrastructure and developer experience topic you mentioned. Yeah, yeah. Around self-driving. You know, you're someone who's worked in that space for a while. How should developers be thinking about these kind of big problems and how to solve them? And how should engineering leaders be guiding teams on that course? Yeah. Yeah. I mean, the way that I would say engineering leaders could guide, like I'm a fan of kind of throwing out controversial statements, having the team disagree with me and prove me wrong in some cases.

30:40Like sometimes like we're going through that right now at Kite, like have an awesome engineering and product team. And one of the challenges I gave them is that every single thing we build should be fully in production. We're going to delete our staging environment. Everything needs to be featured. Oh, that's controversial. Okay. And we're going to put everything into a test market that, you know, no one can discover. like we have a city in the world that we're going to use for a test market. All the experiments are on and, you know, let's deal with the constraints of trying to test everything in the real world and build that, you know, kind of atoms thing.

31:09I think for engineering leaders, like there's a big chunk of that kind of, you know, stretch work and kind of goals that you can set for the team. And they'll tell you if you have a good team, I think, you know, most teams can be really good when they're pushed and they will tell you what's wrong with the strategy. I think the cool things going on in like the self-driving developer experience and like infrastructure world, they work a lot with mega repositories. So it's not a language specific, you know, JavaScript monorepo or a Python monorepo. It's a mega repo that has Terraform and C++ and Python and Go and all of the things that they're doing there and secret management.

31:44And it uses Bazel, you know, in a lot of cases. And so the stuff that they're doing to speed up build times there, I think that will have ripple effects on how you see developer experience work at lots of big tech companies. That's a great point, actually. that haven't dealt with mega repo, but are doing monorepo things. They're learning from that ecosystem and they're applying at an even bigger scale. They're doing kind of crazy things that they have to do because they have a hardware side of the product. They're compiling, you know, CUDA libraries like from scratch and they're doing it next to a bunch of other, you know, kind of like programming languages that don't always fit together in a repository.

32:18And so I think there will be, you know, a lot of innovation come about from companies that are having those hard problems. Trunk.io is one company. David Appirian and Ellie Scheifer, they started that company based on their experience working at ATG and the hard developer challenges that we had with simulation and perception and trying to fuse all that together with just like standard run-of-the-mill software development they were doing for various purposes. So yeah, I think there's a lot of opportunity there for developers to kind of think about what's coming out of these places. Maybe they're not talking about it, maybe they are, but what's coming out of these places that is a very broad approach to something I'm doing, maybe in a little more niche, but the same principles apply.

32:58It's really interesting to think about some of those challenges and how they get solved and how they then percolate out throughout the rest of the industry. Yeah. What are some of the things that you're doing within Kite or within your past work leading teams at Uber to solve problems for your engineering teams? A lot of the things that we've been focused on in the last year and a half at Kite, the team has really done a great job of pushing through just architecture changes in general. you know we're not building for a scale uh that you know in the immediate term that's going to be millions of trips per day and that kind of stuff and so we don't we don't give it three years maybe yeah ideally yeah that would be great um we we're not pushing the team and and kind of envisioning that that that's the scale we need to develop at but we are starting to advance the state of the technology towards that more modular kind of software architecture you know a year and a half I joined, there was not a real great like data infrastructure.

33:50So we have an amazing data infrastructure now. It's built on S3 and we use Athena and lots of other tools, you know, to kind of like provide all of that data to the internal team and then, you know, let them do their own analytics and create analytics products and data products around it. We're trying to create the experimentation and like dynamic configuration culture there with the kind of like focus on post-booking, like mobile first experience. We're doing a lot of things to get the mobile team kind of set up for success there, which is that internal release process, dogfooding, those kind of things.

34:20But over the course of the next year or so, we're looking at what is the kind of current constraints of the software architecture we have? Do we need to improve data model or schemas or relationships? Is there performance issues in the data stores we're using where we can have a slight advantage? We don't have to rewrite the entire stack around, you know, this, this, you know, new update to data stores that we're doing. And, you know, we're not doing anything significantly drastic. But, you know, we are getting set up this year for machine learning and how we apply models to pricing and verification.

34:55And one of our hard challenges is balancing vehicles between lots in the city. So we'll do multi-lot routing. We'll forecast and anticipate what are the next trips coming out of this lot. and we'll use technology and machine learning to kind of like optimize that overall picture of the market and basically using that forecast, have our surfers pick up cars and bring them back to the lot to forecast the next trip. And we can kind of do that logistical balancing in a sophisticated way. And it's a significant efficiency gain for our business overall. And I think a differentiating advantage as well.

35:30Absolutely. I love how you consistently bring back every piece of the product and your approach to how did this differentiate us and how does this apply to real-run customers or bring broad efficiencies internally. And I think one of the challenges some engineering leaders have is when they come into a new org, like you did a year and a half ago at Kite, and they say, okay, how do I make sure the culture shifts to what I need it to be, whether that's experimentation and dog fooding, whether that's, you know, I want to approach things with feature flags and really experiment in market. How do you create that shift when you come into a new organization like you've done at Kite?

36:05Yeah. I mean, you have to kind of look at like meet people where they are. There's a current set of problems, right? Like one of the issues that we had when I joined is that we just weren't great at incident management, right? And we're still not perfect at it. Incident management is, is actually an art. It's not, you know, easy at any company and it's, it's done differently in a lot of different places. I think there's generally a paradigm around incident management and how to do that. But how to do it for your business successfully is an art. And so we're getting better there. That was a muscle that we didn't really have that we started to flex and we say, hey, if we get good at incident management and resolving things for that operational, that Adam side of the business, we create safety for ourselves to make these investments in engineering and have more time for bottoms up work.

36:48And so we have created that safety with the team. It's given them the opportunity to work on real-time service layers, geostores, and streaming like location data in where I think a year and a half ago, we would not look at our engineering stack and say, we're going to be streaming live location from, you know, all the consumer devices or the server devices or the vehicles so that we can create an experience where when those things all come together, you know, the customer really feels like this is very different. The server really feels like they're on a sophisticated platform and they're contributing to, you know, the growth of the business.

37:19And, you know, from a vehicle perspective, we always know where everything is and, you know, we can be very efficient in that regard. So I think like creating space and safety for engineers, listening to the team, you know, letting them kind of plan bottoms up projects along with product endeavors and things like that. And prioritizing those things accordingly. We've been pretty successful at, I think, like creating the right environment to have that kind of innovation culture. and support the ideas, you know, from the team. It sounds like in particular, you came in and you said, I'm identifying a problem that exists, which is, in this case, incident management, where it's taking away from our ability to really build new and focus on the innovation piece.

37:58How can I solve this key problem that's a blocker for my engineers? Maybe it's cutting into their focus time. Maybe it's creating context switching that is, you know, inhibiting the work. How can I solve that? And then enable the rest of my team simply by freeing up hours, freeing up time. Then slowly kind of build that culture and meld it to the way you want to approach. Is that an accurate interpretation? Yeah, I think that's accurate. I mean, there's also just cultural nuance things too, right? Like it's very easy to be in that situation and say, well, we need or we should. And, you know, I constantly tell the team like we will and we are.

38:30Okay. Are the phrases I want to hear and like the phrases that I'm personally using. Like when I write down goals, I don't say we need to build this. We will build this actually. And this is something that is coming for Kite, you know? And I think, you know, using that sort of like bias towards action language, it helps create this atmosphere where folks feel like the things that they're sharing and that they're seeing our problems are actually things that we're going to work on. And they're not just kind of like stuff that we need to do in the future at some nebulous time and, you know, place in time.

38:57That's a nice mental reframing. What led you to start approaching these conversations that way? I think like founders could probably identify with this problem and I identify with this problem just like as I've hired other engineering leaders or worked with, you know, other team members. It's very easy to have worked at a big company. I went through this experience myself, which is why I identify with it. But it's very easy to have worked at a big company, particularly like an Uber or some, you know, someplace similar and see all the engineering rigor that was done. And a lot of Uber had its culture of building too many things internally.

39:29But, um, but seeing all those things and, and you kind of miss a lot of some of that technology and some of those systems that, that were in place. And so you start to form this mentality about like what we need as opposed to what the business actually requires at that point in time. And so, yes, it's nice to have that experience to come from that place and say, yeah, we have all of these things that we need to build or we should put in place in a perfect world. But what kite needs right now, or what this company needs right now is, is really these like we will, we are kind of statements where I'm not, you know, kind of envisioning that we're going to work on these things, you know, again, at some nebulous place in time, we're not building everything in the ideal sense.

40:09We're building what we need to build right now, you know, and sort of addressing real problems and empowering the team to bias towards action. I think that's the big, the big kind of like focus there is we're not creating plans. We're, we're, we're doing work. Yeah. That bias towards action is such a key part, right? I hear it from so many of the best founders and engineering leaders where they say, look, particularly early, you need to execute and you can't spend too much time planning in advance. Like you're going to learn so much more from, to borrow a phrase in military history, first contact with the enemy, because your plan is going to fall apart.

40:40You're going to realize you have to change everything. Absolutely. And that's, that learning process is enabled by the execution you talk about, where like a fast iteration, which I can tell you're really encouraging within your kite culture by the dog fooding, by the feature flag and leveraging things in different markets to experiment. So it's a bit of a chaos engineering approach in some ways where you're going and saying like, all right, let's see, let's experiment with this in prod to see if we break something and go back to it. Do you take inspiration from that kind of methodology? I think a little bit.

41:09Yeah. I mean, you know, the founders of Kite and just generally like the company at large have a really strong culture of getting better every day. And that's one of our cultural values. It's something that we all try to live by. We have kind of very strong company ownership, I think, across all teams. One, one very unique thing about kite is that it feels like everyone is working together towards the same kind of set of problems and challenges. You don't always get that feeling on a team. So it's very unique. And I think, you know, this mentality of iterating quickly by stores action, like, you know, experimenting, it's okay to fail, you know, kind of culture.

41:41Um, obviously we don't want to, we don't want to keep creating failure. We want to learn from our mistakes. Right. But this idea of getting better every day is really fail on new things, right? Like we're going to fail on this one we're going to learn from it. We're going to fail on new things. I mean, you know, just being honest, like not every product we've shipped or every feature we've shipped has gotten great adoption. And there's many reasons for that. And we dig into them and we iterate and we get better. And, you know, product management is it's kind of an interesting science. You know, you hypothesize that you can have some impact to some key metric in the business or some customer, you know, kind of excellence, you know, scorecard.

42:13And you ship something and if it doesn't land, you iterate on it, you try again, you know. Am I right to take this and also kind of extrapolate that you're also spending a lot of time in that learning process around incidents? Totally. Yeah. I mean, we have a postmodern culture. We do a review of incidents every two weeks. I think my team is a little over me trying to review every single one of the incidents. You're like, no, this isn't for it. It's customer facing. Yeah. But I think like the two hardest problems, I think, in engineering, other than naming services like communication and project management.

42:41And those are skills that I think engineers learn to get really good at when you have an incident. You have to communicate the incident to the business. You know, we have a significant physical world business. Those folks on the ground need to know why is revenue getting impacted. They sit in the parking garage and they see whether or not the cars are moving in and out. And so communicating that incident helps them understand, you know, what's going on on the software side of the business. If we have an incident and some downtime, you know, conversion rate issue, anything like that. But then on the project management side, we had some follow-ups.

43:12We have some actions to go take to make the system better over time. we learned a bunch of stuff from the incident. I need to project manage those things, prioritize them and make sure they actually get delivered and follow through. And so I think those skills help engineers, again, get better every day, right? Absolutely. Are there any other takeaways that you would have for engineers and engineering leaders listening to this conversation where it's like, hey, here are the key things that have made me successful or that I think are crucial moving forward? Yeah, I mean, I don't know that I would call myself successful in any regard.

43:41I just like enjoy what I do. And I think like, you know, my big thing is always just say yes to every opportunity and treat everything, even the projects you don't want to work on as as a learning opportunity. So I think, you know, in my career, I've been fortunate to have a lot of managers who have given me the opportunity to do things I didn't want to do, to do things I did and always just tried to say yes. I think in some cases, you know, I've said no, but in most cases tried to say yes. And I started in kind of dinosaur IT and I look back, you know, maybe nine or 10 years ago, I was still in that world.

44:15And so like what's changed in the last decade has just been, you know, forcing myself to be uncomfortable and then saying yes to things that, you know, I get challenged with, uh, in, you know, every day. So, you know, I'm working on security right now. It's not my, not my, not my background, right. But we're learning, you know, and we're working on compliance and security and those things. And that's not something I've, I had the luxury of doing at Uber. We had a great team at Uber that was working on that. And so, you know, it's something new and it's exciting and challenging. Same thing with P &L and financials.

44:46I'm not an MBA, but, you know, I'm learning to read these spreadsheets and everything. Well, that's another incident management and reporting and learning thing, right? Yeah, exactly. Yeah. It's really interesting that you kind of close with that learn from trying things piece, because I think that's, again, another common trait for successful leaders. You don't have to find yourself with that. I'm just going to do it for you. Thank you. An example that I really loved last year, we had Sarvaz Mislicki on the podcast. She's a VP of technology at American Express. And she talked about this feeling where she said every time she starts feeling comfortable, she's like, oh, I have to do something different.

45:18Yeah. Because I need to go say yes to something and try something new that's going to push me outside my comfort zone. And I see that in the best product teams, the best engineering teams, and the best leaders as they take that approach. So, Nick, thank you so much for coming on the podcast and sharing this perspective and your thoughts. Thank you. Diving into some controversial topics. It's been a great conversation. Awesome. Yeah. Thanks for having me. And thank you all for listening. If you enjoyed this conversation, we will have another live stream coming up in May. Really excited to share that with you.

45:44Details will follow this event. Keep an eye out in your inbox so you're ready. And if you haven't already, be sure to sign up for the Dev Interrupted Substack. It's the best place to find news about community events, learn about your favorite podcast guests like Nick, and read articles about everything that's happening in engineering technology. Thanks so much for watching.

46:07We'll see you next time.

From the publisher

It hasn't been smooth sailing for startups this year. As this week's guest Nick Cobb puts it "You can add bank runs to the list of things founders have to deal with." Of course, it hasn't been easy going for engineering leaders either. 

That's why Nick, the VP of Engineering & Head of Product at Kyte, sat down with us to discuss how to build an engineering culture with a bias toward action, why he deleted his team's staging environment, and what it takes to outmaneuver his former employer, Uber. 

An angel investor, Nick also touches on the aftershocks of the SVB crash and its lasting effects on the startup community.

Recorded live at LeadDev New York, this episode is a must-listen for engineering leaders who want to place product innovation in the driver's seat of their engineering org.

Show Notes:

OFFERS

  • Start Free Trial: Get started with LinearB's AI productivity platform for free.
  • Book a Demo: Learn how you can ship faster, improve DevEx, and lead with confidence in the AI era.

LEARN ABOUT LINEARB

  • AI Code Reviews: Automate reviews to catch bugs, security risks, and performance issues before they hit production.
  • AI & Productivity Insights: Go beyond DORA with AI-powered recommendations and dashboards to measure and improve performance.
  • AI-Powered Workflow Automations: Use AI-generated PR descriptions, smart routing, and other automations to reduce developer toil.
  • MCP Server: Interact with your engineering data using natural language to build custom reports and get answers on the fly.

More from Dev Interrupted

All 208 episodes
Surviving SVB's Collapse & Outsmarting UberDev Interrupted · 46 min
Listen in VO