Specialization in IT

murdatapesmurdatapes Member Posts: 232 ■■■□□□□□□□
Hello board. I wanted to know if specialization in IT was a good choice? Ive been in IT for 12 years now (going on 13), and it was brought to my attention from a friend of mine who is also in IT. He said it was less overwhelming and more enjoyable knowing you are the expert at a product(s) that is in demand. He said he would encourage me to find something and specialize in it. Wanted to know your thought and to see if you are a specialist in IT, what product or area in IT (networking, dev, Windows) and how it benefited you.

thanks board,
Next up
CIW Web Foundations Associatef(Knock out some certs before WGU)
ITIL Intermediate Service Operations


  • drkatdrkat Banned Posts: 703
    I think it's a good idea. Specialized folks do make more but some times jobs are harder to find.
  • blargoeblargoe Self-Described Huguenot NC, USAMember Posts: 4,174 ■■■■■■■■■□
    As long as you're not so specialized that you can't transition to the next thing when the current big thing is no longer in demand, you should do fine.
    IT guy since 12/00

    Recent: 11/2019 - RHCSA (RHEL 7); 2/2019 - Updated VCP to 6.5 (just a few days before VMware discontinued the re-cert policy...)
    Working on: RHCE/Ansible
    Future: Probably continued Red Hat Immersion, Possibly VCAP Design, or maybe a completely different path. Depends on job demands...
  • Moki99Moki99 Member Posts: 24 ■□□□□□□□□□
    I think the key is to be well rounded with maybe 1-2 highly specialized areas.
  • UnixGuyUnixGuy Are we having fun yet? Mod Posts: 4,251 Mod
    blargoe wrote: »
    As long as you're not so specialized that you can't transition to the next thing when the current big thing is no longer in demand, you should do fine.

    this. you should specialize, but your foundation should be strong enough to move between different technologies, and you should specialize in more than one thing
    In Progress: MBA
  • elToritoelTorito Member Posts: 102
    I find it particularly hard to decide on WHAT to specialize in. I like it that I'm allround and know a little bit of everything. Everyone at my workplace knows they can ask me anything, and they will get an answer ... sooner or later. However, in technical discussions with specialists - often externally hired - I find that I often just can't offer input that amounts to much.

    There are a ton of things that I want to know in-depth: VMware vSphere and all VMware VDI technologies, Windows Server 2008 and all its roles (AD DS, AD CS, AD FS, WDS etc.), Exchange 2010, SQL Server, Cisco components, Windows PowerShell, Storage architecture, Firewall configuration ... the list goes on. However, there's just not enough hours in a day to learn it all.

    So yeah, specialization should lead to a less overwhelming job, and it should definitely give a sense of fulfilment knowing that you actually grasp one or two subjects 100%. To people like me, it's a hellish choice to make, though :)
    WIP: CISSP, MCSE Server Infrastructure
    Casual reading: CCNP, Windows Sysinternals Administrator's Reference, Network Warrior

Sign In or Register to comment.