Security Architect Q&A Answering Your Security Architect Career Questions

Welcome everybody to our Security Architect webinar from Google Cloud Careers. My name is Chris Johnson, although my thanks as Michael gives my name is Chris Johnson. I am the chief operating officer. There you go. Cloud careers. I am joined by Alonzo Coleman, who is properly named, and, Michael Gibbs, the real Michael Gibbs, our founder, and I, everyone. I always forget to change my name when I come in here and start the meeting before Mike does. Although Mike started it for me, so I don't know why that happened. All right, well, it is time for us to get started. So before I hand it over to Mike, I do want to say a couple of things. We're going to be doing a Q&A session after Mike's presentation. So I want to encourage all of you ask your questions on them in the chat box as you get your questions. Don't wait because you might forget them or you might, get disconnected, or you might have to leave because, a family situation or work situation or whatever it might be. So if you've got a question, put them in the chat box. We're going to be keeping track of all the questions that you put in there. That way we can make sure we answer all the questions whether you hear or not, where we want to answer every question. That's platoon's. So we're going to be recording, and we'll be sharing the recording with you, at the email address that you registered with. So if you put those questions in the chat box, we'll be able to answer them and, and get you taken care of. Now, as it relates to questions, we're also going to invite you to come off mute when we get to the question and answer portion. So if you're able to come off mute and talk with us, that'll help us, help you a little bit better. Otherwise, we'll answer the questions as they're posted in the chat box. I'll read a bot. If you're not able to come off me of, but if you are unable to come off mute, that'll definitely help us. Help you a little bit better. So be on the lookout for that opportunity. As we go through the Q&A sessions. All right, so let me, is this a question or comment? Let's just. If Emmanuel wants to come on. I always like to ask people if they want to come off mute instead of me just reading off their comment. I hey, Chris and Michael. Hi. So nice to speak with you. Yeah. Thank you. Yeah. As I said, go processes. End of January. Yeah. And congratulations. Oh. Thank you. Does a tough exam. Yes. You don't you do not take it twice. Yeah. So my background is, so I started in network engineering, kind of working as, substitute consultants. Yeah, for a transport company and, trying to move into, security architecture role. So, just hoping that your program can help me towards that path. I mean, like, I essentially like, what can I say? Because, I mean, like, in the job they ask you when applying for an architecture role, they want to see you. You've done all this architecture stuff, you know, and, I do want to have those things, you know, so I'm like, coming at second guessing things because the. In my room. Yeah, I do work with, solution architectures, network architectures. Like I review designs. You like high level designs, a level designs, you know, the is easy to be. So that kind of stuff. Yeah. So the one with that kind of I kind of, stitch up examples, you know, just put on my own my CV. Yeah. Okay. So I know what's going on, and I know you're probably not getting a lot of interviews with that. Correct? No I'm not. Okay, so here's the valuable thing. Look, you've got good skill. If you come from networking and a lot of this. But what really is, is there's a difference between engineering and architecture. So getting you involved in looking at some of the technical designs. I love that. What we'll do is we'll translate that into something participation in Architectural Review boards. We'll translate that into what it actually was, and something that's relevant. But what the real critical key is to actually be able to translate what you did into work. For example, I'm fairly sure you can correct me if I'm wrong on your resume or your LinkedIn profile. You don't have a lot of things about managing stakeholders. You probably don't have a lot about a go about conversations and presentations to the C-suite and the board. You probably don't have, crafting of business cases in your resume. I, I'm guessing, for example, are those things true? My assumption so far. Yes, yes. Yeah. 100%. Right. Yeah, yeah. So what you're doing is you're showing the world that, you know, security engineering when you want a security architect job.

