So I moved to the US with my family when I was three years old from India, so I spent my early years in the Midwest and then middle school and high school was in Athens, Georgia, and did my undergrad at Caltech. And then, after I studied planetary science and environmental engineering at Caltech, I decided to pursue a PhD at M. I. T. in climate science where I was working in the laboratory and on machine learning models, and that led me into the tech sector through the experience with coding, and machine learning was a good segue into broadening my experiences there.

ACME AtronOmatic is the maker of a bunch of software solutions, the most popular of which is the MyRadar smartphone app. And so my background and atmospheric science allowed me to bring a science presence to the organization in an early stage. So I was in originally hired to increase the intellectual property holdings and develop the technologies. But through my organizational skills and interpersonal skills, I was promoted up the ladder to run the operations in general. And week to week, my hours changed, you know, with the Coronavirus. It's a little bit different now, but I'd say most of the time I was spending 25% on travel and 75% in the office and then try to keep office hours sort of normal 9 to 5 to handle the more operational sides of the business. And then, you know, paper reading or other academic type tasks I do in the evenings or the weekend whenever I have time.

the most challenging aspects of my job, I think. Arthuis, interface of the technical, um, and personnel Ah, crossroads where, you know, you might have a couple of really smart people you're working with, and they have two different valid technical approaches to, ah, certain problem. And you're trying to work through their personalities in order to get something actually delivered. And so being able to facilitate that collaboration is especially on projects that require higher complexity is really, really important, but also the make or break skill that you need in management.So most recently I was having a conversation with ah, back end engineer about how to implement some sort of authentication between the server and the client. And so the back and engineers like, Well, we really should do it in a way that conforms with how all of this other stuff that we have been building works. But the client engineer, um, was facing ah, different set of constraints and requirements because the iPhone Apple has a specific set of rules of how something can be done and they were having, um they're talking past each other in terms of communicating. Hey, I understand that this is the, ideally the best way to do it. But in practice, these air, these extra constraints that I don't have control of of Ah, um influencing. So how do you help me do my job? More effectively? Is the version of the conversation that eventually ended up being successful as opposed to, you know, understand me? No, you don't understand me. Which is ah easier to get. Um, if you dont spend some time and effort in the communication