Product Manager, Intelligence

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. The posting includes: - Intro about Heidi (company description). That could be "About the role"? Actually "About the role" is a heading for description of role. The intro about company could be placed under "About the role" maybe? But we need to follow instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections with those headings only if there is content. We need to extract content for each. Let's parse: Company description: "We’re Heidi. We're building the future of healthcare by giving every clinician the earth's finest AI Care Partner. Our platform has absorbed the administrative chaos of 175 million patient visits and supported 67 million clinical hours. Today, we support 2.8 million patient sessions a week across 190+ countries, in 110 languages and over 200 specialties. Healthcare systems are failing us; clinicians spend more time on documentation than on patients, and the human connection that makes medicine worth practicing is eroding. Our mission is simple: double the world’s capacity for care and strengthen the human connection at its heart. We found product-market fit with a freemium medical scribe that clinicians love. Now, we're expanding. Every task a clinician hands to Heidi is a patient who feels more attended to, a health system unclogged, and a clinician who gets to be a clinician again. We’ve grown annual recurring revenue from $1 million to $50 million in two years. To go further, we’ve secured US$340 million: a $100 million Series C led by Blackbird, with Phoenix Court, Point72 Private Investments and Headline, alongside a $240 million growth investment led by General Catalyst’s Customer Value Fund. If you want to join us in doing work worth shipping, jump in." That's company overview. Could go under "About the role" maybe? Usually "About the role" describes the role itself, not company. But we can put company description there as it's about the role context. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include About the role with company description and role overview. Then "The role We’re looking for a Product Manager to build the next generation of clinical intelligence at Heidi. Millions of clinical sessions per week generate an extraordinary volume of structured health data. Your job is to turn that into products that help clinicians, health systems, and Heidi itself make better decisions. This role blends structured data products, AI-native experiences, and exploratory product discovery. You will own how clinicians and organisations interact with their clinical data: analytics, reporting, operational insights, and the intelligent surfaces that make Heidi more valuable the more it’s used. When a clinic understands its referral patterns, when a health system sees adoption across departments, when an AI model gets smarter because the data underneath it improved: that’s your work. This role will be based in either our Sydney or Melbourne office. We don’t care about logos; the traditional insignia of competence. We’ll evaluate senior well-credentialed candidates and young, hungry hopefuls alike." That's role description; could be part of About the role or Responsibilities. Usually About the role includes overview; Responsibilities list duties. We'll split: About the role: company overview + role overview (maybe first paragraph). Responsibilities: bullet list of duties from "What you’ll do". Let's extract. "What you’ll do" list: - Own product strategy and roadmap for Heidi’s intelligence products, setting clear goals and being held accountable to achieving them - Build intelligent experiences that help clinicians and health systems unlock deeper understanding from their clinical data - Own reporting, analytics, and insight surfaces that make Heidi more valuable the longer a customer uses it - Scope and ship AI-native features that turn clinical data into proactive insights and decision tools - Match deep customer understanding with business goals to deliver products that drive retention and expansion - Prioritise across new intelligence capabilities, data quality, and the infrastructure that supports them - Work with AI and product teams so intelligence products stay ahead of what the underlying models can do - Work with engineering on architecture trade-offs at a technical level - Spot patterns that multiple teams are solving separately and consolidate them That's responsibilities. Next "What you’ll need" list: - BA/BS in a technical or analytical field (e.g. Computer Science, Engineering, Information Systems, Analytics, Mathematics, Physics, Applied Sciences, or related) - 4+ years in product, infrastructure, or technical roles, though we care more about what you’ve built than time served - A romantic streak about software and a belief that great design transforms someone’s day - Technical enough to hold your own with engineers, credible enough to present infrastructure trade-offs to leadership - Genuine curiosity about what breaks when software moves from development to production at scale - Experience in data products or platforms (metrics layers, data APIs, semantic modelling) is a genuine advantage, though the right person can learn the domain - You build with AI tools (Cursor, Claude Code, whatever ships faster) and can show what you’ve made with them - Fluency with core LLM concepts and systems (prompting, fine-tuning, embeddings, retrieval, evaluation) and the judgment to translate these into reliable, user-facing products - You default to building over requesting - Strong opinions, weakly held; you’ll shift the room when you’re right - Data fluency with diagnostic teeth; you can read usage data and distinguish a product problem from a data quality problem from a customer-specific issue Then there is a set of questions: "If you answer ‘NO’ to these questions, this may not be the job for you: Are you an execution powerhouse? Have you shipped something this week? Are you good at games? Did you have a weird teenage hobby? Are you able to execute without a legion of data analysts, product marketers, and research coordinators at your beck and call? Does the prospect of making health systems a lot nicer make you feel fuzzy inside?" This could be considered part of Requirements or maybe Qualifications? It's more like cultural fit. Could be placed under Requirements or maybe Qualifications. We'll treat as part of Requirements (maybe under "Requirements"). Then "How we show up" section: values etc. Could be omitted as boilerplate? It's not exactly boilerplate but it's cultural. Might be considered not needed for sections; but we could include under "About the role" maybe? However instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's more about culture. Might be okay to keep but we need to decide if we need a section for it. Not listed as a heading; we could incorporate into About the role or maybe not include as separate section. Safer to omit because not requested headings. Then "Why Heidi?" section: benefits etc. This includes benefits details. So we need Benefits section. Benefits list: "We offer healthcare, dental and vision benefits, a 401k with 3% company match, a $700 annual learning and development budget, a $100/month health and wellness allowance, a $500 home office budget, 26 weeks paid primary parental leave and 18 weeks paid secondary parental leave, fertility support up to $7,000, four weeks of work from anywhere per year, and serious equity. We chose to open-source our benefits hub, if you care to take a peek." Also earlier: "We operate on outcomes > inputs, not process theatre. We all take the bins out, metaphorically and literally. We take care of you." That's fluff. Pay and Schedule: Not mentioned explicitly. No pay or schedule details. So we should NOT create Pay or Schedule sections because they are not stated. Qualifications: Could be separate from Requirements? Usually Qualifications includes education and experience. Requirements includes skills etc. But we can combine. The instruction says use headings for those categories if content exists. We have content for Requirements (skills, experience, etc.) and Qualifications (education). We could split: Qualifications: BA/BS in technical or analytical field; 4+ years experience. Requirements: the rest (romantic streak, technical enough, curiosity, data products experience, AI tools, LLM fluency, building over requesting, strong opinions, data fluency). Also the questions could be under Requirements. Skills: Could be separate but we may not need if we already have Requirements. However we could put technical skills under Skills. But we have many skill-like items. Might be better to have Skills section for technical skills: fluency with LLM concepts, AI tools, data products, etc. But we already have them in Requirements. To avoid duplication, we can follow typical pattern: Qualifications (education/experience), Requirements (skills and abilities). But we have many items that are both. Let's decide: We'll create: - About the role (company + role overview) - Responsibilities (list of duties) - Qualifications (education + years experience) - Requirements (skills, traits, etc.) - Benefits (list) We will not include Skills separately because it's covered in Requirements. But the instruction gave Skills as an example heading; we can omit if not needed. Now we need to format as HTML fragment: use

