Senior Technical Product Manager

ComPsych Corporation•,

1d•$130,000 - $180,000•Remote

About The Position

Every risk flag, utilization report, and recommendation our clients and internal teams rely on starts as a row of data somewhere in our systems. As ComPsych's services become digital products, our ability to turn health, wellbeing, and absence data into something trustworthy, governed, and easy to build on matters as much as any feature we ship. We're building that foundation on Databricks — a modern data platform that turns operational and behavioral health data into reusable data products. Increasingly, that data is also a product in its own right: an API offering that internal teams, digital products, and external clients and partners can build on directly. We're looking for a Senior Technical Product Manager to own that platform end to end, including the API layer as something we productize and stand behind — with real documentation, real SLAs, and real accountability to the people building on it, inside and outside the company. This role sits at the intersection of data engineering, product, compliance, and go-to-market. You'll go deep enough with Data Engineering to make good calls on schema, lineage, and pipeline tradeoffs, and just as deep with Sales, Legal, and Security on what an external client or partner can access, under what agreement, and why. Given the sensitivity of the data involved, judgment about who sees what — especially when it includes parties outside ComPsych — is as central to this job as the roadmap itself. You'll report to the Director of Platform Product Strategy, working alongside the broader platform team to shape where the data platform goes next.

Requirements

6+ years in product management, with meaningful time specifically owning data platform, data infrastructure, or API products — not just consuming data as an input to a feature roadmap.
Direct experience with a modern data warehouse or lakehouse (Databricks strongly preferred; deep experience with Snowflake, BigQuery, or similar will be considered).
Experience shipping an API as an external-facing product, not just an internal integration layer — including documentation, developer onboarding, versioning, and support for outside consumers.
Comfort operating at both altitudes: you can read a pipeline or architecture diagram with Data Engineering and write a crisp product brief on the same feature for a business or client stakeholder.
Real fluency in data governance: data quality, lineage, access control, and schema management, with sound judgment about tradeoffs involving sensitive or regulated data — including what changes when that data leaves the company.
A track record of bridging technical, compliance, and go-to-market teams — translating platform capability into terms Sales, Legal, or clients can act on, and vice versa.
Consistent and reliable high-speed internet and workspace free from distraction, disruption, or noise is required
Ability to be present on camera during work-related trainings, meetings, and/or events
Must be able to sit or stand at a desk for prolonged periods while working on a computer

Nice To Haves

Bonus: experience with healthcare, insurance, or another regulated, sensitive-data industry, particularly around external data-sharing agreements.
Bonus: experience partnering with third-party data or BI vendors (e.g., integrating or building on top of platforms like Qlik, Tableau, or Power BI) to extend what your platform can offer.

Responsibilities

Own the product strategy and roadmap for our Databricks-based data platform and its API layer — treating both as products with real consumers, not just infrastructure.
Define data products, not just data sets. Decide what a “product” looks like for a given dataset — its schema, its quality bar, its documentation, its intended consumers — so teams building on it don't have to guess.
Productize the API layer for internal and external consumers. Decide what data becomes an API, who it's for (internal teams, client integrations, partners), what access tiers and SLAs it needs, and how it's versioned, documented, and supported over time.
Own the external developer experience. Documentation, sandbox environments, onboarding, and support for the clients and partners building on our APIs — their experience is now part of ComPsych's product.
Shape how external access is packaged and governed. Work with Sales, Legal, and Security to define what data external parties can access, under what data-sharing agreements, and at what tier or cost, balancing commercial opportunity against the sensitivity of the underlying data.
Partner deeply with Data Engineering and Architecture. Be fluent enough in ingestion, transformation, storage, and compute tradeoffs on Databricks to make real product decisions — not just relay requirements.
Own governance and access tradeoffs for sensitive data, internally and externally. Behavioral health and absence data carries real weight. You'll set and defend policies for who can see what, at what level of detail, and under what agreement — a materially harder problem once “who” extends beyond ComPsych.
Use AI to move faster on your own workflow — exploring schemas, drafting documentation, surfacing data-quality issues worth investigating — and apply your own judgment to what it produces before it ships or informs a policy decision.
Perform other duties as assigned.