- Salary
- $90k – $115k/yr
- Location
- United States - Remote
- Workplace
- Remote
- Type
- Full-time
- Department
- IT
- Seniority
- Manager
- Source
- Pinpoint
Description
Product Manager, Integrations
Department: Product
Employment Type: Full Time
Location: United States - Remote
Compensation: $90,000 - $115,000 / year
Description
- Innovation 🧠 – We embrace creativity and seek better solutions.
- Integrity ⚖️ – Honesty and trust guide everything we do.
- Collaboration 🤝 – Together, we achieve more.
- Growth 🌱 – We’re committed to personal and professional development.
- Empathy ❤️ – We prioritize understanding and human connection.
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:
Make Hi Rasmus easy to integrate with — and dependable once you do.
🎯 What You’ll Help Make Possible
Create an integration experience where partners can connect to Hi Rasmus with confidence — without every new integration becoming a custom project.
How we’ll know it’s working:
- Partners can integrate predictably, with fewer preventable implementation issues and less ongoing intervention from Hi Rasmus.
- Existing integrations remain healthy as Hi Rasmus evolves.
- We increasingly solve recurring integration needs through scalable patterns and capabilities rather than one-off solutions.
Develop a deep understanding of how ABA organizations actually operate — and use that understanding to identify where integrations and data movement can remove friction, manual work, and disconnected workflows.
How we’ll know it’s working:
- Integration priorities are grounded in real customer workflows and clearly understood problems, not simply incoming requests.
- Manual reconciliation, duplicate work, and data inconsistencies decrease in the workflows we choose to support.
- Product and Engineering can clearly connect integration investments back to meaningful customer and operational outcomes.
Become the connective tissue between Engineering, external partners, Customer Success, Implementation, Commercial, and Product — helping Hi Rasmus make thoughtful prioritization decisions and setting our partners up for success.
How we’ll know it’s working:
- Partners have clear expectations around integration scope, capabilities, responsibilities, and changes.
- Engineering and customer-facing teams have the context they need to make good decisions without unnecessary handoffs or escalation.
- We can make hard prioritization decisions across customer demand, partner needs, technical complexity, reliability, and company priorities — and clearly explain why.
- Build a deep understanding of how ABA organizations operate and where technology, data, and workflows intersect.
- Spend time with enterprise operations teams, clinicians, Customer Success, Implementation, and other people close to the work.
- Get underneath integration requests to understand the underlying problem: What is the customer actually trying to accomplish? What happens today? Where does it break? Who feels the pain?
- Learn the Hi Rasmus platform and domain deeply enough to connect customer workflows to meaningful product opportunities.
- Build ongoing feedback loops so Product and Engineering stay close to how integrations perform in the real world.
- Build strong working relationships with external integration partners and the technical teams building alongside Hi Rasmus.
- Confidently lead conversations about operational workflows, product needs, constraints, expectations, and priorities while partnering with Engineering on deeper technical decisions.
- Help partners understand how Hi Rasmus works, what our integrations can support, and where boundaries or tradeoffs exist.
- Create a partner experience built on clarity, predictability, trust, and good communication.
- Help improve the documentation, onboarding, testing, support, and feedback mechanisms partners need to successfully integrate with us.
- Own the product problems, discovery, prioritization, product bets, roadmap, and outcomes within the Integrations charter.
- Turn recurring customer and partner needs into scalable capabilities rather than accumulating bespoke solutions.
- Balance new integration opportunities with the reliability and platform work necessary to keep existing integrations healthy.
- Define what success looks like before building — and stay with product bets after launch to understand adoption, reliability, customer value, and what we should do next.
- Help the organization make thoughtful tradeoffs between customer value, technical complexity, scalability, strategic importance, and effort.
- Explore where integrations and data delivery create enough customer value to support future packaging and monetization opportunities.
- Work with Engineering as one problem-solving team, not as Product writing requirements for Engineering to execute.
- Bring deep customer, partner, operational, commercial, and product context while Engineering brings deep technical and architectural expertise.
- Frame problems, intended outcomes, assumptions, constraints, and tradeoffs clearly enough that the team can shape solutions together.
- Participate meaningfully in technical conversations while knowing when Engineering should lead the technical decision.
- Partner on questions around data exchange, system dependencies, integration reliability, APIs, and technical tradeoffs without needing to design the architecture yourself.
- Use data, prototypes, AI, partner feedback, and experimentation to learn quickly before committing significant engineering investment.
- Partner with Customer Success and Implementation to understand where integrations create friction — and where scalable product capabilities can replace manual work.
- Help customer-facing teams understand what our integrations can and cannot do, how they should be positioned, and where expectations need to be set.
- Partner with Commercial teams to understand enterprise demand, emerging integration needs, and where data delivery creates meaningful customer value.
- Translate what we learn from partners and customers back into context the broader organization can use.
You’ll have meaningful ownership of the problems, discovery, product bets, prioritization, roadmap, and success measures within your charter.
You’ll work particularly closely with:
Engineering — to deeply understand problems and shape solutions together. Engineering owns technical architecture and implementation; Product brings deep customer, partner, operational, and business context. Neither solves the problem alone.
Customer Success + Implementation — to understand how customers actually work, where data movement creates friction, and where better integrations can eliminate manual effort. Ensuring that these teams also have a clear understanding as we release updates to our integrations.
Commercial — to understand enterprise demand, partner opportunities, and where integration and data capabilities create meaningful customer value.
External Partners — to understand their systems and workflows, build trust, navigate constraints, and create integration experiences that work for both sides.
Product Leadership + other PMs — to make hard prioritization decisions and ensure integration work supports the broader Hi Rasmus product strategy rather than becoming an isolated technical roadmap.
🌟 The Kind of Product Person We’re Looking For
You’re technically curious without needing to be the smartest engineer in the room.
You genuinely enjoy figuring out how systems and people fit together.
When someone says, “We just need an integration,” your instinct is to ask: Why?
What is the workflow today? What information needs to move? Which system owns what? Who depends on it? What happens when something goes wrong? And are we solving something once — or creating something that can solve the problem again and again?
You’re equally comfortable talking with an engineer about how systems interact and an operations leader about why two systems disagreeing is making someone’s Tuesday miserable. 🙂
You can walk into a complex domain you don’t yet understand, stay humble and curious, and become knowledgeable enough to make good product decisions.
You’re comfortable saying no, not yet, or there’s a better way to solve this — and can bring customers, partners, and internal teams along with you.
And you care about what happens after something ships.
Because when other people’s workflows and systems depend on ours, “it works” isn’t enough. It needs to keep working.
You likely bring:
- Product Management experience in B2B SaaS, platform products, healthcare technology, developer products, or another technically complex environment.
- Direct experience working with integrations, interoperability, data exchange, APIs, or other connected product ecosystems.
- Experience working directly with external technology partners, enterprise customers, developers, IT teams, or similarly complex stakeholders.
- Enough technical fluency to work credibly alongside engineers and integration partners — understanding APIs, data exchange, system dependencies, integration reliability, and technical tradeoffs without needing to be the engineer designing the solution.
- Strong product discovery and judgment — you know how to get underneath a request to understand the real customer or operational problem.
- Demonstrated ability to learn a complex operational domain quickly and deeply enough to make strong product decisions.
- Experience turning complex customer or partner needs into scalable product capabilities rather than accumulating bespoke solutions.
- Strong prioritization skills and comfort making decisions when customer value, technical complexity, partner needs, and business priorities compete.
- Clear, confident communication and the ability to build trust across technical and non-technical audiences.
- Experience with healthcare integrations, including EHR/EMR, payer, practice-management, or other healthcare technology ecosystems.
- Familiarity with healthcare interoperability standards or data exchange.
- Experience building developer-facing products, APIs, integration marketplaces, or data products.
- Experience with data-delivery or integration-based business models.
- Experience in ABA, behavioral health, or another complex healthcare environment.
Most importantly, you don’t need to arrive knowing ABA.
You do need to be the kind of person who will want to learn it — getting close enough to our customers, clinicians, operations teams, partners, and product to understand how the world actually works before deciding how technology should change it.
We’re building technology in a space where better products can give clinicians time back, make operations easier, improve access to care, and ultimately help more children and families.
You’ll have meaningful ownership, work alongside people who care deeply about the problems we’re solving, and help shape an area of the Hi Rasmus platform that will become increasingly important as we grow.
If you love untangling complex workflows, connecting systems and people, and turning messy problems into products people can depend on, we’d love to meet you.
💙 Perks & Benefits You'll Love
🏥 Health & Wellness:
- 100% covered health, dental, and vision premium for employee-only standard plan (Family can join too, with a variable cost)
- Employer Sponsored Short-Term Disability Coverage
- Employer Sponsored Life Insurance
- Optional group benefits: AD&D, long-term disability
- Participation in a 401k plan through Empower
🎓 Growth & Development:
- Professional development opportunities
- Room for growth within the company
🏖️ Time Off to Recharge:
- Paid Time Off: 10 vacation days, 5 sick days, 7 paid holidays + 3 floating holidays for ultimate flexibility
🐣 Parental Leave:
- All Parents/Caregivers: 6 weeks fully paid
- Birthing Parents: Up to 14 weeks paid
🏡 Work Style That Works for You:
- Fully remote and flexible work environment—work from wherever feels right!
- Opportunity to make a meaningful impact in the Autism healthcare space
Use our applicant tracking system Pinpoint to answer the role-specific application questions. These questions were thoughtfully designed to give you more insight into the role and to give us more insight into you. Please write a thoughtful response—a human really reads these.
If you need accommodations during the application process, just let us know—we’re happy to help. 😊
Skills
EMREHR