Product Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We need to parse the job posting. The posting includes: - Who We Are (company description) - could be "About the role"? Actually "Who We Are" is company description, not role. But we can map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections with those headings if content exists. We need to preserve all substantive information, remove boilerplate (EEO, legal, etc). Also remove duplicated lines, cookie/navigation etc. We need to decide which sections to include. Content: - Who We Are: description of SeekWell, parent company, mission, culture, owned by KKR, etc. This could go under "About the role"? Actually "About the role" usually describes the role, not company. But we have no explicit "About the role" section. However we could treat "Who We Are" as "About the role"? Might be okay. But maybe better to put under "About the role" the description of the role and company? The instruction says use those headings as examples; we can include only those that have real content. The posting includes a "Why you want this job" section describing the role. That could be "About the role". Also there is "What You'll Do" (responsibilities). Then "What You'll Need" (requirements/qualifications/skills). Then "Perks" (benefits). No explicit Pay or Schedule. There's mention: "Ability to work from our Draper, Utah office 1-2 days a week" (schedule). That's schedule info. No pay mentioned. So we can include Schedule section with that info. No Pay, so omit Pay section. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Possibly combine Requirements/Qualifications/Skills into one? But we can separate if content distinct. Let's extract: About the role: Could combine "Who We Are" and "Why you want this job". Provide description of company and role. Responsibilities: "What You'll Do" bullet points. Requirements: maybe "Ability to work from our Draper, Utah office 1-2 days a week" is schedule, not requirement. Requirements: "5+ years of product management experience building consumer facing applications, mobile app experience required", "Experience working with products that leverage advanced mobile technology, such as facial recognition, voice and speech recognition, lidar, device sensors, or other similar technology", "Demonstrated success working in an environment and process that requires detailed documentation, compliance with privacy standards or HIPAA, or regular legal & compliance oversight.", "Experience with medical devices is considered a plus.", "Thrives in a fast-paced, start-up environment with an ability to change approach to meet changing business needs", "Excellent written and verbal communication skills, comfortable communicating with stakeholders from all levels of the organization", "Experience working in agile environments with cross-functional teams.", "Familiarity with tools such as JIRA, Confluence, Figma, Adobe Analytics, Tableau, etc.", "Strong analytical and problem-solving skills; proficient in using data and A/B testing to inform decisions", "Strong technical literacy and the ability to engage in meaningful discussions regarding algorithms, model performance, data structures, and API behaviors with engineers and data scientists." Qualifications: maybe overlapping with requirements. Could treat "Experience with medical devices is considered a plus." as qualification. But we can combine. Skills: maybe list of tools, analytical, communication, etc. But we can split. Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one "Requirements" section. But they ask to use headings for those categories if content exists. We could include all three but risk thin sections. Better to combine into "Requirements" and maybe "Skills" separate if distinct. Let's see: The posting includes a list of skills: tools, analytical, technical literacy, communication. Could be under Skills. Requirements: years experience, mobile app experience, advanced mobile tech experience, compliance/HIPAA experience, medical device plus, fast-paced startup, ability to change approach. Qualifications: maybe not separate. Thus we can have: - About the role (company + why you want this job) - Responsibilities (What You'll Do) - Requirements (experience, etc.) - Skills (tools, analytical, communication, technical literacy) - Benefits (Perks) - Schedule (Ability to work from our Draper, Utah office 1-2 days a week) We should not include Pay. Now format: Use

for each heading. Then content: For prose use

. For lists use

