I currently work 32 hours a week as the main internal IT person for a logistics company with about 110 users. We also use an external MSP, but I handle most day-to-day IT and coordinate with them when needed.
My responsibilities include user and device management, laptop deployments, endpoint policies, identity and access management, security, software deployment and licensing, ticketing and CMDB administration, cloud storage, email and collaboration tools, softphone and call-queue management, troubleshooting hardware and networks, supplier and ISP coordination, documentation, infrastructure changes, and small IT projects.
I also support a small engineering company with around five users, potentially growing to ten, where I am building much of the IT environment from scratch. That includes device management, security, cloud services, software deployment, and general support. Outside work, I run a homelab with several servers and virtual machines.
I started in IT support and workplace management, but my role now overlaps with systems administration, cloud administration, infrastructure, security, telephony, project work, and IT coordination. I enjoy the variety, but I worry about becoming the person who does a bit of everything without developing enough depth in any area.
What job title best describes this kind of work? Should I aim for systems administration, cloud administration, IT management, or continue as a broad generalist? Would it be better to specialize in one area while keeping my broader skills? Which skills or certifications would provide real value, and when does someone move from support into sysadmin work?
4 Answers
Do not choose certifications just to settle the question of who you are professionally. Pick a direction based on the work you enjoy and the roles you want to apply for, then use certifications to fill specific gaps.
Your homelab can help with that decision. Pay attention to which projects make you lose track of time. If that is virtualization and infrastructure, pursue systems or cloud engineering. If it is improving processes and working with people, an IT operations or service-management path may fit better. A broad IT generalist can be very valuable, especially when paired with clear depth in one or two areas.
Titles vary a lot between companies, but your work sounds like junior systems administration with a strong generalist and platform-administration focus. IT operations usually covers systems, storage, networking, and infrastructure, while people who combine operations with significant software development often move toward DevOps or platform engineering.
Since you are interested in infrastructure, virtualization, cloud, and identity, those would be sensible areas to develop further. Networking is useful, but you do not need to become a network specialist immediately. Build confidence gradually through practical projects rather than letting unfamiliar command-line tools define your career choice.
Keeping broad experience early in your career is a strength. You have already built a useful foundation across endpoints, identity, networking, cloud, security, infrastructure, and vendor management.
I would keep that breadth but deliberately deepen one area. Since infrastructure interests you, automation, scripting, Linux, infrastructure as code, cloud services, monitoring, and virtualization would be natural next skills. Try to automate repetitive work in your current environments and document the results; that will demonstrate engineering ability much more effectively than collecting unrelated certifications.
You are already doing sysadmin-level work; the title simply has not caught up with the responsibilities. At a company of roughly 110 users, managing identity, endpoints, cloud services, infrastructure changes, vendors, and security is well beyond traditional help desk support.
The next step depends more on what you want to spend your time doing than on finding the perfect label. If you enjoy variety and communication, IT management or a senior generalist role could suit you. If you prefer technical depth, choose one or two areas such as cloud, identity, endpoint engineering, or infrastructure and make those the center of your next role.
That description feels fair, and I would like to keep moving toward infrastructure, especially systems, virtualization, cloud, and identity. Networking is the area I find least comfortable, although I know avoiding it entirely probably would not be wise.
I am also interested in IT coordination because I enjoy translating between users, management, suppliers, and technical teams. I am not sure whether that should become my main direction or remain a complementary skill.