Now is an amazing time to join Nozomi Networks as we build the future of OT and IoT cybersecurity.
We defend some of the world's largest organizations and critical infrastructure in more than 68 countries and we're just getting started. Our AI-powered cybersecurity platform secures operational technology (OT) and Internet of Things (IoT) infrastructures for enterprises and government entities across energy, manufacturing, transportation, resources, and critical infrastructure.
As we expand our product portfolio, our Product Management team is hiring a Senior / Staff Product Manager to help build a new platform that will become the system of record for industrial operations: every asset, every change, every approval, and its full history, in one OT-native CMDB and service management platform.
Customers asked for this. Plant teams are tired of forcing industrial environments into IT ticketing and CMDB tools that were never built for them. Nozomi Networks already sees what is on the plant floor in real time; now we are building the platform that keeps the record and governs every change. The platform is in its design and early-access phase, shaped with enterprise and mid-market customers, and the data model is still open. You will own the problem and design the solution together with engineering.
This role starts with an advantage. CMDBs live or die on data quality, and this one sits on live, first-party asset data from Nozomi Networks sensors, so the platform can verify that what the record says matches what is actually on the network. AI is part of the core, not bolted on: agents that watch for changes, open the work, and answer questions about an asset's history.
We have deep OT expertise across the company. What this team needs now is someone who has built a CMDB before.
You could be the next "Nozomier"! If this sounds like you, read on.
In this role, you will:
---------------------------
Own the OT-Native Data Model
•Lead the data model for an OT-native CMDB, designed with engineering: assets, installed positions, locations and ISA-95 hierarchies (site, area, line, cell), relationships, and the full change history of every asset from installation to retirement.
•Define how the recorded state of each asset relates to what live network data shows, and what happens when they differ.
•Decide how assets the network never sees (offline equipment, spreadsheet imports) live alongside observed ones, keeping it clear which values were observed and which were only declared.
Define Identity and Reconciliation
•Partner with engineering on identity and reconciliation rules: when records from sensors, integrations, and spreadsheets describe the same physical asset, which source wins for each field, and how every value stays traceable.
•Engineering builds the matching; you define what it must get right.
Shape Workflows, Integrations, and AI
•Shape the default workflows customers start from (planned and unplanned change, vulnerability remediation, asset changes, safety approvals) on a configurable workflow engine, including what proves a change was actually done.
•Define how the platform works alongside systems customers already run, such as an existing CMDB or ITSM tool: which system owns which record, and how work flows between them.
•Help decide where an AI agent acts and where a person must approve.
Drive Decisions and Delivery
•Make the calls: own the problem, negotiate the solution with engineering, hold the line on what a release must include, and turn weeks of debate into days of decisions.
•Work directly with early-access customers to validate, learn fast, and ship.
•Collaborate daily with an engineering team based in Europe and a cross-functional product team, reporting directly to the VP of Product.
•Embody Nozomi Networks' cultural pillars, promoting transparency, trust, and accountability.
To be successful in this opportunity, you will have:
--------------------------------------------------------
•Product ownership of a CMDB, asset, or configuration data product sold to many customers, including its structural decisions: what a record is, how sources are reconciled, how records are attested, and what history is kept. Configuring or implementing a CMDB is not the same experience; this is the experience the team needs most.
•First-hand knowledge of which parts of a CMDB cannot be bolted on later, and the ability to explain why to engineers in two sentences.
•5+ years of B2B product management at a software vendor (not only running your own company's internal CMDB).
•Strong data modeling instincts: you can whiteboard a schema, explain the tradeoffs, and tell us which mistakes you have already made so we don't repeat them.
•Experience defining identity or reconciliation rules: matching messy records across many sources when there is no single reliable key, and modeling how a record changes over time.
•Experience shipping workflow, approval, or change manage