Adapting Product Management to a Remote-First Internship
In July 2020, I began a Product Management internship at Cloudflare on the DDoS team, with a focus on improving the value of Network Analytics for customers. The experience was shaped by the shift to fully remote work during the COVID-19 pandemic, which changed how I onboarded, collaborated, and learned about the product lifecycle.
Remote Onboarding During the Pandemic
Like many others in my cohort, this was my first experience working remotely from scratch. Without the physical cues of an office setting, picking up communication subtleties such as body language and eye contact was notably harder. Cloudflare responded by building a structured remote onboarding experience filled with knowledge-sharing sessions, coffee chats with colleagues across global offices, and weekly seminars covering topics from legal data protection practices to serverless computing with Workers.
Cloudflare didn't just maintain the summer internship program — it doubled the size of the incoming class. As a new hire, I was paired with a mentor, a buddy, and a manager to help me acclimate. Social engagement continued through various virtual activities tailored to different time zones, including group meetups, Pub Quizzes with the EMEA team, and scheduled community sessions designed to foster a sense of shared purpose and belonging during a time when many of us were isolated.
My Scope on Network Analytics
My project concentrated on enhancing the transparency that Network Analytics provides to both customers and internal stakeholders regarding traffic patterns and attacks. Network Analytics is Cloudflare's packet- and bit-oriented dashboard that gives visibility into network- and transport-layer attacks mitigated worldwide. Among the updates I led in visibility features was the addition of trends insights. This period also saw the dashboard extended to Enterprise customers on the Spectrum service, Cloudflare's L4 reverse-proxy that protects networks from DDoS attacks while aiding network performance.
Because of its interdisciplinary nature, effective product delivery in this space required clear facilitation of communication between UI designers, UX researchers, designers, content writers, backend engineers, and others. A significant portion of getting the product right meant aligning those teams behind user needs and creating clear communication channels across their distinct perspectives.
Listening First: Stakeholder Discovery
The first month of the internship was spent consulting internal stakeholders, including Customer Support engineers, Solutions Engineers, Customer Success Managers, and other Product Managers. Drawing on their experience with customers, these conversations provided deep insight into how Network Analytics could help streamline support and reduce internal overhead costs while giving users clearer, more useful visibility.
Initial discussions focused on avoiding redundant efforts — this process clarified which problems had already been investigated and what areas were still open. The learnings formed the backbone for subsequent customer interactions where we validated requirements in-person.
Customer-Driven Feature Development
After interviews with customers, a clear pattern emerged: the dashboard was effective at showing what happened, but not necessarily why it mattered for users trying to determine their next steps. Users wanted answers to questions like: Do I need to act on these numbers, and what should I be concerned about?
To distill these insights into concrete requirements, we developed a Product Requirements Document in pieces, scheduling features around quarterly goals. Following an iterative review process with product managers, designers, and engineers, we rolled out new features on a bi-weekly cadence, always staying open to feedback before and after each launch. The goal wasn't a flawless all-at-once release, but a string of incremental improvements that kept pace with customers' shifting needs.
Finding a Remote Work Rhythm
All customer and stakeholder interactions during this time were conducted over video conferencing and chat. For my role, the instant messaging function was invaluable — it offered a low-friction way to check in with team members and iterate quickly without scheduling a formal call. Weekly touchpoints with managers, the Network Analytics team, and several engineering teams helped keep the project trajectory steady.
Reflections on Growth and the Road Ahead
The experience reinforced that product management is a dual-ended growth curve. Individuals expand their creative thinking and problem-solving skills through the process of developing customer empathy, and in tandem, the product matures by synthesizing customer feedback with cross-functional collaboration. Ensuring that there are constant direct loops between users, stakeholders, and builders is essential for keeping a product like Network Analytics both useful and responsive.
Over the course of the internship, I had a unique vantage point to see Network Analytics serve as a direct window into the efforts of Cloudflare engineering toward securing the internet. Having gone fully remote, I relied on the company’s thoughtfully arranged resources for managing that kind of workflow — from onboarding support to remote communication norms — and was able to learn as much as I’d expect in any "normal" cycle.
The internship underscored the importance of a resilient onboarding structure and the power of consistent collaboration across distributed teams. And working across time zones, I saw for myself how agile, flexible remote work can unlock real growth — both for an individual and for the product they're building.
