Information Technology is an interesting market, I’ve seen a lot of different setups from where people would be Jack of All Trades Master of None to the full silo where you only know one thing, and one thing alone. When I entered the professional services market you focused on a track if you will that was either Security, Collaboration (Voice, Video, IM), Route/Switch, and Wireless. Your development track was highly focused on a single track, you needed to be a master of just that one technology. In wireless this is extremely difficult because you need to understand basics of voice for when you deploy a wireless VoIP for example, you need to know some basics on firewall rules for secure guest deployment, basic CCNP level knowledge to support your access points connected to the wired gear, etc. This was the past, going forward your connected medium shouldn’t be your primary focus, that’s just one aspect of it, you now need to know greater levels of routing/switching and security using policy engines such as ISE and ClearPass.
Going forward being a wireless engineer really needs to change. No longer should a wireless engineer be a person that knows how to install an AP, controllers, etc. The person needs to be a true RF engineer, understanding that makes you the wireless engineer. (Yes one could argue that this has been always the case and I agree, but that isn’t really what we see in the real world all the time!) With a converged access/distributed/vendor-x method there is a larger focus on understanding how a wired network properly works to troubleshoot packet flows. I know I’ve changed some of my development plans to focus more on route/switch training to better understand technologies such as SDN. I still have a desire to obtain my CWNE but now am looking at things like the CCIE R/S or CCIE Security.
Are you changing your development plans? Chime in on the comments if you are!