The Stack Overflow Podcast

A director of engineering explains scaling from dozens of employees to thousands

Episode Summary

On today's episode, we chat with Suyog Rao, director of engineering at Elastic Cloud. Suyog began as an open source contributor, then an IC, and eventually a manager and director. He explains that journey, and how our new normal of remote work will drive a new era of transformation in cloud services.

Episode Notes

You can find out more about Suyog and his career here. True story, he once worked on tablets way before tablets were a thing.

He's on Twitter here. You can check out Elastic Cloud and it's suite of services here.

Suyog talks a bit about data gravity, a concept you can learn more about here.

If you're a fan of release notes and want to get a sense of what Suyog worked on at Elastic over the years, check out his blog archives here.

Thanks to our lifeboat badge winner of the week, lhf, for anwering the question: How can I get the current UTC time in a Lua script?

Episode Transcription

Suyog Rao There's this concept called Data gravity, right? You want to be closer to the data. And if your application is in, in Japan, and then some cloud provider doesn't provide your data center in Japan, then obviously you're forced to use other cloud provider. When you use something like Elastic Cloud, you don't have to make the choice. We pretty much have you covered across the world. And that's why we call it planet scale. Like you can pretty much do it anywhere in the world.


Ben Popper Hello, everybody. Welcome to the Stack Overflow Podcast.

Sara Chipps Heeyy!

BP Hi Sara!

SC Hey Ben! How's it going?

BP It's good. I know you're a little late to the meeting. You were doing your weekly Among Us.

SC Yeah, I had to kill someone. Yeah, it was really rough. So we've had, the community team, we have a weekly, and the LGBTQIA+ affinity group here at Stack Overflow. We have a weekly Among Ss meeting. And we played one more game, and I was the imposter. And everyone was just bunching up. And it was like five minutes and I couldn't I couldn't get anyone alone. So finally, I just had to kill someone in front of everyone else. It was a tough one. [Sara laughs] It was a tough one.

BP We have a great guest on today, Suyog Rao. I hope I got your name right, from Elastic, hello! Welcome.

SR Hi folks!

SC Thank you for joining us.

SR Thanks for having me. Yeah.

BP You and I met a while back. Elastic, we should say is a customer of ours. I think it works both ways. I think we use Elastic Search and you guys use Stack Overflow for teams. But for folks who don't know, tell them who you are and what it is you do at Elastic.

SR Yeah, my name is Suyog Rao. I'm the Director of Engineering at Elastic and my area of management are the groups that manages the SAS software in Elastic. Elastic is as you know, most of your viewers probably are familiar with it, it is the company behind popular open source products like Elasticsearch, LogStash, Kibana, and we have managed and hosted SAS software that that some of our some of my groups manage.

BP And for people who don't know, it started out as an open source project and then became like a for profit company, or what was the order? Like what's the order of operations there?

SR You know, it was three different products that came together are definitely the first one was the Elasticsearch. That's the search engine. That's the our data analytics, open source project. And then LogStash and Kibana, we joined forces, and then the company was formed. And we started building products on top of our open source products. And then and then the rest is history, as they say.

SC Very cool.

BP Yeah, this is a topic Sara and I and Paul's talk about a lot is sort of like, what happens when you launch an open source product. And it becomes very successful? Like how do you support that emotionally, with your time with your money as developer and you know, we've had a few people on where they took this route, you know, they had an open source project, but then sort of productized on top of it to create a company and that allows both sides of the coin to sort of thrive.

SR Yeah, it's a fascinating, you know, the last 10 years, open source infrastructure, especially infrastructure, open source companies just kind of had the same arc, right, they start and then got so popular, and then companies formed around it, beautiful communities around it. It's great. Great to see that.

SC Yeah, we use Elasticsearch here at Stack Overflow. It's a great product.

SC Yeah. What do you see in the community right now? What is your community like? And how is Elasticsearch growing? I know, it's a, it's a huge community, a lot of people using your product.

