(Another) One for the IT bods - first thoughts about specialising

[TallPaul_S]

Short(ish) bit of background - I've been working in IT support in 1st/2nd line (broadly speaking) for nearly 4.5 years, IT was a career change for me (8+ years in financial services before that) so 4.5 years ago I was starting at the bottom.

Spent a little too long at my previous role (4 years) but as a company they were great, very very good at what they do (MSP with a physical datacentre) and a very controlled environment. Everything was strictly controlled and hosted on-site.

Cut to my new job which is quite, quite different Typical small MSP with small customers, 90% of environments are cloud based (O365/sharepoint, should be more AWS in the near future) or workstation based with some various server set ups with file servers/DC's etc etc. Every day is different, and I'm getting a huge amount of exposure to lots of stuff I'd never touched in the 4 years in my previous role. One day I can be at a new office for a customer in London installing and patching in a new switch and getting their network up and running, then the next it'll be doing basic 1st line stuff like setting up new users/installing O365/folder permissions/troubleshooting basic issues, then the next it might a weird group policy issue that has me and the 2nd line* guy looking at it for hours because it just makes no friggin' sense... then the next day it could be installing a UPS in a customers rack on-site, and then the next day troubleshooting network issues for a customer, or setting up VPNs.

*2nd line in our company terms but probably not 2nd line in 'industry terms'. Server rebuilds, high level network issues and escalated stuff from 1st line, that's the same '1st line' that go to customer sites to patch in switches/install servers/UPS or deal with network issues etc etc so not typical 1st line either.

