from the education standpoints. Apparently, um, I am a graduate of years of Utah. I have a bachelor's and master's and information systems. So when I was one of the Earth's to Utah, I was getting a bachelor's degree while I was getting my degree. I was actually working as a student supervisor in the I T department at the uterus and I some of my rolls in there were doing with more of networking and ah, I t Infrastructure and I wasn't planning on going in. The commission technology at all was planning on going in a lot. But once I got into the business school and was taking some of the classes, I really liked and enjoyed some of the classes that they had. So I decided to major in information systems, and as I was going throughout my degree, I started to make some different acquaintances, and a friend of mine that I met worked for a company started company out of San Diego in California, and he asked me if I was interested in looking at a different position with their company while I was getting my degree. And so I applied for a position P Liam and as a what? The solutions engineer. And this is before I got my bachelor's and they decided to work with me while I was getting my bachelor's to allow me to work and have this full time position as well. And then, as I was getting towards the end of my bachelor's degree, the University of Utah had a terminal. They call it a co terminal degree, which allowed you to start taking masters classes for the information systems masters while you were in the under grab and I decided that I'd like to dio from a cost perspective. It worked out really well. So I ended up doing that and graduating from the bachelors, moving on to the Masters portion. And as I was in my current career as well that I was moving along with helium I once I got my masters degree, I had some additional skills and you know, some things that I learned that I was able to allow me to be promoted up within my current career as well in tow. What they we call it a lead engineer in my department and I m a t Liam now, for about five 5.5 years, and I've been graduated from your shitty time now for about 3.5 years.

decisions I have. So as a lead engineer, I work for our customer success department. What that means is, as clients come through, we are software as a service company. So as clients come through the sale cycle and then they are officially doing being deployed or integrated with our solution. We have a team that's called integrations team that helps them to become integrated with our products. And then we have a team that's called our post deploy team, and they essentially work of the clients that have already been deployed with our software. So we have kind of, ah, the implementation side of things. And we have the post implementation support and solutions designing. And my Rosa lead engineer is over that entire department. So essentially, any technical questions that come up that are at, ah a a little bit of a deeper understanding of what some of our standard solutions, engineers or implementation engineers have. Bill come to me is an expert and kind of every single topic that we have my responsibilities air to be, um, considered a an elite or senior level. Ah, you know, knowledge base for every product that we have and then Another thing that I dio One of my big responsibilities is to work with a lot of our our high end and high valued accounts that might be at risk or when we have a really big implementation that needs toe have to met something we've never done before. Maybe there's a new platform or a new integration that our company has just never worked with. That's my responsibility. Look at it from a technical standpoint and understand the feasibility that we're able to do it and help make it happen. Um, in regards to my work hours and and time spent on travel, obviously things right now with that and then they change things a little bit. But this standard that I would have the standard work hours that I would have is typically so our companies in San Diego. So I work a little bit more Pacific time zone hours, but generally all work from about eight oclock or nine oclock in the morning until about five in the afternoon. So your typical kind of 89 hour workday, um, as a startup company, there is naturally an inherent, um, you naturally end up working a little bit more than your typical, um, 9 to 5 job just because of a start up company. You kind of It's all hands on deck. So there have been a lot of weeks, especially my 1st 2 or three years working for t. Liam were attended working, you know, 50 60 hours a week. Not because I was told to, but just because that's what happens when you're working in a startup, Um, and ah, for travel. So I would, um, when I was just a solutions engineer a TV When I first started, I would travel out of San Diego once 1/4 for about a week. Um and then, you know, once every two or three months, I might have an on set with a client that would have now is ah, lead engineer. I have much more responsibility to be troubling, more so to kind of preface that I do work remotely. So I worked remotely from Utah, and I traveled on a San Diego now is a lead engineer at least once a month. And then I will have typically about once a month, also an on site that I'll have with one of our bigger clients. so time spent on travel a month would be, you know, two or three days for clients and then two or three days to go to the office as well you.

high level. So most of our software is going to be client side. So JavaScript html CSS. You know, any front end languages, they're extremely important and, you know, required essentially to know. Um, and along with that, some of ah, more of the libraries that we leverage and things that we looked at would be, like, react and anywhere. Um, you know, a lot of our engineers are very good with mobile applications, and so they understand swift. They understand. Um, you know, a lot of the that, you know, job a tow, understand? A little bit of the the, um, you know, Microsoft Mobile products and what not and then we have service side products as well. So it's very important to understand, you know, databases. How databases or structured sequel. Um, you know, we use a lot of Amazon Red Shift. Amazon s three. So understanding Jason on Ben also a big thing that we use as well is our ap ice. You know, I don't know if you can succeed at all in the marketplace. Teoh understanding ethiad. So those air, that's kind of a general platform reused or some of the client side, you know, Internet browser when you think of it and then also server side. So whatever server language, you know, sequel, those different types of things.