One. So my name is Srinivas, and I'd like to thank you very much for giving me this opportunity to talk to you on once again elected. Thank Professor Rohit giving me this opportunity. So let's start with the question. So the first question that I have is, uh how did I get to where I am today? So let me start off by saying I currently work as a software engineer at the sales force and their Seattle office. So they have. Ah, they're headquartered in San Francisco and they have offices in Bellevue, Billion cells. I'm currently based out of there. Carol Office. So that is where I am today on my story. My story starts off way back in 2009. So I graduated Ah, in 2009 majoring in electronics and communication back in Bangla. Or so during that time, I had a little bit off a difficult time getting a job because, as we know it with other later. The nine was the peak of the financial crisis that happened here in the U. S. And that had an impact on Indian I t industry as well. So Ah, what I did was I kind of took up a few courses after my graduate. I'm enough for my graduation so that I can cannot better be better prepared for my jobs. So and then after that, I had had three different offers. And then I started working at a company called Report Technologies Onda for their client, Erickson. So because of my background in electron, ICS and communication, they wanted somebody who knew how to the communication systems work. And then they also had somebody who know, knew how to hold a white coat. Essentially. So I was like their perfect fit on. Di did that for about 22 years. And then I moved to a company called Siemens, where I was responsible for their trickle energy distribution software. Again going to my background in electron ICS. They wanted somebody who knew how electrical equipment works on. Given that background and given my knowledge and coding, I was like, you know, the perfect fit for that job as well. So I did that for another 11 enough years on done. I got a new approach may be at GE Healthcare, so I worked there for about a year and a half and I the embedded systems stomach. So if you look at my background, you know eso all of my 454 from in four or 500 years of experience in India has been related to my underwear a degree. So that was what helped me can off, you know, start my career on. I've been doing coding for a long time. It's pretty much all of it. It's gonna sell start on, de. So I would urge you to kind off learn things that are outside off your endurance scope. Because at the end of the day, what matters is what the market values on. What do you bring to the table? So that is my story on dso far Onda. After that, I decided, you know, I would like to pursue my masters to kind of further enhance my career. And further and ninth my skill set on, I applied to a whole bunch of in your cities on I decided to go to the University of Utah because I spoke to a lot of different seniors on everybody's for Kylie, of the off the classes that they conduct and off the professors that are teaching their on pretty much. Everybody had really good offers that would really good job off job offers post their completion of the degree. So to me, pretty much it was a home run. So, Andi, I particularly enjoyed the subjects that were talked. Er especially, you know, the Web development program that I took from Roy Tiger Well, and ah, I think he's He's also teaching the data mining course. I think those two are kind of really critical because those other things that you would actually do And to be really honest, the things that actually learned in Web development actually helped me get my first job. And because off the projects that I did in that particular class, all the peace we have development class and then, you know, connecting to the MySQL database and like figuring things out on then that cannot want help me land my full stop as well. Because of that particular project. Andi, Um, after my m s, I s What I did was I started playing two jobs and then I can have moulded my resume for each job opportunity. So ah, lot of people are going to tell you just hey, you know what? Just keep applying. Just keep applying to these jobs. You'll get it somewhere. But that's that's not true. Every job is actually unique, and then you have to take time on. Then prepare your is a me and then can I match it with the skill said that they have. And then you essentially have to tell your story in your raising me right on. A recruiter has close to about me before six seconds in which second process you is, you may so that is how much time you have to actually make or break it. So you have to be really focused and then have the necessary skill set and then make sure that you can a match with what they're looking for weight, because, let's face it, the competition is severe. Right on. You have to stand out among the crowd on. The only way you can do that is if you are very focused in your approach, your dedicated in your approach, and then all of this is going to take time. But it's definitely going to be worth it. So what I did was I focused on all of my learnings that I had from my I am a size coursework and then I breaks basically focused on all of my captain projects. I focused on the things that I did in my courses, the product that I bet on the technical stuff that I quite through that. And in addition to that, my work experience in India, I kind off reliably but on that as well, because those are industrial experiences. Well, so with that, I was able to get a job offer in California in the Bay Area for a company called Arak where so I was a backend engineer. So I worked on back and enduring primarily C plus blast. I tend Ah, little bit of database. We did my sequel, and we also did a little bit off sequel Light on. Of course, I had taken the cloud computing class, so I already knew about AWS, which we use pretty much extensively there. So that is what helped me get a job there. And of course, interviewing is also a skilled right, and then you have to learn how two can present yourself. You have to learn how to present technical knowledge that you have in a way that they want. They kind of perceive it to be of important to the company. So all of this combined is actually shaped my career path on DA. That is also what helped me get my current job here at the felt forced Andi. I applied to their back and engineering rule, and I made sure that my resume is exactly what they wanted. And then I make sure that I learned about the opportunity. I learned what they're trying to do. I learned with complete us on. Then I would also advise you to kind of reach out to your network. Maybe you have your friends are working there. Or maybe you have people on lengthen that you know, that are kind of working in a company. Because if you have somebody that that can vote for you, then that is distant added and wanted to you. So if you have that can reach out to them on DA. Make sure you have the technical skills. Make sure you have the soft skills and then make sure you know which company replying and why you wanna go there. So all of that kind off, you know, helps you tell your story, and then if you do it really well, I'm sure you will be able to land that great opportunity in the US

