Working At AWS - All You NEED To Know - With A National SA Manager

the following is a conversation i had with tony colantonio a national segment leader and solutions architects manager at aws we touched on the day-to-day job of a solutions architect the role of certifications in the hiring process whether it's mandatory or not for an essay to be a programmer and really much more i've put an index in the description so you can navigate to the section you'd care the most about but i suggest you watch the whole video as tony does a great job sharing his perspective and different opinions on the aws ecosystem as a whole one more thing i am trying to grow this channel and reach out to more people to answer your questions so a like and a sub to the channel would be tremendously helpful and with that please enjoy this wide-ranging conversation with tony thank you for joining us today i want to give you you know the opportunity to introduce yourself so let's start by you know answering the uh the first question who is tony colantonio uh thanks um who am i that's an interesting uh question so uh first and foremost uh i'm a father of two i guess if you want to get into the personal level uh i have two kids a son and daughter one is uh 16 another one is 14 both in high school um i am married for 18 years 18 years 19 years this year and you know i'm a technology fanatic so you know anything to do with with technology computing uh really understanding how things work uh that is my passion so uh and that's why this job i think is a perfect fit uh and we can probably get into that a little later today i wanted to ask you a few questions and you know get your perspective and help everyone out there who are looking to join aws having a lot of questions about you know the interview process about how is it to work in aws about the culture at aws so uh how did you end up yourself working at aws and and why did you choose aws specifically yeah well that's a that's a great question so um i would say that i started out my career um pretty much working for a large canadian service provider and i was running you know their video technology uh division managing solution architects uh at the time and you know i i left the company to see kind of what the rest of the world uh was doing right because you kind of get tunnel vision when you're working for a large operator and you kind of think this is the world um but really when you when you leave that world is when you get to see what's um what else is is really happening uh and so i took on a role that allowed me to work with operators across the americas uh so a lot of work in latin america central america and the us and the rest of canada really um and what i saw was really a growing movement to the cloud um basically from 2012 to 2016 you know it really you know got to a a kind of a breaking point for me where um the the move from on-prem buying hardware was um becoming more and more of a [Music] difficult value proposition to give to customers interestingly enough we had one customer who had a whole program called um dfw which you know the first question i have to ask is you know what does dfw stand for yes and i said for uh don't fight the web right this is a major u.s operator and this is you know they had a whole program on don't fight the web and really what that meant was if there was an opportunity to run something in the cloud you will run it in the cloud and that was yeah that was kind of my last draw where i just thought you know i need to what time was that what year was that i'm just curious uh that was in 2017 2017 when we met that uh one customer um and they were already on their 2.0 version of don't fight weapon time so it tells you that they've already been on their journey for a number of years and they're continuing along that front so um you know for me that's when i saw the calling at the time i was working for a company that had a cloud offering it was a sas solution running on aws uh that gave me the opportunity to learn more about the aws platform some best practices what a cloud architecture should look like i got my uh aws uh associate uh certification as a result because i'm like hey i need to learn more about um about aws and more about the cloud uh from there i got my uh pro cert from aws um and then i somehow managed to land a job working at aws which was uh you know almost like a dream come true stars aligning um and now now leading the independent software vendors or isds and digital native solution architects which you are on the team um has been you know phenomenal it's kind of like bridging my past life with you know the journey that customers were on to move to the cloud and now working for a company that's you know obsessed with helping customers you know grow their business um you know and and move forward goes to the cloud i think is a great fit for me would you say that your certifications helped you uh getting the job at aws i mean you're one of the rare managers that have a pro a solutions architect professional certificate um do you think that helped um i i think absolutely um it helped from an earn's trust perspective with the people i was working with because they knew that i was serious right because you can tell someone that you're serious but you know in in the world of aws um actions um speak volumes over words right and so if you have tangible accomplishments um they're gonna go a long way during the interview process but where i think it really helped is having those customer conversations um you know like i like to be in front of customers as much as humanly possible as much as my schedule will allow it and and just knowing that you know you have foundational background knowledge on a plethora of aws services um you can really you know drive a conversation uh home with customers because they know you know you're talking the same language right so um huge benefit you know i'd recommend anyone who's doing anything with cloud to get certified certainly you know aws is you know great certification programs they're really going to help build you know your confidence level um on uh what services are out there certainly the core services there's 200 plus services so there's no way you're going to be like oh i do a search i'm going to be an expert in all things but the certifications definitely give you some of that foundational uh knowledge that um you wouldn't have unless you went through you know that training program and or you know study for that cert i think super helpful my points on that or my my view on that is basically what i tell people is don't don't use the certificate to get knowledge use them more like to validate the knowledge that you already have because you need you know hands-on experience you need to know what the console look like you know don't approach the certificates as an academic you know diploma or an academic badge that you need to have a good amount of learn and be curious so i like to use our leadership principles and i know that's it's odd uh to folks who who don't know what they are but you know we have these leadership principles uh and you know we live by them uh and so it's you know i use them in everyday you know uh uh conversations like with my kids and they always look at me funny um but yeah so one of the major principles that an essay needs to have as such needs to have is a strong learn and be curious and if you you know if you come in and you show that you've gotten certifications that we know that you've gone out and and you know spent some of your own time to learn uh more about aws and i like what you said there about it it's it's not a check mark it's not an academic exercise i i viewed it personally as a translation of what i knew already coming in you know with my architecture experience like what does an on-prem you know uh you know typical three-tier web architecture look like converted to a cloud scale solution running on aws right it's it's translating what you know from the physical world to the you know virtual world so to speak um and and if you have that foundation that's why i didn't feel that the certs were um super challenging to get because i had some background but i could see that if you didn't have that background those stories would be super tricky because you'd be talking about things that you have no you know foundational knowledge of you don't know networking if you don't know compute if you don't know storage if you don't have any concepts on you know like what an ebs volume it actually evs what a block storage volume is um versus a file store right so these are concepts that you don't take the certification to learn about them you should you should have already had them as your foundational knowledge and then you figure out okay so now what does that translate to on aws so i viewed the certification process as a translation exercise to kind of change my mindset on what some of those technologies are that makes life easier when you move to the cloud and um most importantly is the scale right because that's something you know living in on-prem world for at that point 18 years um actually close to 20 years uh you're always building for worst case scenario right like that is um uh the the the goal of any infrastructure you know architect or manager is to make sure that you handle what we used to call the mother's day event and the mother's day event was like when everyone picks up the phone to call their mother you better have a system that's strong enough that has enough resources to be able to handle that right so that's the mother's day event that's in the world of telephony the super bowl event you know in the world of video you've got to be able to handle millions of streams right these are all major events and so you build solutions that can support that and on-prem what that meant is buying a lot of hardware that sat idle for you know 364 days in a year until that one day when you need it you have it and then even then it's always like do we build into enough capacity right because you never really know uh and so changing your mindset uh to work in the cloud and and work with their you know auto scaling functionality and the elasticity of it uh i think is you know one of the things that that is something you just have to learn right because you're not used to that from on-prem so you can't just say i'm gonna apply you know the elasticity of my data center in in the cloud when your data center is not elastic at all you don't have any spare resources that you can throw at it not not quickly anyways so yeah that was uh definitely definitely definitely i'm one of the best advice i've got uh one of the best advice someone gave me a long time ago when i say that i wanted to uh uh to learn about the cloud and he said just join a company that that's already on the cloud and that's pretty much what i did you know i was i was i was i wanted to to to get certifications and all these things and join aws he said no you know what just start by joining a company that's already in the cloud and and you will get hands-on experience and you will learn you know there's going to be this before and after that you're going to feel right um coming from an on-prem and then go into a company that's already in the cloud it shifts your perspective the way you know the velocity the teams gain the way workloads get deployed and new features get pushed uh and then you get all the support that you need and then after that you can get you know the certification to validate your uh the knowledge that you already have so what are your criteria as a segment leader to measure a successful essay let's say you know how do you say that this solutions architect is a successful one what do you look for ah a successful essay i would say um successfully as they would definitely understand that um what they're doing uh is scaling beyond their customer base and you know this goes kind of goes into the topic of the difference between what i would consider a sales engineer uh versus a solution architect right um and so while i would love love love love for every customer to have a dedicated solution architect this would be amazing right the customers see huge value out of it i think everyone would see huge value out of it but with millions of customers it's it's impossible right and so um and what we've seen is that when essays scale by writing blog posts white papers um doing a you know speaking at events where large numbers of customers uh are attending this is where the scale happens and this is when um you know that essays knowledge can then be spread across a large number of customers right so when when an essay writes a blog post and people say you know why rsa is writing blog posts why is this important because that knowledge that they've learned can now be spread across the whole world so they don't need to meet with a million customers but if that blog post touches a million customers that knowledge is already shared right so i think that's one of the key differences between a sales engineer who's really hyper focused or laser focused on their customers and making sure their customers do well i think that the solution architect role is broader and is really also geared to um expanding that essay's career uh in in terms of uh exposure right so if you're thinking about you know i look at some of my most successful um essays they went off on to becoming like ctos at companies right so you know if you were a sales engineer and you became a cto with i think that would be a pretty big leap right because you're like you're late this is one of the customers you happen to be working with maybe and kind of swing that but if if you're gonna you know um become a cto of a company you need to be exposed to you know a broad range of customers and you know have industry wide type of experience um and i think that's really what we're we're trying to help um essays do i know that's what's my goal is to get everyone you know grow their career and make sure they get the right opportunities to expand their knowledge so they can take on big roles right um you know i i view it as you know that preparation meets opportunity you know that is what i call the definition of luck right and so if if uh if you prepare ahead of time then when those opportunities come in you're gonna get them but if you're not prepared i don't care how many opportunities come down down your way um you know you won't get them or if you do it could be it to your own detriment right because you won't be ready to take it out 100 um i i consider myself a lucky guy and uh and i mean there's there's some things that i got out of just pure luck uh but then you're absolutely right so the more you put in the work the more i got lucky you know the the more you you make these decisions you get out of your comfort zone the more you're willing to do things others are not willing to the more you get lucky it's it's actually this is this is how i uh how i see it so um to segue a little bit on that um a question i get a lot on the channel is what is expected from a new essay in the first three months uh in the first nine months and let's say from one year and after that sure sure okay so the first three months is for an essay is pretty programmed um because we have a very um prescriptive uh onboarding plan so uh no essay would speak to a customer in their first three months on their own to give you any sense these are and some people we hire have like 15 20 years of customer experience uh a lot of you know it's just uh you know a lot and they they're expecting to kind of hit the ground running and so uh one of the first realizations that uh essays go through when they when they come on board is here's your onboarding plan and here's what you're gonna be doing for the next three months right you're gonna be watching videos you're gonna be talking to people you're gonna be taking training you're really going to be um uh ready for that first customer conversation uh and i think that is is something that doesn't we don't really talk too much about it publicly um but you know that is the um uh that's the first three months it's you know very regimented um uh program where we really want to make sure that uh an essay is ready before they have that first um that was that was tremendously helpful uh in my case i remember i mean i was so eager to jump on and start working with customers and solving problems and you were like this time will come you know just take the time to go through the and boarding take the time to absorb and to learn how to be an amazonian how to think the amazonian way uh you know learn all these leadership principles you know the time to help customers come and and when i got uh when i once i got in peace with this idea you know the three months at the beginning were just priceless because there was no stress you know because when you joined the company the first time you still don't know how to act you don't know people you don't know you don't know the applications internal you know internal applications you don't know who to talk to but these three months at the beginning they were super helpful um um i'm honestly amazed why other companies don't do this you know don't give this kind of buffer at the beginning to learn uh before just you know jump and start working yeah yeah i wish that they did and um but yeah every company i worked for before this literally they the second day i was on the job it was already in front of customers yeah with knowing very little about the product and the solutions that they're offering which was its own experience um but yes definitely given the opportunity to kind of give essays the the chance to learn about the programs and i think that you learn about them in the first three months but then you don't put them really into practice until the next three months right and so you know the things like immersion days and workshops and whiteboarding sessions that you do with customers once you're solo i think is the next three months right because you're going to be doing things for the first time right like giving an immersion day an all-day immersion day you maybe may have never done that before for any of the customers maybe you were a customer at the time where an immersion day was given to you and so now this is the you know the first time where you're actually the you know the lead of of the um of that type of uh activity right so it's um you know that's where i look at the next you know three to six months where you're putting into practice kind of what you've learned in the first three months and really refining your your skills um and and really kind of understanding the programs to your point right because we have so many programs um at aws so it's um just knowing when to apply which program who to talk to uh when to um call on for help when customer wants to go super deep on a particular service uh and what is the process for getting the right people engaged i look at that as you know the next three six months is you know where you're refining those skills uh which are really specific uh to aws um and and then once that is done you know now you're you've completed you know you're you're approaching a year and i think that's when essays really start to hone in on their career development right they may not realize this but they were building on their career before that but it was unconscious i think and then at the one year mark is really when you start thinking okay where do you see yourself in the next two to three years right and how are you preparing yourself um for whatever that you know that next role um is or you know in the current role if you're looking from like a promotion perspective uh that is something that i find is very unique um about amazon and aws uh and other companies i've worked at you need a position to be open for you to get promoted into it right and so if there is no position at the next level then that's it it's not going to happen right so there's just no no matter how much work you do or what accomplishments you you you manage to achieve um it's not going to happen whereas whereas it at um amazon and aws you know it's really about building your body of work right once you've built your body of work which shows that you're operating at the next level and we you know you work with your manager and we create a promotion doc and we do promotions um four times a year uh for uh majority roles and twice a year for the you know principal and more senior roles uh that is something that you know is to me like very unique out of all the companies i've worked at over the last 20 years uh i've never seen this before uh and so i think that's you know really something that should be celebrated is that you know you do the work you show that you're operating at the next level you show that you can scale right because as but i find this is the growing theme as you go up the ranks at aws your ability to show scale and impact grows right so it starts off with can you can you impact customers outside of your segment or territory that you're assigned to then can you impact customers outside of the province or state that you're in right and then can you go across country um and then can you go across geos and then can you be global so with every you know uh uh increment and scale you know you're looking at the next level uh of promotion that is you know what is expected at that level right this concept of scale is uh uh is really important i've read recently and this is something i was not aware of that the white paper that was written inside amazon to create dynamodb the white paper that built the principles to build dynamodb was the same that was used to build cassandra and so that was that was mind-blowing for me so you have this is a great example of scale so you have something on i suspect it was a team who built a white paper and then two great services were built you know uh from with it within it so i think this uh for amazon and aws to put a lot of emphasis uh on this concept of scale i think i think it's the right way to do it actually uh i think it's really the right way to go about business yeah i i i just want to double down on that because the the the what we call the narrative culture which is the writing culture at uh at amazon is is so uh ingrained in the culture here that um it really opens up the possibilities for literally anything right you don't have to be a great presenter you don't have to be a great sales person to to sell an idea like dynamodb um to the company you simply have to put pen to paper right you start with the two pager right it just explains you know what the value prop is why why you think it's important right and we have you know a template what have you that you'd follow um and then that two pager you know gets traction turns into a six pager but no more than six pages right that's the limit of all of our papers that we write at aws no more than six pages because i don't think anyone can tolerate more than six pages of reading in one session um and so six pages limit although there could be hundreds of pages of appendix there's no limit on the appendix on dependencies where your raw data will resize because some sometimes you need to dig into the raw data um but that's pretty much it at any level right uh in the company you know you put pen to paper on an idea that you think is going to benefit um the company benefit their customers benefit the world uh you write that it will find its way up to senior leadership and you know they'll read it provide feedback and you get that approval and that's it it's it's you know an initiative that has funding it has resources and you know frankly i think you know this is probably one of the biggest [Music] biggest impacts that any employee can have on a company is to invoke change right and we already this this writing you know culture and narrative as without the narrative um the power of the narrative is so um uh key to that uh that uh it's it's really helped to form and shape the company that we work at today i think and even within aws we have something called tfcs right technical field communities can you talk a little bit about what tfcs are and how important they are yeah so tfc is a the technical field community this is a group of of people who have um an expertise on a particular service or industry because we have industry tfcs and we have service tfcs uh where if you need help like you mentioned dynamodb so if you have to go level 400 500 level deep on dynamodb um you can open up a specialist requisition as we call spectrex and that will go to the dynamo tfc and someone from that group which is probably another essay right who um has gone deep into this one particular service who will get on the phone talk to your customer and get them you know answer any questions they may have on best practices on their architecture on the challenges that they're having um so that we can keep the conversation and you know the the opportunity moving forward right uh so they're super important uh it's another great way to show scale because now you're talking you know if you're part of a tfc which we encourage all essays um especially after one year to be part of a tfc to join so that way you can see what customers outside of your patch outside of your territory your segment are doing with a particular service that you happen to be very knowledgeable in right and so i i believe you're part of the uh serverless tfc um and so you've had some opportunities yourself right to to see what other customers are doing and what use cases um they're trying to accomplish yep um being part of tfc uh um helped me and opened a lot of doors for me so instead of just being you know focused on customers on my territory and solving their problems i was able to help customers from you know british columbia customers from alberta customers from all over the country on various workloads various types of problems and i've been involved in in solving problems from all kind of perspective and all kind of industries also so yes i i highly encourage all essays to uh pursue a tfc most essays come in with some uh level of depth on a particular topic if you're a software developer you're gonna you know come in with that knowledge if you're you know used to be like a database administrator or database architect then you're gonna come in with that knowledge so it's it's natural then to expand on that you know kind of double click on it double down on it and then basically be part of a tfc that that's focused on so i look at that as the low hanging fruit um for most essays coming into the company because they usually come with some you know experience or or background in a particular topic so that makes it easy and then you can you can be part of two kfcs right that's usually what we say you know one to two tfcs and your second tfc could be something that you're super interested in but maybe you just didn't have the um exposure to it like i have a lot of essays who um who love iot right you know they never worked for an iot company but they have home automation and that's usually what peaks that starts people's interest in in iot right um you know again that first smart switch or that first smart plug uh and then seeing how that works understanding the protocols um and you know and then learning oh we have a full platform uh on iot that you know will take everything from data ingest to sensor uh analysis and prediction you know uh of maintenance and what have you on the ml front so there's just you know a full um suite of products that we have that you know once essays really dive into it they love it and they want to be part of the you know iot tfc it's um it's great and that's i think goes back to the learn to be curious uh um attributes or leadership principles that we want all essays to kind of have and you know i believe that they all do also for um people who wants to be solutions architects and we think about being solutions architect and they look at the 200 plus services that we have and they get scared of them um know that tfc and and these technical field communities give you an army that you could leverage right so when when as a solutions architect i go and i talk with a customer and the customer has a specific problem to solve in a specific technology sometimes that i don't have exposure to you know i can uh check with someone from a tfc in that specific technology so there's always specialists that you can lean back on and bring into the conversation and help you solve these uh problems for uh for clients yeah absolutely absolutely yeah because your ex you'll never be you know an expert on 200 services take a lifetime and by the time you get there we'll probably have 200 more added to the platform so it'll be never ending so you're right um you know i think it's uh the the power of the tfc is really helps to um keep the conversation moving forward at a faster pace because if a customer wants to go deep on dynamodb and you've never used you know a non-relational database before how long will it take you to get up to speed and to become an expert you know a week two weeks a month two months and we don't want customers to be waiting you know two months to have a conversation with us um you know about a particular topic and so the the tfc's really help us to accelerate that you know and turn these conversations around you know within a couple of days i've seen some as quickly as one day's notice have a specialist on a call have a deep dive conversation with a customer right it happens all the time and and if you think about it if i was you know putting your customer hat on knowing that you're talking to someone who is not only you know at an expert level in a particular service but has real world experience in the deployment of you know that uh that service uh you're gonna leave that conversation with confidence knowing that you know you're not doing something that is um on the bleeding edge right that's something that no one has ever done before you know these services exist because you know thousands tens of thousands sometimes millions of customers are using them every day and knowing that you know that you're talking to someone who has that experience and can help them you know answer their questions uh without you know having to constantly say let me get back to you on that right [Laughter] you know which is what we do because we don't want to tell customers the wrong thing right so we want to make sure that their um their questions are answered you know 100 correct and so i know we often you know revert to let me get back to you on that which which is what was which is my preference versus you know telling a customer uh an answer we're not 100 sure right because then we wrote trust and do you think that an essay is required to to be a developer to have a developer background or to know how to code um absolutely not we have you know a large number of essays have zero programming experience now that's not to say that it's not an advantage to have it right uh and depending on what segment you're in it is more important in some segments than it is in others right so the isd or the independent software vendors or digital native business which is the department that they're wearing um the people that we speak to are primarily developers like when we talk to the ceo of a company they could be the founder and lead developer at least at one point in time for that company software uh so you know from from an isv perspective i would say that you know having software background definitely uh helps but that's not the only conversation we have with customers right when we talk about architecture um you know it goes you know everything from the infrastructure to the uh high availability and redundancy um the latency that is required that has you know often nothing to do with with how you program something and a lot to do with how you deploy the building blocks or services to make sure those needs are met uh and so there's um it is not a let's get down let's look at source code and help troubleshoot and debug you know this lambda function that you wrote like that's um super low level and we typically don't get into that level of detail number one at solution architects um and secondly the other thing which is important is that we don't put our hands on the keyboard for a customer so we never log into a customer's aws account and start changing their configuration or launch confirmation templates for them that is uh outside the scope of the solution architect for that we lean heavily on our proserv or our partners uh that we work with in order to get those production deployments out there that's not to say that we won't build a proof of concept to help the customer understand how services work right um but we won't log into their account or or even have access to their aws accounts to do that um because you know that is uh this is where you know kind of that that line is drawn between an essay role um and what the customer or partner or pro serve with the statement of work would be doing on behalf of that customer we we touched on um tfcs and specialists we touched on partners there's one other uh position that is super important in the role of a solutions architect which is their account manager so a social architect works hand in hand with the account manager could you could you speak to the synergy or to the uh to the ideal you know team effort and teamwork that that happens between those two uh yes yes it is vital uh vital i i i try to think of a word that's bigger than vital um critical that the account manager and the solution architect are in sync always um the better they are in terms of in sync with what the plan is um when engaging with customers and what this is you know what the goals are that need to be accomplished um the more successful that customer will be and it is something that you know i tell when i when i speak to account managers or account execs i'd say you know your responsibility is to make sure you have a good relationship with your essay and then when i speak to essays i say it's your responsibility to make sure you have a good relationship with your account manager um because if both feel that they are both accountable to to have that strong relationship uh then it's it's going to be a two-way street right and and that's really uh what you want uh and i think that um for account teams where that has happened um we've seen wonderful things happen from a customer perspective right um because everyone's uh working towards the same goal and it's not uh what we wanted to try to avoid happening is looking at solution architects as like a tool in the toolbox that you take the tool out when you want to talk technical and then you put the tool back in in the toolbox when the technical discussions stop uh you know i think that is kind of like the worst case scenario um and often you know leaves the conversation um without the proper follow-through and drive right because the the i look at it as you can answer a customer's question and say yeah that's the answer to the question you say that i've done my part as a solution architect you had a technical question i gave a technical answer done but we both know that if that's where the conversation ends um you know we're never going to know where it could have led to had we had done the follow-up and that follow-up could be from a technical perspective it could be from a business perspective and or it could be from both right and i think that is is where when the um account team is in sync with each other right that's when that conversation will um continue and and you're going to be able to see where it leads and often you know you'll you'll dive deeper into the why the question was asked right as we call it the five wise you can't ask the customer five why questions um right off the bat because they're gonna be wondering why you're interrogating them so we don't wanna don't wanna do that um [Music] well it's usually that that's where you know the the account manager and the sa uh and technically the technical account manager in some cases the customers who have enterprise support will have a tam on the call also when all three are working together um you can get to the five wise with you know everyone asking you know one or two why's um in terms of why questions being asked to really get to the root of what the customer is thinking and i think once you understand the root of why a customer is asking a certain question uh you can really help form and shape where the conversation goes and really build a plan that's going to help them you know achieve what they ultimately set out for which is why they asked a question in the first place but it was probably three four levels deep right and you need to go up a few levels to really understand what's motivating them so you don't miss the mark at the end of the day which is that would be a miss on our part if we we did that beautiful yeah um we are nearing i want to be respect very respectful of your time and we are nearing the we're nearly on the top of the hour um i want to thank you very much for your time for your perspective uh for answering all these questions that i keep getting on the channel um anything you wanted to add uh at the end yeah just that uh you know uh the solution architectural is um both very challenging role and also can be very rewarding uh and so i encourage uh any aspiring essays or people who have your essay currently in an essay role uh that you know you know they look to aws uh it is a great place to work is a great place to grow your career uh there's the opportunities are limitless uh here in terms of what you can learn and where you can grow to so i highly encourage uh you know everyone out there who is thinking about a role uh and certainly thinking about a role at aws uh that you know that they definitely apply and uh and try and hey look we've had some essays that are on the team um you know it's their their third or fourth attempt at getting in that got them in right so don't be discouraged um if you don't make it in the first shot uh it took me six months uh to get my role uh here right so it just tells you you know the journey that i i went on um but uh you know don't let it discourage you it's uh it's definitely worthwhile uh and this is a great place to work so i i myself applied at amazon years ago didn't get it years after flight at aws it's a whole different story so yes i 100 agree it's a great place to work for it's worth the effort actually um so thank you very much tony uh where can people find you on on social networks yes uh linkedin is probably the best place to find me um you know so uh i can send you my my linkedin um handle and uh yeah if people want to reach out please do over linkedin i'm always happy to answer uh questions that people have company great great thank you very much and uh talk to you in a few minutes i guess great awesome cheers you

