We are looking for a Product Manager, OSS Network Domain to own the network-and-service semantic core of ' next-generation OSS platform.
This is the role for a builder who already thinks in routers, interfaces, services, and network state – someone who can define what an OSS object means so that automation and AI can safely act on it. You will own one networking-heavy domain area of the platform (for example inventory & resource management, service design & planning, fulfillment, or assurance) and define the domain model, semantics, and product behavior that everything else is built on.
This is a builder PM role, not a requirements-forwarding role. The goal is to turn messy operator and network reality into reusable domain capabilities that R&D can build – not a custom data model or workflow per customer.
Responsibilities:
Own the product vision, strategy, roadmap, and epics for your OSS domain area.
Define the domain model for your area – services, resources, physical/logical inventory, topology, dependencies, state (planned / intended / discovered / active / degraded / stale), intent, policy, and network/diagnostic/remediation action semantics as relevant to your area.
Define source-of-truth and reconciliation behavior: which system is authoritative for which object and state, how freshness and confidence are represented, and what happens when data is stale or systems disagree.
Translate operator workflows and network reality into reusable domain primitives – resisting customer-specific schemas, models, and forks.
Partner with the OSS Platform and workflow engine PMs so that workflow blocks, AI experiences, and integrations are grounded in correct service, resource, topology, and action semantics.
Work closely with R&D and architects to define product behavior, data models, API/contract shapes, state transitions, edge cases, failure modes, acceptance criteria, and MVP tradeoffs – leaving implementation decisions to architects.
Ground the platform's AI and automation in domain truth: define how impact, root cause, and service context are computed and represented so AI output is trustworthy.
Use modern AI tools day-to-day to accelerate discovery, PRD and epic writing, competitive analysis, and modeling.
This is the role for a builder who already thinks in routers, interfaces, services, and network state – someone who can define what an OSS object means so that automation and AI can safely act on it. You will own one networking-heavy domain area of the platform (for example inventory & resource management, service design & planning, fulfillment, or assurance) and define the domain model, semantics, and product behavior that everything else is built on.
This is a builder PM role, not a requirements-forwarding role. The goal is to turn messy operator and network reality into reusable domain capabilities that R&D can build – not a custom data model or workflow per customer.
Responsibilities:
Own the product vision, strategy, roadmap, and epics for your OSS domain area.
Define the domain model for your area – services, resources, physical/logical inventory, topology, dependencies, state (planned / intended / discovered / active / degraded / stale), intent, policy, and network/diagnostic/remediation action semantics as relevant to your area.
Define source-of-truth and reconciliation behavior: which system is authoritative for which object and state, how freshness and confidence are represented, and what happens when data is stale or systems disagree.
Translate operator workflows and network reality into reusable domain primitives – resisting customer-specific schemas, models, and forks.
Partner with the OSS Platform and workflow engine PMs so that workflow blocks, AI experiences, and integrations are grounded in correct service, resource, topology, and action semantics.
Work closely with R&D and architects to define product behavior, data models, API/contract shapes, state transitions, edge cases, failure modes, acceptance criteria, and MVP tradeoffs – leaving implementation decisions to architects.
Ground the platform's AI and automation in domain truth: define how impact, root cause, and service context are computed and represented so AI output is trustworthy.
Use modern AI tools day-to-day to accelerate discovery, PRD and epic writing, competitive analysis, and modeling.
Requirements:
7+ years of product management experience, with real depth in telecom / networking / OSS / NMS / network automation.
Deep, hands-on understanding of networking and service concepts: routers, interfaces, NOS/configuration, routing and forwarding, physical vs. logical inventory, services and how they decompose to network resources, topology, and network/service state.
Able to define what a service / resource / topology object means, model service-to-resource relationships, and reason about source-of-truth and reconciliation across systems.
Strong builder orientation: defines product behavior, data models, edge cases, and acceptance criteria in close partnership with R&D and architects.
Able to say no to customer-specific requests and turn them into reusable domain capabilities.
Comfortable owning ambiguity in a fast-paced, high-growth environment; able to travel as needed for customer and partner engagements.
Good backgrounds include: OSS/inventory/assurance/orchestration vendors (e.g. Blue Planet, Netcracker, Amdocs – screen carefully, Nokia/Ericsson OSS, Cisco NSO ecosystem), network observability/assurance products, or operator network-automation teams.
Education:
BSc/MSc in Computer Science, Electrical/Communications Engineering, or a related technical field; or equivalent hands-on experience.
7+ years of product management experience, with real depth in telecom / networking / OSS / NMS / network automation.
Deep, hands-on understanding of networking and service concepts: routers, interfaces, NOS/configuration, routing and forwarding, physical vs. logical inventory, services and how they decompose to network resources, topology, and network/service state.
Able to define what a service / resource / topology object means, model service-to-resource relationships, and reason about source-of-truth and reconciliation across systems.
Strong builder orientation: defines product behavior, data models, edge cases, and acceptance criteria in close partnership with R&D and architects.
Able to say no to customer-specific requests and turn them into reusable domain capabilities.
Comfortable owning ambiguity in a fast-paced, high-growth environment; able to travel as needed for customer and partner engagements.
Good backgrounds include: OSS/inventory/assurance/orchestration vendors (e.g. Blue Planet, Netcracker, Amdocs – screen carefully, Nokia/Ericsson OSS, Cisco NSO ecosystem), network observability/assurance products, or operator network-automation teams.
Education:
BSc/MSc in Computer Science, Electrical/Communications Engineering, or a related technical field; or equivalent hands-on experience.
This position is open to all candidates.
