Senior Product Manager, Accounting
Clio · Illinois, United States · 3 wk ago
RemoteRemoteMarketing$138k–$186k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes summary, description. We need 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. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We need to preserve all substantive info.
Let's parse content:
- Intro: Clio is global leader... Summary: We are currently seeking a Senior Product Manager, Clio Accounting to join our product team. This role is available to candidates across Canada (excluding Quebec) and the US. If you are located near one of our hubs (Vancouver, Calgary, or Toronto), you will be expected to work in the office a minimum of twice per week on our designated Anchor Days.
- Law firms run on trust... Clio Accounting exists... (description of product)
- What Your Team Does ... (team description)
- What You'll Work On (list of bullet points: Strategic Product Leadership, Customer and Domain Depth, Cross-Functional Execution)
- What You Bring (list of bullet points: 6+ years..., Working knowledge..., genuine interest..., clear perspective..., Experience applying design..., exceptional communicator..., Proactively collaborative..., entrepreneurial mindset..., Outcomes-focused..., Customer-obsessed...)
- Bonus Points (list)
- This is a new role. What you will find here: Compensation is one of the main components... (list of benefits: Competitive, equitable salary with top-tier health benefits, dental, and vision insurance Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin, London, New York City and Sydney) to be in office min. twice per week. Flexible time off policy, with an encouraged 20 days off per year. $2000 annual counseling benefit RRSP matching and RESP contribution Clioversary recognition program with special acknowledgement at 3, 5, 7, and 10 years The expected salary range for this role is $137,500 to $186,100 CAD. Initial placement within the range is informed by geographic region, experience, and skillset, with room to progress as impact and tenure grow. Final offer amounts will vary based on candidate profile.)
- Diversity, Inclusion, Belonging and Equity (DIBE) & Accessibility (boilerplate? It's about DIBE; we need to remove EEO/equal-opportunity boilerplate. This seems like DIBE statement; maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. DIBE might be considered EEO/equal-opportunity. Likely remove.
- We're a Human and High Performing AI company... (maybe not needed; could be considered boilerplate? It's about AI usage in recruitment; could be considered legal? Might be removed as boilerplate. Probably remove.
- Disclaimer: We only communicate with candidates through official @clio.com email addresses. (maybe remove as boilerplate/application instructions? It's about communication; maybe keep? It's not application instructions but a note. Might be considered boilerplate; safer to remove.
We need sections: About the role (maybe summary + location expectation). Responsibilities (What You'll Work On). Requirements/Qualifications/Skills (What You Bring + Bonus Points maybe). Benefits (list of benefits). Pay (salary range). Schedule (Hybrid work expectation). Let's see.
We need to avoid filler like "commensurate with experience". We have specific salary range, benefits.
We need to output only HTML fragment, no html/body tags.
We'll create sections:
About the role
Clio is the global leader in legal AI technology... (summary) ... This role is available to candidates across Canada (excluding Quebec) and the US. If you are located near one of our hubs (Vancouver, Calgary, or Toronto), you will be expected to work in the office a minimum of twice per week on our designated Anchor Days.
But note schedule info also appears later; we might put schedule in its own section. Better: About the role includes summary and location availability; schedule separate. Responsibilities: from What You'll Work On (Strategic Product Leadership, Customer and Domain Depth, Cross-Functional Execution). We'll list as- each bullet.
Requirements/Qualifications/Skills: Could combine What You Bring and Bonus Points into Requirements? Might split: Requirements (core), Qualifications (maybe same), Skills (maybe same). But we need to avoid thin sections. Perhaps combine into one section "Requirements" with both core and bonus as subpoints? But we need to follow instruction: use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those if they have substantive content. We could have Requirements (core), Qualifications (maybe same as Requirements?), Skills (maybe same). To avoid thin, we could include only Requirements and Skills, and maybe Qualifications omitted if not distinct. But we need to decide.
We have core requirements: 6+ years product management, B2B SaaS, bookkeeping fluency, AI perspective, design thinking, communication, collaboration, entrepreneurial, outcomes-focused, customer-obsessed.
Bonus points: legal tech experience, trust accounting familiarity, accounting integrations, launching AI-first features.
We could put core under Requirements, bonus under Skills, or Qualifications.
Let's assign:
- Requirements: core requirements (6+ years PM, B2B SaaS, bookkeeping fluency, AI perspective, design thinking, communication, collaboration, entrepreneurial, outcomes-focused, customer-obsessed).
- Skills: bonus points (legal tech/trust accounting, integrations, AI-first features).
- Qualifications: maybe we could include education? Not present. Could omit Qualifications section if no specific content. Better to omit rather than create thin.
Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Check each for substantive content.
About the role: we have summary and location availability.
Responsibilities: we have bullet points.
Requirements: bullet list.
Skills: bullet list.
Benefits: list from "What you will find here": Competitive, equitable salary with top-tier health benefits, dental, and vision insurance; Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin, London, New York City and Sydney) to be in office min. twice per week. Flexible time off policy, with an encouraged 20 days off per year. $2000 annual counseling benefit; RRSP matching and RESP contribution; Clioversary recognition program with special acknowledgement at 3, 5, 7, and 10 years.
Pay: salary range $137,500 to $186,100 CAD; note about initial placement etc.
Schedule: hybrid work expectation (minimum twice per week for local hubs). Already mentioned in Benefits but we can still have Schedule section with that detail. However we must avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original; but we might want to avoid repeating same info in two sections? It's not prohibited but could be considered duplication. However we need to include schedule info; it's present in Benefits as hybrid work environment. We could keep schedule section referencing that expectation. Might be okay.
But we should not create Schedule section if it's just same as benefits; but we have explicit expectation: "If you are located near one of our hubs (Vancouver, Calgary, or Toronto), you will be expected to work in the office a minimum of twice per week on our designated Anchor Days." That's schedule info. Benefits also mention hybrid work environment expectation for local Clions to be in office min twice per week. So it's same. We could include schedule section with that detail, and benefits section without repeating that line (maybe keep other benefits). Let's parse benefits text: "Competitive, equitable salary with top-tier health benefits, dental, and vision insurance Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin, London, New York City and Sydney) to be in office min. twice per week. Flexible time off policy, with an encouraged 20 days off per year.$2000 annual counseling benefitRRSP matching and RESP contribution Clioversary recognition program with special acknowledgement at 3, 5, 7, and 10 years". It's a run-on sentence; we can split.
We could keep benefits section with all except the hybrid work expectation, and schedule section with that expectation. But we need to preserve all info; we can keep hybrid expectation in schedule and also maybe keep in benefits? Might be duplication but okay. Safer to keep it only in schedule and remove from benefits to avoid duplication. However the benefits text includes that sentence; if we remove it, we are omitting substantive info (the hybrid work expectation). But we will have it in schedule, so not omitted. So we can keep hybrid expectation only under schedule.
Thus benefits section will list: Competitive, equitable salary with top-tier health benefits, dental, and vision insurance; Flexible time off policy, with an encouraged 20 days off per year; $2000 annual counseling benefit; RRSP matching and RESP contribution; Clioversary recognition program with special acknowledgement at 3, 5, 7, and 10 years.
Pay section: expected salary range $137,500 to $186,100 CAD; Initial placement within the range is informed by geographic region, experience, and skillset, with room to progress as impact and tenure grow. Final offer amounts will vary based on candidate profile.
Schedule section: If you are located near one of our hubs (Vancouver, Calgary, or Toronto), you will be expected to work in the office a minimum of twice per week on our designated Anchor Days. Also hybrid work environment expectation for local Clions (Vancouver, Calgary, Toronto, Dublin, London, New York City and Sydney) to be in office min. twice per week. Actually the latter is broader; we could include both. But to avoid duplication, we can combine: expectation to work in office min twice per week for local hubs (Vancouver, Calgary, Toronto) and for other hubs (Dublin, London, NYC, Sydney) also expectation. We'll just state: Employees are expected to work in the office a minimum of twice per week on designated Anchor Days if located near hubs (Vancouver, Calgary, Toronto, Dublin, London, New York City, Sydney). That captures.
Now we need to ensure we don't include boilerplate like DIBE, AI recruitment statement, disclaimer. Remove those.
Now produce HTML.
We'll wrap each section:
About the role
...
etc. For lists:- ...