So, uh, yeah, it's almost like 10 years back that I did my bachelor's in computer science. Yeah, and I started my career with a consulting company that gave I t services to other customers. And, uh, during the initial stage, I was I was hired as a soft as a software engineer for them, But during the initial stages, I My job was not just doing a software engineering, but it was like a lot off kind of interaction and collaboration with our customers and trying to find out what kind of projects we need to implement for them, it was a bit off, like a team management activities there is. There is a bit off business analysts is maybe some kind of product and project management that I had to do initially. And it was kind of not like a completely poor off software engineering, but a lot of mix of things that I had to do. Uh, yeah. And then, uh, yeah switched out on teams and technologies and companies. And then finally, one of the companies that I was working for in India, they gave me an opportunity to come to the U. S. And do a project for them on. Uh, yeah, yeah. After coming here, my my roll up, My role kind of teams. And I I was kind of more involved in, like, uh, doing moral programming and doing doing more off software engineering activities. So yeah, and that's how my journey here has started in the U. S. And, yeah, After coming here, I have devoted more into a kind of blood new technologies, new things and absolute different teams projects. And it has been an exciting journey since then.

shut. Yeah, So to start with kind of responsibilities and decisions, we I think most of the companies nowadays like they work in different sprints. They follow agile methodologies and work in different strains. Thio. So before the sprint starts, we have kind of like a for you Sprint ceremonies like we have to define one of the things that the top most priority for upcoming explained we need to define. Define the stories or the task that we need to do to do in this place. Yeah, we need to decide what we can do and what we cannot do. And what is the most important at this point of time too solve for lower and users of our customers. So, yeah, those are the things that typically happen within, uh, experience. Experience is basically two or three weeks depending on the team, depending on what the team is most comfortable with. So we start off with having these meetings in which we decide what we're going to do that forms the initial pardon. Then we kind off start working on those and develop and implement those using whatever tools and technologies that we're using on board the end goal of the Sprint is to kind of take whatever we're doing at move into a state where our endings also business users can actually start using them. So that is a typical day to day life in in a sprint for me and for most of the software engineers, I'm sure it's kind off some kind of flavor off doing that.just to start with the easy answer. The weekly of our cars are like, kind of like before on their standard is like 40 hours. Uh, but yeah, very much depends. Sometimes we have, like, a easiest grain or, uh, where we have Yeah, some of the tax might not. Might not be that intensive. And it can It can be that we're spending it maybe 25 to 30 hours in the sprint and actually doing our project work and rest of the time gets devoted towards what's learning or towards doing some form of mentoring are being mentored by different seniors. Uh, yeah. So it can start with, like, maybe 25 35 hours on Duh. And sometimes way are on a very a critical task, which which is time sensitive in nature. And it needs to be implemented by the end of the screams. When that this is, sometimes it goes beyond 40 hours, sometimes for 45 50 hours. But it's it's not very common to do that over a long period of time. So most of our of like kind of estimated in a really nice manner, so that all of the class that are assigned toe. The people get completed within the 40 hours of time. But of course there's one off occasions where it might go just a little bit more than that.the top three priorities for for us is to kind of like, uh, in the Sprint is to like, First of all, it's like cooking to try to accomplish whatever is the goal of the Sprint. Like when? When we start a sprint, we decide that this is the goal of the springtime on a sprint. Cool. I might have something like I have finished. At least 90% of the task has been assigned to me or I have to move this much off this much of my work. Most Republics like whatever task that I have taken, I think most probably I have to put that in a state where users can actually start using them. Uh, if it's kind of a delivery story, if it's a research based story, then at least I have toe. I have to do enough results so that either myself or someone else in the team can pick up a story in the upcoming sprints. Yeah, so the foster charities like toe toe accomplice, everything that has been decided but will be part off the next two weeks off work or next three weeks off work. Andi and the subsequent ones that like? Yeah, Like like I said in the previous or examples like if we have any done. So if we have any new members in the team, kind of like mentoring them are making them, uh, more comfortable and making them continue noting populating, uh, driving some of those things is kind of a second. But the third is like, uh, it was like getting prepared for the upcoming work, not just in the current sprint, but for the but for the future Sprint. Like, do we need to up skill ourselves? Do we need to personally train ourselves and new things and new technologies, uh, do some kind of training so that way have enough skills to kind of work in the future projects that are coming up not just in the current scheme of things like the current few weeks, but probably from a long term perspective, like all of the things that we need to do online so that we can keep our project going on

uh, in my current role as Salesforce developer, I mostly use, uh, a picks, which is kind of ah, uh, like property language that is used inside sales force. So that is the language that they use the most. And apart from that, I use JavaScript as well toe do any kind off front and work inside sales force. But it's not very uncommon for a ourselves for a developer to know better for the language is like a let's say, no jails or python Java toe kind of integrate with other tools and other enterprise system with organization. Yeah, so yeah, also exact. Nowadays we're moving into so many different tools and technologies. It's on interacting with so many systems. Uh, it's kind of good to also no other cloud based platforms like infrastructure platforms like either AWS or your are Hiroko. Yeah, the kind of things that we use a day today basis models and algorithms are kind of hard to see, like what? Specific. But yeah, in general, the best practices that are to be followed we can kind of try to do that. And yeah, but all that going things that we learn during the college There's still kind of help at some point. They are not something that we do one a day today basis, but they're definitely helpful over the long run.