Senior Talent Acquisition Specialist

We need to output HTML fragment with sections: About the role? The posting includes summary, who you are, what your team does, what you'll work on, what you bring, bonus points, what you will find here (compensation/benefits), DIBE & Accessibility, etc. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings appropriately. Only include sections when posting has real specific content. We have: - About the role: could be summary/intro: "We are looking to hire a Senior Talent Acquisition Specialist..." plus maybe location and contract length. That's about the role. - Responsibilities: "What you'll work on:" bullet list. - Requirements/Qualifications/Skills: "What you bring:" includes experience, track record, data literacy, consultative mindset, grounding in best practices, expertise across sourcing, engaging passive candidates, curiosity/growth mindset. Also "Bonus points if you have:" could be additional qualifications/skills. We need to decide mapping: Could combine Requirements and Qualifications and Skills? But we must use headings as given; we can include multiple of them if content exists. We should not create empty headings. We have Pay: salary range given. Benefits: described in "What you will find here:" includes compensation, health benefits, hybrid work, flexible time off, EAP, 401k matching, Child Education Savings, Clioversary recognition. Also maybe schedule: hybrid work expectation. Schedule: maybe mention hybrid work expectation: "Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin and Sydney) to be in office minimum twice per week." Also remote USA or hybrid in Vancouver, Calgary, or Toronto CAD. So schedule info. We must not include boilerplate like EEO etc. We should keep DIBE & Accessibility content? It's not in the prescribed headings; maybe we could put under Benefits? But it's not exactly benefits. Could we create a section "Diversity, Inclusion, Belonging and Equity"? Not allowed headings; only those listed. So we should either omit or fold into Benefits? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. Likely we should only use those headings. So we should map content to those headings; any other content not fitting should be omitted or integrated. Thus we need to produce HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Possibly not all needed if content missing. Let's extract: About the role: summary: "Clio is the global leader in legal AI technology... We are looking to hire a Senior Talent Acquisition Specialist to join our Go-To-Market (GTM) and Corporate/Business (G&A) Talent Acquisition Teams. This position can sit in Remote USA or Hybrid in Vancouver, Calgary, or Toronto CAD This will be a 12-Month Fixed Term Contract position." Also maybe "Who you are:" could be part of About the role? But we have separate sections for Requirements etc. We'll keep About the role as introductory description. Responsibilities: bullet list from "What you'll work on:". - Serve as a strategic talent partner for GTM or G&A leaders across Sales, Marketing, Customer Success, Accounting, Finance, Legal, Operations, People building strong relationships that drive alignment on hiring priorities and workforce planning. - Own senior-level and high-impact roles end-to-end, leading full-cycle recruitment with a strong emphasis on proactive, strategic hiring in Canada and the U.S. - Develop and execute data-informed hiring strategies that meet quarterly targets while elevating candidate experience and stakeholder engagement. - Partner with business leaders to align on hiring strategies, meet quarterly hiring targets, and ensure a best in class candidate experience. - Build and maintain a strong pipeline of active and passive candidates through innovative sourcing techniques, talent intelligence, and market insights. - Champion Clio’s mission and values when assessing and aligning candidates to both role requirements and organizational fit. - Identify opportunities to enhance and streamline TA processes, introduce best practices, and contribute to the continuous improvement of our global recruiting function. - Represent Clio with professionalism, integrity, and authenticity. We could combine some but keep as list. Requirements: maybe "What you bring:" core requirements (3-5 years full-cycle recruiting experience, track record, data literacy, consultative mindset, grounding in best practices, expertise across sourcing, engaging passive candidates, curiosity/growth mindset). We'll put those. Qualifications: maybe similar but we could separate "Bonus points if you have:" as Qualifications? Or Skills? Let's assign: - Requirements: mandatory experience and core competencies. - Qualifications: bonus points (Workday ATS, Gem, Talent Insights, DEI initiatives). - Skills: maybe specific skills like sourcing, data literacy, stakeholder management, etc. But we have overlap. We need to avoid duplication. Perhaps better: Requirements = mandatory experience; Qualifications = educational? Not given. Skills = specific competencies (sourcing, data literacy, stakeholder management, etc.). But we can just use Requirements and Skills and leave Qualifications empty? But we must not emit empty headings. So we need to decide which sections to include based on content. We have content for: - About the role - Responsibilities - Requirements (mandatory) - Skills (maybe we can treat "What you bring:" as Skills) - Benefits (from "What you will find here:") - Pay (salary range) - Schedule (hybrid/remote expectations) We could omit Qualifications if we don't have distinct content; but we have bonus points which could be Qualifications. Let's treat bonus points as Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to fill each with appropriate content. Let's draft: About the role:

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. We are looking to hire a Senior Talent Acquisition Specialist to join our Go-To-Market (GTM) and Corporate/Business (G&A) Talent Acquisition Teams. This position can be located remotely in the USA or in a hybrid arrangement in Vancouver, Calgary, or Toronto (CAD). This is a 12‑month fixed‑term contract role.