SR Yeah. And Elasticsearch, our founder keeps talking about this. When he started the software, he was the first support engineer. It was the first community member and he had like basic forum support, right. So it just spread from there. And the software was super easy to use. And as I said, like we now have a very multi product company and the community for some of our open source. software's are still so strong as it happens today, we have a community conference in Elastic. So we invited folks and they submitted proposals or talks happening about Elasticsearch, how they use it and LogStash, Kibana all the different products, open source product. So it's great. It's our software has been downloaded like multiple millions of times. And we see great collaboration in like, you know, the GitHub repositories and in forums and meetups and even the things are virtual now, I see so many meetups happening around Elastic and Elasticsearch. And it's just fascinating to see. That you know, are the developers in the company, a lot of us come from the open source background and I say earlier, our hiring and recruiting was kinda easy because people who loved our software, they were using it, they started contributing to it. And then they're like, well, wow, there's a company behind it. And we're like, come join us. And you can work full time on the open source product and help build products. So that was, that was an easier pitch. And then this is how a distributed work environment started. And we were talking about it, like elastics being distributed as a company since day one, before the pandemic and before the whole move to remote and remote first. And we were like, distributed and and that happens, because we were an open source product and open source community and developers came from everywhere. And then we just said, hey, we've started a company, do you want to join us and it just started thriving from there.

SC I don't know if anyone else had this experience with a family member like that. I feel like the open source background of software and as used to being distributed really helped in this past year, I don't know if anyone had the experience of a family member, my dad, in that first few months of the pandemic every week, it'd be like, you know, it's wild, but you could do online, it's really crazy. You know, we all get on the computers, and we all have meetings, and then we go, it was just like, every month, yeah, yeah.

SR And then, you know, my friends and family were like, "you work from home every day?" like, like, before pandemic happened, right? It was like, how do you do it? How do you do meetings? I mean, I live in San Francisco, we used to have, we had an office here, which we shut down during a pandemic, but we evolved where like, as we hired more people in a certain area, we used to open an office, and that office was, you know, mostly for a social gathering. And people used to come in and hang out. And obviously, there were like, places if you didn't have great internet at home, or if you had to take a meeting. And you know, if you had kids at home, and you're getting disturb and etc, you could come into the office and take a meeting. So people used to ask me before I was like, how do you do this like, and they said, Oh, it's, you know, it works for a 50 person company. And then when you get 200, doesn't work. And then they're like, if you get to 500, you're gonna you're pushing the boundaries of communication. And then now we're 2000 person company, and it works flawlessly. So it's, it's great.

SC Yeah, that's really great.

BP Yeah. Now we've we've learned that what's possible, unfortunately, I think, well, for people like me, it's like, but can we have the office back someday? [Sara laughs] Why would be pay for real estate, when you're all doing great on your own? Just stay where you are. [Sara laughs]

SR I think I think it's definitely the hybrid model works for some, and that's the full on remote model or distributor model works for some. I do miss office, I do miss seeing people. The other thing we used to do at Elastic, before the pandemic was, we would fly the entire engineering team twice a year into some location. And sometimes it's in Europe, sometimes it's in North America, we'll all get together, celebrate our success and, and then talk about things like what didn't what didn't work. And some of these conversations, you have to have face to face, right? It's a little team bonding, it's a little like understanding like friction points as you grow. That was great as well. And now that's moved to virtual as well. And then we were like, We missed those opportunities where, you know, you could just hang out and talk to people. But again, we've began to like adapt to the virtual hangouts as well.

SC That's great. Working on open source company, Director of Engineering, what is your day to day look like? Like, what are the things that are top of mind for you? And are you also in nine hours of meetings a day? How do you deal with it? 

SR I am the Director of Engineering for Elastic Cloud product, which is not open source. But I say that our team and our entire engineering ethos comes from an open source background, right, just because we started as an open source company. So there's a lot of, a lot of cultural, a lot of engineering philosophies, we still and we have embedded in our DNA as an open source company. So my job specifically, I classify it as three responsibilities that I have. One is people, which is probably the most important as a manager, right? So you want to make sure that you hire the best people, create the environment where they can thrive, and you can support them in terms of career growth, and doing the best work here. They come in every day and feel kicked about, like working for, for Elastic, and to create that environment. And then to make sure that the cross team collaboration and communication happens. And some people come in who've never worked in a distributed company before. And some people come in who've always worked in a distributed company and people, we've got 40 countries represented at Elastic. So there's a lot of cultural angle there in terms of like how people communicate, and then you add to it, people from you know, different parts of the world where you don't speak English. So it's, it's yeah, so making sure the flow, the team flow, the communication flow happens. That's all part of the people. And the second part for me is product. We build software and we want to build software that people love, right, people, I got sucked into Elasticsearch because I just loved the software. And I said, this is a beautiful piece of software. And we, you know, we want to continue doing that even though we were to the 2000 person company. Oftentimes, when the company grows bigger the product suffer because you know, there's a lot of different like, "Hey, we want to add this feature, we want to do this." And then you kind of lose your like core, we want to bring that magic, when you use the software, you're like, there's an aha moment every time a user uses it. And we still want to keep that. And that's one of the things where keep building software that people love, and people really find value in that's, that's second part of my job. The third part is what I call us processes. You know, my job is not just the teams that I manage, it's also how do engineering teams at large communicate, right? How do we know, what are some of the things that slows us down, and people sometimes add rules or add things that intentionally felt good at that point, but then as you grow, you kind of constrain yourself by by doing those things. So I'm constantly looking out for what makes us slow, what makes us you know, struggle in some areas. So I think these are the three areas in my job that I focus on, which is people, product and processes.

