 Okay, so I work at a new corporation as a DevOps engineer over there. It's been like 14 months for me when we were there and being a part of DevOps team, my daily job looks like working with the developer teams hands on to help them set up their own infrastructure and then maintaining the site reliability of those systems by setting up the monitoring, alerting and bunch of other stuff which helps them like keeping the systems off time for most of the time. That's the kind of my daily job looks like. Otherwise, I love exploring open source even though if I don't contribute to something I just randomly like to just see that more things are happening and just try to learn about it. I love automated, the unautomated thing that's one of my very own kind of for me that I really practice a lot. So that's me. So what would your journey be becoming a DevOps engineer? Okay, so my journey to becoming a to be a DevOps engineer is definitely a roller coaster right? So I graduated in 2016 May and then I had the option to join in this and then I came here and then I was given the option that whether you want to join to some developer team or whether you want to explore something very much and being fresh out of college I just knew that being a developer it means that you have to write some job or create some process and there's something new and definitely there's something much to it. So then I thought, okay, let's give it a shot. And that's how I entered DevOps. And at that point of time we were having a two-member DevOps team. And then most of the things at that point of time were indexed for very infrastructure. So being in DevOps at that point of time with a very fresh hand experience that most of the things had to be set up in place and you had to build things from scratch and then to make it work to the extent that people start respecting DevOps was up to the level that appreciation it deserves. Because at that point of time index was at the stage because people didn't knew that means problems even existed. So DevOps was that kind of workforce and that was a challenge that was actually thrown to us as a part of DevOps team. And being right fresh out of college it was very interesting for us to just be a part of this community and to just be a part of this problem specifically made by DevOps. So yeah, that's how I entered DevOps and so far it has been, Jeremy has been also in my learning rate, he has been exponentially. I have learned typically all those major fancy tech and not just like the fancy tech to be very honest I have learned that how to be a part of a problem and go from right from the bird's eye view to the most distilled level it is being possible. Just by breaking down the problems step by step and then finally figuring it out that okay, this is the root cause of something that has been there for a while and okay, I am the one who actually will solve it. And then there's also a bunch of satisfactories having solved that. Yeah, so it's like, I'll tell you right, so it's like being the Batman of the organization to work in finance and your success actually makes the noise. So it's that way. So can you tell a little bit about your talk at this conference today about Plutus? Okay, so in one sentence Plutus is a kind of cost-alerting tool that we have built that actually helped us to keep track of the unknown events that have been So why did we build this? So we had, we were working on a lot of things and cost cutting that we were having we were working on a lot of strategies. So Ashman built a lot of tools that helped us save a lot of cost on universe but certain things that we were quite missing on that let's say there happens to be some of the events in our infrastructure which goes out and people don't come across to know about it So how do we actually keep those things in track? And just prevent those costs to be like being heard on a radio. So that was a motivation that we definitely have to figure out something so that these costs, like these untracked events do not cause the vain cost that we have So that was the kind of tool that then became Plutus it's the serverless architecture tool that helps you monitor all these costs and yeah that's what it does and it's helping us to keep our cost like most stabilized over the last 4 days and average around 100,000 dollar bill on an average on native list because that's kind of a good thing for us and with Plutus being in place, I don't remember being in last past year we have crossed 150,000 for this Very interesting Can you now tell us a little bit about why it should be being in place Do you consider speaking at conferences and community events? Like what motivates you to spend so much time in that work to prepare presentation, to prepare for the talk and then my income comes out where I'm starting to actually deliver the talk From my perspective, so I'm probably amongst the youngest people out here so from a pressure perspective if I have to say something to people who are just starting their career so attending conferences like these and attending meetups like these definitely helps you broaden your horizon because at your current organization you are working on a set of problems set of the challenges that your organization in its business point of view faces and you are solving them which might be right or might not be right problems that you have to solve to see yourself somewhat excelling in the career that you actually want to become but you once actually be a part of the community in which the kind of tech area in which you would like to be a part of then you start exploring the challenges of the problem which other people are also solving this helps you identify that there is something more to it than what I'm currently doing and then you become a part of their problems and they learn from you so it's a kind of a tool way process and it ultimately benefits you a lot in the sense that let's say some of the problems you become and then you become very interested then that can kind of give you a start to explore something very new within your own organization also that this is the kind of challenge problem that you are facing since quite a long time but these are the guys who are solving it let's make a shot and give it a shot and try to solve it now if you take that away from a conference and solve something in your own organization so that is something very useful not only from the company side but also from an individual side also you learn something and you actually help your organization grow that's not a thing that can be great for an engineer thank you for spending time with us we hope you have a very good future