Product Manager, Core Product

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Skills & Qualifications, Benefits (maybe), Pay? Not present. Schedule? Not present. Location? Not required as heading? The instruction: use

for section headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only sections with real content. We have About the role (the paragraph after "About the Role"). We have Responsibilities (What You'll Do). We have Skills & Qualifications (the list). We have Benefits (Why Join Us? includes benefits). We have maybe "Location" but not required as heading; could be included as a short paragraph but not heading. The instruction: 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. We have location "Palo Alto On-site" and "Employment Type Full-Time Experience Level Senior." That's minor metadata; we can put in a short

. Also we have "About Youlify Inc" intro; that's company description; could be included as a paragraph before sections? Not required but we can keep as a

. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description. Also we need to remove boilerplate: Equal Opportunity, etc. Remove EEO lines. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation/legal etc. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About Youlify Inc...

About the role

We're looking for a Product Manager, Core Product to own the hardest, least visible part...

Responsibilities

• Research and interpret payer policy, coding guidelines, and billing rules, and make clear, defensible judgment calls in areas where the rules are ambiguous, contradictory, or simply undocumented.
• Translate those judgment calls into product requirements our engineering team can build against.
... etc.

Skills & Qualifications

• Minimum 4 years of product management experience.
• Strong analytical and systematic thinking. Comfortable taking an ambiguous, undocumented, or contradictory rule set and reasoning your way to a clear, defensible answer.
... etc.

Benefits

• Competitive salary & meaningful equity.
• Be part of an early-stage team and share in the company's success.
• Work on a mission-critical problem. Directly impact the lives of physicians and patients, and make a huge impact on the broken U.S. healthcare payment system.
• Top-tier team. Work alongside world-class engineers, AI researchers, product leaders, and healthcare experts.
• Startup culture with stability. Move fast and build innovative tech with the backing of top Silicon Valley investors.
• Great benefits plan. 100% employer-paid premium medical, dental, and vision coverage for employees, with generous coverage for dependents.
• Lunch/Dinner included for on-site employees. Enjoy daily company-provided meals at no cost when working from our Palo Alto HQ.
• Gym on site. Stay healthy and active with access to an on-site fitness center at no cost (Palo Alto HQ).

Location: Palo Alto On-site • Employment Type: Full-Time • Experience Level: Senior

We need to ensure we didn't include sections like Pay or Schedule (not present). Also we need to ensure we didn't include "Requirements" heading separate; we have Skills & Qualifications which covers. Check that we didn't include any filler like "commensurate with experience". Not present. We need to preserve all substantive information from the posting. Let's verify we captured all. Original text sections: - About Youlify Inc (mission etc.) - About the Role (paragraph) - You Won't Be Doing This Alone (support) - Is This Role For You? (comparison with Forward Deployment PM) - What You'll Do (list of responsibilities) - Skills & Qualifications (list) - Why Join Us? (benefits etc.) - Location, Employment Type, Experience Level - Equal Opportunity (remove) We need to preserve "You Won't Be Doing This Alone" and "Is This Role For You?" as they are substantive. Should we include them? They are not under standard headings but contain info. We could incorporate them into About the role or as separate sections like "Team Support" or "Role Fit". However instruction: Prefer a few substantive sections over many thin ones. Could merge them into About the role or maybe a section "About the team". But we must not invent headings not in the list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could use other headings if they reflect content. However they say "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Likely they expect those standard headings. But we can also add other headings if needed, but better to stick to those. The "You Won't Be Doing This Alone" could be part of About the role. The "Is This Role For You?" could be part of About the role or maybe a separate section "Role Fit". But to keep few sections, we can incorporate into About the role. Thus About the role section will include the paragraphs: "We're looking for a Product Manager, Core Product..." plus the support paragraph and the comparison paragraph. We need to ensure we don't lose any detail. Let's craft About the role paragraph: We'll combine: "We're looking for a Product Manager, Core Product to own the hardest, least visible part of what makes our AI trustworthy: getting the underlying logic right. We're building an AI reasoning layer that works the way a skilled medical coder and biller does. Payer policy and billing rules are dense, inconsistent, and full of gray areas that are never fully documented. You'll dig into that ambiguity, make sound, well-reasoned judgment calls about how our AI should behave, and turn those calls into clear product direction. You'll also help shape and improve the AI models behind our product. As the underlying technology evolves, you'll rigorously assess whether a change is actually better for our specific use cases, using real data and real outputs rather than assumptions, and make the call on when and how to move forward. This role is less about talking to customers and more about going deep: reading policy, analyzing patterns in our own data, and thinking systematically about edge cases most people would wave away. You'll need to think like an analyst and a medical biller/coder at once, someone who can look at a messy, ambiguous rule set and find the signal in it. You Won't Be Doing This Alone You'll have real support around you: our in-house medical coders and billers to weigh in on coding-specific questions, an engineering team to build against your product direction, and support from leadership, who built the structure of our current reasoning model, to help you ramp up quickly. Is This Role For You? We're also hiring a Product Manager, Forward Deployment - Enterprise, and the two roles attract different kinds of people. Both are essential, and neither is "more product" than the other; they're just oriented differently. You might thrive as a Product Manager, Core Product if you're more drawn to how the underlying system scales, how the models evolve, and building the logic that has to work well across every customer, not just one. You might be a better fit for our Forward Deployment PM role if you're endlessly curious about why a customer buys and keeps using a product, and you get energy from the business case and real-world impact as much as the product itself." That's a lot but we need to preserve. Now Responsibilities: "What You'll Do" list. We need to capture each bullet. Let's extract bullet points from the text: - Research and interpret payer policy, coding guidelines, and billing rules, and make clear, defensible judgment calls in areas where the rules are ambiguous, contradictory, or simply undocumented. - Translate those judgment calls into product requirements our engineering team can build against. - Systematically review feedback and evaluations from our in-house medical coders and billers on AI output quality, and reconcile inconsistent or conflicting input into a single, well-reasoned final call, grounded in the underlying policy. - Own how we structure and improve the process for labeling and evaluating AI output quality over time. - Evaluate our AI's underlying technology on an ongoing basis: analyze real outputs, transactional data, and performance patterns to decide when a change is worth making, and when it isn't. - Guide the ongoing improvement of the AI models behind our product, working with engineering to define what "better" looks like for our specific use cases. - Design how our AI agents work and coordinate with one another, agent to agent, and improve accuracy on more complex tasks. - Dig into our own product and claims data to identify patterns, edge cases, and opportunities to improve accuracy. - Design product features that shape how humans and our AI interact, so the experience reflects the judgment calls and logic you own. - Partner with our Forward Deployed PMs to understand how policy and model decisions play out with real customers, and feed that context back into your judgment calls. - Own and continuously refine our internal logic and decision framework so it stays consistent, well-documented, and easy to hand off as the team grows. Now Skills & Qualifications bullet points: - Minimum 4 years of product management experience. - Strong analytical and systematic thinking. Comfortable taking an ambiguous, undocumented, or contradictory rule set and reasoning your way to a clear, defensible answer. - Experience building product logic in a rules-heavy, ambiguous domain (e.g., compliance, insurance, tax, legal-tech, trust & safety, or similar). Direct experience with medical coding, billing, or payer policy is a plus, not a requirement; what matters most is a track record of turning dense, inconsistent rule sets into clear, defensible product decisions. - Experience evaluating AI or ML model outputs, ideally in a product context. Comfortable assessing tradeoffs between models based on real data rather than headline benchmarks. - Strong quantitative and data literacy. You should be comfortable working with structured data, statistics, and drawing sound conclusions from it. - Excellent written communication. You'll be documenting judgment calls and decision logic that other people rely on, so clarity and precision matter. - Comfortable with ambiguity and self-directed research; this role involves as much independent analysis as it does collaboration. - Education: Bachelor's degree in Computer Science, Engineering, Statistics, or another STEM field required. Now Benefits from "Why Join Us?": - Competitive salary & meaningful equity. - Be part of an early-stage team and share in the company's success. - Work on a mission-critical problem. Directly impact the lives of physicians and patients, and make a huge impact on the broken U.S. healthcare payment system. - Top-tier team. Work alongside world-class engineers, AI researchers, product leaders, and healthcare experts. - Startup culture with stability. Move fast and build innovative tech with the backing of top Silicon Valley investors. - Great benefits plan. 100% employer-paid premium medical, dental, and vision coverage for employees, with generous coverage for dependents. - Lunch/Dinner included for on-site employees. Enjoy daily company-provided meals at no cost when working from our Palo Alto HQ. - Gym on site. Stay healthy and active with access to an on-site fitness center at no cost (Palo Alto HQ). Now location etc: "Location Palo Alto On-site Employment Type Full-Time Experience Level Senior." We'll put as a paragraph. Now we need to ensure we didn't include any boilerplate