Getting started with a little experience
In my tenure with a Discord help server (GeekCentral), I have encountered an individual that is currently going to a tech course around Microsoft Server. He’s asked for help, and I’ve taken him under my wing, but he’s asked a good question – How do I get a job doing this while I’m in school?
The simple answer is you better present yourself as a rock star in the interview – most IT manager don’t want to train techs while they pay them (because they’ll leave if offered more money). Make sure to mention you’ll be loyal to the people that take up under their wing. This is mostly true for enterprises (larger companies). However, there are IT admin positions at almost any medium sized company, and they are all over. The best idea is to decide where you want to start. The smaller the company, the more roles you will play. So, you might be great at desktop, so they hire you and you learn server or networking because you have to.
Help Desk: you’re answering the phone, walking through scripts for applications fixes, and the first level of support for any issue. From diagnosing the issue, you escalating to the application support team, desktop, network or server team, and generally the first line of support for users. Helps to know AD, Office365 and the Office apps.
Desktop Tech: you’re the 2nd level support for desktop issues – usually hardware related, but could be “I can’t get on the network” or “I can’t print”, most of which require a remote session or a physical visit to the person’s desk. It can be a “the help desk couldn’t do it”, which is why it’s considered 2nd level support. You’re also desktop security support – usually managing the AV/anti-spyware software on the user’s PCs. You’ll also need to know how to operate in Office365 and know the Office suite well. You’ll work directly with vendors for sourcing equipment and services (like Windows 11 upgrades).
Server tech: you’re 2nd/3rd level for anything server related, including Active Directory. You’re taking tickets from the help desk or desktop group, and see why people can’t login, some can’t print (print mapping with auto login scripts), or password expired/I can’t remember it. You’re also now responsible for systems in the back office (behind a secured door, usually). You will be looking at backups and recovery, DR plans (what happens if the office loses power), and welcome to on call! You’ll probably be the sole or in a team of techs that share after-hours call in support for critical server issues (server down, out of space, etc). You usually manage the infrastructure applications: AD, AV, backup, VMware/HyperV, Office365, cloud, and have a domain-admin level access to the servers and desktops. These are usually also part of the executive support team – you’ll be help desk, desktop, network and server support for any or all of the C-level execs. You’re a known asset to vendors. You MIGHT go to conferences.
Network tech: you’re 2nd level for network. You’ll handle new network drops (or manage a cabling company) or new wifi deployment, connect all the office together, manage and connect phones, respond to wireless issues, sometimes you’re also security here too. You’ll need to know firewalls, how to secure the ENTIRE environment from hacks, how to prevent infiltration, and you’ll need to know physical security measures as well. You the networking vendor’s rock star.
3rd levels
From here, there are 3rd level support options for desktop, server and network. They can be team leads or managers, or for larger companies, they are listed as Engineers or Senior Admins. You’ll need to know how the put the company back together for any reason. You’ll specify software and hardware, and help the managers or directors with budgets and planning, be the on call escalation, and have almost all the “keys to the kingdom” – you’ll have access for all network devices, administrative access to desktops and servers, and be able to failover the company for DR purposes. You have the ear of the IT director or CIO/CFO. They also manage the vendor relationships, so get to know them, do things for them, and you’ll reap free lunches, passes and swag from the vendors (depending on the company gift policy). They are at conference a lot, and might even have a blog to gain vendor recognition.
Directors
Director are usually the manager over all IT – so they get heads up on issues, fixes, and security posture for reporting up. The many times will report to a C-level and will sometimes be the “mini C-level” for what he or she does.
Upstream C-levels
Smaller companies will only have one or two, so I’ve seen IT report to the CFO. If this is the case, get good at documenting return on investment (ROI) reports and cost analysis (do it vs don’t do it). You’ll need to know costing, financials reports, etc., which is invaluable going forward, you will just have to fight for EVERY expenditure.
CIO’s are worried about the stability of the systems, and keeping the business running. Good backups, common schedule for patching (desktop, servers, network and security), and being visible for the RIGHT reasons will go far here.
My story
I started with a hospital in the night shift IT. I did backups of the minicomputers that ran the hospital patient and charging system. I knew the system from working in admitting for a year. I learned soft skills, which were invaluable. I start poking my nose around on the Novell network and got accused of hacking. I left shortly after that. I landed at a software company, programming in FoxPro, but knew Novell, so I got my first real IT job with an office furniture company (the largest in Houston) as a Network Admin. I interviewed well, and they figured they could train me. I did remote office hookups, managed vendors, learned NT 4.0, learned Citrix, SQL Server and Exchange, and migrated 2 Novell networks to Windows. It was a fun job, but busy and I looked to learn everything. We were the help desk and desktop and server admin to start, then hired help desk techs, and I went 2nd level. I was with the company for 4 years, then started my run with an outsourcer on-site at an oil/gas company. Big time enterprise, and spent 7 years with them, got into VMWare and Unix/Linux support, and stayed with Unix Engineering for 2 years with an energy company. My knowledge of Windows, VMware, Exchange and SQL was very useful. I then was able to start my consulting career. That took me 14 years, with no degree and mostly on-the-job training. I made a point to try and stay at places. I made myself valuable and pushed for better salaries.
Every step of way, I made relationships, some more personal than others, but since I was right outside the nation’s 4th largest city, I saw the IT in the city was very close-knit – with about 2 degrees of separation for almost any IT Engineer. All that to say, NEVER burn a bridge at a company. Learn to deal with difficult coworkers, learn to diplomatic, but don’t be walked on. Words travels fast in small circles, like local industries. You’ll find yourself needing to move to get a job, and that makes things a little more difficult (interviews and travel, etc). Even as a consultant, I seen managers that think they can treat everyone like their kids and by that time, I had confidence in my knowledge, so I usually pushed back to save face. Still, customer will sometime want to disregard your input, grin and comply and have a better option than “I told you so” when it goes south. Be a part of the solution, not the problem.