> Markdown version of [/jobs/ext/4603132-engineering-product-owner](https://www.wearedevelopers.com/jobs/ext/4603132-engineering-product-owner). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Engineering Product Owner - **Company:** ELISITY, INC. - **Location:** San Jose, CA, United States (Remote available) - **Contract:** Permanent contract - **Skills:** Data Stores, Network Security, Systems Architecture, Large Language Models, Front End Software Development - **Published:** November 6, 2026 - **Apply:** https://www.careerbuilder.com/job-details/engineering-product-owner-san-jose-ca--155b1902-7062-4e2a-81da-107c7635f202 ## About the Role Business-to-Business (B2B), Research & Development (R&D), Product Design, Technical/Engineering Design, Product Management, Establish Priorities, Testing, System Architecture, Metrics, Quality Metrics ## Description Were looking for Engineering Product Owner - a deep domain and technical product/design owner inside the engineering organisation. It is a design / R&D-track role decoupled from day-to-day delivery, it is not a people-management role. EPO plays a key role in Product Management architecture, translates intent into buildable, prioritized epics, owns feature intent; advises on feasibility, engineering backlog & roadmap, enforces ticket rigor, co-publishes one joint roadmap, owns the product/design questions, partners on system design, scale-testing, datastore choice, prioritizes challenges and tradeoffs and owns final product-content arbitration. The person selected for this role is the engineering-side product owner who partners with - and is held to account by - Product Management for what to build, owns the backlog/roadmap/design discovery for how its shaped, and defers system architecture to the architect and final product-content arbitration to Product Management. What Youll Do * Define the metric youll stand behind. Decide the customer-facing classification-quality metric - which population, which confidence threshold, which categories - and close the loop on the strongest real-world signal you have: what operators accept and reject. Todays quality numbers arent yet measured against the true target population; making the metric defendable is the precondition for every downstream bet. * Sequence the roadmap. Turn the competing classification engines and the reporting/compliance backlog into one prioritized plan, per device population and per customer segment. * Own the device taxonomy as product. What the categories are, when one is added or removed, and how it scales as the classification approaches multiply. * Set assistant product strategy. Which questions it must answer well, which capabilities matter most, and the cost-vs-quality envelope of the underlying models. * Own the reporting & compliance roadmap. Which dashboards and compliance reports ship next, their delivery model, and the snapshot SLA youll commit to customers. * Police the Reporting/Insights boundary and keep report generation out of the chat path where it doesnt belong. * Own the engineering backlog and the single joint Product + Engineering roadmap. Groom it, drive PM-originated feature intent into buildable epics, and enforce backlog rigor at ticket creation. * Make the reliability-vs-feature calls. Prioritize the classification and snapshot reliability cliffs against new features - defer the how to the architect, but own the whether and when. * Define the SLOs for both services and decide what instrumentation work to fund, since most of these SLIs are not yet instrumented. What Were Looking For * Deep domain. Network security, device identity, or microsegmentation - or an adjacent security/networking background that maps cleanly onto device intelligence and flow data. * Technically credible enough to challenge an architect. You can read the code, reason about LLM/ML classification and an analytics data plane, and pressure-test a datastore decision - without trying to be the architect. * Product judgment under ambiguity. You can define a defendable metric where no clean ground truth exists, sequence competing R&D bets, and say no. * Backlog and roadmap discipline. You run a tight backlog, hold ticket quality at the source, and can co-own a single joint roadmap with a separate PM org. * Comfortable in a design/R&D track. You drive feature design and prototypes and stay out of standup/troubleshooting ops; you dont need a reporting line of direct reports to have impact. Nice to Have * Prior scale at a security or networking vendor; shipping LLM / agentic features in a real product. * experience taking compliance or audit reporting through analyst evaluations. Why You'll Love Working Here * 100% remote with flexibility and trust. * High-impact role in a fast-growing scaleup environment. * Modern, cutting-edge tech stack with real room to experiment. * Strong ownership and influence over frontend decisions. * Supportive, collaborative team that values learning and initiative.