Monday, July 15, 2019

Workload for network engineers

I'm trying to determine how many engineers we should hire in the future. I work for a large real estate management company that has 100's of remote sites that we manage 24/7. Right now we have 1 senior and 1 mid level engineer, who oversea the network. The VoIP team is managed by another director, which allows us to focus on infrastructure, security, data center, etc.

Our daily volume of trouble tickets is relatively low for the engineering queue. The majority of their time is spent on maintenance, upgrades, troubleshooting high level issues, RMA's, vendors, new/existing circuits, data center work, etc etc.

However, we have 3 major projects coming up. One SDN project that is still in its infancy, but needs to get started by early next year. The second, is a Cisco ISE project which we will implement and manage within the next 2 months, however this project will continue well into the later parts of 2020 and beyond. And three, we have multiple sites turning up which will require A LOT of time and resource.

Questions:

Does anyone have a hard rule on how many projects/tasks we should assign per engineer? What are the best ways to determine when its time to hire more help?



No comments:

Post a Comment