Head of Product

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have description about company, about the role, responsibilities, requirements, benefits & compensation. Also compensation details: base salary range. Also benefits list. No schedule info. So we can have sections: About the role (maybe combine description? The "About Impruvon" is company description; but we can treat as "About the role"? Actually we have "About The Role" heading. Also "Key Responsibilities". Also "Requirements Skills, Knowledge, & Experience". Also "Nice to Have". Also "Personal Attributes". Also "Benefits & Compensation". Also "Work with AI" maybe part of responsibilities? Could be separate but we can include under responsibilities. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. We have: - About the role: we have description about the role (the paragraph after "About The Role"). - Responsibilities: we have "Key Responsibilities" bullet list. - Requirements: we have "Skills, Knowledge, & Experience" list. - Qualifications: maybe not separate; we could combine with Requirements? But we have "Nice to Have" and "Personal Attributes". Could treat "Qualifications" as required qualifications? Might be redundant. Safer to include only sections with real content: About the role, Responsibilities, Requirements, Benefits, Pay (compensation). Also maybe "Skills" as separate? But we already have Requirements covering skills. Could split: Requirements (experience) and Skills (specific skills). However instruction says prefer few substantive sections over many thin ones. So we can combine. We have compensation: base salary range. Also benefits list. Thus sections:

About the role

... (the paragraph(s) describing role).

Responsibilities

• ... each bullet.

Requirements

• ... each bullet from Skills, Knowledge, & Experience.

Benefits

• ... each benefit.

Pay

Base salary of $183,000 to $225,000, depending on experience.

We should not repeat job title. Also we should not include metadata like Department, Location, Compensation as headings; we can incorporate location maybe in a short p? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Department and Location could be minor metadata; we could include a short p at top:

Department: Product • Location: Remote - USA

. But they said we can fold minor metadata into a short

or drop it. It's okay to include a short p. However they said output only HTML fragment; we can include that. We must preserve all substantive information; not invent or summarize away detail. So we need to include all bullet points from responsibilities, requirements, benefits, etc. Also include the "Work with AI" paragraph maybe as part of responsibilities? It's under a heading "Work with AI". Could be its own section but we don't have a standard heading for that; we could include under Responsibilities as an extra bullet. But better to keep as part of responsibilities: we can add a bullet about using AI tools. Also "What This Role Is Not" maybe not needed; it's descriptive but could be omitted? It's substantive but maybe not required; but we could include as a paragraph under About the role? Might be considered filler? It's describing what role is not; could be considered relevant. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that too. Could be a paragraph under About the role or a separate section "What this role is not". But we don't have a standard heading for that; we could incorporate into About the role as a note. Also "Nice to Have" and "Personal Attributes" are substantive. Should we include them? They are under Requirements heading? They are separate sections after Requirements. Could be included under Requirements as additional bullets labeled "Nice to Have" and "Personal Attributes". But we need to preserve detail. We could create subheadings? Not allowed; only

for section headings. Could we add

? Not allowed per instruction; only use

for section headings. So we cannot add other headings. We could embed them as paragraphs within Requirements section, maybe with bold text? But we cannot add arbitrary tags besides

,

• ,

  . We could use

  with strong? Not prohibited but maybe better to keep simple. Could we include them as list items under Requirements with a note? Might lose distinction but still preserve info. Could we create separate sections: Requirements, Nice to Have, Personal Attributes? But we only have allowed headings list; we could use "Requirements" for required, "Skills" for nice to have, "Qualifications" for personal attributes? Might be okay. But instruction: Prefer a few substantive sections over many thin ones. So maybe combine all into Requirements section with sub-bullets? But we cannot nest lists? We could have

  • Required: ...
  • Nice to have: ...

  . That preserves info. Thus:

  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 have: 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
  • Nice to have: Experience with enterprise, government, or state agency customers, including procurement and reporting requirements
  • Nice to have: Experience shipping products that combine software and connected hardware
  • Nice to have: Experience with integration-dependent products (HL7, JSON, REST APIs, pharmacy management systems, EHRs)
  • Nice to have: Experience scaling a Product function from a small team, or shipping products and internal tools you personally prototyped using AI-assisted development
  • Personal attributes: A builder. Your instinct when you have an idea is to make something and test it.
  • Personal attributes: Low ego and strong point of view. You advocate hard for a position and change it when the evidence changes.
  • Personal attributes: Comfortable with ambiguity. You do not need a detailed roadmap to know what to do next.
  • Personal attributes: Intellectually curious. You want to understand why a workflow works the way it does, not just what feature someone asked for.
  • Personal attributes: Energized by the mission. Many of the people affected by our product cannot advocate for themselves. Medication management failures are not abstract software problems here.
  We also need to include "Work with AI" expectation. Could add as a responsibility bullet. Responsibilities bullets from "Key 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. Also "What This Role Is Not" paragraph: could be added as a note under About the role or separate paragraph. We also have "About Impruvon" description and "Our Results So Far". That's company info; could be included under About the role? Actually About the role section should focus on role, but we could include company description as a short paragraph before About the role? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. The company description is substantive; we should preserve it. Could be a section "About the company" but not in allowed headings. Could we put it under About the role as a preamble? Might be okay. We could create a section "About the company" using

  ? Not in list but maybe allowed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could still use other headings? It says use

  for section headings (