Developer to Architect: The Complete Journey | Marius Furtuna | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

Developer to Architect: The Complete Journey

teacher avatar Marius Furtuna

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

18 Lessons (40m)
    • 1. Course overview

    • 2. About myself

    • 3. Setting course expectations

    • 4. Preparation

    • 5. Getting fed up as a developer

    • 6. Changing my environment (reasons)

    • 7. Changing my environment (actions)

    • 8. Learning and time management

    • 9. Getting Certified (Cloud)

    • 10. Getting Certified (Architecture)

    • 11. Execution

    • 12. Taking the leap

    • 13. Made it !

    • 14. What to expect

    • 15. Maintenance

    • 16. Remaining sharp

    • 17. Continuous learning

    • 18. Congratulations

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

My story from a software developer role to a highly paid software architect role.

Meet Your Teacher

Hello, I'm Marius.

See full profile

Class Ratings

Expectations Met?
  • Exceeded!
  • Yes
  • Somewhat
  • Not really
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Course overview: Hi and welcome to my course developer, toe architect. The Complete Journey. My name is Marriage Fortuna. And because when I wanted to make my career transition from software developers toe architect, I couldn't really find what actual steps I needed to take what was the fastest way to becoming a softer rocketing. Now that I made it, I thought I should create the course for those of you looking to make the same transition as I did and share what I've learned on my journey off, moving from one senior developer role so highly paid architectural making, a six figure annual income and in this course, our share to you. My story on the steps I took to make this career transition, how to prepare for it and what to expect once you get there. This course is mostly aimed at experience developers with at least 45 years of experience. But for those of you with less experience out there, you are also working to attend. As you learn valuable information, toe fast track your career 2. About myself: so something about myself. This is me. I might look cool and confident in that picture, but I really wasn't Ah, bit about my background. So I have more than 10 years of experience starting out as a junior Web developer back in the day, working my way up the ranks to senior developer and now architect. I've worked in both small companies as well as in big corporations, and lately I'm working in freelancing. My technical background is in dot net, but as I evolved, I had to learn multiple languages. Such a job are ruby angular, know Jess and so on. Knowing all of these languages is not an absolute requirement toe becoming an architect, but the more you know, the better you will be. I'm currently working as a chief software architect and in my spare time, which is very scarce these days, I'm slowly building my own business, and this is my story on how I became or not 3. Setting course expectations: So before we continue, I would like to set the expectations for this course. In this course, I will guide you through the steps which I think are necessary to make the transition from developer toe architect. Please note that this is no silver bullet. No get rich fast scheme. None of that nonsense. No, this really required hard work and dedication from your part in order to become a successful, softer Actiq. This is not a technical course. I already assume you are great developer with reach knowledge in your preferred programming language or languages. But you don't know how to take your career to the next level. You might have architected solutions already, but you don't quite have the actual architectural. I'm not a big fan of death by PowerPoint, so I've structured this course as a story. My story of moving from developer to architect. I've sprinkled it with a few Mihm's here and there to make the story more fun for people watching it. So yeah, that's it, Andi, if you think you are up to it, then take a short break. Whatever coffee group a beer and I'll see you in the next lecture 4. Preparation: Hi and welcome to this section, which I have named preparation. In this section, I'll talk about how I've started my journey to becoming an architect. What were my biggest challenge is how I overcame them and how I've committed to a life off continues learning. So in the next lecture, I'll tell you what were my reasons and why I've decided to pursue the roll off us off directed. See you there. 5. Getting fed up as a developer: So here I was working as a developer for this corporation for about four years, working with outdated technologies, then actually being promoted as a technical leader. By the way, this was just title change. I was doing exactly the same work as a developer, only much more of it at roughly the same pay for another two more years in which I finally had enough. The problem was not the work. I've always been a hard worker. The problem was that the work was repetitive, having to do similar things over and over again because the product we worked on was outdated and there was no react detector working site despite many of line and my colleagues protests, and this ended up causing a lot of frustration. So I've started creating my own tools, which removes some of the pain off the repetitive tests. But this wasn't enough. I want to be the guy who architected a better software so that other developers wouldn't have to break the product whenever that that software needed extending or new functionalities and modules were needed to be added 6. Changing my environment (reasons): becoming an architect in this corporation would have probably meant at least three more years off working in the same environment, having to deal with the same repetitive test over and over again. Even though I've had the chance to architects some of the internal tools and three major projects, these were extremely rare occasions. Working mostly on the same products with the same outdated technologies for a long period of time Eventually starts making you as outdated on the job market as the tick you are using. I knew I wanted to become an architect, so I've started to do a little research. This this was my goal. The trend for the architect requirements were mostly experience with technologies checked. I had that basic soft skills communication skills, team player, blah, blah checked. I had that as well. Knowledge off a least one cloud platform not checked. And then some architecture skills certification? Not okay, so now I identified what my knowledge gap waas. It was time to take action to fill it. The only problem. Waas that what I was researching my next steps. I was doing it on the company's dime, and since I was the tech lead. I was swarmed to it work and barely had time to do anything, let alone feel my knowledge. Gap. I knew dress dick actions were required I had with my job. 7. Changing my environment (actions): with my job. Easier said than done. OK, I'll quit. Then what? I wasn't that student anymore. I wasn't living in a dorm with my friends, just as a disclaimer. I'm from Romania here, College education. It's mostly free if you keep your grades high enough, But now I I had a lot of bills to pay. I had the bank loan from my house. I had my high school dream car, a BMW five series, which is also known as the ultimate maintains machine, All of which require me to have money coming in. So I've decided to do something which to everybody, seemed very odd and counterintuitive at that time, Not to mention stupid. I quit my job from, AH, technical leader role in a big corporation and got hired as your average everyday developer in a smaller company so that I had a smaller role and more free time to study for my long term goal off becoming an architect. Every one of my colleagues saw this as a step backward, not knowing off my long term intentions, and probably thought I was an idiot. Every interviewer asked me while North they want to make this switch I told them I had my reasons, and I don't see this as a step back. A long story short, I went to three interviews for smaller companies and God, job offers from all of them as they wanted my expertise from the big corporation. I've actually got them in a bidding war by telling each one of them that I had other offers and actually got a salary off her. Bigger than the previous one I had from corporate one. Even skip the technical stage of the interview and extending me the offer directly. I remember I was in Newburgh on the way to 1/4 interview for another company checking my emails on my phone, and all three offers somehow came in on the same day, two of them while I was in the the Khobar car. So, more money, this work, less stress, more free time. Three offers to choose from. Not bad. I was ecstatic. I I always wanted to change the destination and turned the car around to go back home back home. That's I went to that interview anyway. Unfortunately, that one doesn't go as well because they give me an advance mathematics test and my head was so distracted with the offers I had. Plus, I'm not a brighter Spiegel in the jar. And advanced mathematics was never my strong suit. So even though I ended up blowing up that interview, I still left there smiling. 8. Learning and time management: So I ended up choosing on outsourcing company. I thought that I might as well have project diversity and learned as many things as possible more. And I was here and in this company I've worked on on Internal Project for a short while. Then the rest of the time I worked as an external consultant, which is a fancy term for senior developer for a gaming company. Because for most of the tests I was overqualified. I could finish them early in the day and then use the rest of my time to study for my greater goal of becoming an architect. Some of the days I was swamped with actual work, so I couldn't get any studying done. But the texture working, getting experience with your technologies such as elastic Search and docker, which form your new at that time, ends up weighing a lot on my architect interview. But more on that later, it started with learning a cloud platform. From my research, I found out that AWS, which tends for Amazon Web services for those of you who don't know, was the hottest trend out there for cloud. I know some of you might disagree, but that's that's my opinion. Um, I've only worked with Azure and Oracle Cloud previously, but those platforms paled in front of AWS. I immediately fell in love with the number off offer services and pricing and variable trainings out there. Pete's by far any other cloud platform. In my opinion, I don't want to anger any other cloud platform enthusiasts out there. I know Azure and Google Cloud are awesome. A swell, but I personally, uh, before aws so coming back, I've started looking for AWS trainings. And here I found probably two off the most amazing club training companies out there, at least at the time off. Recording this Those are a Cloud Grew and Lenox Academy therefore extremely comprehensive trainings on AWS. Now, as I'm recording this, I see that they extended their trainings to include Azure and Google Cloud as well. So they are an amazing resource, providing everything you need to learn about AWS or order cloud platforms you may like, and to me they don't seem too expensive. A subscription to a cloud. Gorey's about $29 a month. And for Lenox Academy, it's $49 I think per month, which is nothing compared to what you're be earning is not while doing AWS courses. You'll hear that name. Ws Architect is one of the most highly paid roles out there, with an average yearly income off $100,000. I was skeptic as you are probably while watching this, but I don't know how it is in other countries but here in Romania, making this kind of monies on effing lot. But everybody was advertising it like this. So I said, What heck might as well aim high, right and then hide. I did more on that later, so I started learning AWS, my cloud platform of choice. After completing my daily task on the work days and also started sacrificing some, we can says, Well, you can probably do it without sacrificing weekends for learning, but it will take you longer. My corn goal was to get AWS certified 9. Getting Certified (Cloud): So I'm going to continue talking about in the AWS platform certifications because those are the ones I currently hold. And please know that all other cloud platforms ever equivalent certifications, So feel free to pursue any other you may like. On the time off me studying AWS there were three certifications for the associate level developer, architect and sys ops. Uh, these are the ones which I will cover in this course 24 professional level architect and Dev ops and 34 specialty level networking Big daytime security. Now, I think there is one more for inter level just called cloud Practitioner. I can't. We have all three associate ones develop our detectives. It stops the complexity off. Getting them was was in this order. Eso developer was the easiest, an architect and finally stops. I initially went for the architect and then went for the developer and finally sys ops to extend my knowledge. And this is the best way to learn. And the most important is to practice what you learned with the natural AWS account, speeding up servers with both of the knocks and windows, creating V P C's bitter private clouds, or at least taking all the labs on Lenox Academy. I don't want any of these terms are not familiar with you. You will learn them as you would be studying for these certifications. I was just starting with a claw grew and then moving to the Lenox Academy platform. The next academy covers the topics in more death and the brother the knowledge you have, the better. Also, the idea is not. Take all of the courses available there, as you'll probably study for a couple of years from a certification level. At the minimum, you need the architect associate, but I would recommend you to get certified in all three associate level ones once you get certified for one. The difference. The Lambda between them is rather small, So most of the knowledge is is the same. A claw guru offers a lot of trainings for the AWS services, such as Lambda Functions Club, Formacion Docker and someone. While these are good to have, I wouldn't see them as an absolute requirement. I managed to get certified for all three associate level so developer, architect and said, stop saying about, uh, three months off, hard core studying on, and not many three weekends. So this this ments at least two or three hours a day of studying and at least four in the weekend. Uh, you can do it at your own pace. It's up to you how you want to tackle them. Be aware that on top of the training costs, you also have to take on official exam for each of them, which is rather expensive around $150 each. Prices might have changed from them, but I shouldn't vary that much. But again, this would be small change from what you learn, what will be earning as an architect, you can think of it as investing in your future. You can check out the link for the list of exams. Also, if you click on schedule, don't they? Yet? The last step will be to pay. You'll be able to see where are the exam centres near your location. Once you have the information you need, don't forget to cancel your reservation. So once I got my first certification, my a debates architect associate. I felt awesome. I felt I was getting closer to my goal, even though I was just an architect on paper I wanted to get as much hands on experience. Aws is I could. So I started using my account, speaking up pre sources with cloth formacion, creating websites, playing with services with RDS with maybe a gateway Lambda. I was in love. The best thing was that it was almost free to try everything out here. Rarely did I pay a couple of box because I went over the free tier limit again. You're learn all of these terms once you get started. Um, I I wanted more knowledge. So that's why I went for the other to associate certifications so fast. For three months, I was certified in all three levels. Developer Heartache says ups. Oh, yeah. So I am that went back to my initial checklist getting certified in one cloud platform check. I was down to my less requirement architecture certification, mostly toga was specified. 10. Getting Certified (Architecture): so Toga Toga stands for the open group architecture framework and then basically consists off guidelines, high level design and best practices for architect working within an enterprise from how to deal with the demanding CEO toe. How to handle team distribution, tackle different business and Aereo's and so on. It is expensive but well worth it. Take it from me. The information you will get from getting told off certified is invaluable, especially if you are taking on the architectural for the first time. I didn't know that back then, but I saw a lot of job listings had this as a requirement, so I started cracking. Tokyo is divided into two sections. Part one is called Foundation part two. Well, it's called Certified. These are two separate exams ing you need to take, uh, you can only take the 2nd 1 once you pass the 1st 1 and once you pass both, you are toga certified. Um, the 1st 1 It's, uh, take 60 minutes and cost around $20. The 2nd 1 is 90 minutes and has the same price. There is also an option, which is called the combined exam, where you take both exams. The same on the same day, which ah, and that exam has 150 minutes and it costs $495. This way you will save around $150. So ah, where to get started. And this is suffocation is very tricky to get but very useful to have as an architect, even if the job description doesn't necessarily requested. I personally encountered many tough business and areas were working for different companies , which were described in detail in tow graph. And it offered a lot of solutions and that best practices and how to handle each the resurfaces I used to learn toge If work trains on u to me, uh, made by this guy, it's called Duffy. Ah, he has strings on both part one and part two for part one. You can check out his course. Uh, also this one for part two, and you'll also need a ZMA much practice as you can get. So I found a good resource. Also new to me. Check out this link. One special note. Make sure that you are taking the correct version off the exam. I've studied based on Tokyo off 9.1 and had a surprise on the testing day that the test words for Tokyo at 9.0. Luckily, there were only some minor differences, and I passed the test. But the time, By the time of recording this course, no toga off 9.2 is out. And make sure to take that into account. You should probably see some updates on Scott Duffy's trainings on You. Do Me regarding toga. Be sure to take every exam, every quiz and old questions multiple times. Ideally, not in the same order, um, so that you don't memorize the answers in in order, but you have. You have to think off each time at every question. I can't emphasize this enough. You really need to understand the questions, not just memorised answers. As in the exam, the questions may look similar, but they might have key words in them, which can easily score you zero points. The first part. His question. Based with multiple choice, this part is kind of straightforward. Should go through the literature very thoroughly. At least two times. You can tackle them relatively with ease. Part two, on the other hand, is a completely different animal. You are presented with business and areas which, with almost all ranchers being correct, some more than others. Ah, a chance answer has a score starting from zero as the worst answer and moving toe 23 and five points has then sorts improve most. Court 24 out of 40 points, which is a lot easier said than done, as the answers are very similar and can easily score you zero points on questions that you don't read in care for. That's right. Zero. Another village nil. It's where you want to call it should. Don't read it carefully. And you, Misamore, even one key word you won't score. Zero Been there, Done that. Got the T shirt. Taking the combined exam is not easy as the time pressure can really take a toll on you. I was feeling hardcore and I went for it. But after 2.5 hours of ah, very tough exam questions and scenarios, I was like a vegetable to making worse on the Pearson Vue testing site. What? I took the exam. Ah, I took. I took it on a really all computer which occasionally froze, taking some of my valuable time, and when I submitted my final results, it died. Blue screen off death appeared to collect his soul, and I was very close to a heart attack. Luckily, with his dying breath, the machine finished toe submit managed to submit the results. And when I came out of the room looking whiter than Snow, the supervisor came to me and having me the paper which said Congratulations, something something. Only then I felt like life was coming back to getting certified and staying alive checked. 11. Execution: hi and welcome to this section called Execution. This is where you put all of your knowledge into getting a job offer as an actor in this section, I'll talk about how I approached my job architect interview, uh, in which my case was the hiring tournament again, this will probably be different for you, but there are two key points. I want you to take away from this one. Show up to the interviewed confidence and winning mindset and to give it all the guts and have faith in your knowledge that you have gained. 12. Taking the leap: So now I had the requirements checked, had the experience. I had the knowledge I had the certifications. So now I was looking at architect job listings. Most of them were interesting, but not quite what I was looking for. I fell in love with AWS and I wanted the job in which I could leverage that knowledge. And I was also looking for that 100 K per year income, which was advertised. And look, I have it. So one day my wife, which, by the way, was very supportive in those last four months when I was sacrificing most of the weekends for studying, shows me a Facebook ad for US Company, which was having ah, hiring tournament in my country for architect with Don't Net or Java experience. Also having cloud knowledge AWS before offering remote work and 100 K dollars annual income . First, I thought it was too good to be true. I always wanted to work mode from anywhere and avoiding the daily traffic, and I read a fuller. Then I thought, Okay, this this might be it. Luck is basically when an opportunity comes along and you're prepared for it. So I signed up for the tournament, and I showed up me and 30 other people, not to mention hundreds of others which were taking those tests online. On the same day. I did a full day off increasingly difficult tests and interviews, and by the end of the day, only off your left standing in the tournament, including myself. The rest had either quit voluntarily or failed to pass a specific stage on the tests and were knocked out from the tournament. On the final interview, which was face to face to some guys who were already working there, I was asked to design a copy of Instagram, accessible by millions of users. This is where all my AWS training and prior work experience kicked in, and after talking for 10 minutes continuously until one Ah, one of the guys got convinced I knew my stuff and he stopped me. After the interview, I was told that I would have my answer. In the next couple of days. I left the building and went where my wife wife was picking me up and almost passed out from exhaustion in the car. Ah, week went by and I got no answer and but this time I was thinking that, OK, I failed. I wasn't good enough. Wasted all of my time for nothing. Then After two weeks, I've got the car. Congratulations. You have been accepted. We only accept the top 1% of candid candidates around the world. So you don't have to. Do I do it exactly the way I did. But I'm just saying that anything is possible if you put your mind to it. 13. Made it !: Okay, so I made it. I've ain't high enough and wanted it badly enough. And now I was chief softer Actiq working with the latest technologies in a group of highly skilled people playing in the big leagues. It doesn't. It is an entirely new work experience. Sometimes there are great challenges, but it is very worrying not only financially, which is great, by the way, but just learning from the best guys out there and seeing how things work. Mostly in years, companies eyes really a great reward in itself, not to mention my linked in account browsing with new job offers, with even higher pay relocation packages and a lot off good things to choose from from when I get tired of my current job situation. 14. What to expect: so as an architect, you must really change your mindset completely. You're no longer a developer, which gets assigned a specific task, works on it and then moves on to the next with almost zero accountability. If you are anything like me, mostly a tech guy, you probably avoid it management and tried to cut down on boring meetings as much as possible. Well, you will no longer have this luxury. I'm not saying that you will become a project manager spending all of your days in endless meetings, but you will need to change your view on the projects you are taking on. Must have a global perspective Off the project. Leverage Team members, based on their skill set, create the vermin roadmaps, oversee technology adoption, great solid documentation and reports to upper management even established sea level member , uh, relationships, depending on the size of the company you're working in, and I take full responsibility on a project go south. This is what it takes to be an architect and play in the big leagues 15. Maintenance: so final step or as I like to call it, maintenance. This is where you put all your knowledge to use to your daily activities. But you also take the time toe, stay on top of new emerging technologies and keep on learning. 16. Remaining sharp: So now that I was an architect, I had both developers and management looking up to me to make tough decisions, technology, adoption strategies and take four responsibility. In order to make these decisions, you must always be on top of emerging technologies. You must. You may not need to be an expert today on everything, but at least you need to know something about everything so that you can make the most informed decisions. The more knowledge you have, the easier the decision will be. Obviously, you will gain Italy experienced through actual work. But you should not get caught off guard and not knowing what people around you are talking about. Learn everything from everyone. Subscribe toe all the techniques letters that you can find and always staying for. 17. Continuous learning: So, unfortunately, as I've stated before, being an architect requires you to stay on the path off continuous learning. Luckily, there are a lot of sources to keep up to date, but you need to make time for them so that you stay relevant in this game off first base Evolving technologies. I also need to learn design tools if you're not familiar already with them to describe your architecture ideas. Um, el your journalism must have in architectural belt also tools such as, uh, drop dot io. You can check that that site draw that I owe toe learn toe quickly sketch diagrams, skill that is also good to master Ah, in order to present your ideas and, for example, gets work approvals. 18. Congratulations: So congratulations are in order. Thank you so much for listening to my story on becoming an architect. I really hope my experience, which I've shared with you on in this course, will help you on your way to becoming our software architect as well. When I initially thought off making this transition from developer to architect, I really wish I really wish they found some somebody to guide me through the steps. And although I found some good resources which provided me some leveling off information on what to expect but I couldn't find anything as computers. This story as I I shared with you. Um good course on new to me for for the learning on making this transition is from this guy Mark Feniger. I hope I pronounced that right where she talks about what to do after you get in the solution. Architectural. He also has a lot of other great courses you might want to check out. Ah, in my learning process. He also was a great inspiration. I'm sure there are probably others out there as well. Uh, now that you have a starting point, it's time for you to take action. It's not enough Just watching this video. You must also take action and begin your journey. It is a long journey. I told me about four months off hardcore learning and exam taking. But looking back, it was well worth it. So And she liked my course for story, Whatever you want to call it. And it was helpful to you. Please, please rate it on as these. You Jimmy courses are dependent on this ratings. Uh, thanks again. And please reach out. Reach out to me. If my story here helped you become a software architect, I would love to read your feedback on if this helped you in your career in any way. I wish you from the very best.