Director, Content Collections

We need to output HTML fragment with sections: About the role? The posting includes summary and responsibilities etc. We must not repeat job title. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections with real specific content. We need to extract content: The posting includes a summary paragraph, then "What You'll Do" (responsibilities), then "What You Bring" (requirements/qualifications/skills). Then compensation details: salary range, benefits etc. Also mention hybrid work environment, flexible time off, etc. That's benefits and schedule? Schedule: hybrid work environment expectation min twice per week in office. Could be schedule. Benefits: health benefits, dental, vision, $2000 counseling benefit, RRSP matching, RESP contribution, Clioversary recognition program, flexible time off policy (20 days). Also mention competitive equitable salary. We need to avoid boilerplate: remove EEO, DIBE, accessibility, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove "Learn more about" truncated. We must preserve all substantive info. We need to decide sections: About the role (summary), Responsibilities (What You'll Do), Requirements (What You Bring maybe split into Requirements and Qualifications and Skills). Could combine but better to follow headings if content exists. We have: "What You Bring" includes experience, track record, etc. That's qualifications/requirements/skills. We could put under Requirements (or Qualifications). Since we have multiple headings allowed, we can split: Requirements (years experience, managing managers), Qualifications (track record owning multi-market portfolio, delivering outcomes through partner teams, working knowledge of legal system, multi-jurisdiction experience, experience shipping AI-assisted workflows), Skills (credible in front of enterprise buyers, etc). But we need to ensure we don't create thin sections. Might combine into one Requirements section. But instructions: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (covers what you bring), Benefits, Pay, Schedule. We need to include Pay section with salary range. Benefits section with benefits details. Schedule section with hybrid work expectation. Let's extract: About the role: The summary paragraph: "Clio is the global leader in legal AI technology, empowering legal professionals and law firms of every size to work smarter, faster, and more securely. We are transforming the legal experience for all by bettering the lives of legal professionals while increasing access to justice. Summary: The Director of Content Collections owns Clio's legal content collection as a single global portfolio — the substrate of the company's content moat and of Vincent AI's research quality and directly manages the team of Content Managers who have individual ownership and responsibility of the various jurisdictions' datasets. The overarching role of the Content Managers is to own the end-to-end strategy, performance, and resilience of Clio's data collections, a cornerstone of the company's legal-content moat and Vincent AI engine. They assess the ongoing quality and competitiveness of the data sets they're responsible for and determine the strategy and prioritization of ongoing data expansion. Where each Content Manager owns one or more jurisdictions end to end, this role owns the system they operate in; the standards that make collections comparable, the capital allocation that decides which jurisdictions get investment, the single prioritized demand signal into Data Ops and Content Engineering, and the team of managers themselves. Most of its leverage outside its own team comes from the quality of its specifications and the credibility of its ROI cases, not from reporting lines. Success is measured less by any single collection than by whether every collection is getting better, faster, and cheaper at the same time and whether Vincent's research answers hold up in every market Clio sells in." That's a lot; we keep it. Responsibilities: The "What You'll Do" section bullet points (paragraphs). We need to preserve all substantive info, not summarizing. We'll convert each paragraph into

under a

. The section heading

Responsibilities

