Product owner

Job description

Our Mission At Palo Alto Networks®, we’re united by a shared mission—to protect our digital way of life. We thrive at the intersection of innovation and impact, solving real-world problems with cutting-edge technology and bold thinking. Here, everyone has a voice, and every idea counts. If you’re ready to do the most meaningful work of your career alongside people who are just as passionate as you are, you’re in the right place. Who We Are In order to be the cybersecurity partner of choice, we must trailblaze the path and shape the future of our industry. This is something our employees work at each day and is defined by our values: Disruption, Collaboration, Execution, Integrity, and Inclusion. We weave AI into the fabric of everything we do and use it to augment the impact every individual can have. If you are passionate about solving real-world problems and ideating beside the best and the brightest, we invite you to join us! This role is remote, but distance is no barrier to impact. Our hybrid teams collaborate across geographies to solve big problems, stay close to our customers, and grow together. You will be part of a culture that values trust, accountability, and shared success where your work truly matters. Job Summary We are looking for a Product Owner to own a domain of our technical sales experience — end to end, from unmet field need to adopted, value-generating capability. This is not a traditional Product Manager role. We aren't looking for someone to groom a backlog and count features shipped. We want a domain authority who owns an outcome: did the capabilities their domain produces actually get adopted by the global Solutions Engineering (SE) field, and did they make those sellers measurably more effective? You will own the what and the why for your domain — translating raw field signals into prioritized PRDs. And you will own adoption: the rollout, enablement, and feedback loop that turns a shipped capability into real field impact. You will not manage the engineers who build it; you drive the build through the clarity of your specifications and through influence, partnering with a technical counterpart who owns the how. Success is measured not by features shipped, but by the effectiveness, efficiency, and consistency your domain brings to technical sales teams worldwide. What You'll Do Discover — own the field signal Own the canonical understanding of what the global SE force actually needs in your domain — across PoV toolkits, lab scenarios, demo flows, discovery workflows, and field utilities. Practice "AI-Centric Discovery": use conversational AI agents to capture raw field signal and structure it into shippable specs at the same velocity as your engineering counterparts ship code. Run continuous user research — interviews, observation, design partnerships with working SEs — and validate every workflow against real-world selling motions. Define — own the domain strategy and the specs Set and maintain a multi-quarter vision and roadmap for your domain, aligned to business priorities and field truth (not to what is easiest to build). Prioritize and specify the capabilities your domain delivers — for example: discovery workflows, use-case recommendations, demo orchestration, knowledge retrieval, opportunity blueprints, asset generation, evaluations, agent-to-agent workflows, and institutional-memory repositories. Produce engineering-ready PRDs and hand them to your technical counterpart. Hold the strategic line on what is worth building — you can defend a "no" as confidently as a "yes." Drive Adoption — own the field outcome Own the rollout, enablement, and feedback loop for your domain's capabilities. You are accountable for getting SEs to actually adopt them — not merely for shipping them. Close the loop from field-need → capability → measured value: instrument adoption, gather field feedback, and feed it into the next cycle. Partner with Engineering — influence, not authority Partner closely with the technical side (Outcome Architects and Engineering) who own the how. Translate business objectives into prioritized initiatives; balance short-term field wins against long-term platform investment. When a technical constraint reshapes scope, absorb it into the spec — don't route around it. Champion the User and Align the Org Act as the primary advocate for Solutions Engineers across Sales, Solutions Engineering, Enablement, Operations, and Leadership. Drive alignment on what your domain builds and why it matters — influencing without direct authority. Measure Success You will define, and be held to, outcome metrics for your domain, including: Platform adoption and active users Asset reuse and content-contribution rates Reduction in SE preparation time Discovery-quality improvements Demo consistency User satisfaction Pipeline influence and sales-productivity impact Who You Are The Domain Authority — deep, practitioner-level expertise in your CyberArk domain (PAM, Secrets Management, Cloud Security, Privileged Access, Identity). You don't just know what these are; you understand how they get deployed, demoed, and adopted in real customer environments. The Outcome Owner — you measure yourself on adoption and field value, not on features shipped. You own the result end to end, and you can drive it through influence without direct authority over the engineers who build. The AI-Augmented Discoverer — you treat conversational AI agents as your primary discovery and specification interface, structuring field chaos into shippable specs at 10x speed. Outcome Fluent — you choose what to build based on field truth and strategic impact, not on what is loudest or easiest. SE-Native — you have hands-on Sales/Field Engineering experience. You've demoed to customers, run PoVs, and felt the friction of broken lab environments firsthand. You speak SE. Spec Orchestrator — you translate Slack threads, demo failures, customer asks, and sales-call notes into the structured PRDs your technical