BP You mentioned something there, which is that there, there were certain things about the software when it was open source that she fell in love with. Which kind of encouraged you to look at this as a career. Let's let's get into the weeds for a second, like what was appealing to you about it. Maybe tell us a little about sort of like what your background is, as a student of computer science or developer? And then yeah, what in particular about Elastic did you find so inspiring? 

SR Yeah, I studied computer science in school, I went to school in Boston, and then immediately I worked for a startup company. And you know, as they say, startup is all about timing. And that startup didn't do well, because I think we were too ahead of the game in some ways. And then the market wasn't right. So this is back in 2003, or 2004 where we are using tablets for shopping. And you know, it was the adoption was just wasn't that I was like, what is this awkward thing that I have to carry when I'm shopping, right? So now it's your phone. It's just so crazy how 15 years makes all the difference in the world?

SC Oh, yeah. 2003 tablets for shopping? Wow. Yeah. Wild! Now I know we all have tablets for shopping. [Suyog laughs]

SR So wild. And now it's the norm.

BP Now it's like, what's a store? I don't go to a store. I just do online shopping.

SC Exactly. 

SR And then I joined a big company. And it was fascinating. You know, you learn from every company, you learn about how products get shipped in different companies. And then the big company, one of the things that I missed was how do your users see your software, right? How did like when you as a software developer, the most important thing for you is when you write a piece of code, or you write functionality, you want your users to feel it and see it and play with it. And then in some big companies, you actually don't get to see it because it takes like years to ship a software, right. So you write something and then like six or eight months later, or sometimes even a year later, you ship it. I struggled a bit with that. So and then after spending about five years in a big company, I moved to another startup called Loggly. It was doing log management and those SAS software. And there it was about, you know, getting all your diagnostic information, and then being able to search through it, and search and I was exploring all the different search technologies, we were using another software for that. And then I said like, there must be something better here. And then I stumbled on Elasticsearch and, and I was like, I downloaded it and in on my laptop, and then two seconds later, I could put my data and I was able to search. And that was like, that was a click for me. And I said, you know, software that is open source is so graceful to use and so powerful. I mean, this is you could see it at that point software's like Kafka was blowing up, right? People were using Kafka for the message bus. And then there was like, you know, software like Storm. Yeah, it's just like, you know, a big infrastructure projects were being built on open source projects. And they started very small. And I think that was a very powerful concept where you could download it on your laptop, it still works, but then you can put it on your data center or put it on Amazon, AWS, it still works. So that, just that journey of like, from a small PLC to betting your company, sometimes on it, because in our startup, we were betting a company on Elasticsearch in terms of how we use it. That was what got me into it. And then I joined Elasticsearch, because I just fell in love with the software and the company that was starting behind it. 

BP And so Sara, you had asked before what it's like day to day at the director level, when you started, how big was the team and sort of what you know, what was your initial? What were you an IC and just sort of walk us through what it's like to go from being that team to now I think you said 2000 people or more?

SR When I started elastic company was about 50 people altogether, right? So it was 2014, early 2014 when I joined and I joined as a software engineer in LogStash, which is our data extraction and transformation and loading tool, right. So that was open source. It was a very small team and I joined this person called Jordan Sissel who was another very prolific open source contributor. So I was thrilled joining him because he had so much background in open source and I was like kick to learn from him. And quickly the team grew, we and the whole company was growing. And we were hiring a lot of people. And I put my hand up and I said, look, while I love writing software every day, one of the things I can help is getting, you know, others to kind of row the boat in the same direction, right, just making sure that everybody contributing and clarity of vision or clarity of the product is there. And I was really interested in management, I've done this a little bit before, I said, I wanted to become a full time manager. And when you're a small company, a manager is it's like a player coach combination, as I call it and say you, you're definitely managing people, but you're also actively doing 15 other things, right. So you're writing software. And at that stage, as an open source company, I was, you know, traveling it to different companies and places to train our users on Elastic and, and then--