Now, if we take what you've done, and I'm pretty sure there's a lot of it, and then we teach you how to reframe some of those things, because I'm sure you've participated in meetings. I'm sure you've had to inform stakeholders or write up some documentation on things. Right? Yeah, yeah. I'm sure. So what we'd have to do is we would have to tune it up. So first, up, I'd say the skill. So you really know how to walk into an organization and be able to look at it, look at it and see what the organization's assets are and figure out how to get them, and then the rest of those assets. Then being able to look at that policy and understand what they have to be able to look at that business architecture, for example, how does that company operate? How do people do their jobs? Because that's going to be critical to make sure it works and obviously teach you how those things work. Then we'll teach you how to ask the right questions, because if you ask the executives the wrong questions, unfortunately that ends the dialog right there. So we'll teach you which questions to ask and I know this is going to sound strange. We're also going to change the way you think about things, because there's a very different thinking pattern required to do something versus to plan something. For example, earlier in my career, I did spend three months as a network engineer and knowing how to go to a Cisco router say, turn on OSPF router, OSPF with the process, I'd put a network statement and put it in there. That was the engineering side. Now, when I moved into that network architecture role, it was never about configuring things. It was should we use OSPF or intermediate systems, intermediate systems. How much intelligence do we need to have in an area. So what should our areas be look like now for these additional areas. What lessons do they need. So we make it a stub area and not so stubby area a totally stub area where a route redistribution points. So it ultimately became a very different discussion of evaluating trade offs. If we do this, we gain this. Or if we lose this. And I suspect you've done some of that already. But that's going to be most of our job of evaluating the train those options and then framing it to executives. Option one we leave our risk unknown. Our unmitigated risk right now is $87 million. And the likelihood of being breached is strong. And if we were breached here, as our exposure option two is we use this option. It's fairly simple. It's fairly elegant. It's not going to solve all of it, but it'll mitigate these things for only $8 million. Option two is this. Option three is the. So that will be good. I think what will also help you is really getting you to be able to show yourself as an architect. And then when we take that, networking background, which is going to be very helpful, and then when we take what you've done, the CISSP is giving you probably a good intro to security, because that's what I would consider it. And then by the time you're done with us, you'll have such skills that, with, especially with your background in networking, what you've already done, I think you'll have really good options and it won't be a basic entry level architect role. I think it'll be a good one. Okay. Thanks, Michael. You're on. Any other questions? I know? No. No, that's that's all for now. Okay. All right. So looks like, so next we've got, Anderson. I'll see, if Anderson comes up here. Yes, sir. Hi. My name is Anderson. Anderson, I do have a good evening. So my question was, would if you are coming from, dev set ups, background, lots of DevOps, lots, programing in background with Golang and. How would I be able to leverage that skill with, security architecture, AI? And then secondly, what was that other certification besides the CISSP and, CSM? I think you mentioned. So how. Would how good is that cert? Okay. So but can I ask one question real fast. Might. Sure. So Anderson, without telling me about your background, what do you want to do? Build systems and, present them to possible prospects like C-suite. Do you want to build them, or do you want to design them and to develop them and create like create them? Or do you want to build them? That's a tough question because I, I enjoy building things and I also enjoy that aspect of business

of presenting an idea into actual, like an actual productive services that people use. The reason, the reason I ask is because while you may find some places that want you and like you do both those places, you probably not the places that you would like to work. Yeah, you. Well, these are because these are two different domains. These are two different, two different areas. Yeah. Do do you play sports. Do you watch sports. Do you what. American football or anything like that. The athletes professionally. Yeah. Oh okay. Yeah. So it's like it's like a, an American football player playing both defense and offense. While there are those very, very rare few people that can play both defense and offense and American. Yeah. 99. 99999%, American football players play defense or offense. Yeah. So that's why I was asking, what is it that you want to do? Because we know what you're capable of. We know what you've done. Yeah, you know what you're capable of. done to them. What do we want to do? Is the thing that's going to drive? Mike's answer primarily, I believe. Yeah. And the key is they're very different of their own. If it's a real architect job and is going to pay very well, you won't be allowed to touch the technology. Here's how bad it is, Anderson. In my first real architect job, what ultimately happened as I was a network architect at the time, the client had a massive BGP error that was taking down a bank, and while I happened to be there, I said, well, I was a BGP principal consultant for a while. I'll fix it for you. You know what happened? I went into the router. I fixed it now the bank called my manager and said, I really like this. My guy, he communicates well. He's a great architect and he fixed my environment. My manager made me go to New York City, called me into the office and said, if you do it. He said, nice job helping the customer. They like you do it again, you're fired. And he explained to me why. that they would no longer view me as a strategic asset, which they didn't, once they saw me as a techie. He also told me that, you know, Mike, we've got people in the tech that could pay a quarter of what you get paid to go solve those problems, and I don't want to use my expensive resources. And he said, if you want to build stuff, just to let you know, the majority of our development team and building team is in India. And I promise you, they don't get paid what we got paid over here, but I can ship you over there if you're interested in that. And, in a development job. So I love developers. I love the work that they do, but it won't fly in an architect job because you can't fly the airplane and then take care of the passengers in their seats. So what happens is, if you do, here's what's going to give, because I've seen people that try to do both. You won't be managing stakeholders. You won't know what the executives need. You won't be able to find out what the organization's problem are. You won't be able to change the culture that are there. And ultimately, what will happen is you won't be able to do the architect job or be there. So it's not that I don't love those people that are great hands on people. They're magic. Without it, we have nothing is said in the architect job. You won't be able to do that. You just won't be allowed to for those reasons. It's a constant, but it's also it's a job thing predominantly because what you can only focus on one thing at a time, which is why the people that are the military strategists, which are architects, generally aren't the people fighting on the battlefield. It's the people that design the skyscrapers, don't build them. It's just a different job. So if you wanted to be an architect and there's lots of advantages to becoming an architect in terms of salary, in terms of future and not being able to replace by AI and all that, then what? We could definitely help you because we would take what you have, which is and say application side. We would take what you understand about DevOps processes and operations, which is key components to an architecture. And then we would add the remaining elements so we can get you there. But you know, for example, I think Chris was saying he was just did a check in with Pierre. Pierre was a sailboat operator before we trained him. And Ali is a solutions architect. Ivan was a college student. I go back to him all the time working as a waiter before AWS hired him. I forget what aura was doing, but she just joined by joined AWS a few weeks ago. So it doesn't really matter where your background is because there's a lot of set of skills. I'm sure that you probably know more about application security than I do. I guarantee you do, and I guarantee you know more about DevOps operations that I do. And you know it in my architecture team. Remember, architecture is a team sport.