My aim when I moved to this role a few months back was to be earning a certain amount within 2 years of now, with that amount that being 30k minimum, roughly 30% more than I'm on now. Certainly not an unrealistic target as I'll have had 6 years in IT by then (some might say I after 4 years I should already be at that level, but that's what it is). As previously mentioned I didn't get the movement I wanted in my first role and so probably wasted a year or 3 there before moving to my current role - and I'm not a big fan of moving jobs after a short time so have no plans to move again in the next 9 months but I am looking to the future and starting to think about what I can start to specialise in.

I have plenty of choices purely because I get exposed to a load of different stuff every day, and also because my current employers are really looking into ways of doing things better and so there's a lot of potential changes I could suggest/work on based on my previous MSP experience. Automation interests me a bit, a friend and ex-work colleague of mine is heavily getting into this in his new role, he has a fair bit more money and resources to play with though I've only used powershell for an hour tops and not touched scripting stuff but certainly willing to have a play. I learn by doing (and breaking) stuff so setting up a few VM's wouldn't be out the question for me to play with. Networking is a particular weak point for me so again I'd be interested in playing around with that to build up my knowledge.

Oh and I only have CompTia A+ at the moment (well, 2 years ago) but I think MCSA certs will come at some point in the next year or so through work, and probably some AWS certs as that's where we're starting to head.

So, any ideas on how I can decide where/how to start with thoughts about focusing on a certain area in the next 1-2 years? - I've now got my foot firmly in the door in my current place but want to be less of a 'jack of all trades' and more of a master of one or 2 things with still being able to do everything else. I know automation is/will be hot so that could well be something to go into, and if it can improve the processes and procedures at my current place that would be highly beneficial! Also getting off the service desk customer facing side would be a goal to aim for If all else fails then I'm fairly certain in a year or so I could walk into a '2nd line' job at £28-30k without too much issue, but I'd rather start looking at specific areas to focus on.

 

[dowie]

Best thing to do is to find something you enjoy and focus on that, if you're doing something you enjoy then you'll tend to be naturally more enthusiastic about it/keener to learn etc.. Perhaps consider some additional qualifications, an undergrad degree or masters too even (especially if relevant to the path you want to go down) - undergrad might well be generic STEM subject and can be part time, MSc courses though offer you plenty of scope to specialise in say data science, security, software engineering or indeed some aspects of hardware. Obviously its not for everyone and you'll get some jaded people who will try and say that university isn't worth it (often because they've ended up going down some route that didn't require it, did vendor certificates and don't really know any better) but depending on where you want to specialise then it is worth considering.

 

[paradigm]

At this point in the trajectory of the industry I'd suggest focussing on moving into DevOps and Automation. The decent money is still attainable in your more legacy "infrastructure" type roles, but these are becoming rarer and rarer.

 

[Maccy]

At this point in the trajectory of the industry I'd suggest focussing on moving into DevOps and Automation. The decent money is still attainable in your more legacy "infrastructure" type roles, but these are becoming rarer and rarer.

Exactly what I was going to suggest.

 

[ObSene]

DevOps and Automation is fine if you like coding, if not, Security Engineering is another good area.

 

[randomshenans]

Dont have to code to do devops though really do you

 

[Maccy]

Dont have to code to do devops though really do you

I think you would need as a minimum bash/shell scripting and some Python/Java/Ruby understanding too.

 

[randomshenans]

Scripting yes, and OK, I will give you some ruby, but otherwise I don't think so. I know people who don't. They do the aforementioned but they're not coders.

 

[Maccy]

True, it's not necessarily a requirement, but I think it would help if you had an understanding of the "core" languages as it would put you in a better position against competition when going for roles.

 

[dowie]

I'm not really sure what is new about "DevOps" - they don't need to code? They're in R&D or at least work closely with developers etc.. it sounds like what we used to call "software turnover" at a previous place I worked in.

 

[FerretBoy]

Well DevOps is a culture, developers bringing coding practices to operations and operations helping developers build robust development environments.

So yes you do need coding as frankly your infrastructure should as close to code as possible. With cloud you can 100%, but physical devices it will be configuration as code.

That said you don't need to be an OO guru, just some scripting languages under your belt.

 

[FerretBoy]

If I was in your shoes OP I'd go full out AWS certification with maybe some Azure too.

Start with
https://aws.amazon.com/certification/certified-cloud-practitioner/
Then:
https://aws.amazon.com/certification/certified-solutions-architect-associate/

Both can be studied for fairly easy. Check out https://acloud.guru/

That should set you up for a solid salary

 

[dowie]

Well DevOps is a culture, developers bringing coding practices to operations and operations helping developers build robust development environments.

So yes you do need coding as frankly your infrastructure should as close to code as possible. With cloud you can 100%, but physical devices it will be configuration as code.

That said you don't need to be an OO guru, just some scripting languages under your belt.

Well it was being described as a job previously not a culture. Though again having awareness of the requirements of other teams, working together etc.. also doesn't seem to be anything particularly new. This sort of thing has been in place in some companies for years.

 

[HangTime]

Sounds like you are probably underpaid as I would agree the type of activity you describe does not sound like 1st line.
You mention your employer is going down AWS route so get them to stump up for certifications and then use that to get a job paying £30k+ next year.

 

[TallPaul_S]

Thanks for the replies, it's confirmed my thoughts that automation is a good area to get into, I've started a powershell course on the Microsoft virtual academy, I figured that would be a good place to start and I really should learn powershell anyway. I can set up a lab with a DC, file server, workstation etc on my home server to around with some shell scripts.

I'll have a look at AWS certs too, should be able to get them for free through work.

I'll have been here 6 months as of the 19th September and will be due a pay review as per my contract, I'll see how things go after that as I'm currently writing up a document detailing loads of improvements I think would benefit the business.

 

[KungFuSpaghetti]

As other have already said, find an area which interests you most, be it networking, wintel, dev, packaging, automation etc etc. I've been in a similar predicament as you, started working on an IT Helpdesk 18 years ago on a measly £13'900 and had to deal with all sorts, but it was varied and fairly technical. Did that for 3 years and it got less technical as time went on and became more of a glorified customer services type of role where phone skills were more relevant than technical ability. I got the opportunity to apply for a second line role at the same place, then jumped on it. Pay wasn't much more at the time, think it was circa £18k, but at least it exposed me to more technologies.

Eventually after doing that a year, they split the 2nd line team up, so desktop support and network support became 2 separate functions. I was fortunate enough to be picked for the networking team who paid for all of my Cisco courses and exams so I could get my CCNA. Did that for a year or so, but networks didn't really interest me like I thought they would, so when we installed a Nortel CS1K PBX and full contact centre I had the opportunity to get involved in that at grass roots level. Now this was something totally different and I found the whole call routing thing fascinating, so ended up looking after the telephony platform.

Fast forward 13 years, still at the same place, but now I purely focus on contact centre, specifically IVR and ACD so I develop all of the call routing from the hosted NGN platform all the way through to the agent answering the customer through various means of contact. I should really do this as a contractor as I'd easily earn 6 digits, however having a 19 month old, a wife, mortgage etc I like stability and I'm not hugely motivated by money (plus my missus is a solicitor, so between us we do okay). I also love where I work and love my job and actually look forward to coming into work on a morning.

 

[TacticalFish]

snip

Hope this isn't a thread jack, but that sounds really interesting! I've always been interested in the more 'IT' side of telecoms engineering, ever since I met an Avaya engineer when working at Nokia.

 

[Admiral Huddy]

Be careful when specialising into a specific field of IT. The trends of today are soon condemned to history within a flash and before you know it, you're left behind.

Speaking from my own experience, I specialised as an iSeries developer 30 odd years ago starting as an IBM developer then later into the banking sector where I still work. Whilst the platform is still going, it's had its day. Newer technologies and methodologies are coming in fast than I can keep up. In fact, we are in the process of removing the current application that I have worked on for as many years than I can remember. My current employer want something that isn't so hevily bespoked as this is a risk.. so they are looking for an off the shelf product. I'm not going to grumble, it has served me well as both a contractor and as a permanent developer down the years, particularly at the time of the Euro and y2K ....but I never had the ambition to leave and cross train as i thought really , it was a job till retirement so complacency kicked in. So as I approach my redundancy mid-next year.. I doubt I'll return to IT.. Half of this is by choice (I've had enough) but the other half is that there just isn't a need for the skill set there once was so i doubt I'll find anything anyway.

I wouldn't change a thing, but maybe all those years ago I should have delved deeper into C++ or C# instead when i had the chance instead of a niche programming market that i did get into.. but hey.

Bottom line - Whatever you choose, make sure you have a clear personal development plan and stick with it. Don't be frightened to try new things. Never get complacent and if things aren't going your way, then move on. You can't afford to lay back and think you always have a job in IT.. the world catches up - fast.

Good luck

 

[FloppyPoppy]

Be careful when specialising into a specific field of IT. The trends of today are soon condemned to history within a flash and before you know it, you're left behind.
Good luck

best visual representation i could think of



Very true though the specialised fields of IT are a what i would consider to be somewhat volatile. Great whilst they're in and your working in them. Bad when your field has practically vanished due to further advancements within the industry itself.

 

[KungFuSpaghetti]

Hope this isn't a thread jack, but that sounds really interesting! I've always been interested in the more 'IT' side of telecoms engineering, ever since I met an Avaya engineer when working at Nokia.

It is a good field to get into, job wise there certainly aren't as many about, as it tends to be a bit specialised, however if you're lucky or good or even both, then you'll find a decent role and you'll be well paid for it. We had a contractor at our place for a major project delivery who was here for 3 year on £650 a day. Really knew his stuff and was fantastic, learned a hell of a lot from him. But goes to show how well it can pay, as that same role in London he's just taken as a new contract for more than double the daily rate we were paying him!