for each heading, then content: either

for prose,

• for lists. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all points from the lists. Let's extract exact phrasing. About the role: combine company description and role overview. Company description paragraph: "We’re Heidi. We're building the future of healthcare by giving every clinician the earth's finest AI Care Partner. Our platform has absorbed the administrative chaos of 175 million patient visits and supported 67 million clinical hours. Today, we support 2.8 million patient sessions a week across 190+ countries, in 110 languages and over 200 specialties. Healthcare systems are failing us; clinicians spend more time on documentation than on patients, and the human connection that makes medicine worth practicing is eroding. Our mission is simple: double the world’s capacity for care and strengthen the human connection at its heart. We found product-market fit with a freemium medical scribe that clinicians love. Now, we're expanding. Every task a clinician hands to Heidi is a patient who feels more attended to, a health system unclogged, and a clinician who gets to be a clinician again. We’ve grown annual recurring revenue from $1 million to $50 million in two years. To go further, we’ve secured US$340 million: a $100 million Series C led by Blackbird, with Phoenix Court, Point72 Private Investments and Headline, alongside a $240 million growth investment led by General Catalyst’s Customer Value Fund. If you want to join us in doing work worth shipping, jump in." Then role overview: "We’re looking for a Product Manager to build the next generation of clinical intelligence at Heidi. Millions of clinical sessions per week generate an extraordinary volume of structured health data. Your job is to turn that into products that help clinicians, health systems, and Heidi itself make better decisions. This role blends structured data products, AI-native experiences, and exploratory product discovery. You will own how clinicians and organisations interact with their clinical data: analytics, reporting, operational insights, and the intelligent surfaces that make Heidi more valuable the more it’s used. When a clinic understands its referral patterns, when a health system sees adoption across departments, when an AI model gets smarter because the data underneath it improved: that’s your work. This role will be based in either our Sydney or Melbourne office. We don