I would have someone like you because that level of application security knowledge is an asset. I would join the team if I would be the network security person, because that's what I know. Isaac would come in as the IAM person because that's what he knows. So everything that you have is an asset. The question is use what's valuable. Learn the rest. Chris, how about you might have an embarrassed but so back to your original question. How can, how can you leverage the program to add on to your experience? I think Mike just hit the nail on the head there, but that's hopefully now you understand why I was asking my original question back to you of where do you want to go? Like, what is it that we're wanting to work towards so that we can figure out if, if it's the best leverage for you know what? What are your thoughts after that? Anderson? Well, it's very hard after more than 15 years of banging your keyboard to just. Yeah. Right. So that. Yeah, it's I started my journey with, network, believe it or not. Fun fact. The second day, we ran back whole full California, the Japan Undersea cable configuring. And in Unix, Linux, just east of, Worcester alone, we did I've done operations in the network ops. And so I've been used to keyboard keyboard, keyboard. And now it's like, okay, you have to stand in front of people and present. Yep. And I'm just confused now because even at work, they're letting people go because at some point it's people who are just talking at some point in the government start looking at them like a waste of money. So here's, here's how I'm going to do to answer the question, everything that we have in our program, whether it's the Security Architect program or the Cloud Architect program or any of our programs, but the Security Architect program here, since that's what we're talking about, all of it is infused with that non-tech yeah skills. It's infused with that. How do I communicate this highly complex technical thing that I. You took care of with that? I've heard that was highly complex and technical. How do I communicate that to somebody that is going to pay for, how am I going to communicate that to somebody that's going to allocate resources, whether it be people, time, money, that's how you would be able to leverage what we have to add to the technical skill set that you have, changing that way of thinking, that speaking, that communicating that, that relating of, of that information and knowledge and competence that you have, that that's the, that that's what our program is designed for. Yeah. It makes it because that's the big role of an architect. Now, we have had engineers that have taken this program with the goal of becoming architects. Oh yeah. And they found out that they still like engineering and didn't want to be an architect. But then they took director and VP of architecture positions. One person took an incredibly high paying engineering job at Google. Because what's the difference between the regular engineering jobs and the ones that are irreplaceable, paid the most? It's not you doing it. It's more of the trade offs. So I've got option one, option two, option three, option four. And that's your principal engineer and your distinguished engineer all day now okay. Now because I'm the person that knows it best, how do I explain it to the key stakeholders so they understand what reality is? You know okay, I go this way and yeah, that's going to work. But we're gonna have these 22 problems. I'm going to go this way, that's going to work. But we're going to create these new problems. Can we tolerate these problems versus these problems. So that's really the work. So understand that is the difference between those people that are purely irreplaceable and those people that get promoted it to that side. It's can you take this more of this ambiguous thing like BGP and explain to me why you needed to we should use it, why we're investing the time, the resources, what have you, that kind of thing. So kind of hope that makes sense. Or let us know if you've got any questions. That makes sense. Thank you. Absolutely. Thanks for the question. I always enjoyed the questions.

