Product Operations Manager

We're Scan.com . We're building America's national imaging network: the infrastructure that connects patients, providers, and payers to faster, better-value diagnostic imaging. Thousands of patients move through our platform every day, and each is a real person waiting for an answer to a healthcare concern. We exist to get them that answer faster.

We manage the medical imaging pathway end-to-end. Providers order through a single point of entry, and from there, we run the entire medical diagnostic pathway. Managing the full pathway, rather than brokering pieces of it, is what lets us deliver imaging faster, at higher quality, and at a lower cost than the fragmented status quo.

We're looking for a Product Operations Manager at an exciting time. We've raised over $200m in funding to date, reached profitability, and are growing 100% year on year.

Millions of people wait too long for a diagnosis. Come help us fix that.

WHAT YOU WILL BE GETTING INVOLVED IN

Product Operations sits between strategy and execution. It is the function that turns a product team's intent into repeatable delivery and turns delivery into learning. At Scan.com , that work spans the full product surface, from acquisition and integrations to fulfillment and post-scan experiences, and it touches almost every function in the company.

As Product Operations Manager, you will partner closely with our product management team to build the rituals, documentation, and reporting infrastructure that make our product org run well. Your success will not be measured by how much you personally ship, but by how much better the teams around you ship because of the systems you put in place.

This role will suit someone who takes real pride in the craft of operations: someone who finds a well-written playbook satisfying, who can hold the details of five workstreams at once without losing context, and who already uses AI as a core part of their operational practice.

As a scale-up business, you can expect your role to develop over time. Here are some of the types of things you could be getting involved in:

Design and coordinate rollout plans for new product features, working with PMs, Engineering, Design, and Operations to sequence launches, manage dependencies, and ensure the right teams are prepared to support what ships

Create and maintain product documentation that supports both internal training and external communication, including feature briefs for internal enablement, release notes for partners and providers, and reference materials that keep stakeholders informed as the product evolves

Partner with the data team to monitor post-release analytics, helping the product team understand whether launches are landing as intended and surfacing signals that suggest a feature needs iteration, promotion, or reconsideration

Coordinate cross-functional sign-off for feature launches, ensuring the appropriate leaders across Engineering, Operations, Legal, and Clinical have reviewed and approved before release, with clear documentation of decisions and open items

Build and maintain a product knowledge base that is structured for AI agent consumption from day one, including designing information architecture that supports reliable retrieval, writing content that survives being chunked and re-assembled, and iterating on quality based on how well downstream agents perform against it

Support the product team on OKR planning and monitoring: helping to translate strategy into measurable objectives, tracking progress against them, flagging when priorities may need to shift, and reporting product impact to the wider organization in a way that builds shared understanding

THE TOP 5 THINGS WE WANT TO SEE IN YOUR FIRST YEAR

A more predictable release rhythm. By the end of your first quarter, we would expect the product team to have a clearer, more repeatable cadence for rolling out features. Sign-offs happen at the right stage, the right people are informed, and launches feel less improvised.

A knowledge base that powers AI workflows. The documentation you produce is trusted by both humans and agents. Teams reference it before asking questions, and it already serves as the knowledge base for at least one AI-assisted workflow that meaningfully reduces manual effort within the product org.

A closer connection between launches and outcomes. In partnership with the data team, you will have helped establish a practice of reviewing post-release analytics for meaningful launches, so the product team consistently learns from what it ships rather than moving straight to the next thing.

OKR reporting that informs decisions. The wider organization has a clearer view of what the product team is working on, why, and how it is progressing. Reporting is timely and useful, and it supports genuine prioritization conversations.

Trusted operator across the product org. Product managers rely on you to keep the machinery running, and cross-functional stakeholders trust the process you have built around launches and communication. Where things were previously ad hoc, they now feel intentional.

WHAT YOU MIGHT BRING TO THE TABLE

You don't need to tick all the boxes to apply for this role. Whether it's your first role or your fifth, we believe everyone can add value, learn, and grow. However, these might be some of the ways you are currently adding value:

Experience in product operations, program management, or a related operational role within a technology company, ideally one where you saw both the messy early stages and the transition toward more structured delivery

A genuine talent for written communication, including the patience to produce documentation that other people find clear, complete, and worth returning to. This role produces a lot of writing, and quality matters

Comfort working with product and delivery metrics: you can partner with a data team to define what success looks like, interpret the results honestly, and communicate the story to stakeholders without either overstating or burying the findings

Strong coordination instincts across multiple stakeholders. You are the kind of person who notices when a sign-off is missing, when a launch dependency is drifting, or when a team needs a nudge, and you handle it without needing to be asked

A collaborative disposition. Product operations depend on influence rather than authority, and you are comfortable working across PM, Engineering, Design, Operations, and Clinical stakeholders in a way that builds trust rather than friction

Genuine AI fluency in your operational practice. You use AI tools daily, you have opinions about which ones work well for which tasks, and you have first-hand experience structuring information so that AI agents can consume it reliably. You can speak concretely about specific workflows you have improved with AI, and, ideally, about evaluation approaches you have used to assess output quality. Candidates who treat AI as an occasional aid rather than a core part of how they work will not be competitive for this role.

Prior experience in healthcare technology, medical imaging, or an adjacent regulated space is a plus, though strong operational fundamentals in another high-velocity domain are equally valued

AI REQUIREMENTS

At Scan.com , AI isn't a side project; it's how we work. We expect everyone to use AI to think faster, remove drudgery, and multiply their output. What we care about is judgment: knowing when AI makes you sharper, when it doesn't, and how to use it responsibly around patient data. We'll assess this in the way that matters for this role, using the tier below. You don't need to be an engineer. You need to be someone who reaches for the best tool and gets more done because of it.

Tier 1 — For this role, the expectation is that you are an AI-Native. You build with AI directly, shipping, automating, or prototyping real work with LLMs and agents, and have clear judgment on where huma