I currently work a software engineer, so my responsibilities and decision family include making co changes for the existing tablet products on DA. In addition to that, I'm responsible for maintaining the product. I'm responsible for making sure that our test pipeline is in place. I'm making sure that our product is shipped to the customer. It is defect free and buck free. So those are my primary responsibilities as an individual contributor. Onda, I would say the decisions that I have to make overall are primarily going to be technical in nature. OK, does this code look or not? What are the review? Common story has got where the design decisions that we have to take care to make sure that the product is going to be in place without the customer want. So those are primarily why areas off decision making and then my responsibilities, in addition to that as a stop because we're working as a software engineering in a team. Wait, so you are. You also have to make sure that you follow team dynamics. Do you make sure that your interaction with the other team members is corneal on? Then you make sure that your points are kind off, brought across to everyone in a way that is presentable. And then you get along with people. So that is an addition thing that I have to do as an individual response individual country. That would be my responsibilities. So coming down to the weekly work hours on DA, um, I would have to say I work at a full time engineering job. That's gonna be your 40 hours per week. And if I had to give you like a breakdown off that I would say about 20 to 30 hours of that is probably going to be in technical related work. It can either be designed making it can be, ah, coding. It can be testing. It can be maintenance. And then I would say about 10 hours is going to be related to customer activities and but fixing activities. I would say about 55 hours will probably be on call. For example, if your product is out there and you're feature has an issue, then you responsible for it. So I would say we have an on call rotation. I think that it's pretty fairly common in other, larger companies. I would say if I want to be on call and then other fires would be attending meetings and making documentation and then attending, you know, Ah, cause from other system engineers who want to use our product. And they're kind of not familiar with our code base. So that will be my oral split in terms off the 40 hour work. And then some companies also have this weekend where you have to be on call. Ah, luckily in our company that that's not the case. Thank you.

so I currently use a whole bunch of tools that are currently already in place in our organization. I would say as a tool, family is going to be a righty. Your ah visual studio. That is what we used to code. And then, you know, make sure on the burger products, and in addition to that, we use griddle enterprise to make sure builders in place on. Then we also use the get lap C I for our entire CSTV pipeline. And then, in addition to that, we have a whole bunch of third party tools we use new relic to monitor our sluices on. Then we use AWS with easy to use Lambda functions to make sure all of our cloud based applications are intact. So those are something that we would use at this point and coming down to Al Gore with them. Specifically, we are primarily a back in engineering team. So are all of our algorithms are going to be family proprietary tableau on languages are going to be family. Patton on D. U C plus plus Andrea, a little bit of fell scripting where necessary. So those are something that we use