Senior Product Counsel

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No filler. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, navigation, etc. We need to parse the posting. Title: Senior Product Counsel - Healthcare (we ignore as heading). Team: Legal, Location: Remote. We have sections: Why This Role Exists (intro) - could be About the role. What You’ll Spend Your Time Doing - responsibilities. What Makes You a Great Fit - qualifications/skills? Could be Requirements/Qualifications/Skills. We Do Have A Few Requirements To Check - list of requirements: Bachelor's degree required; JD from a top-tier law school; 8+ years healthcare regulatory experience across top-tier law firm and in-house companies, preferably high-growth; Licensed to practice law in your state of residence; Substantial product counseling experience including advising product teams on regulated products, from concept through launch. Where You’ll Work - remote role. Compensation & Rewards - Base Salary: $240,000-280,000 USD inclusive of base salary and variable incentive. A comprehensive Total Rewards package designed to support your whole life — not just your work. Who We Are - company description. Top-rated Employee Benefits - list of benefits. We need to decide sections: About the role (intro), Responsibilities (What You’ll Spend Your Time Doing), Requirements (We Do Have A Few Requirements To Check), Qualifications (maybe combine with Requirements? but we can separate: Qualifications could be education and experience? But we have both. Could put Qualifications for education (Bachelor's, JD) and Requirements for experience? However guidelines: Use sections only when posting has real specific content. We can have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Skills maybe not separate if covered. We need to avoid filler like "commensurate with experience". Not present. We need to include Pay section only if posting actually states them. Yes base salary range given. So Pay section. Schedule: Not mentioned besides remote; no schedule specifics. So omit Schedule. Benefits: Yes list of benefits. We need to include About the role: maybe combine Why This Role Exists and Who We Are? But About the role should be description of role purpose. Use Why This Role Exists paragraph. Responsibilities: What You’ll Spend Your Time Doing bullet list. Requirements: maybe the list under "We Do Have A Few Requirements To Check". Could be Requirements. Qualifications: Could be education: Bachelor's degree required; JD from a top-tier law school. Also maybe "Licensed to practice law in your state of residence". That's a qualification. Could put under Qualifications. Skills: maybe "Learn new areas of law quickly", "creative problem-solver", etc. That's from What Makes You a Great Fit. Could be Skills. But we must not create thin sections. Let's see content: What Makes You a Great Fit: bullet list of attributes. That's substantive. Could be Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Check each for real content. About the role: "Why This Role Exists" paragraph: "Phreesia is looking for a Senior Product Counsel - Healthcare to join our Legal team. In this role, you'll be the legal partner our product teams come to first, the person who understands how our products actually work and what's possible within the regulatory environment they operate in. Healthcare regulation and privacy are the center of gravity for this work, and you'll own our approach to both. But our products increasingly touch payments, financial services, communications, and other regulated domains, so we need someone who can get up to speed on an unfamiliar area of law quickly, form a defensible view, and give product teams a clear answer. You’ll tackle complex healthcare regulatory and privacy issues, translate their meaning and implications for teams across the organization, and provide practical guidance that enables the business to execute effectively while navigating legal and regulatory requirements." That's good. Responsibilities: "What You’ll Spend Your Time Doing" list: bullet points: - Be our healthcare regulatory expert. Provide cutting-edge legal analysis and ideas for navigating the complex U.S. regulatory environment for health technology, including HIPAA, state general and consumer health privacy laws, the Anti-Kickback Statute, OIG Medicare and Medicaid regulations, PhRMA codes, TCPA, CAN-SPAM, accessibility, card processing and payments regulations, and other relevant areas of law. - Partner closely with Product. Develop a deep understanding of Phreesia’s business and how each product works, and advise teams on what is feasible within the regulatory environment. - Get smart fast on new regulated domains. As our products evolve, so does the law that applies to them. You'll build working expertise in adjacent areas including payments and card processing and financial services regulation. - Turn regulatory complexity into actionable guidance. Partner with executive, product, engineering, marketing, and sales teams to build a clear understanding of potential regulatory requirements and identify effective approaches to execution. - Build processes that help teams move effectively. Develop processes that enable teams across the organization to execute based on your guidance in ways that make us faster and more efficient. - Protect patient data. Partner closely with our Chief Privacy Officer to ensure we never jeopardize patient data. - Strengthen the Legal team. Contribute to improving the Legal team and support your Legal team colleagues in doing their best work. That's good. Requirements: "We Do Have A Few Requirements To Check": list: - Bachelor’s degree required; JD from a top-tier law school - 8+ years of healthcare regulatory experience across a combination of a top-tier law firm and in-house companies, preferably high-growth organizations - Licensed to practice law in your state of residence - Substantial product counseling experience including advising product teams on regulated products, from concept through launch We could split education vs experience. But we have Qualifications for education and maybe license. Requirements for experience. Let's decide. Qualifications: Bachelor’s degree required; JD from a top-tier law school; Licensed to practice law in your state of residence. Requirements: 8+ years of healthcare regulatory experience across a combination of a top-tier law firm and in-house companies, preferably high-growth organizations; Substantial product counseling experience including advising product teams on regulated products, from concept through launch. Skills: What Makes You a Great Fit bullet list: - Have significant experience advising product and engineering teams on how to build and ship in a heavily regulated environment - Learn new areas of law quickly and enjoy it, you can go from unfamiliar statute to practical, defensible guidance faster than most - Are a creative problem-solver who is comfortable with ambiguity, complexity, and nuance - Bring excellent legal and business judgment and can balance legal risk with business and commercial considerations - Translate complex legal issues and risks into clear, understandable concepts that colleagues with non-legal backgrounds can act on - Look for safe ways to say “yes” when navigating complex legal risk situations - Are comfortable engaging in healthy dialogue around risk and having your assumptions challenged by internal product owners or outside counsel - Take pride in enabling the best work of others, anticipate your teammates’ needs, and provide the facts others need to make decisions - Are driven to be a great partner and build long-lasting relationships with the people you work with - Can work both fast and right, understanding when precision and accuracy are essential and when an 80% solution achieves the desired outcome - Thrive on being pushed and challenged and communicate effectively both in writing and live, including when navigating tough questions in the moment - Operate like an owner, take personal responsibility, and value personal responsibility in others - Are focused on finding the right answer rather than always having the right answer - Take your work, but not yourself, seriously - Have a demonstrated ability to operate effectively in a remote environment That's a lot but it's substantive. Benefits: Top-rated Employee Benefits list: - 100% Remote work + home office expense reimbursements - Competitive compensation - Flexible PTO + 8 company holidays - Monthly reimbursement for cell phone + internet + wellness - 100% Paid 12-week parental leave to our U.S. employees, as well as a generous parental benefit to our employees in Canada - Variety of insurance coverage for people (and pets!) - Continuing education and professional certification reimbursement - Opportunity to join an Employee Resource Group. Learn more here: https://www.phreesia.com/workforce/ We should include that as Benefits. Pay: Base Salary: $240,000-280,000 USD inclusive of base salary and variable incentive. A comprehensive Total Rewards package designed to support your whole life — not just your work. We could combine with Benefits but Pay separate. We must not include fluff like "We strive to provide a diverse and inclusive environment and are an equal opportunity employer." That's boilerplate EEO; remove. Also remove "Who We Are" maybe not needed as section; but could be About the role? Already have About the role. Could incorporate company description into About the role? But we already have About the role from Why This Role Exists. Could add a brief company description as part of About the role? Might be okay but not required. The instruction: Prefer a few substantive sections over many thin ones. Could merge Who We Are into About the role? But we already have About the role content; adding more may be okay but not necessary. However we must preserve ALL substantive information; we cannot omit company description if it's substantive. The "Who We Are" paragraph describes mission, SaaS platform, awards, etc. That's substantive about company. Should we include it? Could be part of About the role or a separate section like "About the Company". But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the Company". So we need to fit company info somewhere. Could add to About the role section after the role description. That would still be About the role but includes company info. That's acceptable. Thus About the role will contain both Why This Role Exists and Who We Are combined. We must not repeat job title as heading. Already not. We must not include Job ID etc. Not present. We must not include duplicated lines. Ensure no duplicate. Now produce HTML fragment:

About the role

... combined text ...

Responsibilities

• ... each bullet ...

Requirements

• ... each bullet ...

Qualifications

• ... each bullet ...

Skills

• ... each bullet ...

Benefits

• ... each bullet ...

Pay

Base Salary: $240,000-280,000 USD inclusive of base salary and variable incentive. A comprehensive Total Rewards package designed to support your whole life — not just your work.

Check that we didn't include Schedule. Now ensure we didn't include any boilerplate like EEO. Remove. Now craft the combined About the role text. Combine: "Why This Role Exists" paragraph plus "Who We Are" paragraph. Let's write: Phreesia is looking for a Senior Product Counsel - Healthcare to join our Legal team. In this role, you'll be the legal partner our product teams come to first, the person who understands how our products actually work and what's possible within the regulatory environment they operate in. Healthcare regulation and privacy are the center of gravity for this work, and you'll own our approach to both. But our products increasingly touch payments, financial services, communications, and other regulated domains, so we need someone who can get up to speed on an unfamiliar area of law quickly, form a defensible view, and give product teams a