So presumably, I think, another way to ask this question with the like, How did I get into Google? Um um, I would say the path to getting Google took me like six, almost six years, four years in college and then two years in my first role. I think like the 1st 4 years, I think it calm side undergrad degree is fairly challenging. I wanted to detect, so I would say that's a large part of the journey. It is very rewarding, and we'll actually actually joined hurt when a Georgia Tech as industrial engineering switched majors. And uh, I got to say, I think probably the most challenging defining part of before your graduate degree is to get an internship, because that's when you translate your academic skills into something that is actually stamp on your resume. And, uh, the competition is strong because I remember I was like, just work on campus. I was making, like, a couple $100 a month and then suddenly that internships were paying, like whoever who got them like 20 K for two months. So that was what you were competing against. And no, I think your competition often already had, like props. Somehow we have multiple projects and they're the belt or like past internships. So I would say, like probably the defining moment was finally passing. Didn't interview enough so that Atlanta an internship like a legitimate company. In this case, it was a smaller firm for me. Actually, I also had a interview for Google, and I got rejected the very first time. Yeah, I think it's a challenging. So I'll take the 1st 4 years really was just trying to figure out what computer science was about and then landing that very first internship, which I think a lot of students gonna test. It's much harder than itself unless your life, that 1% slight, you know, it's so good, like Cody. And then it hit the post college the 1st 2 years of my life. I actually got a return offer at the internship that I, um, work that in. I just, you know, spent sharpening, spent those two. You sharpen my skills, I think I joined. I was lucky to join a smaller company, and Richard stuck because at a smaller company, you're you're coding. Ecosystem is not as good, so you have to take care of, like every stage of the fought for a funnel. So, like, right now, do I write I write code and I barely know how gets because that's a whole 100 rubles job. But I my former company, like everything you had to spend up your own vmc coded on that p m. And then once he submitted us, you were the tester and awesome deployment. So I think it, like, made me a very strong full stack engineer. Um and I would say, I think I was lucky enough that, uh, like the government were actually reached out to me on Lincoln. So I didn't need to go to the trouble like trying to send my resume, hope that it floats up in the sea, resumes. But if I could give like students tip in college would be to primary things. One. I wish that more undergraduate research because, or try to get a t a position because those two things will really help you stand out. And also it's just fun, like doing research. Doing undergrad is like really rewarding, and you don't really get to do that unless you pursue a master's or PhD later and then, of course, trying to get a t a position. That's also easier said than done. But I did not get off. Yeah, and then the rest was just once I got that interview was just studying for it, and then so I would say those things.

Google is awesome, I think the hype Israel. It's a very, very humane company, and I don't find myself working more than eight hours a day on average. Some days, you know, I worked like six for seven hours and then eventually down the line, I catch up by working like a nine hour or 10 hours a day and for is different across teams. I'm in Google Cloud. I work on a monitoring pages. So what that means is that I have to partner with different teams to figure out their needs. So I'm in the position where you have to work with a lot of different product managers, software engineers and UX to reach consensus. Um, yeah, the workers are great, and it is it does I answer a question, actually can't afford

go Well, I work in front of right now. So for my particular project, I worked on typescript in your So that's like what I'm working on primarily. But occasionally I also need to update the back end, which is a Java. Um, but across the stack, I mean, it's a huge company, and I think we're at, like, 100,000 strong now. So C plus plus is also very popular. Python. So typically in a role like that's, I think of old question, because who was most offer engineers? Uh, we have a very close to ecosystem. We don't use any of the like. We don't use get first that we have. I would say our assistance closer than mercurial, and we have just like a great suite of tools that help you like. Figure out what issues are with your coat. It's but it's not really there's not really outside equivalent. I would say the closest equivalent would probably get home, but it's like much more powerful get home in terms of authorizations. I feel like a lot of people. I feel that the inner once you pass the interview algorithms, you don't actually find a place Bibles. Algorithms? Well, that is true. I have found myself in a position where, like passengers interviews, they strengthened my life mental fortitude enough that, like it's much easier to parse an ambiguous situation, which you were very frequently encountered because you are, you know, you're not right in front of a vacuum, so it's often like you brought this legacy thing that you need. Teoh reached its new destination. There's a lot of like trying is not. Not everything is documented, so you have to rely on.