Technical Product Manager (Data Integrations)

<div class="content-intro"><p>Orcrist is building a next generation data intelligence platform using cutting-edge technologies. We're handling petabyte-scale data with sub-second queries. Our product is a Kubernetes‑based platform delivered as B2B SaaS or as a self‑hosted on‑prem solution, including air‑gapped deployments. We enable customers across defense, law enforcement, and enterprise to turn mission-critical data into actionable intelligence.</p></div><h3>Role</h3> <p data-pm-slice="1 1 []">Every investigation starts with data. As PM for the Integration team, you make sure analysts in law enforcement and defense have the data they need, when they need it. You own the roadmap for integrating data from commercial vendors, open feeds, social media and messaging platforms, as well as the admin interfaces used to manage these integrations. Your work ensures data arrives current, traceable to its source and ready to use.</p> <p>This is a largely technical PM role with significant ownership over a platform and admin experience that are still taking shape. You decide what gets built and in what order, working closely with engineers and other product teams to turn provider APIs and data models into scalable integrations and features that support analysts’ investigations. You’ll read API documentation, map provider data to OIP’s data model and write clear, actionable specs that engineers can build from.</p> <h3>What you'll do</h3> <ul> <li><strong>Own the provider roadmap.</strong> We add a source when it answers a question analysts can’t answer today, so you start from the analyst’s problem, not from a provider’s name. You talk regularly with analysts, admins and solutions engineers in law enforcement and defense, and with the upstream teams whose features bring integration requests. You decide which providers come next and what “done” means for each.</li> <li><strong>Write the technical specs.</strong> Cover authentication, pagination, rate limits and quotas, incremental sync, deduplication, field mapping, and how failures surface. Every object must carry its provider, fetch time and source URL from the moment it is fetched. Our platform runs as SaaS and on-prem, so you also decide how each source behaves in each distribution.</li> <li><strong>Own the connectors as a product.</strong> That covers the contract between connectors and the platform, versioning, and how quickly a new provider goes from evaluation to production. Every connector should make the next one cheaper. Where another team can reach a public source on its own, you give it a safe way to do so instead of putting it in our queue.</li> <li><strong>Own the admin interfaces.</strong> That means creating a connection, managing credentials, scheduling, health and status, logs, quota usage and per