3 ms·
I’m an old fart too (48). I stayed at one company for 9 years and by 2008 at 34, I was the epitome of an “expert beginner”. I changed jobs four times between 2
by scarface74 5y ago
I’m an old fart too (48).
I stayed at one company for 9 years and by 2008 at 34, I was the epitome of an “expert beginner”. I changed jobs four times between 2008 and 2016 and I was just your regular old enterprise “full stack developer”.
In 2016, I was the lead developer at a medium size non tech company and looking at where I wanted to be in four years after I my youngest (step)son graduated and we could move anywhere the money took us.
I looked around at the landscape and saw that my salary was going to plateau with one more job hop locally unless I became a manager. I looked at what it would take to get into $BigTech as a software engineer and I was neither interested in “grinding leetCode” or even working as a software engineer at a large company with a bunch of 20 something’s.
I kind of put the idea to the side and started working on the skills it would take to become a consultant (not a contractor doing staff augmentation who calls themselves a consultant).
Out of the blue, while I was a working as a de facto “cloud architect” at a startup in 2020, BigTech cloud provider recruiter sent me a message about a role in the consulting department. So there I was at 46 with my first job in $BigTech - making about what a 26 year old who was promoted to a mid level engineer was making. But I do get to work remotely.
- jethkl 5y ago> working on the skills it would take to become a consultant Curious to know what you were doing to make this happen. Did you have a guide?
- scarface74 5y agoI yada yada yada’d over a lot. I was first exposed to consultants when I was the newly hired lead at a company in 2016 brought in to design an on prem project. At the last minute, they decided to “move to the cloud”. They brought in two sets of consultants. One set that was suppose to know about AWS. But they ended up just treating AWS like an overpriced Colo and I didn’t know any better at the time and the other set who in hindsight were just following a cookie cutter script who were “helping” the business manage integrating a bunch of recent acquisitions. Once I started belated learning about all the services that AWS had to offer developers and for “DevOps”, I knew I wanted to specialize in consulting in that area and set myself apart from the old school network folks who got one certification and called themselves “cloud architects”. I figured I could bring more to the table from a software engineering standpoint. I changed jobs in 2018 where the then new CTO wanted to be “cloud native”. He was trying to build out an internal engineering department. He knew I had no hands on experience with AWS. But he liked my proposals. Two years and a lot of projects later, I had the technical side down pat. It took me a couple of years at AWS to get good enough at the soft skills/customer interaction side. My original plan was to get a job at one of the big consulting agencies to hone my craft. I got lucky to skip over that part.