All right. I see I'm going to see if Mo, can come up here. If Mo is able to come up with. Great. I'll let them as their question, I joined a little late. If not, I can answer the question. We can easily answer the question without you coming up, but, we always enjoy a conversation. Yeah. While we wait to see if they can come off mute, I'll go ahead and read it off. So. Joined late. Sorry. Not sure if this has already been covered, but I would like to know if there's any prerequisite to joining the program. For example. Experience. Well we're not. No, no no. And here's the reason. Everything you've done can help you or hurt you. Do you want to know who the easiest people are to get an architect job? And I'm not joking. They're medical professionals and sales reps. Wallace A Garner, for example, was a sales rep, got the most senior of all the architect jobs in less than nine months. As an enterprise architect at JPMorgan Chase. Who else did a Jermaine? Jermaine was another one. Never worked in tech in his life. Was selling landscaping gear. But boy, he had a knowledge for math. So what does it really matter? It matters having the skills. And I'll show you where engineers typically have a set of skill for. And then I'll show you why sales reps typically have a set of skill, and then I'll show you why it doesn't matter because we can learn anything we want. Just like I left medicine and moved into architecture myself many years ago. So here's what we're realistically dealing with when we talk about skill set, we're talking about all of these skills. So let's say I have a really good network engineer. Do you know where they're going to have skills, network security. Now they may know a little bit about I am that network engineer and they may know a small about encryption. They will have no knowledge on data security, risk management, writing a security policy, AI operations, incident response planning, business continuity planning, security governance, application security. Generally speaking, that network that's that network engineer probably doesn't have any CXO relevance. Any stakeholder management skills, any sales skills, any vendor management skills, any experience getting information, what have you any experience, you know, giving presentations, communicating with the C-suite, negotiating things or business. But guess what? In about a year, I take lots of people with network engineering backgrounds a year and a half and then working as an architect. Now you give me a sales rep like Wallace is gonna, a sales rep like, oh, who took his first job as a senior solutions architect at Deloitte, a sales rep like, I've got some, like, germane, all sales reps have to know business because you can't sell the business that you'd understand. So they all came to us with business acumen. Do you know who agrees to pay for the purchase order? The C-suite. So the sales reps were CXO relevant. You know, the big part of the job of the sales rep is managing stakeholders. And they knew how to do that. Most sales reps are fairly emotionally intelligent. Most sales reps have to be able to write for executives a two page thing, so they're willing to invest whatever money it is to purchase. Most sales reps have some good knowledge in sales because that's their job. They're typically good at managing vendors, asking the right questions, and influencing others. Now, salespeople typically negotiate higher salaries. Typically, they're in negotiations constantly. They typically have executive presence and executive communication skills. And sales reps do a lot of presentations. So you give me a sales rep and they're the best prepared person to become an enterprise architect or a security architect, because they already have 50% of the skills. Already. A health care worker like me had a lot of those skills. So it doesn't matter what you've done, it really doesn't matter. It matters that you come with you with some skills, you learn the other skills, and that way you'll be there. And it's not just sales reps. It could be a teacher. Mike, set sales rep 50 times. Does that mean it's only sales reps? It could be like Nicole, a lot of other roles like teachers, health care workers. Yeah. Anybody that interacts with people on a regularly consistent basis have it. Yes, I had I but that doesn't mean that those are the only people that are successful. So back to the right. Anybody can do it. Back to the original question is their experience required? No. Because I can't everybody I have to start from ground zero. I have to a level guess said everybody to the minimum level. And then we build you up, build you up. And that way, if you're a medical professional like me, great. If you were a nurse, like, was a Karen that came to us, who's

