Specialist or Multi Skilled - what is your opinion...

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi Gents,

Been a while since I posted, thought I would see what your thoughts are on the matter...

So where would you rather be?

1. Many skills across multiple platforms - Cisco / Microsoft / Virtualisation / Storage / Backup / Design - This is more of an architect role.

2. Specialist - Highly skilled in a particular product or vendor such as Cisco or VMware - I see this as 3rd line / senior engineering role.



What are the reasons for your choice? Also where do you see this fitting into your career and do you see this as progression or recession?

I'll start the ball rolling.

Personally - I take more of the Specialist role, and can see myself moving further in this direction. Understanding the low level element of projects / design and still following this through to implementation. I find more interest in understanding in-depth technical elements such as BGP design for service provider networks, rather than architectural understanding of many concepts and technologies but from a high level perspective.

I know generally architects are seen as higher up the scale than engineers, and probably as career progression.

Where do you stand and what do you think about each type of role? Perhaps you have a different interpretation?

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

It always worries me to see people picking specialities on their 3rd day in the IT business. Guys who don't know the difference between Outlook and Exchange, or a router and a network card, aren't yet in a position to decide which niche to mine.

I also used to worry a little that there are so many people in IT sales who used to be Netware engineers but couldn't transition when that horse died under them.

Specialising is unavoidable, but don't choose what to be until you know what you are rejecting. (Advice which isn't pointed at Braderz, he already knows.)

 

I started out a C++ specialist, then later Java, and then C#. Only ~10 years into my career did I start to focus on more general skills.

Some of this was necessary due to the technical nature of C++ development, but looking back I think getting some general exposure sooner is better.

Ultimately I think you need both, being too narrow means you lack vision and oversight, it is also a high risk strategy in a volatile industry.
Being too broad means you are only fit for meetings and powerpoints and cant have any real insight into the application of technology.

 

I agree with jk2447. I think being a generalist at the start is the best way. I've just done my first year in IT and I need to be aware of multiple technologies before I can even make a concious decision on what to specialise in. After that I'll try and specialise. The only risk with specialisation is that if a certain technology becomes obsolete and you can't transfer the skills, then you're in a predicament.

 

Good to see everyone's thoughts on the matter.

I noticed its quite relevant to where you are in your career as to the decision being made.

For the people quite new or still undecided in their path, generalisation appears to be the favourite.

 

Started off as a generalist, then over the years focus has narrowed pretty much with each new role down to the point where my main thing now is one specific product set from on specific vendor in a very particular area. That's over a period of about 11 years or so.

Not done me any harm and I enjoy it, a lot of skills are transferable though which helps if I did want to go and do something else, as well as the fact that the company is large enough can pretty much work towards any sort of position you like.