Another "Give me a Title" thread
-
How many staff does Ronco have these days?
-
@scottalanmiller said:
How many staff does Ronco have these days?
I think the whole company is 300 or so. Internal IT is 2 system/network admins and a few desktop people. Then there are specialized groups like mine that usually deal with external customers but we help on internal IT projects too. For example I special in Aerohive wireless so I mainly manage our internal wireless but others have access and do some troubleshooting. Our Microsoft group also works extensively on the voice side but internal IT also has a big hand in it. Definitely doesn't seem like a typical way a company runs but somehow works for us. Have heard a few other consulting companies run in a similar fashion once they get big enough and need dedicated internal IT staff.
-
We don't use dedicated internal IT staff either. When you have all those consulting resources, it is hard to justify getting someone to handle their IT for them.
-
@Kelly said:
@Nic said:
So SAM - what's the generic title for a jack-of-all-trades IT person then?
Who does Systems and Network Administration for a majority of their time.
At my last job, I did. It was roughly split half and half. I'd spend half my time chasing down network issues and tweaking switch configurations and adjusting VLANs as needed on a campus with ~800 students and 200 staff / faculty. The other half of the time was spent working on servers doing upgrades, updates, and checking to make sure backups worked. For my first year or so there, I did a lot of desk-side support, but that tapered off after we got the IT team to have good folks in that role.
-
@scottalanmiller said:
We don't use dedicated internal IT staff either. When you have all those consulting resources, it is hard to justify getting someone to handle their IT for them.
I guess it comes down to "who makes the decisions and keeps things consistent between offices?" when all your offices need upgraded equipment or new servers or new printers or troubleshooting. If it was just a few offices and a simple network/server environment it would be so much easier. I think that's why we have dedicated staff.
-
@dafyre said:
@Kelly said:
@Nic said:
So SAM - what's the generic title for a jack-of-all-trades IT person then?
Who does Systems and Network Administration for a majority of their time.
At my last job, I did. It was roughly split half and half. I'd spend half my time chasing down network issues and tweaking switch configurations and adjusting VLANs as needed on a campus with ~800 students and 200 staff / faculty. The other half of the time was spent working on servers doing upgrades, updates, and checking to make sure backups worked. For my first year or so there, I did a lot of desk-side support, but that tapered off after we got the IT team to have good folks in that role.
At 1K+ staff you are starting to edge away from the SMB. That starts to warrant a networking title. Maybe Networking Tech, but networking. Certainly if you really top 50% of workload.
-
@quicky2g said:
@scottalanmiller said:
We don't use dedicated internal IT staff either. When you have all those consulting resources, it is hard to justify getting someone to handle their IT for them.
I guess it comes down to "who makes the decisions and keeps things consistent between offices?" when all your offices need upgraded equipment or new servers or new printers or troubleshooting. If it was just a few offices and a simple network/server environment it would be so much easier. I think that's why we have dedicated staff.
We are global and fully decentralized so makes far less sense here.
-
@scottalanmiller said:
@dafyre said:
@Kelly said:
@Nic said:
So SAM - what's the generic title for a jack-of-all-trades IT person then?
Who does Systems and Network Administration for a majority of their time.
At my last job, I did. It was roughly split half and half. I'd spend half my time chasing down network issues and tweaking switch configurations and adjusting VLANs as needed on a campus with ~800 students and 200 staff / faculty. The other half of the time was spent working on servers doing upgrades, updates, and checking to make sure backups worked. For my first year or so there, I did a lot of desk-side support, but that tapered off after we got the IT team to have good folks in that role.
At 1K+ staff you are starting to edge away from the SMB. That starts to warrant a networking title. Maybe Networking Tech, but networking. Certainly if you really top 50% of workload.
It was ~1k End-users in all. (Just out of curiosity): Does it matter to you that 800 of them were students, and only ~200 of them were Facutly and/or staff -- or do you lump them all together into the "End user" category?
-
@dafyre said:
@scottalanmiller said:
@dafyre said:
@Kelly said:
@Nic said:
So SAM - what's the generic title for a jack-of-all-trades IT person then?
Who does Systems and Network Administration for a majority of their time.
At my last job, I did. It was roughly split half and half. I'd spend half my time chasing down network issues and tweaking switch configurations and adjusting VLANs as needed on a campus with ~800 students and 200 staff / faculty. The other half of the time was spent working on servers doing upgrades, updates, and checking to make sure backups worked. For my first year or so there, I did a lot of desk-side support, but that tapered off after we got the IT team to have good folks in that role.
At 1K+ staff you are starting to edge away from the SMB. That starts to warrant a networking title. Maybe Networking Tech, but networking. Certainly if you really top 50% of workload.
It was ~1k End-users in all. (Just out of curiosity): Does it matter to you that 800 of them were students, and only ~200 of them were Facutly and/or staff -- or do you lump them all together into the "End user" category?
From an IT perspective, is there any difference? IT normally refers to uses, not categories of users. Except other IT staff and/or developers as a special group, sometimes.
-
I think the only time you wouldn't count them is if you don't have to do anything to support them - but then why would they even be on your radar?
-
@scottalanmiller said:
@dafyre said:
@scottalanmiller said:
@dafyre said:
@Kelly said:
@Nic said:
So SAM - what's the generic title for a jack-of-all-trades IT person then?
Who does Systems and Network Administration for a majority of their time.
At my last job, I did. It was roughly split half and half. I'd spend half my time chasing down network issues and tweaking switch configurations and adjusting VLANs as needed on a campus with ~800 students and 200 staff / faculty. The other half of the time was spent working on servers doing upgrades, updates, and checking to make sure backups worked. For my first year or so there, I did a lot of desk-side support, but that tapered off after we got the IT team to have good folks in that role.
At 1K+ staff you are starting to edge away from the SMB. That starts to warrant a networking title. Maybe Networking Tech, but networking. Certainly if you really top 50% of workload.
It was ~1k End-users in all. (Just out of curiosity): Does it matter to you that 800 of them were students, and only ~200 of them were Facutly and/or staff -- or do you lump them all together into the "End user" category?
From an IT perspective, is there any difference? IT normally refers to uses, not categories of users. Except other IT staff and/or developers as a special group, sometimes.
Faculty will always be more of a pain because they need "special" access to servers, applications, and networks. I'd consider them separate from an IT perspective just because of the extra headaches they cause.
-
@quicky2g said:
@scottalanmiller said:
@dafyre said:
@scottalanmiller said:
@dafyre said:
@Kelly said:
@Nic said:
So SAM - what's the generic title for a jack-of-all-trades IT person then?
Who does Systems and Network Administration for a majority of their time.
At my last job, I did. It was roughly split half and half. I'd spend half my time chasing down network issues and tweaking switch configurations and adjusting VLANs as needed on a campus with ~800 students and 200 staff / faculty. The other half of the time was spent working on servers doing upgrades, updates, and checking to make sure backups worked. For my first year or so there, I did a lot of desk-side support, but that tapered off after we got the IT team to have good folks in that role.
At 1K+ staff you are starting to edge away from the SMB. That starts to warrant a networking title. Maybe Networking Tech, but networking. Certainly if you really top 50% of workload.
It was ~1k End-users in all. (Just out of curiosity): Does it matter to you that 800 of them were students, and only ~200 of them were Facutly and/or staff -- or do you lump them all together into the "End user" category?
From an IT perspective, is there any difference? IT normally refers to uses, not categories of users. Except other IT staff and/or developers as a special group, sometimes.
Faculty will always be more of a pain because they need "special" access to servers, applications, and networks. I'd consider them separate from an IT perspective just because of the extra headaches they cause.
Yes but there are always pools of high pain users and low pain users in any business. The percentages are probably similar.