SC Wow! Those are some very different things to be working on.

SR This is where like, when you join an open source company or startup at that stage, you're pretty much wearing different hats, right. And if you like how much you can do is just based on your, you know, how much you want to restrict yourself, because you know, I love doing support, and we'll get into support in a bit. But I love doing support, I wanted to be close to our users. So doing multiple things. And then as we grew, you know, we just kept on, I said, you know, what, want to manage more teams and get more responsibility. So I was fortunate to be in Elastic at the moment where the growth was kind of exponential. And when that happens, you pretty much hold on to your seats and try to bring clarity and try to bring like some management experience into the team. So that was my journey.

SC That makes sense. So Elastic Cloud specifically is cloud hosting for Elasticsearch, I'm guessing or do I have that wrong? 

SR Yeah, that's right. Elastic Cloud is a fully managed software as a service where we do Elasticsearch as a service. We have multiple products now, not just Elasticsearch. So we have we built solutions on top of Elasticsearch, right. So a lot of companies use Elasticsearch, and bill like observability, and logging solutions on top of it. So we host all of that stuff on our different cloud providers, we host on AWS, GCP and Azure. So yeah, definitely. That's my everyday area of responsibility.

BP Sara, have you ever heard anybody say before I really love doing support? I'm not sure I've ever heard that or believe it? [Ben & Sara laugh]

SC Yeah. Sometimes I've heard that before! I've heard that before. 

BP Yeah. So tell us a little about that. I mean, you said you were sort of wearing multiple hats and doing different things. I personally find that, yeah, it helps you keep energized. It's not like exactly like pomodoro. But if you're doing an hour of this, and then you take a break, and you use a different side of your brain to do an hour of that, you know that that can feel like a good way to keep yourself going sometimes. But yeah, support like, where did that come in? You were actually talking to customers in a forum or what?

SR When we joined, when Elastic was small, you know, this, again, comes from our open source background, in open source, when you're a maintainer, or even contributing, everybody is giving you both positive feedback and negative feedback and constructive feedback, right? So you manage that relationship with your users. It's very raw, and you get, you're so close to the user, right? You release something, you immediately get feedback from your user, whether it's a GitHub issue, or it's like, wow, this is wonderful. And can I add something else to this. So continued inside of Elastic, and we were, you know, we had a support team, it was a small support team. And what was great about Elastic and how we evolved that is that, like, all the engineers, and all the developers, were very close to our user. So even though the support team was the first level of, you know, answering questions, sometimes we were training the support team itself on the products, and we would, because the rate of innovation at elastic is so high and we were developing new products, we sometimes used to directly talk to our users and customers. So you know, one of the things I love is being close to your users like, again, when companies get bigger that keeps getting far away from you, right? So you have like so many different functions and teams between you and the user. So wanted to keep that. And our support was, it was a combination of like, you know, people used to file escalations and support tickets, and then we would, you know, we would help behind the scenes in understanding their performance benchmarks. For example, understanding how we can tweak the software for performance and what kind of consultative help we can give them. So the thing here is that the as the company grew, we wanted to scale this right, we wanted everybody to do support. So we started doing rotation. So we said, even though we have a support team, every engineering team has one or two engineers every day, who spends time just doing support. So we wanted to get this feedback so that you can understand how your products being used and like what kind of difficulties your users are facing. So we still do that even today. And it's not like you have to get up at 3am and do support. We have a full on Support Team. But then as your day to day jobs, you just take a break, as Ben said, but you do it for a whole day, right? You start doing support and answering questions. You have the team to help with customer conversations if you want to, but you can directly talk to a customer. And that's a very powerful thing. You know, one of the scaling things, and this is where I came to Cloud from the other team that, I was managing--Cloud is a very young product. So there was a lot of support queries and support engineers used to come to our Slack channel and keep asking the same questions, right. So there would be like, "Hey, how does this user configure X or Y? How do we, how do we support this feature?" And this is where I was like, you know, it's great that we want to help support. But we know you want to get the most difficult questions to your engineers, because you want to make sure that, you know, some of the consultative things that keeps happening over and over again, you train the support team and enable them to answer that, right. So and if we were, frankly struggling, and this is where I said, look, I think what we need is a better place for us to store all the questions and answers that people are asking and repeatedly asking. And we did a small PLC, and we discovered Stack Overflow Teams.

