Project Manager - Advanced

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting: It includes intro about Clarus, mission, etc. Then "As we continue to scale..." then "Job Summary". Then "Job Location: Remote – USA, or Hybrid from Boston, MA". Then "Main Responsibilities" with bullet points. Then "Qualifications". Then "Additional Information" includes work authorization, hours flexible, travel up to 10%, benefits list. Then interview notices etc which we should remove (boilerplate). Also "All of our jobs come with great benefits..." etc. We need sections: About the role (maybe the intro + job summary). Responsibilities (Main Responsibilities). Requirements (maybe qualifications? but they have Qualifications section). Skills maybe not explicit; we could combine skills within qualifications. Benefits: we have benefits list. Pay: not specified (no salary). So we should NOT include Pay section because no specific content. Schedule: maybe mention flexible hours, core business hours Eastern, travel up to 10% - that could be schedule info. The posting says "Hours are flexible, but availability during core business hours (Eastern) is expected." That's schedule-related. Also travel up to 10% could be schedule. So we can include Schedule section with that info. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to include About the role: maybe combine the introductory paragraphs up to Job Summary? Let's extract. The posting text: "At Clarus, we are harnessing intelligence to propel pet health towards a brighter, smarter, more connected future. A future where information flows freely across caregivers & care environments, insights are more instant and actionable, and financial decisions are empowered. For us, that future starts by fundamentally changing how pet insurance operates. We’re engineering systems that decomplexify coverage and facilitate reimbursement, so more pets can get the care they deserve. Our team of pet industry veterans and passionate pet people come from across the tech and health continuums. Together, we’re openly challenging industry convention in service of creating totally new possibilities. Which is why our culture is built on the values of curiosity, entrepreneurship, humility and fierce collaboration. Clarus is a pioneering pet health technology company on a mission to transform the future of pet healthcare. We are dynamic entrepreneurs improving pet health by providing trusted and transparent information across the entire pet health landscape. Join us in shaping a smarter, healthier future for pets everywhere. As we continue to scale our platform, products, and partnerships, we are looking for a Project Manager - Advanced to help drive our most critical, cross‑functional initiatives, including business‑critical programs that require strong execution, leadership, and comfort operating in ambiguity. Job Summary Clarus is seeking a highly experienced Project Manager - Advanced who serves as a central execution leader across the business. You will own delivery of complex, cross‑functional initiatives, from business workstreams to internal operating improvements, by driving clarity, momentum, and accountability where structure may not yet exist. This role is ideal for someone who thrives in fast‑moving environments, is comfortable creating processes (not just following them), and can lead teams through ambiguity to deliver tangible business outcomes. You will partner closely with Data, Product, Engineering, Commercial, Marketing, Sales, Customer Success, Operations, Finance, Legal, and Leadership to ensure initiatives are aligned, launch‑ready, and executed with rigor." Then "Job Location: Remote – USA, or Hybrid from Boston, MA" Then "Main Responsibilities" with bullet points. Then "Qualifications" with bullet points. Then "Additional Information" includes: "You must be authorized to work in the U.S.Hours are flexible, but availability during core business hours (Eastern) is expected.Requires travel of up to 10%. All of our jobs come with great benefits including healthcare, parental leave and opportunities for career advancements. Some offerings are dependent upon the location of where you work and can include the following: Comprehensive full medical, dental and vision InsuranceBasic Life Insurance at no cost to the employeeCompany paid short-term and long-term disability12 weeks of 100% paid Parental LeaveHealth Savings Account (HSA)Flexible Spending Accounts (FSA)Retirement savings planPersonal Paid Time OffPaid holidays and company-wide Wellness Day offPaid time off to volunteer at nonprofit organizationsPet friendly office environmentCommuter BenefitsGroup Pet InsuranceOn the job training and skills developmentEmployee Assistance Program (EAP) Interview Technology Notice ..." We need to strip interview notices etc. So we keep benefits list. We need to decide sections: - About the role: could include the introductory mission and job summary. Probably combine first paragraphs up to Job Summary. - Responsibilities: Main Responsibilities bullet list. - Requirements: maybe combine Qualifications and maybe some of the Additional Info like work authorization, travel? But Additional Info includes benefits and work auth etc. Requirements could be Qualifications (8+ years experience etc). We'll put Qualifications under Requirements heading? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has a "Qualifications" section. So we should use

Qualifications

