At the company where I was the dev lead, I first encountered outside consultants who were there to “help” us transform the company and “move us to the cloud”.
After realizing in hindsight how easy it was being a consultant - in the land of the blind the one eyed man is king - I realized that coming at AWS consultancy from the viewpoint of a software architect with some dev ops experience and some infrastructure experience I could be the two eyed king that may be had just a little blurry vision in one eye.
So, after changing jobs again last year, and taking a slight demotion (not in pay - in responsible) I’m on a four year journey to be a real “full stack consultant”. Someone who knows the front end well enough to talk to the front end guys, middleware (.Net/Node/Python) , databases, Linux, Docker, Devops, netops (at least on AWS) and maybe a project management certification.
There are a few gaps and a few more certifications I need, but I think I should have enough breadth as a consultant for the high paying jobs and enough depth to be your typical “full stack developer” to be able to land a job quickly.
I will see....
May I ask how much is the general pay in those “high paying jobs”?
But, outside the west coast and New York City. In most major cities in the US, a semi hands on software architect can make between around $125K - $150K. A consultant can make from $140K to $200K.
Do years of experience matter to make that kind of money?
But with diminishing returns. After 8-10 years. Any additional “years” of experience doesn’t matter. What you have done does.
I’ve officially been developing for over 20 years, but my first 12 years might as well been 3 years + 1 year doing the same thing 9 times.
Job hopping over the past 10 years has helped me make a lot more money but more importantly helped me learn a lot.
And by “consultant”, I mean the buzzwordy “implementation consultant”, “digital transformation consultant”, etc.
Yes I die a little every time I say it.
Reckon this is when most people establish their own business
Whether their clients tend to actually be familiar with the organisations endorsing or providing the Y certification I have no idea, but even if all it does is give them a warm fuzzy feeling, that's probably enough to make it worthwhile for the consultancy that wants their business.
I’m thinking about the AWS Big Data later, but I don’t have any practical experience in that area and I refuse to be a “paper tiger” collecting certifications with no practical experience and probably a project management certification because everyone has a PMP after their name in consultancy it seems like.
I would probably study for some type of Linux certification just to transition from the Microsoft ecosystem but whether I would spend the money to get it and keep it updated is another question.
In particular, to be an “Amazon Partner” your company has to have a certain number of certifications. It also helps to have some type of project management certification.
Your skepticism of certifications is well founded, I’ve come across many “paper tigers” who had certifications up the wazoo but couldn’t code/architect thier way out of a wet paper bag.
And the sword of Damocles hangs over my neck ever day. Worth it? Probably, but still not actually clear.
You seem to have an unlimited thirst for knowledge. I envy that at a personal level.
Especially if you want to.
- If I stuck with a focus on database programming from my early career, I would have a very valuable specialty.
- If I stayed more technical I probably would have weathered 2008 with more sanity.
But...
- Being a generalist opened up some international work.
- I met my wife on a career tangent.
- I get bored doing the same thing over and over.
- My last two roles (in a long career) have finally pulled everything together.
> "But I know all these other things (that you don't care about)!"
Having the skills be related to each other is also key. If you can't mix the skills in what you're doing, in a way that no 2 specialists can easily coordinate, then that's not very useful.
I think it's a matter of making use of one's advantages, but it's probably true that it's easier for a specialist, if all they have to do is apply to well known organizations for employment, as opposed to starting a new business or applying to startups.
[1] I've developed (professionally/ for money) compilers, VMs, image processing, web apps (mostly middleware), desktop apps, "big data"(spark, kafka streams, etc.); Have done product management, data science, and even worked on the architecture of a DSP processor at a time. Worked in most of the "mainstream" languages (Java, Scala, C. C++, Javascript, Python, C#, Vb.net; and of course various kinds of assembly language).
Now my interest is shifting to low-level computing and I'm getting my MS with a focus on high-performance computing and operating systems, but applying those principles to our cloud initiative (and after my MS is over, I plan to focus on hardware and electrical engineering MOOCs).
Where that'll take me (if anywhere), I have no idea. I occasionally regret not majoring in CS from the start and sometimes I think doubling down on the fullstack thing would be a more stable career move, but it's been a fun, weird ride and I plan to continue following my natural curiosity at least until stability becomes more of a requirement.
[1] https://en.m.wikipedia.org/wiki/Generalist_and_specialist_sp...
> You simply have more chance of career success if you have more skills.
I think that depends on how one intends to apply those skills. Being a generalist means that you don't depend on any one particular skill to always keep you in demand, and you can do more on your own to do tasks that specialists need to do in groups. However, I think a group of specialists will always outperform a lone generalist. Because of that, I imagine specialists are in general more preferable in a company environment.
EDIT: I'm curious if there are people here that have chosen to practice a wide breadth of related skills, as opposed to lasering in to one very specific skill. Do you feel glad/happy about it, or have you regretted it?
EDIT 2: What is a generalist or a specialist is of course very relative. One's specialist is another's generalist. I also get the sense that, in the tech world, what is a specialist today, is a generalist tomorrow. Maybe that's just natural of an expanding industry.