Technical Product Manager (Data Integrations)

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 Saa S 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.

Role

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.

What you'll do

• Own the provider roadmap.

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.

• Write the technical specs.

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 Saa S and on‑prem, so you also decide how each source behaves in each distribution.

• Own the connectors as a product.

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.

• Own the admin interfaces.

That means creating a connection, managing credentials, scheduling, health and status, logs, quota usage and permissions.

A source we can't monitor isn't delivered, so every live connection needs a health check and clear failure states.

• Work with partnerships and legal.

You collaborate with the Director of OSINT and the Data Acquisition Manager to evaluate vendors, raise licensing and terms‑of‑service questions before we build, and turn the legal framework (storage, retention, redistribution) into product requirements.

You also give the people negotiating contracts technical findings and cost per call.

• Manage the teams around you.

Upstream, you work with the teams building user‑facing features, such as graphs and maps, who bring integration requests from their intelligence domain.

You help them find the analyst question behind each request and decide whether a shared connector can serve several of them.

Downstream, you work with the foundation teams for ontology, machine learning and processing, so incoming data arrives in a shape they can use.

You forecast the load of every high‑volume source before it goes live.

• Shape person‑focused investigation tools.

You own how analysts go from a first lead about a person to a reviewed set of linked online identities.

That includes how results are presented and reviewed, and how to avoid paying for the same lookup twice.

• Measure the integration layer. Track sync success rate, data freshness, time to onboard a provider, active connections, and time to resolve a failed connection.

About you

• 5+ years as a Product Manager in B2B Saa S, with experience owning a technically complex area end‑to‑end, such as an integration platform, an API product, or data pipelines.
• You are comfortable in API documentation.

You can discuss OAuth versus API keys, polling versus webhooks, pagination and rate limits with engineers as an equal, and you can try an endpoint yourself in Postman or curl.

• You have designed admin or configuration interfaces for technical users: connection setup, status and error states, audit trails.
• You write specs and acceptance criteria that are specific enough to build and test against.
• You are data‑fluent and define quality metrics for reliability and coverage, not just feature delivery.
• You are comfortable with the legal side of third‑party data: licensing, terms of service, GDPR, and provenance requirements.
• You work well across teams, since integrations touch engineering