for that. For Requirements, maybe we could include the work authorization and travel expectations? But those are more like "Additional Information". Could treat as Requirements? However the instruction says include a section ONLY when the posting has real, specific content for it. So we need to see if there is content for Requirements separate from Qualifications. The posting does not have a separate "Requirements" heading; it has Qualifications. So we could either not include Requirements section, or we could treat Qualifications as Requirements. But we have both headings possible; we should not create empty sections. So we will not include a Requirements heading if no specific content labeled as Requirements. We'll use Qualifications heading for the qualifications list. Skills: Not explicitly listed; maybe we could infer from qualifications but better not to create a Skills section unless there is explicit skills list. There's no separate skills bullet list. So we omit Skills. Benefits: we have benefits list. So include Benefits heading. Pay: no specific salary info, so omit. Schedule: we have "Hours are flexible, but availability during core business hours (Eastern) is expected. Requires travel of up to 10%." That's schedule-related. So include Schedule heading with that info. We also need to include Job Location maybe as part of About the role or separate? Could be part of About the role or maybe we could include a short paragraph under About the role. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Job Location is minor metadata; we can include it in a

under About the role or maybe as its own paragraph. Probably include it in About the role section as a paragraph. We must preserve all substantive information: so we need to keep the mission description, job summary, responsibilities bullet list, qualifications bullet list, benefits list, schedule info (flexible hours, core hours, travel). Also work authorization: "You must be authorized to work in the U.S." That's also substantive; we should keep it. Where to put? Could be under About the role or maybe under Schedule? It's eligibility. Could be under About the role as a paragraph. We'll include it in About the role. We must remove boilerplate: interview technology notice, text messaging notice, etc. Also remove "All of our jobs come with great benefits including healthcare, parental leave and opportunities for career advancements." That's somewhat generic but still part of benefits intro; we can keep it as part of benefits paragraph leading into list. It's not boilerplate; it's describing benefits. Keep. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... mission description ...

Job Location: Remote – USA, or Hybrid from Boston, MA

You must be authorized to work in the U.S.

Then responsibilities:

Responsibilities

• ...
...

Then qualifications:

Qualifications

• ...
...

Then benefits:

Benefits

All of our jobs come with great benefits including healthcare, parental leave and opportunities for career advancements. Some offerings are dependent upon the location of where you work and can include the following:

• Comprehensive full medical, dental and vision Insurance
• Basic Life Insurance at no cost to the employee
• Company paid short-term and long-term disability
• 12 weeks of 100% paid Parental Leave
• Health Savings Account (HSA)
• Flexible Spending Accounts (FSA)
• Retirement savings plan
• Personal Paid Time Off
• Paid holidays and company-wide Wellness Day off
• Paid time off to volunteer at nonprofit organizations
• Pet friendly office environment
• Commuter Benefits
• Group Pet Insurance
• On the job training and skills development
• Employee Assistance Program (EAP)

Then schedule:

Schedule

Hours are flexible, but availability during core business hours (Eastern) is expected. Requires travel of up to 10%.

We must ensure we didn't miss any substantive info: The responsibilities bullet list includes many items; we need to capture them exactly as in posting. Let's extract them precisely. From posting under "Main Responsibilities": - Cross-Functional Program & Project Leadership Lead high-impact, business-critical initiatives that span multiple functions, teams, and stakeholders. Translate company strategy and leadership priorities into clear objectives, decisions, roadmaps, and execution plans. Serve as a trusted partner to business and executive leaders, driving alignment, decision-making, and accountability. Navigate complex dependencies, competing priorities, and organizational change to achieve business outcomes. Support Data and Engineering teams through capacity planning, prioritization, and delivery management, while maintaining flexibility to lead cross-functional initiatives across the broader organization - Program & Workstream Delivery Own delivery of a cross-functional project or dedicated business workstream from planning through completion. Build and manage project plans, timelines, dependencies, milestones, and success criteria. Proactively identify, mitigate, and escalate risks, issues, and blockers to protect commitments. Provide clear visibility into progress, decisions, and tradeoffs to ensure on-time, high-quality delivery. - Operating in Ambiguity & Building New Processes Drive clarity in ambiguous problem spaces where goals, scope, or pathways may not be fully defined. Design and implement lightweight, scalable processes, templates, and operating rhythms to improve execution as the business grows. Continuously improve how Clarus plans, tracks, launches, and executes initiatives across teams. - Governance & Executive Communications Develop executive-ready updates, dashboards, and leadership readouts that provide clear visibility into progress, risks, decisions, and outcomes. Serve as a primary point of coordination across functions for assigned initiatives. Facilitate governance forums, status reviews, and decision-making processes across stakeholders. Ensure commitments, decisions, actions, and escalations are documented, communicated, and tracked to resolution. Influence without authority by building trust, aligning incentives, and keeping teams focused on outcomes. We need to represent these as list items. Could be each bullet as

containing the sentences. Might need to preserve line breaks? We'll just put each bullet as

with the text. We have multiple sub-bullets under each heading. The posting uses headings then indented bullets. We could treat each line as a