Sagar Batchu

leverage point for us because everyone we hired early on was a great fit on the team they had already spent many weeks building and training with us so that was i think one of the things that worked really well for us on hiring the other thing that has worked really well we really think about our engineering as marketing so all the stuff all the design decisions and a lot of the early tug of wars we had internally around how to build we externalize into blog posts

leverage point for us because everyone we hired early on was a great fit on the team they had already spent many weeks building and training with us so that was i think one of the things that worked really well for us on hiring the other thing that has worked really well we really think about our engineering as marketing so all the stuff all the design decisions and a lot of the early tug of wars we had internally around how to build we externalize into blog posts

That helped give, I think, folks out there, candidates, prospects, to get an insight into how we design and develop and how we collaborate. Any kind of brand building, I think, always helps hiring. In terms of what's, I think, really working for us now is that core philosophy of ask for forgiveness, not permission, really is quite pervasive at our company.

That helped give, I think, folks out there, candidates, prospects, to get an insight into how we design and develop and how we collaborate. Any kind of brand building, I think, always helps hiring. In terms of what's, I think, really working for us now is that core philosophy of ask for forgiveness, not permission, really is quite pervasive at our company.

That helped give, I think, folks out there, candidates, prospects, to get an insight into how we design and develop and how we collaborate. Any kind of brand building, I think, always helps hiring. In terms of what's, I think, really working for us now is that core philosophy of ask for forgiveness, not permission, really is quite pervasive at our company.

I think everyone is really empowered to make roadmap decisions, design decisions, work with customers. run sport, make some pretty impactful decisions. And sometimes we get it wrong because of that high autonomy, but I think that's okay. I think you have to think about it as, in the medium term, those sometimes wrong decisions, do they go towards building the right culture?

I think everyone is really empowered to make roadmap decisions, design decisions, work with customers. run sport, make some pretty impactful decisions. And sometimes we get it wrong because of that high autonomy, but I think that's okay. I think you have to think about it as, in the medium term, those sometimes wrong decisions, do they go towards building the right culture?

I think everyone is really empowered to make roadmap decisions, design decisions, work with customers. run sport, make some pretty impactful decisions. And sometimes we get it wrong because of that high autonomy, but I think that's okay. I think you have to think about it as, in the medium term, those sometimes wrong decisions, do they go towards building the right culture?

And over time, it normalizes, and the end result is an organization that's very effective at making decisions because it's happening grassroots, autonomously, and not getting gated on top-down heavy processes.

And over time, it normalizes, and the end result is an organization that's very effective at making decisions because it's happening grassroots, autonomously, and not getting gated on top-down heavy processes.

And over time, it normalizes, and the end result is an organization that's very effective at making decisions because it's happening grassroots, autonomously, and not getting gated on top-down heavy processes.

And to your point, the SDK product is so opinionated, right? Kind of the shape and quality of a great SDK can really differ company to company, like TypeScript idioms that are agreed on, Python idioms that are agreed on. But even in those, you often get into debates with the customer that really come down to a handful of characters. And that can have a serious impact on developer experience.

And to your point, the SDK product is so opinionated, right? Kind of the shape and quality of a great SDK can really differ company to company, like TypeScript idioms that are agreed on, Python idioms that are agreed on. But even in those, you often get into debates with the customer that really come down to a handful of characters. And that can have a serious impact on developer experience.

And to your point, the SDK product is so opinionated, right? Kind of the shape and quality of a great SDK can really differ company to company, like TypeScript idioms that are agreed on, Python idioms that are agreed on. But even in those, you often get into debates with the customer that really come down to a handful of characters. And that can have a serious impact on developer experience.

So where we've gotten to at this point to scale this is it really comes down to providing the users with great out-of-the-box defaults. So a combination of deterministic config as well as a little bit of LLM powered magic on the OpenAPI spec means that we can make a lot of great decisions for the customer to get them to like a 90% and 95% great SDK out-of-the-box.

So where we've gotten to at this point to scale this is it really comes down to providing the users with great out-of-the-box defaults. So a combination of deterministic config as well as a little bit of LLM powered magic on the OpenAPI spec means that we can make a lot of great decisions for the customer to get them to like a 90% and 95% great SDK out-of-the-box.

So where we've gotten to at this point to scale this is it really comes down to providing the users with great out-of-the-box defaults. So a combination of deterministic config as well as a little bit of LLM powered magic on the OpenAPI spec means that we can make a lot of great decisions for the customer to get them to like a 90% and 95% great SDK out-of-the-box.

But then it's really important to invert control at that point and give the customer a number of really nice knobs and configs to decide how to take that great SDK and make it absolutely the best for their end user. We take the customers 95% of the way in that build process and then give them the config and utilities to make those final last mile decisions.

But then it's really important to invert control at that point and give the customer a number of really nice knobs and configs to decide how to take that great SDK and make it absolutely the best for their end user. We take the customers 95% of the way in that build process and then give them the config and utilities to make those final last mile decisions.

But then it's really important to invert control at that point and give the customer a number of really nice knobs and configs to decide how to take that great SDK and make it absolutely the best for their end user. We take the customers 95% of the way in that build process and then give them the config and utilities to make those final last mile decisions.