Product Manager, Cloud Platform (Data & Telemetry) (Remote)

<div>The application window is expected to close on: 08/31/2026<br/><b>Job posting may be removed earlier if the position is filled or if a sufficient number of applications are received</b>.<br/><br/><strong>This role is open to remote candidates within the United States.</strong><br/><br/><strong><b>Meet the team</b></strong><br/><br/>Come join the Cloud Platform team. We build the data and telemetry foundation behind cloud-managed networking experiences for customers. Partner with passionate product teams and engineers who use our platform to deliver reliable, high-fidelity insights and capabilities. Work in a cross-functional environment spanning product management, engineering, data science, and design, with a collaborative, technically curious, and customer-focused vibe. Connect streaming telemetry infrastructure and data services to Meraki's broader cloud strategy, enabling internal teams to build differentiated customer experiences. Help shape a platform that is evolving to support the next generation of AI-driven and agentic networking.<br/><br/><strong><b>Your impact</b></strong><br/><br/>Define and own a multi-quarter roadmap for telemetry ingestion and data-platform capabilities to advance Meraki's cloud strategy. Lead planning and prioritization across engineering partners, balancing performance, scalability, reliability, customer needs, and market opportunities. Translate distributed-system constraints and data requirements into clear product requirements, user stories, and measurable outcomes for high-availability, low-latency services. Build and evangelize APIs, tools, data structures, and access patterns that help internal product teams and future AI/ML capabilities use telemetry effectively. Measure success through platform reliability, latency, scale, adoption, and the customer experiences enabled by the platform.<br/><br/><strong><b>Minimum qualifications</b></strong><br/><ul><li>7+ years of related experience and 3+ years of product management experience with cloud platforms, data infrastructure, SaaS networking, or a comparable technical product area.</li><li>Bachelor's degree in Computer Science, Engineering, Data Science, or a related technical field, or equivalent practical experience in technical product development.</li><li>Experience defining a product roadmap and requirements for at least one backend, platform, data, or infrastructure capability delivered to production.</li><li>Experience partnering with engineering teams on APIs, distributed systems, data pipelines, or cloud architecture.</li><li>Experience using product, platform, or operational metrics to prioritize work and evaluate outcomes.</li></ul><br/><strong><b>Preferred qualifications</b></strong><br/><ul><li>Familiarity with one or more streaming, messaging, caching, relational, or time-series technologies, such as Kafka, RabbitMQ, Redis, PostgreSQL, or time-series databases.</li><li>Experience with Kubernetes or Amazon Elastic Kubernetes Service (EKS) environments.</li><li>Experience defining data structures or access patterns for AI/ML models, analytics products, or autonomous agents.</li><li>Experience with enterprise networking, telemetry platforms, observability products, or large-scale SaaS services.</li><li>Ability to communicate complex technical tradeoffs clearly to engineering and non-technical stakeholders.</li></ul><br/>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...