SC Yay! 

SR And I was a big user of Stack Overflow, right, the general Stack Overflow, and I said, you know, like, this is definitely solved, right? This this this is there's a product out there. And it would be great to bring it in, into our problem that we were facing. 

SC That's great. We do the same thing internally.

SR Yeah. And yeah, and I, you know, this is another tip I can give to, you know, any listeners. In a big company, at that point, we were pretty big. We were about 1000 people, it's always better to start things as a small pilot as a small PLC, right? And then adoption just kicks in, right? If you try to do like, top down, hey, this is a piece of software, everybody should start using it now. It never works.

SC We're all gonna use it.

SR Yeah, right. It's always gonna be like, why is, why am I using a new software, we have this, you know, we have GitHub, we have Excel sheet, and we have a spreadsheet. So this is what I did. It was just a small PLC, we curated content initially for Stack Overflow Teams. And, you know, we knew all the questions that we were getting. So we we took all that stuff. And we put that into teams. And we opened up for like 10 support engineers and said, hey, look, this is, you know, does this answer your question? And they were like, Wow, this is great. So then it 100 people started using it, it was successful. And sometimes we still got friction from other teams that like, this is just cloud, let's just cloud use that right? And then when they saw the, the the power of it, and we didn't have to do anything, this is the network effect, right? This is like where people saw the power of it. And then now we're actually 1000 plus users in Teams, and we've got about 1500 questions. And I stepped away from it. Because you know, my job was done. Right. So it was like, people were using it naturally. It was just beautiful.

SC Great! 

BP Yeah, I like that idea. If you just give it 10 people, and they like it, then other people are jealous. They're like, why can I use this tool? And suddenly, yeah, you sort of a little reverse psychology there, as opposed to trying to force feed it to them.

SC So for the cloud team, so do you find that you're--who do you recommend Elastic Cloud for? Is it enterprise clients? Is it smaller clients? Who do you see using that product the most?

SR Actually, with with SAS, the beauty of SAS is that you could use like, you know, if you are a developer in a big company, and you want to start a project, just like we talked about like a PLC, right, you want to try out the product, SAS is great, because you can just put your credit card in there. And then you can, you can start using it at the beginning of your development cycle, or maybe you know, you were trying to prove out something where you have a bunch of data and they want to use Elasticsearch, you don't have to download any software, right. So it's easy, there's like, less friction for you to try new software. And if it works, great, then you can again, like the network effort in your team, other developers are gonna start using it. So we definitely recommend it for all sizes of companies. And then as you grow, we have features that are appealing to enterprise customers like Single Sign On and like, cross, we have this ability to, you know, search your data across providers. And I think that is super cool, right. So you can have your data in AWS and your data in GCP. And your application can now you don't have to worry about it. A lot of companies now do multi cloud strategy, right? You don't want to, you know, bet on one company maybe and you know, your company or your subsidiary in Singapore, you want GCP and then in North America, you want in AWS. So we use Elastic Cloud, you kind of can search across to you don't have to really worry about it. It's just kind of really, really powerful concept. So getting started experience for SAS makes it appealing for any size company.

BP Plus, the more cloud providers you can use, the more you can force them to give you discounts. Like you don't want to get stuck with one person, you want to let them know, "Hey, we're using these guys over here. We're using this team over here." It's advantageous to your company.

SR Yeah. And then sometimes, you know, there's this concept called data gravity, right? You want to be closer to the data. And if your application is in, in Japan, and then some cloud provider doesn't provide your data center in Japan, then obviously you you're forced to use other cloud provider. And then when you use something like Elastic Cloud, you don't have to make the choice, we pretty much have you covered across the wall. And that's why we we call it planet scale, like, you can pretty much do it anywhere in the world.

BP So Suyog, yeah, like just thinking about cloud and search, some of the trends that have been going on, and maybe some of what's been accelerated over the last, you know, year, we've seen this huge shift to remote work. What are you seeing on the horizon? Like, what are you thinking about for 2021? And beyond? Are there particular, like technologies or frameworks or ways that people might start to work that you're you're interested in?

