Computer Network Analyst

A typical week tends to mix performance monitoring, ticket-driven troubleshooting, capacity planning, change management, and the slower work of evaluating new tools or topology changes. You'll often trace intermittent issues across multiple systems — a slow application that turns out to be a misconfigured switch, packet loss that points to an ISP problem. Documentation and runbooks are more important than the heroic-fix mentality suggests.

Coordination involves systems administrators, security teams, application owners, vendors, and sometimes business stakeholders explaining why their dashboard is slow. On-call rotations are common, and outages don't respect business hours. Cloud and SaaS shifts have changed the role significantly in recent years.

People who tend to thrive here are patient with ambiguous failure modes, methodical about documentation, and energized by knowing how things actually connect. If you want pure development work or strategic architecture roles, the day-to-day operational rhythm can feel constraining. If you find satisfaction in keeping the network humming and being the person others trust to figure out the weird ones, the work tends to feel quietly essential.