Product Manager, Integrations

As Hi Rasmus grows, our customers increasingly operate within an ecosystem of systems alongside ours — EHRs, practice management platforms, payer systems, data platforms, and tools we haven’t met yet.

Those systems need to work together.

A broken or poorly designed integration isn’t simply a technical problem. It can create duplicate work, unreliable data, disconnected workflows, frustrated clinicians and operations teams, and less confidence in the systems people depend on every day.

But building great integrations requires more than connecting two systems.

Someone needs to understand how the work actually happens: what information needs to move, who depends on it, which system owns what, where workflows break down, and which problems are important enough to solve.

That’s where you come in.

📍 Location: Fully remote - US

💼 Department: Product

🤝 Reports to: Product Leadership

⏳ Job Type: Full-time, Exempt

💰 Compensation: Range of $90,000 to $115,000 annually

🕜 Working Hours: Flexible within US time zones. Because this role partners closely with our Denmark-based team, some morning overlap with European hours matters most—Eastern Time works seamlessly, and Pacific or other time zones work well for those able to start their day a bit earlier.

As our Product Manager, Integrations, you’ll own a product area that sits at the intersection of customers, partners, operations, data, and Engineering.

You’ll become deeply curious about how ABA organizations operate and how Hi Rasmus fits into their broader technology ecosystem. You’ll work directly with customers and integration partners, get underneath their requests to understand the actual workflow problems they’re trying to solve, and help determine where Hi Rasmus should invest.

You’ll also partner deeply with Engineering.

On this team, technical discovery may often be engineering-led — and that’s a good thing. Your job isn’t to tell engineers how to build an integration. Your job is to bring the customer, partner, operational, product, and business context that helps the team decide what problems are worth solving and why.

This isn’t a requirements-handoff role.

You don’t need to be an engineer, but you should be technically curious and fluent enough to ask good questions, understand tradeoffs, build credibility with technical partners, and connect what’s happening between systems back to the people and workflows depending on them.

Your goal is deceptively simple: