Senior Product Counsel
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to output only HTML fragment, no /, no markdown fences.
We need to decide which sections to include. The posting includes:
- 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 Qualifications or Skills.
- We Do Have A Few Requirements To Check -> Requirements.
- Where You’ll Work -> maybe Schedule? Actually location remote, but schedule not given. Could be omitted if no schedule specifics.
- Compensation & Rewards -> Pay (and Benefits). They give base salary range and total rewards. So we can have Pay section with salary range, and Benefits section with benefits list.
- Who We Are -> About the company, could be omitted? Might be considered boilerplate? It's substantive about mission. Could be included as About the role? But we already have About the role. Might be considered "Who We Are" not required. Could drop as it's somewhat generic but still substantive. However instruction: prefer few substantive sections over many thin ones. We could combine company description into About the role or maybe omit. But we need to preserve ALL substantive information; cannot invent or summarize away detail. If we omit, we lose that info. So we need to include it somewhere. Could add a section "About the company" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? That heading is for role description, but we could expand to include company info. Might be acceptable. Or we could add a section "About the company" but not allowed; risk of violating instruction. Better to incorporate into About the role paragraph.
- Top-rated Employee Benefits -> Benefits section.
Thus we will have sections: About the role (includes why role exists and company description), Responsibilities, Requirements, Qualifications (or Skills), Pay, Benefits.
We need to decide between Qualifications and Skills. The posting has "What Makes You a Great Fit" which is a list of attributes (qualifications/skills). Also "We Do Have A Few Requirements To Check" which is specific requirements (education, experience). So we can have Requirements for the hard requirements, and Qualifications for the fit attributes. Or we could combine into Qualifications. But we have both headings allowed. Let's do Requirements (hard) and Qualifications (fit). Skills maybe not needed.
We must use
- for any list of duties/requirements/benefits. So for Responsibilities (list of duties), Requirements (list), Qualifications (list), Benefits (list). Pay: just a paragraph with salary range.
Schedule: not provided, so omit.
Now we need to preserve all substantive information. Let's extract details.
From posting:
Title: Senior Product Counsel - Healthcare
Team: Legal
Location: Remote
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."
What You’ll Spend Your Time Doing bullet list (actually paragraphs with bold headings). Let's capture each bullet:
- 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.
What Makes You a Great Fit bullet list (each starts with bold phrase). Let's capture:
- You don’t need to check every box — but this role will feel energizing if you:
Then 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
We Do Have A Few Requirements To Check:
- 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
Where You’ll Work: "This is a 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: paragraph about Phreesia mission etc.
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 strive to provide a diverse and inclusive environment and are an equal opportunity employer. (This is EEO boilerplate; we should remove EEO/equal-opportunity boilerplate per instruction. So drop that line.)
Also note: "We strive to provide a diverse and inclusive environment and are an equal opportunity employer." is EEO boilerplate; remove.
Also "Learn more here: https://www.phreesia.com/workforce/" is a link; we can keep as part of benefits list.
Now we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit application instructions.
Now we need to output HTML.
We'll have:
About the role
... combine Why This Role Exists and Who We Are? Actually Who We Are is about company; we could include after the role description. Let's include both paragraphs.
But we must not repeat job title as heading. Already not.
We'll include:
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.
At Phreesia, we’re looking for smart and passionate people to help drive our mission of creating a better, more engaging healthcare experience. We’re committed to helping healthcare organizations succeed in an ever-evolving landscape by transforming the way healthcare is delivered. Our SaaS platform digitizes appointment check-in and offers tools to engage patients, improve efficiency, optimize staffing, and enhance clinical care. Phreesia cares about our employees by providing a diverse and dynamic work environment. We’re a five-time winner of Modern Healthcare Magazine’s Best Places to Work in Healthcare award and we’ve been recognized on the Bloomberg
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to output only HTML fragment, no /, no markdown fences. We need to decide which sections to include. The posting includes: - 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 Qualifications or Skills. - We Do Have A Few Requirements To Check -> Requirements. - Where You’ll Work -> maybe Schedule? Actually location remote, but schedule not given. Could be omitted if no schedule specifics. - Compensation & Rewards -> Pay (and Benefits). They give base salary range and total rewards. So we can have Pay section with salary range, and Benefits section with benefits list. - Who We Are -> About the company, could be omitted? Might be considered boilerplate? It's substantive about mission. Could be included as About the role? But we already have About the role. Might be considered "Who We Are" not required. Could drop as it's somewhat generic but still substantive. However instruction: prefer few substantive sections over many thin ones. We could combine company description into About the role or maybe omit. But we need to preserve ALL substantive information; cannot invent or summarize away detail. If we omit, we lose that info. So we need to include it somewhere. Could add a section "About the company" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? That heading is for role description, but we could expand to include company info. Might be acceptable. Or we could add a section "About the company" but not allowed; risk of violating instruction. Better to incorporate into About the role paragraph. - Top-rated Employee Benefits -> Benefits section. Thus we will have sections: About the role (includes why role exists and company description), Responsibilities, Requirements, Qualifications (or Skills), Pay, Benefits. We need to decide between Qualifications and Skills. The posting has "What Makes You a Great Fit" which is a list of attributes (qualifications/skills). Also "We Do Have A Few Requirements To Check" which is specific requirements (education, experience). So we can have Requirements for the hard requirements, and Qualifications for the fit attributes. Or we could combine into Qualifications. But we have both headings allowed. Let's do Requirements (hard) and Qualifications (fit). Skills maybe not needed. We must use
- for any list of duties/requirements/benefits. So for Responsibilities (list of duties), Requirements (list), Qualifications (list), Benefits (list). Pay: just a paragraph with salary range.
Schedule: not provided, so omit.
Now we need to preserve all substantive information. Let's extract details.
From posting:
Title: Senior Product Counsel - Healthcare
Team: Legal
Location: Remote
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."
What You’ll Spend Your Time Doing bullet list (actually paragraphs with bold headings). Let's capture each bullet:
- 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.
What Makes You a Great Fit bullet list (each starts with bold phrase). Let's capture:
- You don’t need to check every box — but this role will feel energizing if you:
Then 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
We Do Have A Few Requirements To Check:
- 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
Where You’ll Work: "This is a 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: paragraph about Phreesia mission etc.
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 strive to provide a diverse and inclusive environment and are an equal opportunity employer. (This is EEO boilerplate; we should remove EEO/equal-opportunity boilerplate per instruction. So drop that line.)
Also note: "We strive to provide a diverse and inclusive environment and are an equal opportunity employer." is EEO boilerplate; remove.
Also "Learn more here: https://www.phreesia.com/workforce/" is a link; we can keep as part of benefits list.
Now we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit application instructions.
Now we need to output HTML.
We'll have:
About the role
... combine Why This Role Exists and Who We Are? Actually Who We Are is about company; we could include after the role description. Let's include both paragraphs. But we must not repeat job title as heading. Already not. We'll include:
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.
At Phreesia, we’re looking for smart and passionate people to help drive our mission of creating a better, more engaging healthcare experience. We’re committed to helping healthcare organizations succeed in an ever-evolving landscape by transforming the way healthcare is delivered. Our SaaS platform digitizes appointment check-in and offers tools to engage patients, improve efficiency, optimize staffing, and enhance clinical care. Phreesia cares about our employees by providing a diverse and dynamic work environment. We’re a five-time winner of Modern Healthcare Magazine’s Best Places to Work in Healthcare award and we’ve been recognized on the Bloomberg