• . We need to preserve all substantive information, not invent or summarize away detail. So we need to keep each bullet point as separate
• . Ensure we don't lose any detail. Let's extract each piece. About the role: From "Who We Are": "SeekWell is the parent company of 1-800 Contacts, Luna, and The Framery. Our goal is to make it simpler, easier, and more accessible for people to get the vision care they need. We maintain the legendary, award-winning culture 1-800 Contacts started almost 30 years ago and continue to develop innovative, pioneering products and businesses that make consumers cheer. We’re owned by KKR – one of the world’s largest and most successful private equity investment companies. We’ve built an excellent company and changed an industry by putting the customer first, always. The best is yet to come!" From "Why you want this job": "As a Product Manager, you’ll help make getting an eye exam and prescription easier for millions of glasses and contacts wearers. You’ll own the customer experience for an innovative, app-based vision exam and help shape the product vision, roadmap, and go-to-market strategy. You’ll work closely with engineering, design, data, legal, and compliance teams to turn big ideas into a simple, seamless experience that makes it easier for customers to get the vision care they need and buy glasses online." We can combine into a couple paragraphs. Responsibilities (What You'll Do): List items: - Plan and execute the product roadmap for regulated prescription technology, aligning initiatives with broader company goals and customer needs. - Lead discovery and validation efforts with customers and end users to ensure solutions address real-world pain points and deliver meaningful outcomes. - Understand customer needs, motivations, and pain points to create user interfaces that transform complex tasks into simple-to-follow experiences. - Lead an agile software development team and work cross-functionally to drive ideas from inception to launch. - Collaborate with cross-functional teams—including engineering, data science, UX design, marketing, and customer success—to define, build, and launch impactful product experiences. - Understand and track product metrics & KPIs, and deliver features that meet defined business outcomes. - Partner with compliance team to maintain and optimize processes for change management and regulatory adherence. - Ensure proper measurement, validation, and documentation of software changes prior to release. - Partner with marketing and ecommerce to understand market response to the product, create effective messaging and product positioning, and develop cohesive customer journeys from awareness through adoption and purchase. Note: Some lines have line breaks but we keep as is. Requirements: List: - Ability to work from our Draper, Utah office 1-2 days a week (actually schedule, but we will put in Schedule section) - 5+ years of product management experience building consumer facing applications, mobile app experience required - Experience working with products that leverage advanced mobile technology, such as facial recognition, voice and speech recognition, lidar, device sensors, or other similar technology - Demonstrated success working in an environment and process that requires detailed documentation, compliance with privacy standards or HIPAA, or regular legal & compliance oversight. - Experience with medical devices is considered a plus. - Thrives in a fast-paced, start-up environment with an ability to change approach to meet changing business needs - Excellent written and verbal communication skills, comfortable communicating with stakeholders from all levels of the organization - Experience working in agile environments with cross-functional teams. - Familiarity with tools such as JIRA, Confluence, Figma, Adobe Analytics, Tableau, etc. - Strong analytical and problem-solving skills; proficient in using data and A/B testing to inform decisions - Strong technical literacy and the ability to engage in meaningful discussions regarding algorithms, model performance, data structures, and API behaviors with engineers and data scientists. But we moved schedule to separate section. So remove that line from Requirements. Thus Requirements list excludes the schedule line. Skills: We could list: - Familiarity with tools such as JIRA, Confluence, Figma, Adobe Analytics, Tableau, etc. - Strong analytical and problem-solving skills; proficient in using data and A/B testing to inform decisions - Strong technical literacy and the ability to engage in meaningful discussions regarding algorithms, model performance, data structures, and API behaviors with engineers and data scientists. - Excellent written and verbal communication skills, comfortable communicating with stakeholders from all levels of the organization - Experience working in agile environments with cross-functional teams. But note some of these overlap with requirements. To avoid duplication, we might keep them under Requirements only and not have Skills separate. However instruction says we can include Skills if content exists. But we risk duplication. Better to keep Requirements as the combined list of experience, qualifications, and skills. Then we can omit Skills section to avoid thin duplication. But we need to follow instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must include all; we include only those with real specific content. If we put all under Requirements, we still have content for Requirements. Skills may be thin if we separate; better to not include Skills. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Now Benefits (Perks): List: - Free eye exams for your entire family - Deep discounts on lenses, glasses, and other services - Amazing healthcare coverage - 401(k) match - Flexible PTO - Tuition reimbursement program - In-house restaurant with highly discounted meals (Steak dinner under $6) - Free snacks, ice cream, and drinks every day - Full onsite gym Schedule: - Ability to work from our Draper, Utah office 1-2 days a week Now we need to output HTML fragment only, no /, no markdown. We'll produce:

  About the role

  SeekWell is the parent company of 1-800 Contacts, Luna, and The Framery. Our goal is to make it simpler, easier, and more accessible for people to get the vision care they need. We maintain the legendary, award-winning culture 1-800 Contacts started almost 30 years ago and continue to develop innovative, pioneering products and businesses that make consumers cheer. We’re owned by KKR – one of the world’s largest and most successful private equity investment companies. We’ve built an excellent company and changed an industry by putting the customer first, always. The best is yet to come!

  As a Product Manager, you’ll help make getting an eye exam and prescription easier for millions of glasses and contacts wearers. You’ll own the customer experience for an innovative, app-based vision exam and help shape the product vision, roadmap, and go-to-market strategy. You’ll work closely with engineering, design, data, legal, and compliance teams to turn big ideas into a simple, seamless experience that makes it easier for customers to get the vision care they need and buy glasses online.

  Responsibilities

  • Plan and execute the product roadmap for regulated prescription technology, aligning initiatives with broader company goals and customer needs.
  • Lead discovery and validation