JEREMY HAYNES / PROFESSIONAL PORTFOLIO
Network Operations
Before moving into business intelligence and analytics, I worked in broadband technical support and network operations, progressing through increasingly technical roles and ultimately into Tier 3 network operations. The work involved complex broadband and network issues that required tracing problems across systems, evaluating technical evidence and coordinating with other technical teams.
Technical operations
Network operations required understanding how individual systems and components interacted rather than treating each problem in isolation. Troubleshooting meant identifying where a failure was occurring, testing assumptions and following the problem through the network until the underlying cause could be identified.
I also created and maintained network maps using Microsoft Visio, documenting network infrastructure and relationships in a form that could be used by technical teams.
From network operations to business intelligence
I moved from network operations into a business intelligence role, bringing the technical and operational knowledge I had developed with me. Understanding the systems, workflows and data behind the operation gave me useful context when I began developing reporting and analytics for the organization.
The same habits used in network troubleshooting continue to influence how I approach analytics: understand how the system works, trace data to its source, test assumptions and determine whether the result makes sense in the real-world operation.
That transition eventually led to more than seven years developing operational reporting and analytics for telecommunications operations, followed by broader business intelligence and analytics work.
See my operational reporting and analytics work or the full experience overview.