Channel: iLyas in the cloud

Views: 17,019

Keywords: AWS Solutions Architect Interview, Amazon web services explained, Working At AWS - All You NEED To Know, aws certifications, aws for beginners, aws interview questions, aws interview questions and answers, aws interview tips, aws introduction, aws job opportunities, aws solution architect interview questions, aws solutions architect interview questions, solutions architect interview amazon, what is aws, working at amazon, working at aws, working at aws all you need to know

Id: vEsaMMceW_o

Length: 44min 54sec (2694 seconds)

Published: Mon May 10 2021

Reddit Comments

[u/isbkch]

I finally got my manager to accept an interview where we go through all kind of questions people have been asking me recently as a senior solutions architect at AWS... Feel free to drop any question you have and I'll do my possible to address them as well

[u/camdyer21]

What suggestions would you give to a CIS student with one year left in school and wanting to work in cloud architecture in the future. I first started with the Az-900 and AWS CCP. I applied for AWS student internships but did not get interviewed. I want to be as prepared as possible by the time I graduate. Maybe certain certificates or entry level jobs you can think of. Thank you!

[u/jackster829]

I just accepted a role as a Sr. SA at AWS. I start on June 1st. This video is great. Thank you.

[u/FakeitTillYou_Makeit]

I really enjoyed this. Thank you!

[u/stewtech3]

What is your YouTube channel called?

[u/[deleted]]

I for some reason find it annoying when he's asked the question where did you get your start he begins with "I was running their video technology division managing their solution architects..." It's like what? So unrelatable. Every single person in this thread is a help desk jocky start further back....

[u/jorge123222]

I have my SA need advise on how to get a job as a Aws SA