now a director of architecture, she had lots of emotional intelligence. She had a lot of experience asking questions. getting patients to do what was necessary, Karina. necessary. She had given lots of presentations in health care when she was a manager in health care. So, I mean, you know, she did really well, had hairdressers and nail stylists, too. So, yeah. So, like it truly. So the way our program works, we've got the, we've got kind of like two linear tracks here, the on demand stuff that you do at your own pace. And we've got live classes where you, you apply it and you practice it and you ask questions and you, you get, break stuff. The, but in the on demand stuff, we have orientation. So your frame like here's the orientation, just like you got I got a new Herrero and tuition, just like you got a new student orientation in school. We got orientation, and we got straight from that orientation into a what we call an introduction of technology. And with the way that those videos are done is truly an introduction to technology. We didn't quite go how to use a keyboard, but we did go, what is the cloud? What is the network? What is security like? So we truly start at introduction of technology. That is our very first thing after the orientation. And then we go into fundamentals. So and a lot of places fundamentals is that first thing no fundamentals. That's the second thing for us. So and we have it set up to where that intro to technology, if you're if you've got experience okay great. You can watch it at two times speed or one time speed. You can just breeze right through it and, get to the fundamentals. And then we're after the fundamentals. If it's a security architect program, then of course we've got the security architect specific training. And if it's the enterprise and we at the enterprise specific training and depending on the program, it's everything goes through that funnel of intro to technology and fundamentals and then into your, your things. And we do that because even that person with 15 years of engineering background doesn't necessarily have the introduction. They have that that baseline understanding of that, that piece of technology from an architect's perspective, if we're talking about networking, they might have that understanding of networking from the engineer perspective, from the implementers perspective, but now from the designer's perspective. So even low hit are hasa who got 15 years of engineers. So they're going to watch this. What is a load balancer video, which is going to be very introductory to them. But it's purely from the architect's perspective, purely from the design perspective. But how to configure your load balancers or how to, that do implement your storage container and your VMs and all this stuff, in case you can't tell, I'm the operations guy, so my tech terminology doesn't seem to sync up. That's why. But hey, we all of our stuff is taught from that. That perspective of this is your first exposure to it. So whether you're no tech experience or whether you come with 15 years of engineer experience or some people that have joined our program and they've been working as an architect for ten years, and they're trying to get that CTO position like Angelo. Yep. You know, so it's everybody kind of starts with that same framing. Absolutely. Let's see. Michael kind of made a statement there. Actually, let me kind of help with that. Yeah. I mean, do you want Michael wants to come with me or. No, I'm going to address it because I think it'll help a lot of people here. So, Michael, the key with the CISSP is it is an architecture exam. And I'll explain to you what I mean by that. There is never going to be a right answer on the CISSP exam, just like there's no right answer on which medicine I subscribed per prescribed for this patient, because based on the patient's condition, there could be 50 options. Same thing with an architecture exam. So with the CISSP exam, because it's an architecture exam, you're going to have four answers and none of them are going to be great. One of them will address four out of the five issues. One will address three of the issues, but one won't address a critical flaw. And you're going to have to choose what the best option is after evaluating all trade offs. Now, when I took it, I already was an architect.

