Head of Product

Impruvon•Baltimore, MD

1d•$183,000 - $225,000•Remote

About The Position

Impruvon builds software and connected hardware that makes medication management safer for vulnerable populations in group homes, supported living, assisted living, behavioral health, and long-term care. In these settings, a large share of medication administration is handled by non-clinical staff working from paper, spreadsheets, and memory. Our platform combines eMAR+ software, Smart Medboxes, emergency kits, and gamified self-medication tools into one connected system that prevents errors before they happen rather than documenting them after. We support providers, state agencies, and pharmacy partners across 20+ states, and we recently won the first statewide medication management contract of its kind in the United States. We are looking for a Head of Product to own product strategy and execution at Impruvon and to build the Product function from the ground up. You will lead a team of two today, a Product Lead and a Product Specialist, with plans to grow. We are a growing startup, and this function is being built rather than maintained. You will have real ownership, very little inherited process, and a direct line to the CEO and senior leadership. Product has been driven by our leadership team to date, and we are committed to a deliberate, unhurried handoff of that ownership to you, including knowledge transfer, context on customers and commitments, and hands-on support while you take the reins. You will not be handed a backlog and left to guess. We are building toward empowered product teams, where leadership sets priorities and outcomes and teams have real autonomy to discover how to achieve them. You and our engineering leadership will define how Product and Engineering work together. Our engineers are product-minded and deeply involved in how the product takes shape, and we are intentionally not prescribing a rigid handoff model. Our product operates in a regulated, high-stakes environment. A missed dose is a patient safety event, not a support ticket, and our customers are audited by state agencies whose requirements differ state by state. Product judgment here means understanding what actually happens in a group home at 7am during a shift change, not what looks good in a spec.

Requirements

8+ years in product management, including end-to-end ownership of a roadmap covering discovery, definition, and delivery, not solely execution of a roadmap someone else set
Experience leading product people, including hiring and onboarding rather than only managing an inherited team
A track record of shipping B2B SaaS in close partnership with Engineering
Experience building product process where little or none existed
Strong discovery skills: customer interviewing, problem validation, prototyping, and experimentation, with examples of how evidence changed your approach
Experience with products where the buyer and the user are different people. Our contracts are signed by provider executives and state agencies, and the software is used by non-clinical caregivers mid-shift
Practical, frequent use of LLMs in your day-to-day work
Comfort working with data directly, strong written communication, and the judgment to decide with incomplete information and own the outcome
Willingness to travel occasionally, up to roughly 15%, for customer and facility site visits, team meetings, and industry events

Nice To Haves

Experience in healthcare technology, IDD services, assisted living, behavioral health, long-term care, or medication management, or another regulated environment where safety and compliance shape product decisions
Experience with enterprise, government, or state agency customers, including procurement and reporting requirements
Experience shipping products that combine software and connected hardware
Experience with integration-dependent products (HL7, JSON, REST APIs, pharmacy management systems, EHRs)
Experience scaling a Product function from a small team, or shipping products and internal tools you personally prototyped using AI-assisted development

Responsibilities

Own the roadmap: Own product strategy and the roadmap across our full surface area: software, connected hardware, and pharmacy and EHR integrations. Publish it so the company can see what is coming and why
Bring a point of view on where the platform should go over the next 12 to 24 months, and make the case for it
Weigh patient safety, HIPAA, and state-by-state regulatory requirements from the start rather than retrofitting them. In our environment, "ship it and iterate" is not always available
Treat reporting, audit trails, and business intelligence as first-class product. Audit-ready documentation is one of the main reasons customers choose us
Lead discovery: Spend real time with caregivers, house managers, administrators, nurses, and state agency stakeholders, and observe workflows rather than consuming feedback secondhand
Distinguish recurring needs from individual feature requests, and explain the difference to Sales and Customer Success
Design for three very different users: administrators who need oversight and audit readiness, caregivers who need speed and clarity mid-shift, and the individuals receiving care, some of whom are building medication independence for the first time
Design into existing routines rather than around them. Our customers cannot absorb a system that reshapes how a shift runs, and for non-clinical staff on shared devices, usability is a safety requirement rather than a preference
Set the bar for product definition: clear problem statements, acceptance criteria, and edge-case thinking Engineering can build from without guesswork. Define success measures before work starts, and measure what actually happened after release
Build the function: Establish how product gets practiced here: how problems get framed, how discovery happens, how decisions get made, and how outcomes get measured
Lead, coach, and develop the Product team, and hire as scope expands, including roles that do not exist yet
Keep Engineering, Customer Success, Sales, and Operations aligned on priorities and what is changing, and support them on strategic accounts and state-level opportunities where product credibility matters
Work with AI: We expect our product leader to set the standard on AI rather than delegate it. Use tools such as Claude Code, Codex, or equivalent agentic development environments to explore the codebase, work with data, and build functional prototypes rather than relying only on mockups and specs. Establish these practices across the Product team and coach your people into them. The goal is better-informed decisions about scope and value, not handing engineering a flashy prototype to productionize. You do not need to be a software engineer, and you will have strong engineering partnership for that. You do need to be willing and able to build.