My Professional Journey

A personal archive of my journey through tech, from 1999 to today.

View on GitHub

← Back to README

F5 Networks

Company Overview

F5 Networks is the global leader in Application Delivery Networking (ADN). In 2019, the company was in the midst of a critical strategic pivot, moving away from its legacy as a hardware appliance vendor (Big-IP) to become a software-first, multi-cloud application services platform. This period was defined by the aggressive pursuit of “Application Services Everywhere” and the bridging of the divide between traditional NetOps and modern DevOps teams.

Company Transformation

Timeline Entity Logo
2019 F5 Networks F5 Networks Logo
March 2019 NGINX Acquisition F5 Acquires NGINX

Strategic Transformation

Feature Traditional F5 (Pre-2019) Modern F5 (2019 Transition)
Core Product Big-IP Hardware Appliances Virtual Editions (VE) & NGINX
Deployment On-Premise Data Centers Multi-Cloud & Kubernetes
Target Audience Network Operations (NetOps) DevOps & Cloud Architects
Licensing Model Perpetual Hardware Software Subscriptions (ELA)
Strategic Focus Load Balancing & Security Application Services Platform

Company Profile

F5 Business Card
Business Card: Systems Engineering Manager, F5 Networks Australia

The Technology Shift

From Hardware to Software: The Telco Challenge

The core mission was specific and high-stakes: F5 had a massive installed base of hardware appliances within Australia’s largest Telco. The challenge was not just technical but existential—how to migrate this legacy footprint to a virtualized, software-defined environment without losing the reliability the customer depended on. My role focused on defining this roadmap, proving that F5 could pivot from being a “box vendor” to a software partner.

The NGINX Pivot

In March 2019, F5 acquired NGINX, the open-source web server powering a vast portion of the modern web. This was the critical narrative piece needed to convince the Telco market of F5’s commitment to open standards. It allowed us to tell a story that wasn’t just about preserving the old (Big-IP) but embracing the new (Open Source), providing a bridge for the customer’s own internal transformation.

Bridging NetOps and DevOps

A significant part of the role involved cultural translation. I worked to help traditional Network Operations teams understand the requirements of DevOps pipelines, showing them how F5 tools could be automated and integrated into CI/CD workflows rather than acting as a bottleneck.


Reflections

My tenure at F5 was a deliberate engagement to tackle a specific industry problem: the friction of modernizing legacy infrastructure at scale. However, as the work progressed, it became clear that my passion lay not just in bridging the gap to cloud-native, but in living there.

After several months, I realized that while F5 was making the right moves, I needed to take a decisive leap towards a pure software-oriented and cloud-native experience. This decision marked the end of the “transition” phase of my career and the beginning of a full commitment to the software-defined future.


F5 Networks tenure documentation during the Cloud-Native Transformation era.