Responsibilities:

• ...

Requirements:

• 3‑5 years of full‑cycle recruiting experience, ideally in a high‑growth, high‑velocity SaaS environment.
• Demonstrated track record of delivering against ambitious hiring goals, balancing quality, speed, and stakeholder alignment while navigating competing priorities.
• Strong data literacy—leveraging metrics, talent intelligence, and market insights to influence leaders, shape hiring strategy, diagnose challenges, and drive continuous improvement.
• Highly consultative, strategic mindset, positioning yourself as a trusted advisor to senior leaders and bringing thoughtful, solutions‑oriented problem‑solving to every stage of the process.
• Deep grounding in recruitment and HR best practices, ensuring fairness, compliance, and strong alignment between talent strategies and organizational goals.
• Expertise across a wide range of sourcing and attraction channels—building and sustaining diverse, high‑quality pipelines through outbound outreach, referrals, events, talent mapping, and proactive market engagement.
• Proficiency in engaging, nurturing, and converting passive candidates, using personalized outreach and long‑term relationship building to secure top talent.
• Curiosity and a growth mindset, with a commitment to continuously refining your craft and embracing new technologies, including AI‑powered tools, to elevate performance and efficiency.

Qualifications (bonus points):

• Experience with Workday ATS, Gem, and Talent Insights, including optimization, reporting, or workflow refinement.
• Experience leading or shaping diversity, equity, and inclusion hiring initiatives, programs, or strategies.

Skills: maybe we can list specific skills like stakeholder management, strategic hiring, pipeline building, etc. But we already covered many in Requirements. To avoid duplication, we could treat Skills as "Core competencies" like stakeholder management, strategic hiring, data‑driven decision making, etc. But we already have those. Perhaps we can combine Requirements and Skills into one? But we need separate headings if we have content. Could we put Skills as a short list of specific abilities: "Strategic talent partnership, full‑cycle recruitment, data‑informed hiring strategy, proactive sourcing, candidate experience optimization, process improvement, stakeholder engagement." That is not duplicate but summarizing. However we must not invent or summarize away detail; we can rephrase but must preserve all substantive information. Summarizing may lose detail. Better to avoid Skills section if it would be just a summary. But we need to decide. We could treat Skills as the same as Requirements but that would duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can omit Skills if it would be thin. But we have content for Skills? Not explicitly separate. So we could omit Skills heading. Similarly Qualifications we have bonus points; that's substantive enough. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for each: - About the role: yes. - Responsibilities: yes. - Requirements: yes (mandatory). - Qualifications: bonus points. - Benefits: from "What you will find here:" includes compensation, health benefits, hybrid work, flexible time off, EAP, 401k matching, Child Education Savings, Clioversary recognition. - Pay: salary range. - Schedule: hybrid/remote expectations. We must not repeat Pay content also in Benefits; but Benefits includes compensation mention; but we can keep Pay separate for salary range, Benefits for other benefits. Now we need to ensure we don't include boilerplate like DIBE & Accessibility, EEO, etc. We'll omit. Now produce HTML fragment. Let's craft each section. About the role: combine intro and role details. Responsibilities: list as above. Requirements: list as above. Qualifications: list bonus points. Benefits: list items: Competitive, equitable salary with top-tier health benefits, dental, and vision insurance; Hybrid work environment, with expectation for local Clions (Vancouver, Calgary, Toronto, Dublin and Sydney) to be in office minimum twice per week; Flexible time off policy, with an encouraged 20 days off per year; EAP benefits for you and household members, including counseling and online resources; 401k matching and Child Education Savings; Clioversary recognition program with special acknowledgement at 3, 5, 7, and 10 years. Note: salary mention in Benefits duplicates Pay; but we can keep generic "Competitive, equitable salary" but we have Pay section with specific range. Might be okay but could be considered duplication. However we must preserve ALL substantive information; the Benefits section includes mention of salary as part of total rewards. If we omit that, we lose that piece. But we could keep it but note that salary details are in Pay section. However we must not invent or summarize away detail. The phrase "Competitive, equitable salary with top-tier health benefits, dental, and vision insurance" is substantive; we should keep it. Pay section will give specific range. That's fine. Schedule: we have remote USA or hybrid in Vancouver, Calgary, or Toronto CAD; plus hybrid work expectation for local Clions to be in office minimum twice per week. Also maybe mention 12-month fixed term contract? That's more about role. We'll put schedule details