. We need to extract each bullet: The text after "What You'll Do" includes several paragraphs each starting with a bold heading? Actually the text: "Lead and Develop the Content Manager Team Hire, onboard, and develop country and regional Content Managers, building a bench deep enough that opening a new jurisdiction isn't gated on a new hire.Set the operating rhythm; roadmap reviews, quarterly business reviews, coverage-parity readouts, and 1:1s that raise the quality of judgment, not just the reporting of status.Define the Content Manager role ladder and performance standards, making the difference between a good and a great collection owner explicit and coachable.Create the Content Manager guild, so jurisdictional learnings, source-acquisition tactics, and enrichment patterns propagate across countries rather than being rediscovered.Own succession and continuity so no collection carries single-person risk. Own the Global Collection PortfolioDefine the multi-year content strategy: which jurisdictions Clio invests in, at what depth, in what sequence, and anchored to Product's market roadmap and to the coverage bets worth making ahead of it.Allocate budget, headcount, licensing spend, and partner-team capacity across jurisdictions against a consistent value model — not by whoever argues loudest.Maintain the global coverage picture: parity versus AI-native players (Harvey, Legora), global legal publishers (Westlaw, LexisNexis), and regional incumbents, with a clear view of where Clio is ahead, at parity, or exposed.Set the bar for what "market-ready" means in a new jurisdiction, own the go/no-go on launch readiness, and arbitrate trade-offs between depth in mature collections and breadth into new markets.Own the build/buy/license decision per jurisdiction with Secondary Content, Licensing, and Corp Dev — including when licensing a collection makes more business sense than building one. Govern Content Surfacing and Vincent Research QualitySet the framework governing where each collection surfaces. The same content is exposed differently in Clio Library, Clio Work, and Vincent for licensing, cost, and product reasons; Content Managers co-own the call with Product, and this role is accountable for consistency across the portfolio and for keeping licensing and cost constraints honoured.Own the global framework for the Vincent research skill: how sources are tiered across Clio Library, private index, and agentic web search, and what evidence is required to move a source between tiers.Own the evaluation methodology, benchmark question sets, and quality gates that make Vincent answer quality measurable by jurisdiction rather than anecdotal — so "good research output" means the same thing in São Paulo as in London.Diagnose research-quality failures to the right owner — missing coverage, bad parsing, weak citator linking, retrieval configuration, or model behaviour — and drive remediation with that team rather than escalating undifferentiated complaints. Set the Standards the Content Supply Chain Runs OnOwn and version global metadata and structural standards — citation models, court and legislation hierarchies, amendment tracking, document typing — so cross-jurisdiction features are possible at all. Data Ops and Content Engineering implement to these standards; Collections defines them.Define acceptance criteria and quality thresholds for ingested and enriched content, and own the sign-off on whether output meets spec.Specify citator requirements per jurisdiction treatment types, linking depth, precision and recall targets as the authoritative input to Content Engineering's build.Set freshness, reliability, and data-integrity requirements for the portfolio, and make the business case for the pipeline resilience and disaster recovery they imply.Set the enrichment agenda: what is worth human effort, what should be AI-assisted, and what should be automated outright — with the quality bar and evaluation method that makes those calls evidence-based, and generalizable patterns productized once rather than solved per country. Partner with Product on Roadmap and Content ReadinessServe as Product's counterpart for content: translate roadmap intent — a Clio Work launch in a new market, an enterprise segment push, a new research capability into a costed, sequenced content plan with an honest timeline.Give Product an early, honest read on feasibility: what a jurisdiction realistically takes to reach market-ready, where licensing is the only viable path, and where a launch date is not supportable by the corpus. Being the person who says this before launch, not after, is core to the role.Own the content readiness gate for market launches: define the criteria, run the assessment, and hold the go/no-go recommendation.Make content lead times visible in planning cycles, and surface coverage, enrichment, or citator assets Product may not have considered, so the roadmap is informed by what the corpus can support.Translate enterprise customer requirements from Product and Revenue into portfolio priorities, and be explicit about which are worth serving and which are not. Own the Demand Signal into Data Ops and Content EngineeringConsolidate every Content Manager's asks into a single, ranked, rationale-backed demand queue - one prioritized list, not eleven competing ones.Represent Collections in Content Engineering's planning cycles and secure capacity for pipeline, parser, and citator work with quantified impact cases.Push jurisdiction-specific needs onto common infrastructure and shared enrichment patterns wherever possible (e.g. the Iceberg pipeline migration), and actively resist a sprawl of bespoke per-country pipelines and manual workarounds.Give Data Ops forward visibility on volume, new sources, and jurisdiction launches to staff and sequence against; hold a shared view of throughput, backlog, and cost per document, and use it to argue for investment rather than to assign blame.Ensure the primary corpus meets the structural requirements Secondary Content depends on, and coordinate where a publisher relationship touches primary materials so Clio isn't paying twice or building what it already licenses. Commercial, ROI, and Executive AccountabilityBe the senior content authority in front of customers. Where Content Managers speak to their jurisdiction, this role explains the whole portfolio; coverage across markets, enrichment approach, how Vincent grounds its answers, and the roadmap behind it — to global firms and enterprise buyers evaluating Clio across several jurisdictions at once.Support enterprise pursuits, RFPs, and renewals alongside Product and Revenue, committing to coverage roadmap items where the business case justifies it and declining where it doesn't; own multi-jurisdiction content escalations.Own the investment case for coverage; cost per jurisdiction, licensing spend, acquisition cost, and the return attributable to collection investment — and the portfolio dashboard behind it.Present to the Content Committee and executive leadership on portfolio health, investment cases, and risk, partnering with FP&A, Corp Dev, and Licensing on portfolio-scale decisions.Own competitive intelligence for content, and source and negotiate strategic upstream relationships with courts, publishers, and open-data initiatives, especially where they span markets.Bring the customer signal back into the portfolio, and work with Product Marketing, Sales Enablement, and Revenue to turn collection differentiation into positioning and enablement." We need to split into list items. Each bold heading maybe a separate item. We'll create
• for each sentence group. Could be many items but that's okay as long as substantive. We'll produce
  • Lead and Develop the Content Manager Team... (the paragraph until next bold heading). We'll need to capture each block. Let's parse blocks: 1. Lead and Develop the Content Manager Team Hire, onboard, and develop country and regional Content Managers, building a bench deep enough that opening a new jurisdiction isn't gated on a new hire. Set the operating rhythm; roadmap reviews, quarterly business reviews, coverage-parity readouts, and 1:1s that raise the quality of judgment, not just the reporting of status. Define the Content Manager role ladder and performance standards, making the difference between a good and a great collection owner explicit and coachable. Create the Content Manager guild, so jurisdictional learnings, source-acquisition tactics, and enrichment patterns propagate across countries rather than being rediscovered. Own succession and continuity so no collection carries single-person risk. 2. Own the Global Collection Portfolio Define the multi-year content strategy: which jurisdictions Clio invests in, at what depth, in what sequence, and anchored to Product's market roadmap and to the coverage bets worth making ahead of it. Allocate budget, headcount, licensing spend, and partner-team capacity across jurisdictions against a consistent value model — not by whoever argues loudest. Maintain the global