I already knew security. So for me, I took a five day prep class and then took the exam. Why? Because it was architecture thinking. And when I saw those questions, I said, oh, this is familiar. This is just like when I went to school and I learned what medication would be right. For what condition? No right answer. Look at all your options and choose the best. So because the architect is such a business mindset, you've got to look at it from the architecture perspective. Given option A, option B, option C, which would be the right architectural trade offs for the business? And what is architecture always about? Solving business problems. So what happens is people go through the exam, they pass the exam, with a practice exam. But it's the thinking that shows you why you should choose one option versus another. And that is that executive thinking an architect is an executive position, which is why engineering typically doesn't translate so well even though it can be transition, which is why engineers think that test is a useless exam. And engineers don't like the CISSP because for them, where's the beef? Where's the actual piece? Where's the this where's the that? Where's that hard core? Yes or no answer. It's not there. It's an architecture exam. So for architects like me, it's simple, normal and straightforward. If you're looking for that precision answer, this test is going to drive you nuts. That's the reason why. So, a manual. Is it possible to trial a few of your sessions for free, perhaps for a couple of days? So we don't offer free, free trials or free, free access to any of our career development programs. And the reason we don't do that is because we train the same way on YouTube as we do in class. And we actually I'm going to put a link here and reply to your message. Emmanuel. That's one. So I put a link to the playlist from our recent, Cybersecurity Fundamentals series. This was literally classes. And they're now available on YouTube. So these are the so anything that you see on our YouTube channel that is the same way, same style, same interaction, same everything. Yeah. The only difference is, if it's on YouTube, if it's if it was originally native on YouTube, and we can't, we can't bring people off mute like we are. Yeah. But you'll see on that cybersecurity is fundamental. We tried that one was hosted on zoom. And that's where all of our classes are like this. Like we encourage people to please. Right. Please talk. Please take part. Please ask questions. Please, please ask us why we did X, Y, and Z, or why we did a, B and C? Yeah. So we don't offer free trial, so to speak, to any of our career development programs. Mainly just because the way that our programs are, are long form, immersive type of training. If we try to do a it's a trial period, you just be dropped in the middle of a, of 1000ft deep lake and didn't know how to swim. And there's not any life preservers anywhere near you. Just be kind of like, what's happening? And so it wouldn't be fair to you to expect you to have to grasp that entire thing. So that's why we put all of it out on YouTube, so that you get a feel for the way that Mike teaches, the way that we teach, asked to interact with students, engage with students, whiteboard all this stuff. So that's my operation's answer to that. I because then to talk on this, what I tend to do is a lot of little tutorials on YouTube. For example, I think, this week we're going to one on platform architects versus enterprise architect versus security architects. I think it's on this week. It's on the calendar. Now what that was going to be on zoom. So that one actually will be more of like our classes. Yeah. So and that one will be on zoom. And the key is by doing that, I can teach the same class that I would, I invite people from all the time, and that way I keep our exclusive content for the program, members of our content. And I still provide a lot of free. So if you look at that cybersecurity fundamentals class, of course, that we took there was probably, I don't know, 15, 20 hours of training in a as opposed to the thousand hours that's in our main architect program. So, that's kind of the difference. Yeah. So Joseph has a very good question here. And this is very, very important. So Joseph asks, what's the difference between the live version of the Cloud Architect and the non version. So the non live version has. All the on demand content.

The introduction of technology, the cloud architecture fundamentals. Now we only have an online version of the Cloud Architect career development program at this time. And that's because of the nature of the, the way that program works. So the non life program is not intended to be a replacement of the Cloud Architect career development program. It's intended to be a an opportunity for those that aren't able to afford, the price point of the live version. So there's never a if anybody ever tries to tell you that there is an equal replacement for live training, that is not true. You can not replace the value of live instruction. So that's why it's at a completely different price point, because you cannot match the value of that live opportunity. So I do not I want to be very clear upfront that we don't try to make any representation that, that if the non life version is equal to the live version. So the non live version has all of the on demand components and the and the class recordings. However we are not what we're not able to do any of the mentoring, the group interaction, the student, the facilitating of interaction with you as far as engaging with questions and coaching, giving tips here and there like we we are in the live so that is the difference is because it's not just the, the live four times a week. Well, in the case of the Cloud Architect for development program, three classes a week, it's not just the taking out those three live class sessions. It's taking out all the live interactivity, you know, over the course of your involvement in the program, whether that be messaging or whatever it might be. So I'm not I hope that gave a good. And so it's, it's truly meant for those that aren't able to afford that the, the price point of the, the live version, we want to so they get the classroom, they get classroom recordings of the live classes. They get the on demand content, the, the intro to technology, the Cloud Architect fundamentals and so on and so forth. But it's that mentor, the coaching, the development, the grooming, the all of that. It's not possible because it's not life. So, that's the difference there. Mike, did you want to add anything to that? No, I, I mean, what we did was we tried to create the best experience we could in an online manner for us and for the least, Cosby probably that was our goal. But, you know, it's a big difference when someone's in class and I can coach them on their presentation architecture, and I can coach them on the delivery, and then Chris can interview somebody with and see how they explain it. And there's a lot of that. And that makes a big impact when it comes to getting hired. So we do offer it, but we generally talk about the lie because that ability to be there, interact, work with people, get a chance to be in that live architecture sandbox and actually do that job with us, and then to learn from other people that have done the job we just feel is incredibly important. And that's where the magic happens, right, exactly. And again, going back to, so we're not just talking about the two hour class sessions that are to, you know, on Tuesday, Thursday and Friday. We're talking about the live Cloud Architect for development program has the group projects. We just finished a group project. Only the people that are in the live program to stay in the group projects. And those happen outside those class sessions that to those team meetings as researching the solution, the putting the solution together, brainstorming, putting a presentation together, putting the written response together, all that stuff, all that stuff is the stuff that happens in the live program. The and also something to consider if I always like to point this out, because sometimes people look at the not live because they're concerned about the time obligation. We specifically built the program. What the expectation that we only we

