Senior Product Manager, Core App
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal. Also remove duplicated lines.
We need to preserve all substantive info. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to include sections only when posting has real specific content. So we need sections: About the role? The posting has "About Lark" (company overview) and "The Role". Could map "About the role" heading to the description of role? Probably we can have "About the role" section containing the role overview (the paragraph after "The Role").
Then "Responsibilities" for "What You'll Do" bullet list.
Then "Requirements" or "Qualifications" for "What You'll Need". Could combine as Requirements.
Then "Pay" for compensation range.
We might also have "Benefits" if mentioned: "comprehensive benefits package" and "bonus program and stock awards". That's benefits info. So we can include Benefits section.
Schedule? Not mentioned. So omit.
Working at Lark includes remote organization requirement US residence. Could be part of "About the role" or maybe "Working conditions". Not a standard heading; we could incorporate into About the role or maybe a separate section like "Work Environment" but not in allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put remote requirement under About the role or maybe under Requirements? Probably under About the role as part of role description.
We must not invent sections like Skills if not present. Could we extract skills from What You'll Need? That includes many skill-like items. Could put them under Skills heading. But we also have Requirements/Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section, maybe "Requirements". Or we could have "Requirements" and "Qualifications" separate if content distinct. The posting includes "What You'll Need" which is a mix of requirements and qualifications. Could split into Requirements (experience, track record) and Qualifications (skills). But to keep few sections, maybe just "Requirements". However we need to follow allowed headings; we can use either Requirements or Qualifications. Choose Requirements.
We also have Skills heading allowed; we could put skill-like items there. But to avoid many thin sections, maybe combine into Requirements.
We need to output only HTML fragment.
Let's extract content:
About Lark paragraph: "At Lark Health, we’re leading the way into a new era of cardiometabolic care, leveraging advanced AI techniques–including deterministic and generative models–to provide scalable, affordable, and compassionate care. We help our healthcare partners manage over 30 million lives and prevent conditions like obesity, hypertension, type II diabetes, and behavioral health. Our platform delivers real-time personalized counseling and health monitoring for each patient. By providing compelling and actionable insights, we empower every user to live happier, healthier lives. Come join our team!"
The Role overview: "Are you a passionate product leader who wants to make a real impact on people's health? Lark Health is looking for a Senior Product Manager to own the future of our core member app and AI coaching. At Lark, we are leading the way into a new era of cardiometabolic care, leveraging advanced AI to provide scalable, compassionate care. Our platform helps manage millions of lives for our health plan partners, empowering users to prevent and manage conditions like diabetes, hypertension, and obesity. If you're excited to work at the intersection of healthcare, AI, and human-centered design, we'd love to meet you."
What You'll Do bullet list (each starts with "You will:" then list). Actually the text: "You will: Lead the development of our core app and AI coaching, guiding the entire development cycle from concept to launch.Use a hypothesis-driven approach to define and refine key features, leveraging market analysis, user testing, and data to create products that deliver real value.Own a portion of the product roadmap, translating user insights and business goals into clearly shaped initiatives, user stories, product requirements, and launch plans.Run a sharp measurement practice: clean experiments, the right metrics, and real evidence behind key decisions.Define and track success by setting and monitoring key results, and communicating those results to stakeholders and leadership.Partner tightly with the Enrollment and EHR teams on shared work and shared goals, keeping everyone aligned around member outcomes."
We need to split into list items. Each item separated by a period? Actually they are separated by periods but no line breaks. We'll parse:
- Lead the development of our core app and AI coaching, guiding the entire development cycle from concept to launch.
- Use a hypothesis-driven approach to define and refine key features, leveraging market analysis, user testing, and data to create products that deliver real value.
- Own a portion of the product roadmap, translating user insights and business goals into clearly shaped initiatives, user stories, product requirements, and launch plans.
- Run a sharp measurement practice: clean experiments, the right metrics, and real evidence behind key decisions.
- Define and track success by setting and monitoring key results, and communicating those results to stakeholders and leadership.
- Partner tightly with the Enrollment and EHR teams on shared work and shared goals, keeping everyone aligned around member outcomes.
What You'll Need paragraph: "You bring a builder's mindset. You've taken major features from zero to one, you're comfortable in ambiguity, and sharp with data. A track record of shipping consumer mobile products and features that people love. You've built under real constraints and learned from real users.Real product judgment. You can feel the craft in what you've built.Hands-on experience shipping AI-powered features, with a feel for what makes AI hard: accuracy, member trust, and designing for outputs you can't fully predict.Strong analytics and experimentation instincts. You're fluent in tools like Braintrust, Mixpanel, Looker, or Snowflake, and you know quality takes more than a standard A/B test.Familiarity with modern lean product development methodologies within a distributed team environment.A feel for behavior change and for the line between coaching and clinical care, so you design responsibly in a regulated space.Experience with the Medicare or older-adult population, or in B2C health, wellness, or fitness.Familiarity with responsible AI practices and the healthcare-specific questions that come with them."
We can turn into list items.
Working at Lark: "Lark operates as a remote organization, requiring all employees to reside within the United States. The specific salary offered to a candidate will depend on various factors, including their location, job level, and verified job-related knowledge, skills, and experience. In addition to a comprehensive benefits package, candidates may be eligible for additional compensation, such as participation in a bonus program and stock awards, where applicable. Lark is an Equal Opportunity and Affirmative Action Employer. We believe that diverse teams foster innovation and add to our mission-driven culture. We strongly encourage people from underrepresented groups to apply. Compensation Range: $136,400 - $206,780"
We need to remove EEO boilerplate lines: "Lark is an Equal Opportunity and Affirmative Action Employer. We believe that diverse teams foster innovation and add to our mission-driven culture. We strongly encourage people from underrepresented groups to apply." That's boilerplate; remove.
Also remove duplicated lines? Not seeing.
We need to keep compensation range and benefits info.
Thus we can have sections:
About the role
containing About Lark + The Role overview? Might be too much. But we can split: About the role could contain the role overview paragraph (the "Are you a passionate product leader...").
About Lark could be considered company description; but we don't have a heading for About the company. Could incorporate into About the role as context.
Alternatively we could have About the role (role overview) and then maybe a separate section like "About Lark" not allowed. So we incorporate Lark description into About the role.
Thus About the role section will have two paragraphs: first the Lark description, then the role overview.
Then Responsibilities section with ul list.
Then Requirements section with ul list (from What You'll Need).
Then Benefits section with ul list? Benefits: "comprehensive benefits package", "bonus program and stock awards". Could be two items.
Then Pay section with p containing compensation range.
We must not include Schedule.
Check for any other specifics: remote organization US residence. Could be placed under About the role or maybe under Requirements? It's a work condition. Could add a paragraph under About the role after role overview: "Lark operates as a remote organization, requiring all employees to reside within the United States."
We must not include EEO lines.
Now produce HTML.
Let's craft:
About the role
At Lark Health, we’re leading the way into a new era of cardiometabolic care, leveraging advanced AI techniques–including deterministic and generative models–to provide scalable, affordable, and compassionate care. We help our healthcare partners manage over 30 million lives and prevent conditions like obesity, hypertension, type II diabetes, and behavioral health. Our platform delivers real-time personalized counseling and health monitoring for each patient. By providing compelling and actionable insights, we empower every user to live happier, healthier lives. Come join our team!
Are you a passionate product leader who wants to make a real impact on people's health? Lark Health is looking for a Senior Product Manager to own the future of our core member app and AI coaching. At Lark, we are leading the way into a new era of cardiometabolic care, leveraging advanced AI to provide scalable, compassionate care. Our platform helps manage millions of lives for our health plan partners, empowering users to prevent and manage conditions like diabetes, hypertension, and obesity. If you're excited to work at the intersection of healthcare, AI, and human-centered design, we'd love to meet you.
Lark operates as a remote organization, requiring all employees to reside within the United States.
Responsibilities
- Lead the development of our core app and AI coaching, guiding the entire development cycle from concept to launch.
- Use a hypothesis-driven approach to define and refine key features, leveraging market analysis, user testing, and data to create products that deliver real value.
- Own a portion of the product roadmap, translating user insights and business goals into clearly shaped initiatives, user stories, product requirements, and launch plans.
- Run a sharp measurement practice: clean experiments, the right metrics, and real evidence behind key decisions.
- Define and track success by setting and monitoring key results, and communicating those results to stakeholders and leadership.
- Partner tightly with the Enrollment and EHR teams on shared work and shared goals, keeping everyone aligned around member outcomes.
Requirements
- You bring a builder's mindset. You've taken major features from zero to one, you're comfortable in ambiguity, and sharp with data.
- A track record of shipping consumer mobile products and features that people love.
- You've built under real constraints and learned from real users.
- Real product judgment. You can feel the craft in what you've built.
- Hands-on experience shipping AI-powered features, with a feel for what makes AI hard: accuracy, member trust, and designing for outputs you can't fully predict.
- Strong analytics and experimentation instincts. You're fluent in tools like Braintrust, Mixpanel, Looker, or Snowflake, and you know quality takes more than a standard A/B
for prose. We need to include sections only when posting has real specific content. So we need sections: About the role? The posting has "About Lark" (company overview) and "The Role". Could map "About the role" heading to the description of role? Probably we can have "About the role" section containing the role overview (the paragraph after "The Role"). Then "Responsibilities" for "What You'll Do" bullet list. Then "Requirements" or "Qualifications" for "What You'll Need". Could combine as Requirements. Then "Pay" for compensation range. We might also have "Benefits" if mentioned: "comprehensive benefits package" and "bonus program and stock awards". That's benefits info. So we can include Benefits section. Schedule? Not mentioned. So omit. Working at Lark includes remote organization requirement US residence. Could be part of "About the role" or maybe "Working conditions". Not a standard heading; we could incorporate into About the role or maybe a separate section like "Work Environment" but not in allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put remote requirement under About the role or maybe under Requirements? Probably under About the role as part of role description. We must not invent sections like Skills if not present. Could we extract skills from What You'll Need? That includes many skill-like items. Could put them under Skills heading. But we also have Requirements/Qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section, maybe "Requirements". Or we could have "Requirements" and "Qualifications" separate if content distinct. The posting includes "What You'll Need" which is a mix of requirements and qualifications. Could split into Requirements (experience, track record) and Qualifications (skills). But to keep few sections, maybe just "Requirements". However we need to follow allowed headings; we can use either Requirements or Qualifications. Choose Requirements. We also have Skills heading allowed; we could put skill-like items there. But to avoid many thin sections, maybe combine into Requirements. We need to output only HTML fragment. Let's extract content: About Lark paragraph: "At Lark Health, we’re leading the way into a new era of cardiometabolic care, leveraging advanced AI techniques–including deterministic and generative models–to provide scalable, affordable, and compassionate care. We help our healthcare partners manage over 30 million lives and prevent conditions like obesity, hypertension, type II diabetes, and behavioral health. Our platform delivers real-time personalized counseling and health monitoring for each patient. By providing compelling and actionable insights, we empower every user to live happier, healthier lives. Come join our team!" The Role overview: "Are you a passionate product leader who wants to make a real impact on people's health? Lark Health is looking for a Senior Product Manager to own the future of our core member app and AI coaching. At Lark, we are leading the way into a new era of cardiometabolic care, leveraging advanced AI to provide scalable, compassionate care. Our platform helps manage millions of lives for our health plan partners, empowering users to prevent and manage conditions like diabetes, hypertension, and obesity. If you're excited to work at the intersection of healthcare, AI, and human-centered design, we'd love to meet you." What You'll Do bullet list (each starts with "You will:" then list). Actually the text: "You will: Lead the development of our core app and AI coaching, guiding the entire development cycle from concept to launch.Use a hypothesis-driven approach to define and refine key features, leveraging market analysis, user testing, and data to create products that deliver real value.Own a portion of the product roadmap, translating user insights and business goals into clearly shaped initiatives, user stories, product requirements, and launch plans.Run a sharp measurement practice: clean experiments, the right metrics, and real evidence behind key decisions.Define and track success by setting and monitoring key results, and communicating those results to stakeholders and leadership.Partner tightly with the Enrollment and EHR teams on shared work and shared goals, keeping everyone aligned around member outcomes." We need to split into list items. Each item separated by a period? Actually they are separated by periods but no line breaks. We'll parse: - Lead the development of our core app and AI coaching, guiding the entire development cycle from concept to launch. - Use a hypothesis-driven approach to define and refine key features, leveraging market analysis, user testing, and data to create products that deliver real value. - Own a portion of the product roadmap, translating user insights and business goals into clearly shaped initiatives, user stories, product requirements, and launch plans. - Run a sharp measurement practice: clean experiments, the right metrics, and real evidence behind key decisions. - Define and track success by setting and monitoring key results, and communicating those results to stakeholders and leadership. - Partner tightly with the Enrollment and EHR teams on shared work and shared goals, keeping everyone aligned around member outcomes. What You'll Need paragraph: "You bring a builder's mindset. You've taken major features from zero to one, you're comfortable in ambiguity, and sharp with data. A track record of shipping consumer mobile products and features that people love. You've built under real constraints and learned from real users.Real product judgment. You can feel the craft in what you've built.Hands-on experience shipping AI-powered features, with a feel for what makes AI hard: accuracy, member trust, and designing for outputs you can't fully predict.Strong analytics and experimentation instincts. You're fluent in tools like Braintrust, Mixpanel, Looker, or Snowflake, and you know quality takes more than a standard A/B test.Familiarity with modern lean product development methodologies within a distributed team environment.A feel for behavior change and for the line between coaching and clinical care, so you design responsibly in a regulated space.Experience with the Medicare or older-adult population, or in B2C health, wellness, or fitness.Familiarity with responsible AI practices and the healthcare-specific questions that come with them." We can turn into list items. Working at Lark: "Lark operates as a remote organization, requiring all employees to reside within the United States. The specific salary offered to a candidate will depend on various factors, including their location, job level, and verified job-related knowledge, skills, and experience. In addition to a comprehensive benefits package, candidates may be eligible for additional compensation, such as participation in a bonus program and stock awards, where applicable. Lark is an Equal Opportunity and Affirmative Action Employer. We believe that diverse teams foster innovation and add to our mission-driven culture. We strongly encourage people from underrepresented groups to apply. Compensation Range: $136,400 - $206,780" We need to remove EEO boilerplate lines: "Lark is an Equal Opportunity and Affirmative Action Employer. We believe that diverse teams foster innovation and add to our mission-driven culture. We strongly encourage people from underrepresented groups to apply." That's boilerplate; remove. Also remove duplicated lines? Not seeing. We need to keep compensation range and benefits info. Thus we can have sections:
About the role
containing About Lark + The Role overview? Might be too much. But we can split: About the role could contain the role overview paragraph (the "Are you a passionate product leader..."). About Lark could be considered company description; but we don't have a heading for About the company. Could incorporate into About the role as context. Alternatively we could have About the role (role overview) and then maybe a separate section like "About Lark" not allowed. So we incorporate Lark description into About the role. Thus About the role section will have two paragraphs: first the Lark description, then the role overview. Then Responsibilities section with ul list. Then Requirements section with ul list (from What You'll Need). Then Benefits section with ul list? Benefits: "comprehensive benefits package", "bonus program and stock awards". Could be two items. Then Pay section with p containing compensation range. We must not include Schedule. Check for any other specifics: remote organization US residence. Could be placed under About the role or maybe under Requirements? It's a work condition. Could add a paragraph under About the role after role overview: "Lark operates as a remote organization, requiring all employees to reside within the United States." We must not include EEO lines. Now produce HTML. Let's craft:About the role
At Lark Health, we’re leading the way into a new era of cardiometabolic care, leveraging advanced AI techniques–including deterministic and generative models–to provide scalable, affordable, and compassionate care. We help our healthcare partners manage over 30 million lives and prevent conditions like obesity, hypertension, type II diabetes, and behavioral health. Our platform delivers real-time personalized counseling and health monitoring for each patient. By providing compelling and actionable insights, we empower every user to live happier, healthier lives. Come join our team!
Are you a passionate product leader who wants to make a real impact on people's health? Lark Health is looking for a Senior Product Manager to own the future of our core member app and AI coaching. At Lark, we are leading the way into a new era of cardiometabolic care, leveraging advanced AI to provide scalable, compassionate care. Our platform helps manage millions of lives for our health plan partners, empowering users to prevent and manage conditions like diabetes, hypertension, and obesity. If you're excited to work at the intersection of healthcare, AI, and human-centered design, we'd love to meet you.
Lark operates as a remote organization, requiring all employees to reside within the United States.
Responsibilities
- Lead the development of our core app and AI coaching, guiding the entire development cycle from concept to launch.
- Use a hypothesis-driven approach to define and refine key features, leveraging market analysis, user testing, and data to create products that deliver real value.
- Own a portion of the product roadmap, translating user insights and business goals into clearly shaped initiatives, user stories, product requirements, and launch plans.
- Run a sharp measurement practice: clean experiments, the right metrics, and real evidence behind key decisions.
- Define and track success by setting and monitoring key results, and communicating those results to stakeholders and leadership.
- Partner tightly with the Enrollment and EHR teams on shared work and shared goals, keeping everyone aligned around member outcomes.
Requirements
- You bring a builder's mindset. You've taken major features from zero to one, you're comfortable in ambiguity, and sharp with data.
- A track record of shipping consumer mobile products and features that people love.
- You've built under real constraints and learned from real users.
- Real product judgment. You can feel the craft in what you've built.
- Hands-on experience shipping AI-powered features, with a feel for what makes AI hard: accuracy, member trust, and designing for outputs you can't fully predict.
- Strong analytics and experimentation instincts. You're fluent in tools like Braintrust, Mixpanel, Looker, or Snowflake, and you know quality takes more than a standard A/B