where I got to become a software engineer. I've studied computer science in college, but before college, I actually didn't know anything about computer science, and I didn't have any computer science background. So there is definitely, you know, if you don't know necessarily what you want to study before you go into college is completely okay. And to be a software engineer, you don't necessarily have to start coding from a very young age or anything like that. And so I started studying computer science towards the middle of my first year of college, and I really, really enjoyed it for me. I think that's a really essential part. I think of figuring out what you want to dio post college, and you want to do potentially with your career is you should have some enjoyment from from the work that you're doing and so don't feel necessarily pressure to just go into computer science or or software engineering or a field that's very popular because you feel that you should, or that it's going to make you the most money because because computer science can be very hard and it's not necessarily the easiest thing to study and software engineering is not, Let's say that you things brought to take You want to make sure that you do get some type of enjoyment from programming. And I think for me, um, what was really essential for me to solidify to knowing that I wanted to be a Sapporo engineer was really during my internships during the summers of between school between my years of school. So I did three internships while I was in college, and my internships actually really were able to help me understand what it's like to be a software engineer and be in the working world versus when you're in school. You're doing a lot of theoretical work, and sometimes it's hard to know how that work is going to apply to the world world. So doing those internships really cut me grounded and company focus than knowing that I wanted to continue to study computer science. I think the incidents that I had along the way that were kind of tough was like I said before, Computer science can be really hard. The classes can be really hard, the workload can be tough. And so for me, I definitely had times where I didn't know if I was going to be able to continue in the major because of men, and I have been doing as well in the class remained my hardest class in my whole Major was discrete mathematics. I really love during project based work. I love programming encoding, but we did have to take some more of those theoretical classes. So doing that discrete mathematics was really, really tough for me. But I just went to every office, our I went to, you know, every open TA session and just worked my hardest to try to pass the class that I can continue in the major because I knew that I really enjoyed it. And so I think that's the thing. You just have to figure out what experiences can really ground you in tow. Feeling secure in knowing that you want to continue on the path forward. Teoh, start your career up your college

one thing here is that I was engineered specifically a calm. We tend to work pretty normal hours. So you know, your 9 to 5 or 10 to 68 hours per day on before quarantine. Before we were all forced to work from home. We work in an office setting, so I will come into the office and usually work. A typical day is a mix of programming collaborating with others and meetings, Um, and excuse me and technical review and discussion. So the coating is working on whether it's new feature work or working on maintaining the code being. So fixing bugs or doing some technical were factoring in the code base. That's a portion of the day and then you'll have meeting. So the meetings usually will be with the product managers on my team who are responsible for coming up with the new feature ideas and that the road map of what We're going to be working on it and, uh, for a particular quarter, Um, and then, well, something with the designers. So the designers air actually creating what the future should look like, right, what the technology should look like. And so we have to discuss and talk about what's feasible and what's not. And so We'll Dio will meet about that, and then another portion of the day will be around technical review. So, as engineers, we review jumpers work to ensure that we want to put it into the main cold base, and it's of the quality that we all agree on. And so you'll be reviewing other engineers. Work I'll, you know, I have my work reviewed in orderto get into the main up. And so that's kind of like a typical day work travel. My my job doesn't consist of much travel, but I do do a lot of speaking engagements and speaking engagements at technical conferences. And so sometimes it'll consist of talking about actual things that you know I did in my work or but something that I'm learning in relation to Iowa's or technology that I'm very interested in. So I would if I'm doing travel and usually would be for a technical cop friends, but don't weren't necessarily as often and then work from home before, you know, we're all working from home. They were pretty flexible it, and you can work involved once a week if you wanted to. But because of meetings, a lot of times we were in the office and we were collaborating in the office, and there wasn't as much kind of remote environment before. You know everything.

wondering if you're interested in creating APP for the iPhone, you typically have to know Swift, which is the program language and objective. See another programming language Abducted Seeing is older language. It's been around for a long time, and was is mainly news in older code basis. So now all of the all of the newer code bases are using Slip and Swift came out about six years ago, and it's, you know, much kind of easier syntax and beginner friendly languages and objected scene, which is more of a rowboat ver boast. And if you have familiarity with C, so you have to do a lot of memory allocation and management there. But Swift is similar to a language like python or Java script, and in terms of frameworks, you have to be familiar as an Iowa's engineer with you, I kit, which is Apple's primary. You I library and framework for how to actually build Iowa saps. You're usually you're gonna have to work an ex code, which is the environment in which allows you to build the eyeless absent, touch them with a simulator or on the device itself. Um, in terms of algorithms, that's a really interesting question because I think in school you're studying a lot of algorithms in a lot of theories. But in reality for your work, you're not necessarily using those algorithms in your day to day, so you might not be using, like, binary search or, you know, depth first search or things like that. But you will come up with your own algorithms in order to problem solved or create a new feature. So it could be an example. I was working on an on boarding future in which we're trying to do a questionnaire for users so that that when they open up, the APP reacts in a series of questions for how they want their experience to be. So I did have to build out and kind of questionnaire system for that, and so you're building out the algorithms, ensure that you know you can go back and forth in the questions. You can change your answer. And once you do get your answer, you can have a recommendation engine after that. So there are there are over the rhythms that what you will come up with yourself and problems something. But they're not necessarily traditional algorithms that you learn in school