SR Yeah, I think, you know, especially with COVID. And you saw last year, it like, before, COVID, people were like, I'm starting our cloud journey, right? That's, that's when there were like, a lot of companies in Silicon Valley, and others and places had already, you know, transformed into Cloud, but then others were, like, slowly getting into it. But just with COVID, as everybody said, it just accelerated 10 years, right. So you had to get on cloud, because you don't want to spend time on data centers, etc. So I think more of that is going to happen in 2021. And I, you already see this as a proliferation of SAS tools, like, it's so many SAS tools, which is great. Like, as a consumer, you've got so many choices, that, I mean, I love the fact that you don't have to download anything on your laptop, and then try it. And I mean, 10 years ago, that was the case. And now you got great software that you know, in, like, just a credit card. Right. And that's so powerful. I think that's gonna that's gonna help people bring more software into the into the world. And a, I think I heard that somewhere like, you know, it's not just that people are using software, they're all becoming software companies, right. So it's like your bank, your bank, and Chase is now a software company. And Netflix is not a media company. It's a software company. So I think more of these things will happen. And the amount of data is just mind boggling that that just happens to go across boundaries. And, you know, there's going to be more proactive machine learning that's going to come in, right. So as you get more data, you don't want to just be reactive, you want to you want to be able to get through all the data. And then machine learning is a is a, you know, it's a very overused term where like, everyone wants to be an AI and machine learning. But then it's definitely what you want out of machine learning and how you can you can get the best value to your users and your company. I think that's the power of it, to define it and to be able to use it.

BP Yeah, Sara, I'm sure you see this from sort of your perspective at Stack Overflow and openJS, I saw a slide this morning about venture funding and early stage startups. And there's sort of two things happening, which is interesting. Sayog, like you said, it just feels like everybody now has the ability to very quickly start to think about what could I create something here. And so simultaneously, the government is kind of saying, look, we need to break up these monopolies. And, you know, nobody can compete with the giants. But at the same time, the number of startups who are getting funded and going public has only accelerated, so there's definitely still a lot of room within the software industry to create value it feels.

SR Yeah, and I think another powerful concept with SAS, which is something that I deal with every day, is the notion of, you know, paper use or consumption building. Right. So this is this is another powerful concept. And you know, with the infrastructure product, and there's so many infrastructure products and, and then that transcends to like applications software too. We basically, only pay for what you use, is as simple as that, right? It's like your electricity bill, like, you know, if you, if you want to keep your lights on your bathroom all the time, then go for it, right? So it's very transparent. It's like, as your company and your use case gets bigger than you consume more, and then you see it in your bill. I think AWS kind of pioneered it right for the cloud provider. And I see this now. And like, Twilio is another great example. We're using API based, like, you know, metering of your like, how you use it, it's pretty much everywhere now, right? Every time you see like SAS companies were talking about, like, when nobody talks about seat licenses anymore, right? Nobody wants to say, you know, this is like number of users is about more about like how how you consume your resources, and that resource could be anything. So that's another great benefit of SAS.


BP Alright, everybody. Thank you so much for listening. It's been a pleasure. If you enjoy the episode, go ahead and give us a little rating or review, whatever podcast platform you're using. It does help.

SC Like and subscribe!

BP Like and subscribe, smash that like button.

SC Smash that like.

BP You can send us an email You can send Sara crypto kitties. SaraJo at...

SC @SaraJo.eth!

BP SaraJo.eth, that's right. You saw that Nyan Cat sold for $500,000? I don't even know what's going.

SC Yeah, send me Nyan Cat!

BP Our lifeboat winner of the week, LHF "how to get current UTC time in a Lua script?" 

SC Ooff!

BP I will link that in the shownotes if you need that answer. I'm Ben Popper, Director of Content here at Stack Overflow and you can always find me on Twitter @BenPopper.

SC I'm Sara Chipps, Director of Community here at Stack Overflow. You can find me on GitHub at @SaraJo.

BP Suyog, tell people who you are what it is you do. And if you want to be found on the internet, you can share that too.

SR My name is Suyog, and I'm the Director of Engineering at Elastic and it was great having, you know, participating in this show. And you can find me on LinkedIn and Twitter, Suyog Rao, which is my name. Suyog Rao. 

BP Okay, terrific.