we hope that people can attend at least one class a week. We're not sitting here expecting people are going to be able to attend every class every week, week after week. Over 80% of our students work full time or more. Yes, we have students in every single time zone, so. Our times don't work for everybody. Just because they think it logistically is impossible. So we truly hope that people can attend maybe one class per week, and if they're able to attend, maybe it's for 15 minutes, maybe it's for 30 minutes, maybe they're, signed in and they got it. They got one headphone off so that they can hear the kid in the background and make sure the kid's not breaking anything in the kitchen because they're the one at home watching the kids that day. So we fully understand that, that there's life. That's why we're not a boot camp. Mike briefly mentioned earlier, you know, we're not a boot camp. We're not in a 16 week, eight hours a day, five days a week, or 44 weeks, four hours a day, every other day, whatever these, these boot camps do that. That's not what we do because we don't we understand that people have lives. Also another reason why we don't the, that people used to ask us about income sharing agreements, the reason we don't do income sharing agreements is because they require time constraints, like boot camps. They don't like our methodology. You are with us until you are hired. That does not work for an income sharing agreement company. So, that's because we don't try to force people to attend our stuff eight hours a day, five days a week, 16 weeks in a row. It's a little bit more flexible. real. Some of, apply that provided some context on the online live versus the live and a little bit about why we do our live classes, the way that we do them and what we expect. We don't expect everybody to be there every Tuesday for two hours, every Thursday Friday for two hours, if they're able to. Also, if they're not, they got a recording and they can interact with us based on the recording. Absolutely. So we kind of went down a rabbit hole there. I want to see if anybody's got any last questions. While I tried to get some last questions from people, I'm going to ask Alonzo first. Tyron, don't you do it. Alonzo, I know you've got something that you like to put in the chat box about reaching out or emailing or scheduling calls or whatever it is. And if you'd like to, If you'd like to put that in the chat box, that would be awesome. There I will ask Tyron after Alonzo does that if Tyron would share the link to our training page with our 60%, discount, there's Alonzo. Big beautiful message. So I'm going to read it out if you've got additional questions. If you'd like a copy of Silva email us at info at go Cloud Career. Stop that. All right. You can call us. I can't read those numbers. (772) 212-0166. You think I would know that by now? Schedule a call on calendar with one of us? That's what you got in there in the chat box from Alonzo. Karen's going to be sharing the link to our training. Post. There it is. I am going to be sending a, It might be Alonzo. We'll be sending out a follow up email as soon as we finish the webinar. Just as a reminder. Hey, if you want to talk with us, here you go. If you want to email this, you got our email now. I'll be doing that after the webinars finish tomorrow. Be on the lookout for the recording of the webinar and all your questions. Other juicy insights that Mike shared earlier. So that's what we've got planned. And since I haven't had any questions pop in while I've been doing this closing bit, I will ask Mike if he will do his closing bit. Well, if there's no last questions, I'll go play with my cat, Cindy, because I'm sure she's looking for somebody to feed her tuna or shrimp. Because she's a little bit too pepper.

I hope, all of you, had learned something about being coming an architect tonight. This is that. You know, I've had a couple jobs in my life. I was a firefighter, paramedic, then a nurse, then a nurse practitioner, internal medicine. And then I moved into architecture. And it was the most fun job that I've ever had. So now I'm spending my retirement training the next generation of architects. That's why we run in an environment where you can stay on the program until you're hired. This is, you know, this is my thing. It's training people for the next generation. And I just love this world. We've got lots of experts helping us create these programs and making a great lots of people on our team that really make sure that you stay on this program until you're hired. And I'm pretty proud of what we built here. For those of you that joined us, I tell her and others, congratulations. I can't wait to, see more of you in classes, especially these other security classes. And welcome. And I can't wait till you graduate to. And by graduate, I mean hired. So stick with it until you're at it. For those that didn't, I hope you do. And I get to meet more of you on zoom like this, where we get to talk more often, you get to start asking questions, give some architecture presentations. And I love architecture. So what can I say? Architecture and cats, that kind of thing. So, I hope you had a good time. For those of you, they were here. It was so nice to meet you. I hope to see you in class or another webinar, or come back and ask more questions another day. Don't be shy. This is a career where we really want to help you. Have a great night everyone. Good night everybody have a good night.